Previous Topic: TMSXTEND Utility—Dynamic TMC Extend Process Control ProgramNext Topic: Report Description

Utilities › TMSXTEND Utility—Dynamic TMC Extend Process Control Program › Restrictions for TMSXTEND

Restrictions for TMSXTEND

  1. Nonstandard Volume Serial Numbers: A few CA 1 customers have defined nonstandard volume serial numbers in their TMC that TMSXTEND cannot process. A nonstandard VOLSER is defined as any VOLSER with alpha characters in the rightmost positions of the VOLSER or with blanks to the left of a 4- or 5- character VOLSER. Examples of nonstandard VOLSERs are 0920XT, 00010A, or '12345'. These customers must continue to run the special versions of CA 1 user exits TMSXITU and TMSXITE that they have coded to support these VOLSERs. Plan to eliminate the use of these VOLSERs over time to enable them to take advantage of the convenience of the TMSXTEND utility.

    Short 3, 4, or 5 character VOLSERs with the blank on the right are valid. And VOLSERs with alpha characters on the left or even middle are also valid. Examples of VALID VOLSERs would be '12345 ', 9XT456, and ABC123. For all these types of VOLSERs, you do not have to maintain the CA 1 TMSXITU and TMSXITE exits.

  2. Reverse Conversion: An IPL is necessary. The output of the TMSXTEND utility is a new format TMC. The volume ranges defined internally in a new type of record, the Volume Definition record. A TMC created in this format is described as an Extended Format TMC. Once a TMC has been converted to this format, the only way to convert back to the previous TMC format is by running TMSSPLIT to SPLIT off (export) all TMC and DSNB entries to a sequential file. This process is followed by a MERGE process to import them into a TMC defined with TMSFORMT. This process can be time-consuming in larger installations. Re-activate user exits TMSXITU and TMSXITE with an IPL. Plan your conversion to the Extended Format TMC well and do not convert back.
  3. User Written Programs: Customers who have written their own programs to read and/or update the TMC must check to ensure that they can process the new Extended Format TMC. In general, programs that do not process DSNBs should work without modification. Contact your local CA 1 Support organization if you need help in determining if your user written programs need modification.
  4. CA VM:Tape: Customers running CA VM:Tape must apply maintenance to that product if it is configured to share a TMC with CA 1. If you are running CA VM:Tape and sharing a TMC, contact CA Technical Support for CA VM:Tape to obtain the necessary maintenance. The TMSAUDEX utility can be executed to determine if a VM:Tape system sharing the TMC is back level. Refer to the description of TMSAUDEX for further information.
  5. The first time that you set the new Unique_RNAME parameter to YES in the SYSIN control statements, you cannot code any EXCLUDE control statements in the CPULIST control statements. Once Unique_RNAME has been activated, this restriction no longer applies. This restriction does not apply if the Unique_RNAME parameter is disabled.

Changes to existing utilities:

  1. TMSREMOV should NOT be used to remove volume ranges already in DELETE status on an Extended Format TMC. Instead, the REMVOL control statement of TMSXTEND should be used to remove those volumes.
  2. TMSFORMT should NOT be used when the input is an Extended Format TMC. If you need to add more volumes to a TMC that is already in the new format, run TMSXTEND again.
  3. TMSBINQ reports report zero (0) as the number of ranges for a new format TMC. Since there is no longer a limit to the number of volume ranges, there is no reason to maintain a count field of them in the control records.
  4. TMSBINQ is the online TMSTIQ display of the volume ranges. The CA 1 ISPF online display of the volume ranges are different on an Extended Format TMC. The display now shows the starting and ending VOLSER in each range and the starting and ending relative record number for each of those VOLSERs.