Use any combination of keywords. The two basic groups of keywords are:
Some filters allow the following standard wildcards:
The filter keywords provide filtering for JES2 and JES3 jobs. The output variables contain information for only those jobs matching the input filter criteria. For the keywords JOBID, JOBNAME, MEMBER, OJOBID, OWNER, SCHEDUL, SECLABEL, SPOOLVOL, SYSTEM, and WLMSERVICE values should be UPPERCASE.
Specifies classes for filtering.
You can use the following classes, which allow ranges:
Length: 1
Parameters: 16
Example: CLASS(@,A,B,C,M-R, 0-3)
Specifies to filter jobs with specific destinations.
Destination is the default print or punch destination that is assigned to the job.
Length: 8
Parameters: 4
Wildcards: In JES2, the user ID part of the destination can contain the generic characters * and ?. This can filter jobs with a default print route code that contains a corresponding user ID routing.
Example: DESTINATION(PRODSYS1)
Specifies to filter jobs with specific execution nodes (NJE node where the job is to, or was, executed). This filter is only available on JES2.
Length: 8
Example: EXECNODE(PRODSYS1)
Specifies to filter the type of held jobs.
The valid values are:
Jobs that are held.
Jobs that are not currently held.
Jobs are held because they are duplicate jobs.
Example: HELDJOBS(DUPL)
Specifies to filter jobs with specific job IDs.
The JOBID must start with one of the prefixes: JOB, TSU, STC, INT, or any abbreviation of these prefixes: J, T, S, I.
Length: 8
Example: JOBID(JOB12345)
Specifies job names for filtering.
Length: 8
Parameters: 8
Wildcards: * and ?
Example: JOBNAME(*TEST*, INIT??1)
Specifies job types for filtering.
Parameters: 4
Example: JOBTYPE(STC, TSU)
Specifies to filter jobs that are active on specific JES MAS members. This parameter is valid on JES2 only. The job can be actively executing or active on a device on that member.
Length: 8
Wildcards: * and ?
Example: MEMBER(TEST30)
Specifies to filter jobs with specific original job IDs. This parameter is not supported on JES3. If the job was sent by NJE the original job ID can differ from the job ID. The ojobid must start with either the character J or JOB and followed by the original job number.
Length: 8
Example: OJOBID(JOB54321)
Specifies to filter jobs with a specific original node (NJE node where the job originated). This parameter is valid on JES2 only.
Length: 8
Example: ORIGINODE(PRODSYS1)
Specifies to filter jobs with the user ID of the owner.
Length: 8
Wildcards: * and ?
Example: OWNER(JO?H*)
Specifies to filter jobs with a specific job phase. This parameter is valid on JES2 and JES3.
Note: For the list of JES2 and JES3 phases, see the two bullet items in this section.
Example: PHASE(EXEC)
Specifies to filter jobs with a specific priority. In JES2, priorities are from 0 to 15.
Length: 3
Example: PRIORITY(15)
Specifies to filter jobs with a specific scheduling environment. Jobs have scheduling environments that are assigned to them only if they have completed conversion processing and the jobs have not completed execution processing.
Length: 16
Wildcards: * and ?
Example: SCHEDUL(DFG)
Specifies to filter jobs with a specific seclabel that the security product has assigned to the job.
Length: 8
Wildcards: * and ?
Example: SECLABEL(SYSHIGH)
Specifies the spool volume. This parameter is valid on JES2 only.
Length: 6
Parameters: 4
Example: SPOOLVOL(SPOL10)
Specifies to filter jobs with a specific submitter. This parameter is valid for JES3 on z/OS v1r7 or higher only.
Length: 8
Wildcards: * and ?
Example: SUBMITTER(ADMIN*)
Specifies to filter jobs that are active on the specified MVS system. The job can be actively executing or active on a device on that system.
Length: 8
Wildcards: * and ?
Example: SYSTEM(SYS1)
Specifies to filter jobs with a specific WLM service class. This parameter is valid on JES2 only.
Length: 8
Example: WLMSERVICE(ONLTEST)
Job is active in input processing.
Job is queued for the, conversion.
Job is actively converting.
Job is queued for SETUP (not currently used by JES2 code).
Job is active in SETUP (not currently used by JES2 code).
Job is queued for the execution.
Job is actively executing.
JES2 is processing SPIN data sets for the JOB.
Job is queued for output processing.
Job is active in output processing.
Job is on the hard copy queue.
Job is queued for a purge.
Job is being purged.
Job is active on an NJE SYSOUT receiver.
Job is queued for execution on another NJE node.
Job is active on an NJE JOB transmitter.
Job has not completed execution (combines multiple states in one phase request)
Job has completed execution (combines multiple states in one phase request)
No subchain exists.
Job is active in conversion/interpretation in an FSS address space.
Job is awaiting postscan (batch)l
Job is awaiting postscan (demand select).
Job is awaiting volume fetch.
Job is awaiting start setup.
Job is awaiting or active in the MDS system select processing.
Job is awaiting resource allocation.
Job is awaiting unavailable volumes.
Job is awaiting volume mounts.
Job is awaiting or active in the MDS system verification processing.
Job encountered an error during the MDS processing.
Job is awaiting selection on main.
Job is scheduled on main.
Job is awaiting breakdown.
Job is awaiting the MDS restart processing.
The main part and the MDS processing complete for the job.
Job is awaiting output service.
Job is awaiting output service writer.
Job is awaiting rsvd services.
Output service complete for this job.
Job is awaiting selection on main (demand select job).
The ending function request waiting for an I/O completion.
The ending function request that is not processed.
The maximum request index value.
This section provides the processing keywords.
Creates an output variable with the specified name. If omitted, the default name OPSJESX will be used.
Indicates the number of returned jobs.
Length: 50
Example:
STEM(MYOUT)
Note: The output variable is used as a stem for the number of jobs returned and for each output section returned. See the Output Variables section for further details.
Defines the name of the JES subsystem. If omitted, the JES subsystem provided by the system is used.
Length: 4
Example:
JESSUBSYS(JES3)
Limits the number of output variables.
Length: 10
Example:
MAX(2000)
Specifies which sections to return in the output.
Valid parameter values are:
Indicates the Member Affinity section
Indicates all sections
Indicates the JES2 terse section
Indicates the JES3 terse section
Indicates the Execution Scheduling section
Indicates the Schedulable Systems section
Indicates the SECLABEL Availability section
You can use any combination of keycodes. However, the ALL keycode cannot be combined with other keycodes. Use the ALL keycode if you want all sections returned.
The JQTR section is always returned. Therefore, JQTR is not included as a keycode.
If SECTION is omitted, only the JQTR is returned.
The job information returned for each section is provided in Section Variable Output Mappings. Refer to the mapping section for details on what job information is returned for each section.
Note: The sections above correspond to the Job Information Elements for the Extended Status Function Call (SSI 80) as described in the IBM guide z/OS MVS Using the Subsystem Interface. To determine the name of the Job Information Element that corresponds to a keycode, add the prefix STAT to the keycode. For example, STATAFFS is the name of the Job Information Element that corresponds with keycode AFFS.
Example:
SECTIONS(AFFS, J3TR)
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|