TMSXTEND Utility -- Dynamic TMC Extend Process Control Program

Use the TMSXTEND utility to build a new TMC dynamically while tape processing is allowed to continue across the shared TMC environment.
Use the TMSXTEND utility to build a new TMC dynamically while tape processing is allowed to continue across the shared TMC environment. For this information in a video format, see TMSXTEND Videos.
You can add or remove volume ranges by specifying the desired ranges as SYSIN parameters. The TMSXTEND utility saves the volume ranges internally in a new TMC record type, the Volume Definition Record.
You can also use TMSXTEND to assign a new unique RNAME to all enqueue or reserves of the TMC and AUDIT file. Unique RNAME is especially important when multiple TMCs exist within a single GRSplex or MIMplex environment. You can use the unique RNAME instead of TMS-TMC, TMS-AUD, and TMSAPEC. The unique RNAME includes the full DSN of the TMC and AUDIT files and the volser that the files reside upon.
To verify the shared TMC environment before you perform a switch, run TMSXTEND in TEST mode. TMSXTEND also provides a RECOVER function to return the TMC to its previous state in the event of a failed extend attempt. The utility is designed to check as many environmental details as possible before proceeding with a TMC switch, greatly reducing the likelihood of a problem.
TMSFORMT was previously used to define a new TMC or Audit and to extend an existing TMC. TMSXTEND now performs this functions, except for the formatting of a new Audit file. Customers with nonstandard volume serial numbers should continue to use TMSFORMT to extend the TMC or define a new TMC.
Restrictions for TMSXTEND
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 non-changing alpha characters in the right-most positions of the VOLSER, or with blanks to the left of a 4- or 5- character VOLSER. Examples of nonstandard VOLSERs are 0920XT (that increases to 0921XT), 00010A (that increases to 00011A), 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. Users should plan to eliminate the use of these VOLSERs over time to enable them to take advantage of the convenience of the TMSXTEND utility.
Short three, four, or five character VOLSERs with the blank on the right are valid only if the portion of the VOLSER that increments is numeric. If the right-most portion is alphabetic and increases (as in A-Z), then some additional rules exist. These types of VOLSERs must be 6-characters in size, and the right-most 3 characters must all be alphabetic and must change. Also, if an alphabetic range is defined, the left-most 2 characters must be un-changed and the fixed portion (left-most portion) can be either alpha or numeric values. Examples are 00AAAA-00ZZZZ (adding 456,976 volumes) and 1BAAAA-1BZZZZ (can be added for a total of 913,952 additional volumes).
Adding 456,976 additional volumes will require that the TMC.N file be allocated (assuming a block-size of 8840) with an additional 196 cylinders than is currently allocated for the TMC.
  • 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.
  • 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.
  • 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.
  • 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.
Report Description
Subprograms of TMSXTEND are TMSBLDVR and TMSAUDEX these create two reports - TMS REPORT-80 and TMS REPORT-81 respectively.
Job Control Statements
//stepname EXEC PGM=TMSXTEND,REGION=0M, // PARM='parm1,parm2 ' //TMSRPT80 DD SYSOUT=* /* TMSBLDVR RPT */ //TMSRPT81 DD SYSOUT=* /* TMSAUDEX RPT */ //SYSPRINT DD SYSOUT=* /* IDCAMS OUTPUT */ //CAISNP DD SYSOUT=* //SYSUDUMP DD SYSOUT=* //SYSIN DD * ADDVOL 001800-001899 ROBTY=02 VENDOR=BASF ADDVOL VM5000-BM5099 /* adding a second range */ REMVOL VT0100-VT0199 /* sample of removing a volume range */ ADDDSNB 1000 /* //CPULIST DD * EXCLUDE CPU9 /* this is a test system we are removing */ INCLUDE CPU6 /* PROD system with no tape activity */ /*
Parameter Definitions
The DIAG parameter can be specified alone or with the TEST or RECOVER parameter. You can specify parameters in any order and you can separate parameters by commas or blanks. If the RECOVER parameter is omitted the program will execute in extend mode.
  • DIAG
    This parameter causes TMSXTEND to write diagnostic snap dumps to the CAISNP output. Snap dumps are created to display internal volume tables, key data areas and changes to control records.
    This parameter causes TMSXTEND to run in recovery mode. In recovery mode TMSXTEND will determine the status of a failed extend. If the signal to switch to the new TMC has not yet been given to all CPU's sharing the TMC, it will rename and return the old TMC to its original status, updating any control records necessary. If the signal to switch to the new TMC has been given to all CPU's sharing the TMC, it will finish updating any control records necessary.
  • TEST
    This parameter causes TMSXTEND to run in test mode. In test mode, TMSXTEND will perform all of the checks and most of the functions of the actual extend mode. The new TMC is created and synchronized but the TMCs are not renamed and the CPUs do not switch to the new TMC. This mode allows you to preview or test the extend process. In test mode, if errors are detected they will be reported but the process does not fail as it does with an actual extend.
