Conversion Utilities › Preconversion Data Validation Utility - CAL2DCVP › Database Field Validation Messages

Database Field Validation Messages

The following messages are issued for database field validation:

001 Validation failed for DDNAME: xxxxxxxx DSECT/Field: dddddddd.ffffffff

xxxxxxxx

Specifies UCC7JLIB, UCC7VRM, UCC7ARF, or UCC7DMPQ and indicates the file from which the record was read.

dddddddd.ffffffff

Identifies the internal r11.3 identifier for the field that did not pass the validation.

Sometimes, simply updating the element that is identified in the first part of the dumped record corrects this type of issue.

002 Invalid SCBDATE detected in IDS for DSN: dddddddddddddddddddd

dddddddddddddddddddd

Identifies the data set name in the IDS entry that has one or more invalid creation dates.

Note: This message is also issued for networks.

You can issue an LCTLG command to display the invalid entry and provide more information about any entries to delete.

To update the SCBDATE field, use the CTLG command with TYPE=REPL for the DSN.

Note: For more information about CTLG and LCTLG, see the Command Reference Guide.

Contact CA Support for assistance.

003 Schedule Member has invalid ISE SSTYPE

A schedule member whose type and number are identified in the dumped record has an invalid ISE schedule class.

Contact CA Support for assistance.

010 Schedule Member has invalid workstation due out time

A schedule member whose type and number are identified in the dumped record has an invalid ISE schedule class.

Update the workstation schedule due out time on the DB.2.3-E panel.

013 Job jjjjjjjj includes requirement and/or DDE references to undefined DSNBR nnnnnnnn

jjjjjjjj

Identifies the job that references an undefined data set number.

nnnnnnnn

Identifies the undefined DSNBR that is referenced.

You can correct this type of issue by removing the references to the identified DSNBR from the job. This correction includes updating job DSN requirements, reloading the job’s JCL, or both.

015 Job xxxxxxxx has duplicate requirements for DSNBR xxxxxxxx and SCHID yyyyyyyy

Job xxxxxxxx has multiple requirements for the same DSNBR and SCHID. Use the DB.3.1 panel to remove the duplicate requirement.

016 Job# nnnn has multiple unsatisfied requirements for JOB|USR yyyyyy

nnnn

Identifies the CA 7 job number that references an unsatisfied requirement.

yyyyyy

Identifies the CA 7 JOB or USR requirement that is a duplicate.

You can correct this issue by posting all but one of the duplicate requirements using the XQ command.

999 xxxxxx will be changed to yyyyyyyy for zzzzzzzz

A date/time field is automatically corrected during the conversion process.

xxxxxxxx

Identifies the type of field (such as last maintenance date) that is changing.

yyyyyyyy

Identifies the value that is assigned to the field.

zzzzzzzz

Identifies the object (such as a job name or a data set name) of the object that is corrected during the conversion.