Previous Topic: Report DescriptionNext Topic: Job Control Statements

Utilities › TMSREMOV Utility—Remove TMC Volume Records › TMSREMOV Procedure

TMSREMOV Procedure

To remove a range of volume records from the TMC, use the TMSREMOV utility.

Follow these steps:

  1. Stop tape processing on all CPUs. If the volume has already been through OPEN processing and sufficient tape remains on the reel, you can leave online transaction tapes (CICS, IMS, and so on) on the drives. The condition prevents the invocation of end-of-volume processing during the procedure (all eight steps).
  2. Execute TMSCOPY to provide a backup of the TMC and Audit data sets.
  3. Allocate a target TMC on a device other than the production TMC using a target data set name and the following DCB parameters: 
    DCB=(RECFM=FB,LRECL=340,BLKSIZE=n*340,DSORG=PSU)

    Note: The BLKSIZE can be any multiple of the LRECL, 340, but not 680. When blocking the TMC, the smallest valid block size is 1020. When formatting a small blocked test TMC, ensure that it consists of at least two blocks. A recommended value is BLKSIZE=8840. For small block sizes, you can add an appropriate BUFNO=nn value to the DCB parameter to improve performance in batch utilities.

  4. Format the target TMC with TMSFORMT(PARM='NEW'), specifying only the volume ranges you wish to retain in production. The number of DSNBs that you allocate to the target TMC must match the number of DSNBs that is allocated to the production TMC. Determine the current DSNB allocation using either the online facilities or TMSBINQ (executed with the HEADERS control statement). The current DSNB allocation is reflected in TMC control record #2.
  5. Request the DBS subtask to RELEASE the TMC through the CTS address space commands.
  6. Rename the production TMC to a backup name and rename the target TMC to the production name. Catalog both the backup TMC and the renamed production TMC on all CPUs sharing the TMC. The renamed production TMC is used as input to the TMSREMOV process.
  7. Execute TMSINIT on all CPUs sharing the TMC, and place CA 1 in batch active mode. CA 1 resident module addresses the target TMC as the production database once reinitialized. TMSREMOV uses this empty database to receive the input from the renamed production TMC. TMSREMOV copies the records that are not reflected (formatted) in the target TMC to a backup data set. The utility also copies the records that are read from the production TMC to a backup data set.
  8. Execute TMSREMOV. Check for errors on TMS Report 40. If errors exist, the target TMC can be recataloged back to the original work name. The renamed production TMC can be recataloged to the production name. To reestablish the production TMC in the resident modules, execute TMSINIT on all CPUs. Tape processing can resume while the errors are corrected, then these steps can be repeated. If no errors are present, submit the TMSEARL CTAPJCL member using the TMEVSNM CTAPECPB member as input to the SYSIN DD. You generate an inventory of the new TMC. If the TMSREMOV execution encounters errors, CA 1 issues an S1yy-104 abend. The target TMC is rendered unusable in a production environment.

    Note: You cannot remove DSNB records with TMSREMOV. To remove DSNB records, use the CA 1 split and merge facilities or TMSXTEND.

  9. Reinitialize CA 1 into an active state on all CPUs with TMSINIT.
  10. Request the DBS subtask to OBTAIN the TMC through the CTS address space commands.
  11. Back up the new TMC using TMSCOPY and resume tape processing.

More information:

TMSINIT Utility—Activate, Deactivate CA 1