Reason:
TMSMERGE has completed the first pass of processing where it verifies that enough DSNB and Audit records are available for the merge process.
Action:
No action is required. This is an informational message.
Reason:
TMSMERGE has completed the second pass of processing which did the actual merge of the import records.
Action:
No action is required. This is an informational message.
Reason:
The Audit threshold has been reached. No further updates by CA 1 batch programs are allowed.
Action:
Execute TMSCOPY with a parameter of BACKUP to reset the Audit pointers and resubmit the job.
Reason:
A new external volser was assigned because a control statement with either AIVS=xxxxxx or FOREIGN=xxxxxx was specified.
Action:
None. This is an informational message only and should be used to relabel the external label or the tapes.
Reason:
Informational message to show what the control card statement was.
Action:
None. This is an informational message.
Reason:
The first pass of TMSMERGE has determined that xxxxxxx number of Audit records is required to complete the merge process and only yyyyyyy are available.
Action:
If the Audit file contains enough formatted records to satisfy the merge process, execute TMSCOPY to reset the Audit pointers. Otherwise, format a larger Audit file for the merge process with TMSFORMT.
Reason:
The first pass of TMSMERGE has determined that xxxxxxx number of DSNB records are required to complete the merge process and only yyyyyyy are available.
Action:
execute TMSFORMT with the EXTEND option to add more DSNB records to the TMC.
Reason:
The data set name specified by the IMPORT ddname did not contain any records.
Action:
Correct the JCL and resubmit the job.
Reason:
VOLSER xxxxxx in the IMPORT file is not contained in the range of the receiving TMC.
Action:
If the volume serial number is alphanumeric, verify that TMSXITU is correct. Otherwise, correct the IMPORT file and resubmit the job.
Reason:
This error occurs if PARM=RESTART processing detected that an import volume record was bypassed due to previously being imported by an earlier run of TMSMERGE. When regular processing (not PARM=RESTART) stops for some reason during the process of importing a chain of DSNBs, DSNB errors occur.
Action:
Execute TMSPTRS to correct chaining errors. Verify that all multifile records from the import have been merged correctly.
Reason:
Volume xxxxxx in the IMPORT file is not contained in the range of the receiving TMC.
Action:
If the volume serial number is alphanumeric, verify that TMSXITU is correct. Otherwise, correct the IMPORT file and resubmit the job.
Reason:
There are insufficient Audit records available to record the merge process. This is based upon the required number of Audit records passed on the import tape from TMSSPLIT.
Action:
Check the output from TMSSPLIT to determine the number of Audit records required for the TMSMERGE job. Either execute TMSCOPY to reset the Audit pointers, or format a new, larger Audit file for the merge process with TMSFORMT.
Reason:
TMSMERGE has determined that there are insufficient DSNB records available to track the secondary files being merged into the TMC.
Action:
Check the output from TMSSPLIT to determine the number of DSNB records required for the TMSMERGE job. Extend the number of DSNB records using TMSFORMT.
Reason:
An invalid control statement was found.
Action:
Ensure the control statements begin in column 1, statements are spelled correctly, and all specified volsers are defined in the TMC.
Reason:
Restart cannot be used with SYSIN control statements.
Action:
Remove the restart parameter or run with no SYSIN control statements.
Reason:
VOLSER xxxxxx in a multivolume chaining field is in error.
Action:
If the volume serial number is alphanumeric, verify thatTMSXITU is correct. Otherwise, correct the volume serial number and resubmit the job.
Reason:
When an import volume overlays an active volume record on the target TMC, TMSMERGE clears any DSNBs associated with the set and unchains any volume chaining to avoid pointer errors. During the unchaining process, VOLSER xxxxxx was associated with a multivolume pointer and is not contained in the range of the TMC.
Action:
If the volume serial number is alphanumeric, verify that TMSXITU is correct. Otherwise, correct the volume serial number and resubmit the job.
Reason:
TMSMERGE has successfully recreated the TMC from the purge tape.
Action:
No action is required. This is an informational message.
Reason:
Control #4 from the Audit data set does not contain TMSCTL#4 as the record identifier.
Action:
The Audit data set is invalid. Format a new Audit with TMSFORMT.
Reason:
An attempt to assign a new external volser was made because a control statement with either AIVS=xxxxxx or FOREIGN=xxxxxx was specified. However, this volume could not have a new external volser assigned because there was an insufficient number of tape volumes in DELETE status.
Action:
Restore the TMC from the backup taken prior to TMSMERGE. Ensure enough tapes are in DELETE status to merge all of the duplicate or foreign tapes being received.
Reason:
The volume record being merged into the TMC from the IMPORT tape is overlaying a record which is not in scratch or inactive (DELETE) status.
Action:
Either rebuild the original TMC with TMSMERGE as specified in Step 7 of the Merge Procedure or research the data and determine whether the resulting TMC is acceptable.
Reason:
This message indicates that the active target record that was overlaid had DSNBs associated with it which were released back into the free chain.
Action:
Either rebuild the original TMC with TMSMERGE as specified in Step 7 of the Merge Procedure or research the data and determine whether the resulting TMC is acceptable.
Reason:
This message indicates that the overlaid active target record was part of a multivolume chain and the volume chains have been broken.
Action:
Either rebuild the original TMC with TMSMERGE as specified in Step 7 of the Merge Procedure or research the data and determine whether the resulting TMC is acceptable.
Reason:
This message indicates the number of Audit records that are needed to recreate the original TMC from the purge tape (if necessary).
Action:
No action is required. This is an informational message.
Reason:
This message indicates the number of DSNB records that are needed to recreate the original TMC from the purge tape (if necessary).
Action:
No action is required. This is an informational message.
Reason:
The PARM=RESTART option directs TMSMERGE to compare the import tape records with the receiving TMC and to resume the update process at the first discrepancy between the records. When the update began, the specified number of DSNB records were bypassed due to matching values.
Action:
No action is required. This is an informative message.
Reason:
The specified number of TMC Volume and DSNB records were read from the import tape.
Action:
No action is required. This is an informational message.
Reason:
The PARM=RESTART option directs TMSMERGE to compare the import tape records with the receiving TMC and to resume the update process at the first discrepancy between the records. The update began after xxxxxxx number of records compared.
Action:
No action is required. This is an informational message.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|