Sharing the CA 1 TMC › Working with the CA 1 TMSXTEND Utiliity › Running TMSXTEND

Running TMSXTEND

The ALTTMC record specifies the virtual device number of the disk containing the alternate TMC dataset (pre-allocated by OS).

Before the TMSXTEND utility is run, you must prepare the CA VM:Tape service virtual machine by performing the following:

1. Add a LINK or full pack minidisk definition of the disk containing the new TMC to the CA VM:Tape directory entry.
2. Ensure CA VM:Tape links to the new TMC minidisk.
3. Update the CA VM:Tape configuration to specify the device number of the new disk on the ALTTMC CONFIG file record.

   Note: CA VM:Tape does not support dynamic updating of the CONFIG file. Therefore CA VM:Tape must be restarted after the CONFIG file is updated and before using TMSXTEND.

   After the TMSXTEND utility completes, CA VM:Tape uses the TMC on the ALTTMC device without additional changes. However, the following post execution maintenance must be performed:

4. Detach the disk containing the original TMC as specified on the OSTMC CONFIG file record.
5. Remove the LINK or full pack minidisk definition of the original TMC disk from the CA VM:Tape directory entry.
6. Remove the ALTTMC record and replace the device number on the OSTMC CONFIG file record with the device number previously specified on the ALTTMC record.

This should be done during normal maintenance when CA VM:Tape can be restarted.

Note: The CONFIG file can be changed while CA VM:Tape is running. However, the changes do not take effect until CA VM:Tape is re-initialized. If the CONFIG file is changed while CA VM:Tape is running, processing is suspended while the edit is invoked.