JCL Considerations
The JCL provided in this document assumes that the CA 1 load library is defined as a LINKLIST data set.
  • TMSRPT80
    Defines the report output data set for the TMS REPORT-80. This DD statement is required.
  • TMSRPT81
    Defines the report output data set for the TMS REPORT-81. This DD statement is optional.
    Defines the report output data set used by IDCAMS, which is invoked to perform the TMC renames. This DD statement is required.
    TMSXTEND writes snap dumps to this DD statement when requested by PARM=DIAG. This DD statement is required only if PARM=DIAG is specified.
    Defines the input data set for volume range and DSNB control statements. This DD statement is optional. If you do not specify a SYSIN DD statement all volume ranges and DSNBs in the existing TMC will be copied to the new TMC. This approach may be used to copy a TMC to a new, blocked TMC without adding or removing any volume ranges.
    Defines the input data set for CPU include or exclude control statements. This DD statement is optional and if not specified, all CPUs sharing the TMC must be found in the current Audit file.
Completion Codes
The following completion codes are issued by TMSXTEND:
  • 0
    Successful completion.
  • 8
    TMC extend failed. Refer to the TMS REPORT-80 or 81 reports and the job log to determine cause of failure.
  • U0006
    Invalid control statement error. Check TMS REPORT-80 or 81 to determine cause of failure.
  • U0996
    The current TMC could not be allocated. Check to ensure that the TMC is cataloged on the system where you are running TMSXTEND.
  • U0997
    The new TMC could not be allocated or opened. Refer to messages TMSVR03E or TMSVR05E.
  • U1022
    TMSXTEND had abended for one of many reasons.
Procedures for Executing the TMSXTEND Utility
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. Verify that the output accurately reflects your shared TMC environment. If a system has not been active, with
CA 1 Tape Management System
tape activity being recorded to the Audit, that system is not known. If you start
CA 1 Tape Management System
later on that system and you do not apply the necessary maintenance,
CA 1 Tape Management System
fails to initialize. First run the TMSBLDVR utility in standalone mode and evaluate your TMC volume ranges. If you have coded
CA 1 Tape Management System
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 Tape Management System
    , 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.
Run TMSXTEND to build a new TMC dynamically.
Follow these steps:
  1. Allocate the new CA 1 Tape Management System TMC data set on the desired volume with the naming convention of the current TMC name and add a suffix of '.N'. When executed in standalone mode, TMSBLDVR can be used to identify the volume ranges in an existing TMC, validate volume range or DSNB control statements, and determine the size requirement of the new TMC.
    Existing TMC name - SYS3.CA1.TMC
    New TMC name - SYS3.CA1.TMC.N
    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.
    • 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 Programming.
    • 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.
  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 Tape Management System
    daily maintenance or any other
    CA 1 Tape Management System
    batch job. Before you execute TMSXTEND, stop
    CA 1 Tape Management System
    batch utilities and shut down the DBS and APEC subtasks of CTS. Disable the CA Vantage™ Storage Resource Management script for
    CA 1 Tape Management System
    . 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.
    For more information about the DBS and APEC subtasks of CTS, see Administrating.
  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.
    TMSXTEND issues the TMSXT09I SIGNAL ALL CPUS TO ACCESS THE NEW TMC message. Once you see TMSXT09I , 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. The final switch over command is message TMSXT21I SIGNAL CPUS TO SWITCH TMCS in the TMSXTEND job. 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 CA 1 SWITCHED TO NEW TMC, 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.
    If you execute TMSCOPY after a TMSXTEND, some records duplicate to the AUDUMP and AUDUMP2 files. Depending on your audit filesize 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 3, restart it now. If you had been logged on to the CA 1 ISPF interface or the older TIQ interface, log out and back onto the CA 1 ISPF interface or TIQ interface.
    If using scratch subpools, make sure the new ranges are added to the appropriate TMOSCRxx pool. They can be added days or weeks before the ranges are added to the TMC itself. Once the TMOSCRxx member has been updated, you must run TMSINIT to activate the new definition.
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.
Control Statement Specifications
Control statements for the SYSIN DD statement
The control statements are parsed through column 80. Do not use sequence numbers on these statements in columns 73 - 80.
If you want to remove a range to clear the data in the TMC and then add it back for use with new tapes, run the TMSXTEND procedure twice. Run TMSXTEND first with the REMVOL and second with the ADDVOL for the same range.
  • ADDDSNB nnnnnnnn
    Requests that nnnnnnnn additional DSNB records be added to the new TMC. A maximum of 99,999,999 total DSNBs can be defined.
    Lowvol-Highvol DEN=nn ROBTY=nn TRTCH=nn VENDOR=cccccccc DELETE specifies that the volume range lowvol-highvolbe added to the new TMC. Optional parameters are provided to initialize the volume records with a density (DEN), robottype(ROBTY)recordingtechnique(TRTCH)and vendor (VENDOR). For the DEN, ROBTY and TRTCH parameters, nnshould be replaced with hexadecimal values. For a list of these values see Programming. The DELETE parameter simply indicates thevolume(s) are added in DELETE status in the new TMC. VENDOR is an1-8 character string that is used to identify the media manufacturer. In addition to a range, a single VOLSER may also be specified on the ADDVOL statement.
    • The dash ("-") is required between lowvol and highvol.
    • VOLSERs shorter than six characters are supported. They are left justified and padded with blanks. The volumes added willbe in SCRATCH status if you do not use the DELETE keyword in the control statement.
  • REMDSNB nnnnnnnn
    Requests that nnnnnnnn free DSNB records be removed from the new TMC. Only DSNBs from the end of the free chain that have never been used can be removed. A maximum of 99,999,999 total DSNBs can be defined.
  • REMVOL lowvol-highvol
    Specifies that all volumes in the range lowvol-highvolbe removed from the TMC. All volumes in this range must be in DELETE status, otherwise the entire range is not removed. A single VOLSER may also be specified on a REMVOL control statement. You cannot remove all VOLSER entries from a TMC.
    Specifies if UNIQUE_RNAME is used with this TMC. If you want to code this statement, code it as the first statement in the SYSIN DD. You can also use the CA CSM configuration user interface to set this option on. Add "Unique_RNAME=YES/NO" on TMSBLDVRjob when you configure the creation of a new TMC using CA CSM.
