Why should I use TMSXTEND and what is the procedure.
CA 1 rel 12.0, 12.6, 14.0
Also valid at lower levels but the exits would be TMSUX2E and TMSUX2U.
This new process will allow you to add or remove volume ranges, and DSNBs. It also allows you to get rid of the alphanumeric volser conversion exits, TMSXITE and TMSXITU.
There are a few restrictions that need to be followed. All systems that are using the TMC must have been IPL'd with a release of CA 1 supporting TMSXTEND. The volser numbers can not end with an alpha character and can not be less than 6 characters with padding on the left. If you do have a short volser then the padding of spaces must be on the right.
Before starting the extend procedure you should:
- Verify that all systems sharing the TMC are at the correct maintenance level.
- Run TMSAUDEX to identify all of the systems updating the TMC as recorded in the Audit file. Compare this list to your systems to see if you need to INCLUDE or EXCLUDE any system.
- Run TMSBLDVR utility in standalone mode, specifying the control statements you want to use in the extend. This will help identify any possible problems. It will also report on the amount of space needed for the new TMC.
- Verify that you can run TMSRINIT on all systems. You can do this by specifying PARM=STATUS on the EXEC statement in the JCL.
The general procedure for running TMSXTEND is:
- If you run CTS, you must either stop the DBS task, or release the TMC and Audit files.
- If you run CA-Vantage, you will need to stop using the CA-1 interface.
- Run TMSXTEND with a PARM=TEST, this will give you information about the format of the new TMC.
- Run TMSCOPY to take a backup of the production TMC.
- Stop all CA-1 batch utilites, CTS DBS subtack, and the BrightStor CA-Vantage CA-1 interface.
- Run TMSXTEND without the PARM=TEST. This will do the actual extend to a new TMC.
- After the message TMSXT09I "SIGNAL ALL CPUS TO ACCESS THE NEW TMC" is issued, run TMSRINIT on all CPU's sharing the TMC. We recommend that TMSRINIT be set up as a started task. These TMSRINIT's will NOT end immediately, but instead will simply stay active until the final switch-over command is issued (TMSXT21I). All TMSRINIT's will end within 1 minute of the TMSXT21I message being issued. Do not use the PARM=STATUS on the TMSRINIT's executed for this step.
- Verify that the extend is correct.
- Run TMSCOPY to take a backup of the new TMC.
- Start CTS DBS subtack, and the CA-Vantage CA-1 interface.
A few items you should be aware of:
- You should not use this to remove small segments of your TMC just to make it physically smaller. This can give you a large number of volser ranges which can actually slow the response time of CA-1. For example if you have a range of 1000 tapes and half of them are in delete status, but not all sequential.
- Once you have completed the extend you can remove the old TMSXITE and TMSXITU modules from the CTAPLINK library. There is no reason that they must be immediately removed, but can be done with your next scheduled IPL.
- There are new records added to the TMC during the TMSXTEND. They are after the VOLSER records and before the DSNB records. If you have a job that reads the TMC volume and DSNB's sequentially, you may need to program for these new records.
- You can use the TMSXTEND procedure to get to the new format without doing a physical remove or add to the TMC. By specifying a SYSIN DD DUMMY in the TMSXTEND JCL, CA-1 will move the TMC to the new allocation and put it into the new format. At this point you can remove the TMSXITE and TMSXITU exits.