Utilities › TMSXTEND Utility—Dynamic TMC Extend Process Control Program › Procedures for Executing the TMSXTEND Utility › Planning

Planning

Planning is an important part of running the TMSXTEND utility, especially the first time. The TMSXTEND utility creates new Volume Definition records in the TMC. Every system sharing the TMC must be at the correct maintenance level to perform an extend. TMSXTEND checks the maintenance level of every system it finds having written records to the Audit file. Make sure that the output accurately reflects your shared TMC environment. If a system has not been active, with CA 1 tape activity being recorded to the Audit, that system is not known. If you start CA 1 later on that system and you do not apply the necessary maintenance, CA 1 fails to initialize. First run the TMSBLDVR utility in standalone mode and evaluate your TMC volume ranges. If you have coded CA 1 user exits TMSXITE and TMSXITU to support volume serial numbers with alpha characters in the rightmost position in the VOLSER, you are not able to use TMSXTEND.

Plan the Execution of TMSXTEND

To ensure seamless execution of TMSXTEND, verify the following prerequisites:

Follow these steps:

1. Before you first run TMSXTEND, upgrade every system that shares the TMC to r11.x or higher and IPL every system.
2. To verify that you have identified all of the systems updating the TMC as recorded in your active Audit file, run TMSAUDEX. Include any systems that you find in an old Audit and not in the active Audit explicitly with an INCLUDE control statement. If the system is not a production system, you can exclude it with an EXCLUDE statement. If the system should share the new TMC, upgrade it later.
3. Run the TMSBLDVR utility in standalone mode, specifying the ranges that you want to add or remove. TMSBLDVR analyzes the existing and new volume ranges and reports any possible errors. TMSBLDVR also reports on the amount of space that the new TMC requires to support the existing ranges and newly added ranges.
4. Fix the errors coming out of TMSBLDVR. If any volumes with alpha characters in the rightmost position are found, you are not able to use the TMSXTEND utility.
5. Verify that program TMSRINIT can be run on all systems in the shared TMC environment. Specify PARM=STATUS on the JCL.
6. If you are removing volume ranges from the TMC and you use the scratch subpooling feature of CA 1, ensure that any volume ranges being removed are not defined in a range statement in the TMOSCRnn member of CTAPOPTN.
7. To determine if the TMC is cataloged in any nonshared catalogs, review your catalog environment. Any recatalog actions that the TMSXTEND utility performs are performed from the catalog environment on the system where TMSXTEND runs.

More information:

Follow Up Procedures after Initial Run of TMSXTEND

Run TMSXTEND

To build dynamically a new TMC, execute TMSXTEND.

Follow these steps:

1. Allocate the new CA 1 TMC on the desired volume. Use the following naming convention. Use the current TMC name and add a suffix of '.N'. The TMSBLDVR report contains the space requirements of the new TMC.

   Example:

   Existing TMC name - SYS3.CA1.TMC

   New TMC name - SYS3.CA1.TMC.N

   Important! Catalog the new TMC name on every system that shares the TMC. TMSXTEND renames the production TMC to TMC.O and the TMC.N to TMC.

   Notes:

   • You can change the blocking factor for the TMC by allocating the new TMC with the desired blocksize. For more information about blocking the TMC, see the Programming Guide.
   • If more than 4,369 cylinders are required for the TMC, add DSNTYPE=LARGE to the DD statement in the allocation step for the TMC. TMSPTRS does not support DSNTYPE=LARGE. If DSNTYPE=LARGE is used, use TMSAPEC instead of TMSPTRS.
2. To ensure that any critical chaining errors in the DSNB free chain are corrected, run TMSPTRS or TMSAPEC. Minor errors in DSNB or volume records do not cause any problems for TMSXTEND (such as incorrect DSN17 fields or a bad 1STVSN field). Errors in the DSNB free chain can cause TMSXTEND to abend.
3. Plan to run TMSXTEND before or after the CA 1 daily maintenance or any other CA 1 batch job. Before you execute TMSXTEND, stop CA 1 batch utilities and shut down the DBS and APEC subtasks of CTS. Disable the CA Vantage™ Storage Resource Management script for CA 1. The ISPF interface and the old TSOTIQ interface work correctly for individual volume or DSNB inquiries or updates. The range-display in the ISPF interface does not work while TMSXTEND is in progress.

   Note: For more information about the DBS and APEC subtasks of CTS, see the Administration Guide.

4. Back up the TMC by running TMSCOPY. Perform this step within three hours of running TMSXTEND.
5. Run the TMSXTEND utility first with PARM=TEST. You verify that all systems are in the proper status and that the range/DSNB control statements are valid. This test also validates that the new TMC is large enough to hold all records that you requested.
6. Submit the TMSXTEND utility without the PARM=TEST and monitor its execution. The utility provides numerous messages indicating the status of the extend and the switch-over to the new TMC.

   Note: TMSXTEND issues the TMSXT09I SIGNAL ALL CPUS TO ACCESS THE NEW TMC message. Now run TMSRINIT on all CPUs that access this TMC. These TMSRINITs do not end immediately, they stay active until the final switch over command is issued (TMSXT21I). The TMSRINITs end within one minute after the TMSXT21I message is issued. Do not use PARM=STATUS on the TMSRINITs that are executed for this step. If TMSXTEND uses PARM=TEST, all messages are issued and you run TMSRINIT. The physical switch is not done. Set TMSRINIT as a started task.

7. Review messages that TMSXTEND issues. If TMSXTEND cannot automatically recover from abends, run TMSXTEND with PARM=RECOVER. To see if the automatic recovery already took place, refer to the messages that TMSXTEND issues.
8. Verify that all systems switched to the new TMC by checking the job log of the TMSXTEND utility. Review the system consoles for message TMSMR04I, which confirms the switch. To finalize the switch to the new TMC, TMSRINIT must run on all CPUs. Set TMSRINIT as a started task.
9. Create a postconversion backup of the TMC by running the TMSCOPY utility again.

   Note: If you execute TMSCOPY after a TMSXTEND, some records duplicate to the AUDUMP and AUDUMP2 files. Depending on your audit file size and the amount of processing, some records or records for several days can be duplicated. The duplicate records do not have any impact on a noncurrent restore.

10. If you stopped the DBS subtask or CTS in step 4, restart it now.

Follow Up Procedures after Initial Run of TMSXTEND

After you convert to an extended format TMC, retire exits U and E and verify the TMC.

Follow these steps:

1. Remove exits U and E from your LINKLIST library.
2. If you use a nonshared MVS/catalog environment, verify that the TMC is cataloged on the correct volume on all systems. For systems that are not in a shared catalog structure, uncatalog the old TMC. Catalog the TMC on the new volume where you allocated TMC.N.