ERR01 Through ERR66

Utility Report Messages › TMSPTRS and TMSAPEC Messages › ERR01 Through ERR66

ERR01 Through ERR66

ERR01 VOLUME xxxxxx PREVVOL IS yyyyyy WHICH IS UNHASHABLE

Reason:

This is a multivolume chaining error. The field indicated contains a VOLSER that is not defined within the ranges of the TMC.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volume if no longer needed.

ERR02 VOLUME xxxxxx PREVVOL IS yyyyyy BUT NEXTVOL OF yyyyyy ISHEXZEROS

Reason:

This is a multivolume chaining error. The backward and forward pointers between the volumes indicated are not consistent.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volumes if no longer needed.

ERR03 VOLUME xxxxxx NUMDSNB xxxxxx 1STDSNB xxxxxx PREVVOL yyyyyy NUMDSNB nnnnnn 1STDSNB zzzzzz.

Reason:

This is an aggregate chaining error. If the NUMDSNB field of two chained volumes is not zero, the 1STDSNB field of the two volumes must be the same number.

Action:

Correct the 1STDSNB field in the Volume record. If the volume is no longer needed, clear all pointer fields, set VOLSEQ to 1, and expire the volume.

ERR04 VOLUME xxxxxx NEXTVOL IS yyyyyy WHICH IS UNHASHABLE

Reason:

This is a multivolume chaining error. The field indicated contains a VOLSER that is not defined within the ranges of the TMC.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volume if no longer needed.

ERR05 VOLUME xxxxxx NEXTVOL IS yyyyyy BUT PREVVOL OF yyyyyy ISHEXZEROS

Reason:

This is a multivolume chaining error. The backward and forward pointers between the volumes indicated are not consistent.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volumes if no longer needed.

ERR06 VOLUME xxxxxx NUMDSNB xxxxxx 1STDSNB xxxxxx NEXTVOL yyyyyy NUMDSNB nnnnnn 1STDSNB zzzzzz.

Reason:

This is an aggregate chaining error. If the NUMDSNB field of two chained volumes is not zero, the 1STDSNB field of the two volumes must be the same number.

Action:

Correct the 1STDSNB field in the Volume record. If the volume is no longer needed, clear all pointer fields, set VOLSEQ to 1, and expire the volume.

ERR07 VOLUME xxxxxx 1STVOL IS yyyyyy WHICH IS UNHASHABLE

Reason:

This is a multivolume chaining error. The field indicated contains a VOLSER that is not defined within the ranges of the TMC.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volume if no longer needed.

ERR08 VOLUME xxxxxx 1STVOL IS yyyyyy BUT 1STVOL OF yyyyyy IS zzzzzz

Reason:

This is a multivolume chaining error. The backward and forward pointers between the volumes indicated are not consistent.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volumes if no longer needed.

ERR10 VOLUME xxxxxx 1STVOL IS HEXZEROS BUT NEXTVOL IS yyyyyy

Reason:

This is a multivolume chaining error. The backward and forward pointers between the volumes indicated are not consistent.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volumes if no longer needed.

ERR11 VOLUME xxxxxx 1STVOL IS HEXZEROS BUT PREVVOL IS yyyyyy

Reason:

This is a multivolume chaining error. The backward and forward pointers between the volumes indicated are not consistent.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volumes if no longer needed.

ERR12 VOLUME xxxxxx 1STVOL IS yyyyyy BUT NEXTVOL AND PREVVOLARE HEXZEROS

Reason:

This is a multivolume chaining error. The backward and forward pointers between the volumes indicated are not consistent.

Action:

Replace the erroneous field with the correct VOLSER or clear the chaining fields and expire the volumes if no longer needed.

ERR15 VOLUME xxxxxx HAS DIFFERENT DSN THAN PREVVOL yyyyyy

Reason:

This is a multivolume chaining error. The data set name in each Volume record for a multivolume chain should always reflect the DSN for File 1 of the first volume.

Action:

Replace the erroneous field with the correct DSN or clear the chaining fields and expire the volumes if no longer needed.

ERR16 VOLUME xxxxxx HAS VOLSEQ nnnn, BUT PREVVOL HAS VOLSEQ zzzz

Reason:

