Utilities › TMSMERGE Utility—Merge TMC Data › Merge Procedure (without using AIVS or foreign control statements)

Merge Procedure (without using AIVS or foreign control statements)

Step 1

Execute TMSBINQ with the HEADERS control statement to generate a report on the TMC and Audit Control Records. The output of TMSSPLIT (TMS Report 50) shows the number of DSNB and Audit records required of the receiving site. The output of TMSBINQ provides verification that sufficient records exist in each database for the merge operation. The output of TMSSPLIT also shows each Volume record that is to be placed in the receiving TMC.

If the receiving TMC does not have the necessary records available, TMSFORMT needs to be executed to perform an extend operation and add any additional Volume or DSNB records as required. If the Audit data set does not contain the required number of records identified by TMSSPLIT, TMSFORMT needs to be executed to reformat the Audit data set. (It can later be reformatted to its original size.) For additional information, see Extending the TMC and Formatting the Audit Data Set.

Step 2

Execute TMSPTRS on the receiving TMC and correct any multivolume or multi-data set chaining errors reported. TMSPTRS must run with a condition code of 0 before you continue to the next step.

Step 3

TMSMERGE requires that CA 1 is initialized into either a batch active or active status. While batch active, CA 1 will not track any realtime tape activity but a nominal amount of such activity is indicated if CA 1 remains active. No other CA 1 batch or online processing should be performed during the merge, whether CA 1 is active or batch active.

Step 4

Execute TMSCOPY to back up the receiving TMC and reset the Audit data set pointers.

Step 5

Execute TMSMERGE using the import tape created by TMSSPLIT.

Step 6

Review the reports generated by TMSMERGE. In a successful merge, the output of TMSMERGE should match that of TMSSPLIT. If desired, the receiving TMC can be backed up with TMSCOPY.

Step 7

If the merge is invalid (for example, a Volume record was unintentionally overlaid), the TMC can be recreated with TMSMERGE. Modify the IMPORT DD to reference the purge file created in the bad merge and catalog a new PURGE DD file. Once a corrected import tape is available, the merge procedure can be reexecuted.

Note: As an alternative, the TMC can be restored by executing the TMSCOPY utility with PARM='RESTORE,NOAUDIT' using the backup tape created in STEP 4.

Step 8

If the merge abended and TMC recreation is not required, the PARM=RESTART option directs TMSMERGE to compare the sending TMC records with the receiving TMC. No Audit records are created until the first discrepancy in the TMC records is encountered, at which point TMSMERGE resumes the update process.

Step 9

Initialize CA 1 as active if CA 1 was made batch active in Step 3.