Control Statements for the CPULIST DD Statement
When all systems sharing the TMC have tape processing performed on them at least once a day, there is no need for any CPUs to be included in the CPULIST control statements. However, if there are some CPUs that have NO tape processing performed on them, or when the tape processing is very sporadic that can go for days at a time without any tape processing, it would be recommended to use the INCLUDE type of CPULIST control statement.
The EXCLUDE control statement should only be used when there is a CPU that shares the TMC AND that CPU will not be active when TMSXTEND is running AND that CPU is 100% guaranteed to be at the correct maintenance level applied. If that CPU will be active, but there will not be any tape jobs running on it, it should not be excluded using the EXCLUDE control statement.
You cannot exclude the CPU that TMSXTEND is running on itself. If the SMF ID of the CPU that TMSXTEND is running on is listed on the EXCLUDE statement, it will be automatically included and shown as forced on Report-81.
  • INCLUDE smf id
    This control statement defines the SMF ID of a system running
    CA 1 Tape Management System
    that should be included in the list of systems to process when performing an extend function. INCLUDE must begin in column 1 followed by a blank and then the SMF id. Only one SMF id may be specified per control statement.
  • EXCLUDE smf id
    This control statement defines the SMF ID of systems running
    CA 1 Tape Management System
    that should be excluded from processing by TMSXTEND. EXCLUDE must begin in column 1 followed by a blank and then the SMF id. Only one SMF id may be specified per control statement. Note that failure to find a system specified on an EXCLUDE statement is not considered an error.
    Comments identified by an asterisk in column 1 may be specified in both CPULIST and SYSIN DDs but are not listed in any report.
ADDVOL Examples
The following would define 3,741,856 volumes with only 7 ADDVOL statements:
  • ADDVOL 000000-999999 (adds 1 million volumes, all numeric)
  • ADDVOL 0AAAAA-0AZZZZ (adds 456,976 volumes)
  • ADDVOL 0BAAAA-0BZZZZ (adds 456,976 volumes)
  • ADDVOL 0CAAAA-0CZZZZ (adds 456,976 volumes)
  • ADDVOL 0DAAAA-0DZZZZ (adds 456,976 volumes)
  • ADDVOL 0EAAAA-0EZZZZ (adds 456,976 volumes)
  • ADDVOL 0FAAAA-0FZZZZ (adds 456,976 volumes)
The following are good examples:
  • ADDVOL 00AAAA-00ZZZZ - This is valid and adds 456,976 volumes in a single range.
  • ADDVOL A01AAA-A01ZZZ - This is valid and adds 17,576 volumes in a single range.
  • ADDVOL ZZ0000-ZZ9999 - This is valid and adds 100,000 volumes in a single range.  
The following are bad examples:
  • ADDVOL 0A0A0A-0A0Z9Z - This is not valid because both alpha and numeric values are changing.
  • ADDVOL 1234AA-1234ZZ - This is not valid because, at a minimum, if the right-most character is alphabetic, at least 3 characters must change.
  • ADDVOL 00AAAA-03ZZZZ - This is not valid because both alphabetic and numeric values are changing. However, this could be broken down into four ranges individually and would be valid (for example 00AAAA-00ZZZZ, 01AAAA-01ZZZZ, 02AAAA-02ZZZZ, and 03AAAA-03ZZZZ).