This is a multivolume chaining error. The VOLSEQ fields should always be consecutive throughout a chain.

Action:

Correct the erroneous field, or clear the chaining fields and expire the volumes if no longer needed.

ERR17 VOLUME xxxxxx HAS DIFFERENT DSN THAN NEXTVOL yyyyyy

Reason:

This is a multivolume chaining error. The data set name in each Volume record for a multivolume chain should always reflect the DSN for File 1 of the first volume.

Action:

Replace the erroneous field with the correct DSN or clear the chaining fields and expire the volumes if no longer needed.

ERR18 VOLUME xxxxxx HAS VOLSEQ nnnn, BUT NEXTVOL HAS VOLSEQ zzzz

Reason:

This is a multivolume chaining error. The VOLSEQ fields should always be consecutive throughout a chain.

Action:

Correct the erroneous field or clear the chaining fields and expire the volumes if no longer needed.

ERR24 UNUSED DSNB xxxxxx IS NOT IN CHAIN AND CHAINSTHRU END-OF CHAIN

Reason:

This is a Control Record #2/DSNB free chain error. A series of unused DSNBs, or a single unused DSNB, is not part of the free chain referenced by Control Record #2.

Action:

This chain of DSNB(s) can be returned to the free chain with TMSUDSNB.

ERR24 UNUSED DSNB xxxxxx IS NOT IN CHAIN AND CHAINS THRU DSNB yyyyy, nnnnnn DSNBS IN CHA

Reason:

This is a Control Record #2/DSNB free chain error. A series of unused DSNBs, or a single unused DSNB, is not part of the free chain referenced by Control Record #2.

Action:

The DSNB can be returned to the free chain with TMSUDSNB. As an alternative, update the ACTIND field in the DSNB to X'80' with TMSUDSNB (REP ACTIND=80), and the DSNB can then be cleared and returned to the free chain with TMSAGGR. The highest number DSNB should always be the end of the chain. It should always have a NEXT of zero.

ERR25 NO END-OF-CHAIN FOR UNUSED DSNBS

Reason:

This is a Control Record #2/DSNB free chain error. The last DSNB in the allocation should always be unused and should always have a value of zero in the NEXT field. In this instance, the NEXT field refers to something other than zero.

Action:

Display Control Record #2 to determine the last DSNB allocated and update the NEXT and DSN fields in that DSNB to HEXZEROS.

ERR26 UNUSED DSNB xxxxxx POINTS TO LAST DSNB

Reason:

This is a Control Record #2/DSNB free chain error. The DSNB allocation has reached capacity. At this point, all jobs requesting secondary files for output receive a CA 1 system abend (S2yy).

Action:

Additional DSNBs can be added to the free chain by executing TMSCLEAN. As tapes with secondary data sets are scratched, the associated DSNBs are cleared and returned to the free chain. The allocation of DSNBs can be increased with the TMSFORMT utility EXTEND control statement.

ERR26 USED DSNB xxxxxx POINTS TO LAST DSNB

Reason:

This is a Control Record #2/DSNB free chain error. The DSNB allocation has reached capacity. At this point, all jobs requesting secondary files for output receive a CA 1 system abend (S2yy).

Action:

ERR27 UNUSED DSNB xxxxxx IS POSSIBLE END-OF-UNUSED-CHAIN

Reason:

This is a Control Record #2/DSNB free chain error. Based on the number of DSNBs allocated (reflected in Control Record #2) the DSNB specified is considered the end of the free chain. Due to other errors with the free chain, this could not be verified by TMSPTRS, so this informative message is generated.

Action:

Eliminate other errors to prevent this message from being issued.

ERR31 VOL xxxxxx POINTS TO DSNB xxxxxx NOT TO yyyyyy

Reason:

This is a multi-data set chaining error. The volume indicated has a chain of DSNBs or no associated DSNBs, but a DSNB not part of the chain is referencing the volume in VOLSER.

Action:

The DSNB should be cleared and returned to the free chain with TMSAGGR or the VOLSER field set to the proper VOLSER.

ERR32 VOL xxxxxx DSNB xxxxxx - FILSEQ IS nnnn, SHOULD BE zzzz

Reason:

This is a multi-data set chaining error. A DSNB chained off of the indicated volume does not reflect the proper file sequence.

Action:

