Previous Topic: DYNSYNC MessagesNext Topic: Health Check Messages


DYNUPDTE Messages

CA 1 DATE MODULE OPEN ERROR.

Reason:

CA 1 could not open the date processing routines.

Action:

Ensure that all CA 1 libraries are correctly specified in the link list or STEPLIB and resubmit the job.

ERR01: VOLUME NOT IN TMC

Reason:

This message indicates that the VOLSER in the transaction does not match a VOLSER in the TMC.

Action:

Verify that the CA 1 and CA Dynam/T databases contain the same volume serial numbers.

ERR02: CANNOT UPDATE CA 1 OWNED VOLUME

Reason:

A transaction was received from the CA Dynam/T database for a volume owned by CA 1. This indicates that the CA Dynam/T information about this volume is more accurate than the CA 1 information (determined by most recent creation date and time).

Action:

Determine the correct ownership and status for this volume and update the database(s) accordingly. The CA 1 batch update utility, TMSUPDTE, should be used to update the TMC.

ERR03: ATTEMPTING TO CHANGE OWNERSHIP

Reason:

The TMC indicates that CA Dynam/T owns the volume. CA Dynam/T indicates that the volume is owned by CA 1

Action:

Determine the correct ownership and status for this volume and update the database(s) accordingly. The CA 1 batch update utility TMSUPDTE should be used to update the TMC.

ERR06: VOLUME IN DELETE STATUS ON TMC

Reason:

The TMC indicates that the volume is inactive (DELETE status).CA Dynam/T shows the volume to be in ACTIVE or SCRATCH status.

Action:

Determine the correct ownership and status for this volume and update the database(s) accordingly. The CA 1 batch utility TMSDELET can be used to mark the record as active (if indicated), and the batch update utility TMSUPDTE should be used to update the TMC.

PARM ERROR.DATEFMT= VALUE MUST BE ENCLOSED WITHIN ()

Reason:

The DATEFMT= parameter value must be enclosed within parentheses.

Action:

For valid DATEFMT specifications. See Overriding the Preferred Date Pattern in the chapter "CA 1 Utilities and Reports" in the Utilities and Reports Reference Guide. Correct the JCL and resubmit the job.

PARM ERROR. INVALID DATEFMT.

Reason:

The DATEFMT= parameter value is invalid.

Action:

For valid DATEFMT specifications, see Overriding the Preferred Date Pattern in the chapter "CA 1 Utilities and Reports" in the Utilities and Reports Reference Guide. Correct the JCL and resubmit the job.

PARM ERROR. UNKNOWN KEYWORD.

Reason:

The only valid JCL parameters are DATEFMT= and TEST.

Action:

Correct the JCL and resubmit the job.

THE FIRST RECORD OF THE UPDATE EXTRACT FILE IS NOT ANIDENTIFICATION RECORD

Reason:

This critical message may appear when processing cannot be performed. The first record in the extract update file contains information about the extract file. This record is not present or is invalid.

Action:

Verify that the correct file is being used as input on the UPDATES DD statement.

THE UPDATES FILE IS NOT THE CA 1/MVS UPDATES FILE

Reason:

This critical message may appear when processing cannot be performed. The identification record in the UPDATES file does not contain the CA 1 NODEID.

Action:

Verify that the correct extract UPDATES file from DYNSYNC is being used.