Actions against jobs - target limitations

JES Job Monitor does not provide z/OS® Explorer users full operator access to the JES spool. Only the Hold, Release, Cancel, Purge, change CLASS, and change MSGCLASS commands are available, and by default, only for spool files owned by the user. The commands are issued by selecting the appropriate option in the client menu structure (there is no command prompt). The scope of the commands can be widened, using security profiles to define for which jobs the commands are available.

Similar to the SDSF SJ action character, JES Job Monitor also supports the Show JCL command to retrieve the JCL that created the selected job output, and show it in an editor window. JES Job Monitor retrieves the JCL from JES, making it a useful function for situations in which the original JCL member is not easily located.

Table 1. JES Job Monitor console commands. This table lists JES Job Monitor console commands.
Action JES2 JES3
Change CLASS

$Tx(jobid),C=class

with x = {J, S or T}		 *F,J=jobid,C=class
Change MSGCLASS

$TOx(jobid),Q=queue

with x = {J, S or T}		 *F,U,J=jobid,NCL=class
Hold $Hx(jobid)

with x = {J, S or T}

 *F,J=jobid,H
Release $Ax(jobid)

with x = {J, S or T}

 *F,J=jobid,R
Cancel $Cx(jobid)

with x = {J, S or T}

 *F,J=jobid,C
Purge $Cx(jobid),P

with x = {J, S or T}

 *F,J=jobid,C
Show JCL not applicable not applicable
The available JES commands listed in Table 1 are by default limited to jobs owned by the user. This can be changed with the LIMIT_COMMANDS directive, as documented in "FEJJCNFG, JES Job Monitor configuration file" in the Host Configuration Guide (SC27-8437).
Table 2. LIMIT_COMMANDS command permission matrix. This table lists LIMIT_COMMANDS command permission matrix.
Job owner
LIMIT_COMMANDS User Other
USERID (default) Allowed Not allowed
LIMITED Allowed Allowed only if explicitly permitted by security profiles
NOLIMIT Allowed Allowed if permitted by security profiles or when the JESSPOOL class is not active

JES uses the JESSPOOL class to protect SYSIN/SYSOUT data sets. Similar to SDSF, JES Job Monitor extends the use of the JESSPOOL class to protect job resources as well.

If LIMIT_COMMANDS is not USERID, then JES Job Monitor will query for permission to the related profile in the JESSPOOL class, as shown in the following table.
Table 3. Extended JESSPOOL profiles. This table lists extended JESSPOOL profiles.
Command JESSPOOL profile Required access
Hold nodeid.userid.jobname.jobid ALTER
Release nodeid.userid.jobname.jobid ALTER
Cancel nodeid.userid.jobname.jobid ALTER
Purge nodeid.userid.jobname.jobid ALTER
Show JCL nodeid.userid.jobname.jobid.JCL READ
Use the following substitutions in the preceding table.
Table 4. Substitutions. This table lists substitutions for the names used in the preceding table.
Name Substitution
nodeid NJE node ID of the target JES subsystem
userid Local user ID of the job owner
jobname Name of the job
jobid JES job ID

If the JESSPOOL class is not active, then there is different behavior for the LIMITED and NOLIMIT value of LIMIT_COMMANDS, as described in the "LIMIT_COMMANDS command permission matrix table" in "FEJJCNFG, JES Job Monitor Configuration file" in the Host Configuration Guide (SC27-8437). The behavior is identical when JESSPOOL is active, since the class, by default, denies permission if a profile is not defined.