The CTMTAPUL Tape Pull List Procedure

The Tape Pull List procedure creates a list of all tapes to be mounted in a specified period. The list can be sorted and edited in various ways, such as

• all tapes to be mounted, sorted by the expected mount time
• all tapes to be mounted, sorted by volume serial number

Note: It is highly recommended that the simulation be run from the current time, that is, not from a time in the future. Otherwise, the Tape Pull list results may be inaccurate because new tape files may be cataloged in the time remaining before the start of the simulation run.

The procedure takes into account the expected order of job execution and the order of creation of tape data sets.

The procedure also does the following:

• checks the syntax of all AutoEdit statements in all jobs that are planned for the given period
• checks the JCL syntax
• produces a list of data sets that are still missing for the execution.

  These are usually input data sets due to arrive, but they may be JCL execution errors

Note: For the Tape Pull List procedure to be executed properly, the internal reader (INTRDR) must have authority to submit jobs.

The Tape Pull List procedure uses files from the Simulation procedure as input. In preparation for the Tape Pull List procedure, run the Simulation procedure using the production Control-M Active Jobs file, Control-M Resources file, and IOA Conditions file.

The Tape Pull List procedure works as follows:

• The procedure looks for "SUBMISSION" messages in the simulation output LOG file.
  • For each submission message, it looks for the appropriate job having a WAIT SCHEDULE status on the simulation input Active Jobs file.
  • If a job is found, the Tape Pull List procedure actually submits the job with the TYPRUN=SCAN parameter specification, reads the SYSOUT of the job, retrieves the data set information, and produces the required reports.
• The procedure recognizes tape data sets by either the appropriate unit specification in the JCL, such as UNIT=TAPE, or by retrieving information from the system catalog. It is therefore not necessary to have all tape data sets cataloged in the MVS catalog.

  Note: A highlighted warning message appears on the operator console while the jobs are being submitted. During this stage, the operator console may display several messages regarding the job submission. The highlighted message disappears at the end of this stage.

  The procedure can detect that a certain tape is used by more than one job, and which job creates it, as illustrated in the following example.

  Job A creates a new generation of a tape data set:

  //OUTUPD DD DSN=PFX.DATA(+1),DISP=(,CATLG),...

  Job B, a successor of Job A, accesses the same data set:

  //INUPD DD DSN=PFX.DATA(0),DISP=SHR

  The procedure detects that Job A is the creator of the data set used by Job B and reports the same tape volser for both jobs.

• After the job sysout has been analyzed, the sysout is deleted from spool.
• The next stage of the procedure produces reports according to the requested parameters.