The job control language (JCL) statements generated by the Batch processing option are accumulated in a temporary data set named userid.SPFTEMPn.CNTL or prefix.userid.SPFTEMPn.CNTL, where n is the screen number. This data set contains the job cards generated by ISRJB1 and job steps generated by the option CLISTs. In all cases, file tailoring services are used to generate the JCL. If VIO is used, the generated JCL is in a VIO data set allocated to DDname ISPCTL1.

ISRJB1 generates up to four job statement lines from information that you supply in the Batch Selection panel, ISRJPA. A job statement line is not generated if the corresponding field on the panel is blank. An attempt is made to provide unique jobnames by using this algorithm:

1. The four lines entered in the selection panel are scanned for the first ‘//’ card.
2. If the string following the ‘//’ is equal to the TSO user ID, and if the user ID is followed by an alphabetic character or a numeric character, that character is automatically incremented each time a job is submitted.
3. If the string following the ‘//’ is not equal to the TSO user ID, the job name will not be automatically incremented each time a job is submitted. ISRJB1 increments and changes jobnames only if they begin with the user ID.

If you bypass the Batch Selection panel (for example, by selecting option 5.n from the ISPF Primary Option Menu), the job statement lines that would have been displayed on the selection panel are used as if you had not modified them.

The file skeleton associated with each option controls the JCL generated for that option. See "Batch (Option 5)" in the z/OS ISPF User's Guide Vol II for a general description of skeleton formats. Each variable in the skeleton is replaced by its current value (the contents of the corresponding panel input field, as entered by you, or a previously entered value). Following variable substitution, each record in the skeleton is written to the temporary data set, which is eventually submitted to the job stream by the TSO SUBMIT command. Skeletons must be coded so that the maximum length of a record after substitution does not exceed 71 characters; otherwise, invalid JCL might be generated.