Determine the correct sequence and correct the appropriate fields.

ERR33 VOL xxxxxx HAS NO END TO DSNB CHAIN

Reason:

This is a multi-data set chaining error. This error is listed when (1) the end of the DSNB chain associated with a volume cannot be found (NEXT= pointing to an unused DSNB), (2) when the last DSNB references a previous DSNB already allocated to the volume, or (3) the VOLSER in the DSNB record is not the VOLSER of the TMC Volume record, but the last DSNB associated with the volume is referencing a DSNB with the invalid VOLSER.

Action:

Determine which DSNB reflects the last physical file on the volume or which VOLSER field is out of synchronization and correct the appropriate fields.

ERR35 VOL xxxxxx IS INVALID IN DSNB xxxxxx

Reason:

This is a multi-data set chaining error. The DSNB record indicated reflects a VOLSER not assigned to the TMC.

Action:

Update the DSNB with the correct VOLSER or, if it is not needed, return the DSNB to the free chain with TMSAGGR.

ERR36 DSNB xxxxxx IS NOT IN CHAIN FOR VOL xxxxxx

Reason:

This is a multi-data set chaining error. The volume indicated has one or more DSNBs that refer to a DSNB that does not reflect the indicated volume in the VOLSER field.

Action:

Update the invalid DSNB with the correct information or set the NEXT value in the DSNB referencing the DSNB not in the chain to HEXZEROS. Return the invalid DSNB to the free chain with TMSAGGR.

ERR37 DSNB XXXXXXX IS CHAINED TO VOL XXXXXX, AND VOL IS IN DELETESTATUS

Reason:

This is a chaining error. The active DSNB indicated is chained to a Volume that is in delete status.

Action:

The DSNB is returned to the DSNB free chain.

ERR37 DSNB XXXXXXX IS CHAINED TO VOL XXXXXX, AND VOL IS IN SCRATCHSTATUS

Reason:

This is a chaining error. The active DSNB indicated is chained to a Volume that is in scratch status.

Action:

The DSNB is returned to the DSNB free chain.

ERR39 VOLUME xxxxxx HAS VOLSEQ OF nnnn AND VOLUME IS NOT CHAINED

Reason:

This is a multivolume chaining error. The VOLSEQ fields should always be consecutive throughout a chain.

Action:

Correct the erroneous field or clear the chaining fields and expire the volumes if no longer needed.

ERR40 xxxxxx DSNBS GENED, yyyyyy DSNBS READ

Reason:

This is a Control Record #2/DSNB free chain error. The number of DSNBs allocated according to Control Record #2 differs with the number processed by TMSPTRS, usually a result of other free chain errors that prevent complete TMSPTRS verification. If no other errors are indicated, there may be a structural problem with the TMC, such as a defragmentation operation relocating the tracks on which the TMC resides.

Action:

Correct any other errors. If there are no other errors, restore the TMC with the TMSCOPY utility. For assistance, contact Technical Support at http://ca.com/support.

ERR41 xxxxxx DSNBS USED(HDR), yyyyyy ACTUALLY USED

Reason:

This is a Control Record #2/DSNB free chain error. The number of DSNBs marked as used in Control Record #2 (HDR) differs with the number of used DSNBs actually counted by TMSPTRS, usually as a result of other DSNB chaining errors.

Action:

Correct any other errors. If there are no other errors present, update Control Record #2 with TMSUDSNB to reflect the number actually used as counted by TMSPTRS.

ERR42 LAST DSNB xxxxxx IS USED, MUST BE UNUSED, VOLSER IS xxxxxx

Reason:

This is a Control Record #2/DSNB free chain error. The last DSNB is incorrectly assigned to a volume record, usually as a result of other chaining errors. The last DSNB allocated should always be unused (DSN=HEXZEROS).

Action:

Update the last DSNB record to reflect unused status, and the DSNB record NEXT field that references this to HEXZEROS. Then use TMSAGGR to purge and reconstruct the DSNB chain for the VOLSER specified, if necessary.

ERR43 DSNB xxxxxx SHOULD BE END OF UNUSED CHAIN, POINTS TO yyyyyy

Reason:

This is a Control Record #2/DSNB free chain error. The last DSNB allocated incorrectly has a NEXT value other than zero. This DSNB should always have a NEXT value of zero.

