TMSOSCAT Messages

********* NO CATALOG ENTRY FOUND *********
ca1tms
********* NO CATALOG ENTRY FOUND *********
Reason:
For the data set name, volume serial, volume sequence, and file sequence indicated in the message. No corresponding data were found in the catalog.
Action:
Research the cause of the mismatch and correct the TMC or catalog.
********* NO TMC ENTRY FOUND *********
Reason:
For the data set name, volume serial, volume sequence, and file sequence indicated in the message. No corresponding data were found in the
CA 1
TMC.
Action:
Research the cause of the mismatch and correct the catalog or TMC.
DSN FOUND ON CATALOG=data.set.name
Reason:
TMSOSCAT was run with a parm of RESYNC. All active files on volumes (that are not in scratch or deleted status) in the TMC are checked with the operating system catalogs to see if they are currently cataloged. If the catalog indicators in the TMC record match the status in the OS Catalog (both say that the file is
not
currently cataloged or both say that the file
is
currently cataloged), then no information is printed in the report and no updates are performed.
If the DSN being checked ("data.set.name" in the message) is found in the OS Catalog and the TMC catalog indicators are not currently on, the following catalog indicators are set on:
  • Volume record:
    TMISCAT - FLAG4 X'08' (OSC bit) FILE ON OS CATALOG TMCATLOG - FLAG2 X'80' (CAT bit) DATA SET WAS ON MVS CATALOG
  • DSNB record:
    DSNBISCA - FLAG1 X'08' (OSC bit) FILE IS ON OS CATALOG DSNBWSCA - FLAG1 X'02' (CAT bit) DATA SET WAS ON MVS CATALOG
The following catalog counter fields are set to 1:
TMCATCNT - CATALOG COUNT (CTLGCNT field) DSNBCCNT - CATALOG COUNT (CTLGCNT field)
Action:
This message documents the actions
CA 1
has taken to update the TMC to reflect the correct status of cataloged tape data sets. This message could also indicate that some systems sharing the TMC are not also sharing the MVS Catalogs properly.
DSN -NOT- ON CATALOG=data.set.name
Reason:
TMSOSCAT was run with a parm of RESYNC. All active files on volumes (that are not in scratch or deleted status) in the TMC, are checked with the operating system catalogs to see if they are currently cataloged. If the catalog indicators in the TMC record match the status in the OS Catalog (both say that the file is
not
currently cataloged or both say that the file
is
currently cataloged), then no information is printed in the report and no updates are performed.
If the DSN being checked ("data.set.name" in the message) is not found in the OSCatalog and the TMC catalog indicators are on the following catalog indicators are set off:
  • Volume record:
    TMISCAT - FLAG4 X'08' (OSC bit) FILE ON OS CATALOG
  • DSNB record:
    DSNBISCA - FLAG1 X'08' (OSC bit) FILE IS ON OS CATALOG
