Archive log data sets on tape
If you store your archive logs on tape, the offload task constructs two files on tape during the archiving process. The first file is the BSDS, and the second file is a dump of the active log that the offload task is currently archiving.
If a failure occurs during the time that the offload task is archiving the BSDS, Db2 might omit the BSDS. In this case, the first file contains the active log.
If you perform archiving on tape, the first letter of the lowest-level qualifier varies for both the first and second data sets. The first letter of the first data set is B (for BSDS), and the first letter of the second data set is A (for archive). Hence, the archive log data set names all end in Axxxxxxx, and the DD statement identifies each of them as the second data set on the corresponding tape:
LABEL=(2,SL)When reading archive log data sets on tape (or copies of active log data sets on tape), add one or more of the following Job Entry Subsystem (JES) statements:
For the JES3 environment:
- JES3 environment JCL
- Description
- //*MAIN SETUP=JOB
- Alert the z/OS® operator to mount the initial volumes before the job executes.
- //*MAIN HOLD=YES
- Place the job in HOLD status until the operator is ready to release the job.
- TYPRUN=HOLD
- Perform the same function as //*MAIN HOLD=YES. The system places the JCL on the JOB statement.
For the JES2 environment:
- JES2 environment JCL
- Description
- /*SETUP
- Alert the z/OS operator to prepare to mount a specified list of tapes.
- /*HOLD
- Place the job in HOLD status until the operator has located the tapes and is ready to release the job.
- TYPRUN=HOLD
- Perform the same function as /*HOLD. The system places the JCL on the JOB statement.
Alternatively, submit the job to a z/OS initiator that your operations center has established for exclusive use by jobs that require tape mounts. Specify the initiator class by using the CLASS parameter on the JOB statement, in both JES2 and JES3 environments.