Action:

Clear the NEXT field in the last DSNB allocated.

ERR44 TMSCTL#2 POINTS TO USED DSNB xxxxxx

Reason:

This is a Control Record #2/DSNB free chain error.TMSCTL#2 should always reference an unused DSNB in the NXAVAIL field. This error results in a CA 1 abend (S3yy) when attempting to create new secondary data sets. Other chaining errors will be listed.

Action:

In this instance, TMSCTL#2 references a used DSNB in the NXAVAIL field, and other errors identify other unused DSNBs. Use TMSUDSNB to attach a valid free chain of DSNBs to the NXAVAIL pointer in Control Record #2.

ERR45 TMSCTL#2 CHAINS THRU DSNB xxxxxx, nnnnnn DSNBS IN CHAIN

Reason:

This is a Control Record #2/DSNB free chain error.TMSCTL#2 should always refer to an unused DSNB in the NXAVAIL pointer, which should reference the next unused DSNBs through the end of the free chain.

Action:

In this instance, the free chain of DSNBs has been broken, and other errors identify other unused DSNBs that can be attached to the last DSNB in the free chain referenced by Control Record #2 with TMSUDSNB or the CA 1 online facilities.

ERR46 TMSCTL#2 CHAINS THRU END OF CHAIN, nnnnnn DSNBS IN CHAIN

Reason:

This is a Control Record #2/DSNB free chain message.TMSCTL#2 is correctly referencing a chain of unused DSNBs terminating at the end of the free chain.

Action:

No action is required unless other chaining errors exist.

ERR47 DSNB xxxxxx DOES NOT CONTAIN A RECORD IDENTIFIER - BID NOTEQUAL FF

Reason:

This is a Control Record #2/DSNB free chain error. All DSNB records should contain X'FF' in the record identifier field, BID. A DSNB record has been encountered that does not satisfy this requirement.

Action:

Update the field BID in the designated DSNB record to X'FF' with TMSUDSNB.

ERR48 VOLUME xxxxxx POINTS TO DSNB xxxxxx, BUT DSNB xxxxxx ISGREATER THAN NUMBER ALLOCAT

Reason:

This is a Control Record #2/DSNB free chain error. An invalid DSNB record reference has been encountered in the NEXT field of a DSNB record. This reference value exceeds the maximum value for DSNBs allocated.

Action:

Update the appropriate DSNB record to remove the invalid reference with TMSUDSNB or the CA 1 online facilities.

ERR49 UNUSED DSNB xxxxxx DOES NOT CONTAIN A RECORD IDENTIFIER -BID NOT EQUAL FF

Reason:

This is a Control Record #2/DSNB free chain error. A DSNB record has been encountered that does not satisfy this requirement.

Action:

Update the field BID in the designated DSNB record to X'FF' with TMSUDSNB.

ERR49 USED DSNB xxxxxx DOES NOT CONTAIN A RECORD IDENTIFIER -BID NOT EQUAL

Reason:

Action:

Update the field BID in the designated DSNB record to X'FF' with TMSUDSNB.

ERR50 UNUSED DSNB xxxxxx POINTS TO DSNB xxxxxx, BUT DSNB xxxxxx IS GREATER THAN NUMBER ALLOCATED

Reason:

Action:

Update the NEXT field to HEXZEROS with TMSUDSNB or the CA 1 online facilities.

ERR51 TMSCTL#2 POINTS TO A DSNB THAT IS GREATER THAN NUMBER OF DSNBSGENERATED

Reason:

This is a Control Record #2/DSNB free chain error. TMSCTL#2 should always reference an unused DSNB in the NXAVAIL field. This error results in a CA 1 abend (S4yy) when attempting to create new secondary data sets.

Action:

In this instance, TMSCTL#2 references a DSNB that exceeds the maximum value for DSNBs allocated. Use TMSUDSNB to attach a valid free chain of DSNBs to the NXAVAIL pointer in Control Record #2.

ERR55 DSNB xxxxxx HAS AN INCORRECT CURDSNB FIELD

Reason:

This is a multi-data set chaining error. The CURDSNB field is not set properly.

Action:

Update the invalid DSNB with the correct DSNB number.