The following catalog counter fields are set to 0:
TMCATCNT - CATALOG COUNT (CTLGCNT field) DSNBCCNT - CATALOG COUNT (CTLGCNT field)
Action:
This message documents the actions
CA 1
has taken to update the TMC to reflect the correct status of cataloged tape data sets. This message could also indicate that some systems sharing the TMC are not also sharing the MVS Catalogs properly.
DSNB xxxxxx HAS 1ST VOLUME OF yyyyyy WHICHIS INVALID AND POINTS TO DSNB zzzzzz, AND DOES NOT HAVE SAME 1ST VOLUME OF yyyyyy.
Reason:
DSNB xxxxxx has an invalid first volume pointer (does not contain the first VOLSER).
Action:
Execute TMSPTRS and correct the invalid chain using TMSUDSNB or
CA 1
online facilities.
ERROR01 - NO SYSCATIN AND/OR IDCAMS DD FOUND
Reason:
Either a SYSCATIN DD statement or an IDCAMS DD statement is required.
Action:
Provide an IDCAMS or SYSCATIN DD statement for the appropriate catalog listing data set.
ERROR02 - NO KEYWORD FOUND
Reason:
An entire SYSIN control was scanned and no keywords were detected.
Action:
Provide valid SYSIN control keywords or delete the record.
ERROR03 - INVALID KEYWORD FOUND
Reason:
An invalid keyword was detected.
Action:
Correct the control statement(s) and resubmit the job.
ERROR04 - 'VALID' - INVALID DATA
Reason:
The VALID= keyword specified contains invalid data.
Action:
Correct the control statement(s) and resubmit the job.
ERROR05 - 'LOCATE' - INVALID DATA
Reason:
The LOCATE= keyword specified contains invalid data.
Action:
Correct the control statement(s) and resubmit the job.
ERROR06 - 'EXPCATLG' - INVALID DATA
Reason:
The EXPCATLG= keyword specified contains invalid data.
Action:
Correct the control statement(s) and resubmit the job.
ERROR07 - 'CDATE' - INVALID SUB-KEYWORD
Reason:
The CDATE= keyword specified an invalid subkeyword. DAYS= and DATE= are the only valid subkeywords.
Action:
Correct the control statement(s) and resubmit the job.
ERROR08 - 'CDATE=DATE' - INVALID DATA
Reason:
An invalid value for DATE has been specified. Delimiters are required if the date contains blanks or commas. The date must be compatible with the TMMDATE macro discussed in the
Programming.
Action:
Correct the control statement(s) and resubmit the job.
ERROR09 - CDATE=DAYS - INVALID DATA
Reason:
An invalid value for DAYS has been specified. This value must be numeric and greater than zero.
Action:
Correct the control statement(s) and resubmit the job.
ERROR10 - 'SCRTCH' INVALID DATA
Reason:
An invalid value for the SCRTCH= keyword was specified. The only valid values are YES and NO.
Action:
Correct the control statement(s) and resubmit the job.
ERROR11 - 'LIST' - INVALID DATA
Reason:
An invalid value was supplied for the LIST= keyword. Valid values are TOTALS and ERRORS.
Action:
Correct the control statement(s) and resubmit the job.
ERROR12 - MUTUALLY EXCLUSIVE OPTIONS
Reason:
The VALID and SCRTCH options are mutually exclusive, as are the EXPCATLG and SCRTCH options.
Action:
Correct the control statements and resubmit the job.
ERROR13 - BAD RETURN FROM SORT
Reason:
A nonzero return code was returned by SORT. This return code is stored in Register 15.
Action:
For information on the error and corrective action, see your SORT program documentation.
ERROR14 - 'NODE' - INVALID DATA
Reason:
Invalid data was supplied for the NODE= keyword. Each node is specified using from one to eight characters, which is consistent with MVS data set naming conventions.
Action:
Correct the control statement(s) and resubmit the job.
ERROR15 - 'EDM' - INVALID DATA
Reason:
Invalid data was specified for the EDM= keyword. This value can be only YES or NO.
Action:
Correct the control statement(s) and resubmit the job.
FILE SEQ IS LESS THAN PREVIOUS DSNB
Reason:
The file sequence number for the DSNB just retrieved is less than the file sequence for the last DSNB retrieved in the current chain.
Action:
Execute TMSPTRS and correct the invalid chain using TMSUDSNB or
CA 1
online facilities.
VOLSEQ IS NOT GREATER THAN PREVIOUS VOLUME
Reason:
The volume sequence number of the volume just retrieved is not higher than the volume sequence of the previously retrieved volume of the chain.
Action:
Execute TMSPTRS and correct the invalid chain using TMSUPDTE or
CA 1
online facilities.
VOLUME IS NOT IN DEFINED TMC RANGES
Reason:
The indicated volume was not found in the
CA 1
TMC because it is outside the TMC volume range table.
Action:
This indicates a severe error in the TMC. Contact Technical Support at http://ca.com/support for assistance.
VOLUME xxxxxx HAS NEXTVOL OF yyyyyy WHICH IS INVALID
Reason:
The next volume pointer for the volume indicated points to a volume that does not exist in the TMC.
Action:
Execute TMSPTRS and correct the invalid chain using TMSUPDTE or
CA 1
online facilities.
VOLUME xxxxxx, NUMDSNB=yyyyyy BUT 1ST DSNB = 0000
Reason:
Volume xxxxxx indicates that there should be a DSNB chain but the first DSNB pointer contains zeros.
Action:
Execute TMSPTRS and correct the invalid chain using TMSUDSNB or
CA 1
online facilities.
xx,xxx,xxx RECORDS WERE UPDATED RECORDS WOULD HAVE BEEN UPDATED
Reason:
PARM=SYNC was specified and this message reflects the number of records that were updated (or would have been updated if test was included).
Action:
No action is required. This is an informational message.