|
|
|
The only exception to this rule is when the input stream JCL overrides the JCL in the procedure library. When this occurs, you find /X in columns 1 and 2 to indicate which statement was overridden. In any case, JES stores the merged JCL stream on an input queue for later execution. Depending on which of the two job entry subsystems is used with the operating system, this is one or more job queues. (JES2 uses one queue; JES3 uses multiple queues.) An initiator then selects the JCL from the appropriate queue, and the job begins allocation.
Another lesser‑known function of proclib is the storage of the JCL that is used for computer operator started tasks. These are special jobs that are activated from the operator console by a “start” command. Started task JCL must be stored in SYS1.PROCLIB or one of its concatenations.
Therefore, a review of JCL should always include the various proclibs, starting with SYS1.PROCLIB. Determining the names of the additional proclibs is well worth the effort. JES2 users can use the Proclib Display (4.2) to obtain the default library names. If the display indicates that an operator can modify any of the default names, you should obtain a copy of the console SYSLOG for the time period around IPL. This lets you determine if JES2 was started with any symbolic substitutions for library names.
Look for the HASP426 SPECIFY SYSTEM OPTIONS operator prompt that is generated by JES2 when it first starts. If symbolics are used, you see them following the S JES2... command that the operator entered. On the Proclib Display (4.2), enter the exact same S JES2 information that the operator specified. CA Auditor performs all substitutions and displays the actual proclibs used for this execution of JES.
| Copyright © 2009 CA. All rights reserved. | Tell Technical Publications how we can improve this information |