CA EARL abending with U3000 and receiving errors +TMSEARL14 - *** INVALID DSNB CHAIN *** and +TMSEARL15 - VOLUME/FILSEQ ---> ....

Products

• CA 1 Flexible Storage

Issue/Introduction

When running an EARL job to create reports using the TMETPUSE EARL source, the follow types of errors were generated: 

EARL     ABENDED U3000 IN PROGRAM UNKWN1   AT OFFSET +008CE6.

And multiple errors such as the following were also appearing in the output: 

11:49:48  +TMSEARL14 - *** INVALID DSNB CHAIN ***
11:49:48  +TMSEARL15 - VOLUME/FILSEQ --->NCL691-00068 NOT ONE GREATER
11:49:48  +            THAN PREVIOUS --->NBO701-00001

Etc.  etc.

The TMSPTRS job was run, but no errors were found.  

Environment

Release : 14.0

Cause

The EARL job was NOT using the current/active TMC to report against.

Resolution

The U3000 EARL abend was caused by having the batch job running for the TMETPUSE EARL report using a backup copy of the TMC instead of the ACTIVE TMC.  The TMETPUSE EARL uses TYPRUN=R_CHAINED which requires that the TAPEDB parameter reference the active TMC.  The current/active TMC in use can be determined by issuing the command TMS STATUS. 

Additional Information

Additional information can be found here (see the info found under the description for CHAINED).