ERR56 DSNB xxxxxx DOES NOT HAVE THE AUFLAG1 LEFT/RIGHT SET CORRECTLY

Reason:

This is a multi-data set chaining error. The AUFLAG1 flag byte is not set correctly.

Action:

Update the invalid DSNB with the correct setting.

ERR57 DSNB xxxxxx HAS AN INCORRECT PREV FIELD

Reason:

This is a multi-data set chaining error. The DSNB record indicated reflects a PREV field that is not part of the DSNB chain.

Action:

Update the DSNB with the correct information for PREV.

ERR58 VOLUME xxxxxx POINTS TO DSNB xxxxxxx BUT LDSNB IN VOLUMERECORD IS ZERO

Reason:

This is a multi-data set chaining error. A volume record is referencing a DSNB in the 1STDSNB field but the LSTDSNB value is zero.

Action:

Determine the actual status of the files on the volume and update the erroneous field with the correct value.

ERR59 VOLUME xxxxxx POINTS TO LDSNB xxxxxxx, BUT LDSNB xxxxxxx ISGREATER THAN THE NUMBER

Reason:

This is a multi-data set chaining error. A volume record contains a LSTDSNB value greater than the total number of DSNBs allocated in the TMC.

Action:

Determine the actual DSNB number (or zero if there are no secondary data sets associated with the volume) and update the volume record with the correct LSTDSNB value.

ERR60 VOLUME xxxxxx HAS LDSNB xxxxxxx WHICH IS UNUSED

Reason:

This is a multi-data set chaining error. Unused DSNBs should never be logically associated with a volume record.

Action:

If the LSTDSNB field reflects a valid used DSNB, update the volume record accordingly. If not, update the LSTDSNB field to zeros.

ERR61 VOLUME xxxxxx HAS LDSNB xxxxxxx, BUT DSNB xxxxxxx POINTSTO VOLUME yyyyyy

Reason:

This is a multi-data set chaining error. A volume record is referencing a LSTDSNB in which the VOLSER field does not correctly reference the volume.

Action:

Determine which record is in error and update appropriately.

ERR62 VOLUME xxxxxx HAS LDSNB xxxxxxx, BUT 1STDSNB IS ZERO

Reason:

This is a multi-data set chaining error. A volume record is referencing a LSTDSNB record but the 1STDSNB value has no valid value.

Action:

Determine which DSNB the volume record should be referencing in 1STDSNB and update appropriately. If there is no DSNB to be associated, clear the LSTDSNB field.

ERR63 DSNB xxxxxxx HAS VOLSER xxxxxx WHICH IS INVALID

Reason:

This is a multi-data set chaining error. A DSNB is referencing a VOLSER value for a volume record not formatted in the TMC.

Action:

Determine the correct VOLSER value and update the invalid field.

ERR64: DSNB xxxxxxx HAS F1STVSN xxxxxx WHICH IS INVALID

Reason:

This is a multi-data set chaining error. A DSNB is referencing a F1STVSN value for a volume record not formatted in the TMC.

Action:

Determine the correct value and update the invalid field.

ERR65 VOLUME xxxxxx HAS NO DSNB CHAIN, BUT NUMDSNB IS xxxxxx

Reason:

This is a multi-data set chaining error. A volume has a NUMDSNB value greater than zero, but no 1STDSNB pointer.

Action:

Determine which DSNB the volume record should be referenced in 1STDSNB and update accordingly. If there is no DSNB to be associated, clear the NUMDSNB field.

ERR66 VOLUME xxxxxx POINTS TO 1STDSNB xxxxxxxx, BUT NUMDSNB IS ZERO

Reason:

This is a multi-data set chaining error. A volume is referencing a DSNB in the 1STDSNB field, but the NUMDSNB value is zero.

Action:

Determine the correct NUMDSNB value and update the field accordingly. If the DSNB chain is invalid, clear the 1STDSNB pointer.

ERR67 DSNB xxxxxx DOES NOT CONTAIN A VALID RECORD IDENTIFIER -BID NOT EQUAL FF

Reason:

All DSNB records must contain X'FF' in the record identifier field, BID. A DSNB record has been encountered that does not satisfy this requirement.

Action:

Update the field BID in the designated DSNB record to X'FF' with TMSUDSNB