|
IOF Problem Resolution
Problem D02
|
| Previous
| Next
|
| Description
|
A batch clist or Rexx exec terminates with a "REFUSED" error.
(SLAM, JAR, IOFWTR, OUTQUE, IOFLISTG, or local execs and clists)
|
| Background
|
The batch TSO session must be authorized to perform the required
function. SLAMRUN and SLAMMEMO browse SYSLOG. SLAMWTR browses and
cancels a SYSLOG data set. OUTQUE browses the specified jobs and
performs the requested action (cancel, route, etc.). IOFWTR selects
and modifies or cancels specified output groups.
In most sites, a batch job assumes the same characteristics as
the submitter of the job. If the TSO user who submits the job has
access to a function, the batch job should have the same access. If
the submitter's userid is not automatically given to the batch
job, then USER and PASSWORD JOB statement parameters may be
required.
|
| Solution
|
The JOB or STC must be authorized to perform the specific IOF
function.
Started tasks are permitted to do all IOF functions at most
sites. If this is a batch job, perhaps it can be changed to
run as a started task.
|
| Information
|
The distributed B23ALLOW options member defines a started task
group, STCGROUP, which is authorized to perform all IOF
functions. If you have removed or modified the group macro for
STCGROUP, or if you have modified any of the ALLOW macros it
references to restrict the access permitted to started tasks, you
may have removed the authority for the clist to perform the
function it is designed to do. You must grant the task permission
to perform the function.
A copy of the distributed B23ALLOW option is included in OPTION
data set member Z23ALLOW.
|
| Information
|
Started tasks are not automatically assigned a userid.
The userid may have to be assigned via the security system
(RACF, ACF2 or TSS).
|
| Information
|
Most of the distributed clists and execs can be traced by
specifying the "TEST" parm.
Local execs can be traced by adding a "TRACE R" statement to
the exec. Local clists can be traced by adding a "CONTROL LIST
CONLIST" statement to the clist.
|
| Information
|
The PAUSE command is used by several IOF batch TSO clists, including
SLAMRUN, SLAMPROC, SLAMOPER and IOFWTR. The userid under which
these clists is run must be assigned to an IOF GROUP that allows
the EVERY and PAUSE commands. See the MINPAUS parm on the IOF GROUP
macro description in the B23$DOC member of the IOF OPTIONS library.
|
| Information
|
Most of the distributed batch clists and Rexx execs display
the value of several IOF variables in the SYSTSPRT output data set.
This information may be valuable in debugging the batch problem.
It may be useful to run a simple test clist under the same
conditions as the failing clist or exec. The following simple
clist will display many IOF variables that may be useful.
Add the following clist to the IOF CLIST library as member
TESTDVAR.
PROC 0
IOF * OPTMENU CLIST
%IOF$OP1 ALL
JUMP X
This clist invokes the IOF$OP1 clist to display IOF variables.
IOF$OP1 resides in the IOF clist library.
The JCL below can be used to run the TESTDVAR clist.
|