Actions against jobs: target limitations

Edit online

Only some JES spool commands are available through Job Monitor, and access to these commands is also limited by file ownership.

Job Monitor does not provide full operator access to the JES spool. Only the Hold, Release, Cancel, and Purge commands are available, and by default, only for spool files that you or another user own. You can issue these commands by selecting the appropriate option in the client menu structure. There is no command prompt. You can widen the scope of the commands using security profiles to define which jobs the commands are available for.

Like the SDSF SJ action character, Job Monitor also supports the Show JCL command to retrieve the JCL that created the selected job output, and then display it in an editor. Job Monitor retrieves the JCL from JES, which can help you to find an original JCL member that is otherwise not easily located.

Table 1. Job Monitor console commands.
Job Monitor console commands
Action	JES2	JES3
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 you or another user own. You can change this with the LIMIT_COMMANDS directive, as documented in Job Monitor configuration file BLZJCNFG.

Table 2. Job Monitor command permission matrix.
Job Monitor command permission matrix
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. Like SDSF, Job Monitor also extends the use of the JESSPOOL class to protect job resources.

If LIMIT_COMMANDS is not USERID, then Job Monitor will query for permission to access the related profile in the JESSPOOL class, as shown in the following table:

Table 3. Extended JESSPOOL profiles.
Extended JESSPOOL profiles
Header	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:

Substitutions in the preceding table

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 defined for the LIMITED and NOLIMIT value of LIMIT_COMMANDS, as described in Job Monitor configuration file BLZJCNFG. The behavior is identical when JESSPOOL is active, because the class, by default, denies permission if a profile is not defined.