Messages ERR68 through ERR83 are issued while multivolume and multi-data set chain are verified in parallel. Since comprehensive information about all records belonging to the chain may not be available at the time an error is detected, it is recommended to resolve all errors with lower numbers associated with a chain and eventually rerun TMSPTRS before researching one of these messages.
{CHAIN PROCESSING STOPPED}
ERRnn CHAINING FROM BASE bbbbbb: VOLUME vvvvvv DSNB {CORRECTION SEE TMSUPDTE DD}
{CORRECTION SEE TMSUDSNB DD}
bbbbbb Base volume of the chain.
vvvvvv Volume currently processed when the error was detected.
ddddddd DSNB currently processed when the error was detected (if applicable).
CHAIN PROCESSING STOPPED This is a critical error which disabled the utility from continuing forward chaining.
CORRECTION SEE TMSUPDTE DD Control statements were written to the specified data set. These can be used as SYSIN to TMSUPDTE to correct the chaining error. For more information see the utility TMSUPDTE.
CORRECTION SEE TMSUDSNB DD Control statements were written to the specified data set. These can be used as SYSIN to TMSUDSNB to correct the chaining error. Supply your system password in the first statement before submitting the job. For further information, see the description of utility TMSUDSNB.
Reason:
An error in the multivolume chain disables further chain processing.
Action:
Review multivolume error messages issued for the volumes of the chain, correct the error, and rerun TMSPTRS.
Reason:
Two subsequent volumes point to different DSNB chains.
Action:
Determine the correct value and update either 1STDSNB field. Rerun TMSPTRS.
Reason:
The volume has no DSNB chain associated, but either LSTDSNB or NUMDSNB is greater than zero.
Action:
Determine the DSNB, the volume should be referencing in 1STDSNB and update the field accordingly. If there is no DSNB chain to be associated, clear the LSTDSNB and NUMDSNB values and rerun TMSPTRS.
Reason:
An invalid DSNB number (greater than the number of DSNBs allocated)was found in the chain.
Action:
Update the 1STDSNB or NEXT pointer with the correct DSNB number and rerun TMSPTRS.
Reason:
This is not a chaining error. The DSNB number in the record does not conform with the number of the DSNB which should have been read.
Action:
For single occurrences, update the CURDSNB field with the DSNB number indicated in the message. Multiple occurrences indicate a hash problem. Run TMSINIT and rerun TMSPTRS.
Reason:
This is not a chaining error. The record read is not marked as a DSNB record.
Action:
For single occurrences, update field BID with value X'FF'. Multiple occurrences indicate a hash problem. Run TMSINIT and rerun TMSPTRS.
Reason:
An unused DSNB was found in the multi-data set chain.
Action:
If the DSNB contains valid data and belongs to the chain, update field ACTIND with value X'80'. Otherwise, review further messages issued for the chain. Update the invalid 1STDSNB or NEXT pointer referencing the unused DSNB with the correct DSNB number or HEXZEROS.
Reason:
The file sequence is not 1 greater than the file of the previous DSNB (or not equal 2 for the first DSNB).
Action:
Verify that the DSNB is chained correctly within the multi-data set chain and correct the FILSEQ field as indicated; otherwise reestablish the DSNB chain.
Reason:
The VOLSER field in the DSNB is not equal to the VOLSER of the previous DSNB, or not equal to the volume referencing the DSNB as 1STDSNB.
Action:
Determine if the DSNB belongs to the chain. If so, update the VOLSER field with the correct value, else reestablish the DSNB chain and rerun TMSPTRS.
Reason:
The number of the DSNB pointing to this DSNB as NEXT is not referenced in the PREV field.
Action:
Update the PREV pointer as indicated.
Reason:
The F1STVSN value is either missing or incorrect.
Action:
Update the field with the indicated VOLSER. TMSUDSNB control statements are generated by the program.
Reason:
The DSN17 field does not contain the last 17 characters of the data set which is the first on the tape, according to the structure of the multi-data set or multi-volume chain.
Action:
Verify the chain and update the DSN17 field with the correct value. It should match the DSN from HDR1 label of SL tapes.
Reason:
The tape was not created under CA 1 control or the DSN17 filed was cleared manually.
Action:
Update the DSN17 field with the correct value, if desired.
Note: As long as the field is HEXZERO, no verification is performed against the DSN of the HDR1 tape label when the tape is recreated. This prevents 'NOT SCRTCH (28)' rejects for SL tapes if the TMC data does not correspond to the tape label information.
Reason:
According to the NUMDSNB value, this DSNB should be referenced in the LSTDSNB field of the volume.
Action:
Update the LSTDSNB field accordingly.
Reason:
The multi-data set chain is longer than indicated in the NUMDSNB field of the last volume of the chain.
Action:
If the NUMDSNB field is incorrect, update it with the correct value. Otherwise, verify and rebuild the multi-data set chain and rerun TMSPTRS.
Reason:
The multi-data set chain is shorter than indicated in the NUMDSNB field of the volume.
Action:
If the NUMDSNB field is incorrect, update this volume and any subsequent volumes with the correct value. Otherwise, verify and rebuild the multi-data set chain and rerun TMSPTRS.
Reason:
The multi-data set indicator TMULTIF of FLAG3, which was introduced with Version 5.1, does not have the correct value.
Action:
Turn ON/OFF the flag bit as indicated. TMSUPDTE control statements are generated by the program. All other errors related to the chain should be corrected and TMSPTRS should be rerun before the updates are performed.
Reason:
A volume with no first-volume, or a first-volume equal to itself was found with a volume sequence greater than 1.
Action:
If this is the first volume in the chain, update the VOLSEQ field with a 1. Otherwise, correct the volume pointers.
Reason:
Either the TMACVOLI bit in FLAG4 or the TMVTEXP bit of FLAG5 was on and ACTVOL was blank, or ACTVOL was non-blank and both flag bits were off.
Action:
If this is an AIVS volume, turn the TMACVOLI flag bit on and update ACTVOL with the actual internal volser. If this is an exported virtual volume, set the TMVTEXP flag bit and update ACTVOL with the volser of the physical container volume that was used for the export. Otherwise, turn both flag bits off and set ACTVOL to HEXZEROS.
Reason:
The TMC cannot be scanned because it is not a valid TMC. TMSAPEC cannot scan the TMC because the TMC control record has been damaged or the TMC may be an old TMC that has been extended using the TMSXTEND utility. When TMSXTEND creates a new TMC, the control record in the old TMC is invalidated to prevent a site from accidentally running with the old TMC.
Action:
Verify the TMC being scanned is a valid TMC and restart the scan.
Reason:
TMSAPEC stopped scanning the TMC before the end of the TMC was reached. The scanning of the TMC was manually stopped before the scan was finished.
Action:
Restart the scan and allow the scan to complete.
Reason:
The NEXT field has the same DSNB number as CURDSNB which is invalid.
Action:
Ensure that this DSNB is not part of a valid chain. If so, rechain accordingly. If not, verify ACTIND=80 in the DSNB record and then use TMSAGGR to return it to the free chain.
|
Copyright © 2013 CA Technologies.
All rights reserved.
|
|