Similar to the SDSF SJ action character, JES Job Monitor 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.
Authorization for the Show JCL command is controlled by the LIMIT_COMMANDS directive in FEJJCNFG , and profiles in the JESSPOOL class of your security product.
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 table below.
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 table above:
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. The behavior is identical when JESSPOOL is active, since the class, by default, denies permission if a profile is not defined.
Note that Show JCL is not an operator command like the other JES Job Monitor commands (Hold, Release, Cancel and Purge), so no profile is needed in the OPERCMDS class.