TMCC Program

Products

• MICS Resource Management

Issue/Introduction

Does your TMCC program interact with the catalog or some other source? 
We are processing an old backup of the TMC and are seeing many of these error messages in the JESMSGLG;

+TMSEARL03 - INITIALIZING FOR CHAINED PROCESSING
+TMSEARL14 - *** INVALID DSNB CHAIN ***
+TMSEARL15 - VOLUME/FILSEQ --->PC8739-00010 NOT ONE GREATER
+            THAN PREVIOUS --->1A0036-00001
+TMSEARL14 - *** INVALID DSNB CHAIN ***
+TMSEARL15 - VOLUME/FILSEQ --->8I0530-00118 NOT ONE GREATER
+            THAN PREVIOUS --->1A0086-00001
+TMSEARL14 - *** INVALID DSNB CHAIN ***
+TMSEARL15 - VOLUME/FILSEQ --->1X5348-00062 NOT ONE GREATER
+            THAN PREVIOUS --->1A0108-00001
+TMSEARL14 - *** INVALID DSNB CHAIN ***
+TMSEARL15 - VOLUME/FILSEQ --->M32721-00013 NOT ONE GREATER
+            THAN PREVIOUS --->1A0125-00001

Environment

Release : 14.2

Component : CA MICS

Cause

We're trying to extract an input file from a TMC Backup that has been restored to DASD and are seeing many TMSEARLxx messages…

Resolution

The TMCC program calls a program from CA-1, TMSEARL, to process the tape catalog.
That is the program that's producing these messages.

TMSEARL14 - *** INVALID DSNB CHAIN ***

Reason:

A volume chaining error on the TMC has been detected. This message is followed by messages TMSEARL15 and TMSEARL08.

Action:

Examine accompanying messages for more detailed information, correct, and resubmit the job.

TMSEARL15 - VOLUME/FILSEQ --->vvvvvv-sss NOT ONE GREATERTHAN PREVIOUS --->vvvvvv-sss

Reason:

A DSNB chaining error on the TMC has been detected. The volume serial numbers and file sequence numbers are shown for analysis.

Action:

The TMC chaining pointers must be corrected. Run the CA 1 utility TMSBINQ to do an inquiry of the volume(s) shown. You should also run TMSPTRS to report on chaining errors. Correct and resubmit the job

Additional Information

The messages can be found in the CA-1 documentation.