TMS Report 80 - Report Field Definitions
If you do not code the ADDDSNB or REMDSNB control statement, the number of DSNBs that can be deleted is not analyzed. The report displays the following line:
  • External Volser Range
    This field shows the low and high VOLSER numbers for a range found in the TMC.
  • TMC Rec Number
    This field shows the low and high relative record number of the volume serial numbers for each range in the TMC.
TMS REPORT 80 also lists the TMC name being evaluated, the input control statements, and the ranges that would be created for the new TMC. The report also gives the number of DSNBs currently allocated, currently unused, and how many can be removed. If you run TMSBLDVR in standalone mode, the report also gives the space requirements of the TMC based on an unblocked TMC or a TMC allocated with a blocksize of 8840.
You are using use UNIQUE_RNAME=YES to create a TMC or you are extending an existing TMC.
None. The message is informational.
You are using UNIQUE_RNAME=NO when you are extending an existing TMC and unique RNAME was previously activated.
None. The message is informational.
UNIQUE_RNAME is not the first control statement coded. TMSBLDVR ends with the reason code 12.
Code UNIQUE_RNAME as the first control statement.
An error was detected during TMSXTEND processing which caused TMSBLDVR to end prematurely. The new TMC has not been fully created.
Search and fix any errors in the TMSXTEND job and resubmit.
TMS Report 81 - Report Field Definitions
THURSDAY, APRIL 17, 2008.108 Y O U R C O M P A N Y N A M E ROxxxxx PAGE=00001 TMS REPORT-81 AUDIT EXTRACT BY CPU CPU RECORD COUNT LO--DATE TIME HI--DATE TIME FLG CTL STMT ERRORS CPU1 1,199 2008105 8:40 2008108 9:49 Y CPU2 0 ZEROS 0:00 ZEROS 0:00 N EXCLUDE ********************************* * CONTROL STATEMENTS PROCESSED: * ********************************* EXCLUDE CPU2
  • CPU
    The SMF id of the z/OS system creating audit records. SMF ids for systems specified on an INCLUDE or EXCLUDE statement are also listed even if no audit records were found for the requested system. Users running VM Tape and sharing the TMC with that product may see a report line with a blank SMF id. This is an indication of the VM Tape system not being at the necessary maintenance level for sharing the TMC and is considered an error.
    Total number of audit records found for the system.
    Lowest date and time of any audit record found for the system.
    Highest date and time of any audit record found for the system.
  • FLG
    Flag indicating if the system is at the required level to run the TMC extend utility TMSXTEND. All systems listed must be at the required level in order to run TMSXTEND. 'Y' or 'N' will be listed in this column indicating whether or not the system is at the right maintenance level.
    This column will show INCLUDE or EXCLUDE if a control statement was specified for this system.
    This column provides a description of any errors encountered in processing the Audit file.
This message will be issued by TMSAUDEX if TMSINIT has not run on that system or if there has been no tape processing since the last backup or the system does not have the required maintenance to support TMSXTEND. Either run TMSINIT or a tape job, or apply the correct maintenance to support TMSXTEND and rerun the procedure.
The Unique_RNAME feature was being activated when TMSAUDEX experienced an EXCLUDE statement. CPUs are not allowed to be excluded while the Unique_RNAME feature is being activated.
Cancel the Unique_RNAME activation by removing the "UNIQUE_RNAME=Y" or remove EXCLUDE control statements from TMSXTEND and resubmit.
TMSXTEND Recovery Procedures
If an abend situation occurs in TMSXTEND, it will probably recover by itself. Look for messages TMSXT41I and TMXST49I. If the machine that TMSXTEND is running on goes down, there will be some manual recovery necessary.
The first scenario is when the TMC being extended is shared by more than 1 CPU. This is the easiest situation to recover from. Simply run TMSXTEND with PARM=RECOVER on any other CPU that shares the same TMC and AUDIT.
The second scenario is when the TMC being extended is only accessed from 1 (one) CPU, and that CPU goes down. After it uses IPL and CAS9 has run, but BEFORE the TMSINIT job has been run, you may be required to perform some manual intervention. If the TMSXT30I message had been issued, but NOT the TMSXT31I message OR TMSXT21I messages, then you must manually rename TMC.O to TMC before running TMSINIT. In this situation, after TMSINIT has been run you should also run TMSXTEND with a PARM=RECOVER to finish the cleanup of CTL#4.
In the same scenario, if the TMSXT30I message had not yet been issued by TMSXTEND, then there is no recovery necessary and you may simply run TMSINIT.
Also in this same scenario, if the TMSXT31I AND TMSXT21I messages had both already been issued, there is also no recovery necessary and you may simply run TMSINIT.