Modify the TMC and Audit Data Sets

ca1tms14
The TMC and Audit data sets should not reside on the same DASD unit, and are preferably located on a different bank/channel, to ensure that the TMC can be restored in the event it is destroyed. Both data sets should be allocated as unmovable (DSORG=PSU) to prevent relocation during DASD defragmentation or compaction operations. In a multi-CPU environment where each CPU is sharing a common TMC and Audit, some of the procedures below must be performed for each CPU accessing the database.
Restore the TMC
The batch utility TMSCOPY is used for restoration of the TMC. This same TMSCOPY utility is also responsible for creating the TMC backup used during the restore process.
The Audit data set is not restorable from the TMSCOPY backup files. In the event the Audit data set is destroyed, it should be reformatted with the TMSFORMT utility.
Rename the TMC and/or Audit Data Sets
The name of the TMC and Audit data sets are identified to
CA 1
during TMSINIT processing from the TMCDSN and AUDDSN parameter specifications in the TMOOPTxx member of
hlq
.CTAPOPTN.
To set new names for TMC and Audit data sets, use the following process:
  1. Quiesce all tape processing on all CPUs sharing the TMC and/or Audit.
  2. Request the DBS subtask to RELEASE the TMC and/or Audit data set through the CTS address space commands.
  3. Ensure that no
    CA 1
    batch or online facilities are executing.
  4. Rename the entry for the TMC and/or Audit in the system catalog.
  5. Update the TMCDSN and/or AUDDSN parameters in
    hlq
    .CTAPOPTN, member TMOOPTxx, to reflect the new system catalog name(s).
  6. Execute TMSINIT to reinitialize
    CA 1
    in all CPUs sharing the TMC or Audit.
  7. Request the DBS subtask to OBTAIN the TMC and/or Audit data set through the CTS address space commands.
Move the TMC
The simplest way to move a TMC is by using the TMSXTEND utility, allocating the new TMC on the desired volume.
To move the TMC to a different DASD device without using the TMSXTEND utility, use the following process:
  1. Stop tape processing on all CPUs sharing the TMC. Online transaction tapes (CICS, IMS, and so on) can stay on their drives as long as the files have already been OPENed. Check to ensure there is enough tape available on such volumes so that end-of-volume processing is not invoked while you are performing this procedure.
  2. Request the DBS subtask RELEASE the TMC data set through the CTS address space commands.
  3. Back up the TMC using TMSCOPY.
  4. Allocate the space for the TMC on the device desired under an alternate data set name. Make sure the device is available to all CPUs. Be sure to use DSORG=PSU in the DCB parameter. If you plan on moving the TMC to an SMS controlled volume, a DSORG of PSU is not allowed. Therefore, you must manually ensure that it is excluded when you perform defragmentation or compactions on the device in question.
  5. Execute IEBGENER to copy the production TMC to the new device.
    //COPY    EXEC PGM=IEBGENER //SYSUT1    DD DSN=CAI.CA1.TMC,DISP=OLD //SYSUT2    DD DSN=CAI.CA1.TARGET.TMC,DISP=OLD //SYSIN     DD DUMMY //SYSPRINT  DD SYSOUT=*
  6. Rename the production TMC to a backup data set name, and catalog the alternate TMC under the production name on all CPUs.
  7. Execute TMSINIT on all CPUs to establish the new location, and continue tape processing.
  8. Request the DBS subtask to OBTAIN the TMC data set through the CTS address space commands.
Add New Volume Ranges and/or DSNB Records
The TMSXTEND utility provides the ability to perform volume range additions or deletions as well as DSNB additions or deletions, while tape processing is allowed to continue. This procedure is simpler than using TMSFORMT which requires that
CA 1
be put in batch active mode. Alternatively the following procedure can be used.
New TMC Volume and/or DSNB Records are added to the TMC in a process called
extending
the TMC. The TMSFORMT utility, which was used to create the original TMC, is used for this purpose. In order to execute TMSFORMT,
CA 1
must be placed in a
batch active
mode.
You cannot use TMSFORMT to extend a TMC created by TMSBLDVR or has had TMSXTEND run against it to change the format.
Remove Volume Ranges from the TMC
A range or ranges of volume records that are no longer in use, and have been marked as inactive (deleted) in your TMC, can be physically removed from the database by using the TMSXTEND or TMSREMOV utilities, depending on the format of your TMC.
Remove DSNB Records from the TMC
DSNB records can be removed from the TMC by performing an in-house split/merge operation or by using TMSXTEND. Two batch utilities, TMSSPLIT and TMSMERGE, are used in this process. While split/merge processing is normally used to accommodate the importing of a TMC from another data center, it is possible to perform a split/merge in-house for the purpose of reducing an excessively high DSNB allocation in which a large number of DSNBs are unused, and there is no anticipation of growth. See the discussion, Merging Two TMCs, later in this section.
The TMSXTEND utility can also be used to remove DSNB records from the TMC.
Increase or Decrease the Audit Allocation
Reduction or expansion of the number of Audit records is performed with the TMSFORMT utility.
Move the Audit Data Set
Use the following process to move the Audit data set to a different DASD unit:
  1. Stop tape processing on all CPUs sharing the Audit. Online transaction tapes (such as CICS, IMS) can stay on their drives as long as the files have already been OPENed. Check to ensure there is enough tape available on such volumes so that end-of-volume processing is not invoked while you are performing this procedure.
  2. Request the DBS subtask to RELEASE the Audit data set through the CTS address space commands.
  3. Back up the TMC using TMSCOPY.
  4. Allocate the space for the Audit on the device desired under an alternate data set name. Ensure that the device is available to all CPUs, and use identical DCB attributes. DSORG=PSU should be specified in the DCB parameter.
    If you plan on moving the Audit to an SMS controlled volume, a DSORG of PSU is not allowed. Therefore, you must manually ensure that it is excluded when you perform defragmentation or compactions on the device in question.
  5. Execute IEBGENER to copy the production Audit to the new device.
    //COPY    EXEC PGM=IEBGENER //SYSUT1    DD DSN=CAI.CA1.AUDIT,DISP=OLD //SYSUT2    DD DSN=CAI.CA1.TARGET.AUDIT,DISP=OLD //SYSIN     DD DUMMY //SYSPRINT  DD SYSOUT=*
  6. Rename the production Audit to a backup data set name, and catalog the new Audit under the production name on all CPUs.
  7. Execute TMSINIT on all CPUs to establish the new location, and continue tape processing.
  8. Request the DBS subtask to OBTAIN the Audit data set through the CTS address space commands.
To reblock the Audit file, back up the TMC using TMSCOPY and format a new blocked Audit using the TMSFORMT utility.