Messages CLHG00 through CLHGxx

This group includes messages for the Control-D, Control-D/Image, and Control-D/Page on Demand products.

CLHG85E INVALID INPUT PARAMETER NOSYS=.

Explanation: An invalid value was specified in the NOSYS parameter of the EXEC JCL statement activating the CTDCLHST utility, and was passed to the program. The only valid values are N, Y, or S.

The utility ends with a return code of 12.

Corrective Action: Correct the JCL, and rerun the job.

CLHG87I READING BACKUP CONTROL RECORDS.

Explanation: This information message indicates that the CTDCLHST utility started reading backup control records.

Corrective Action: No action is required.

CLHG88I READING SYSDATA RECORDS.

Explanation: This information message indicates that the CTDCLHST utility started reading SYSDATA records.

Corrective Action: No action is required.

CLHG89I number SYSDATA RECORDS READ.

Explanation: This information message indicates the number of SYSDATA records read by the CTDCLHST utility from the History User Report List file.

Corrective Action: No action is required.

CLHG8BI DELETION OF THE SELECTED RECORDS.

Explanation: This information message is issued by the CTDCLHST utility when it runs in PROD mode, and indicates that the utility started deleting selected records.

Corrective Action: No action is required.

CLHG8CI USER RECORD NOT FOUND FOR NOTEPAD RECORD userId jobName ODATE=odate RID=recordId

Explanation: The CTDCLHST utility discovered a notepad record in the History User Reports List file without a matching USER record.

The variables in this message are:

• userId
• jobName
• odate
• recordId

The notepad record is deleted.

Corrective Action: Investigate the cause of this occurrence. It should not happen in a proper Control-D operation.

CLHG8DI SYSDATA RECORD NOT FOUND FOR USER RECORD userId jobName ODATE=odate RID=recordId

Explanation: Unless NOSYS=N is requested in the CTDCLHST utility call, the utility scans all USER records in the History User Reports file and for each USER record, checks if there is a matching SYSDATA record. If a SYSDATA record is not found, this message is issued and the USER record is deleted.

The variables in this message are:

• userId
• jobName
• odate
• recordId

The USER record is deleted.

Corrective Action: Investigate the cause of this occurrence. It should not happen in a proper Control-D operation.

CLHG8EI SYSDATA RECORD NOT FOUND FOR INDEX RECORD jobName ODATE=odate RID=recordId

Explanation: Running with parameter NOSYS=Y or NOSYS=S, the CTDCLHST utility scans all INDEX records in the History User Report List file and for each INDEX record, checks if there is a matching SYSDATA record in the file. This message indicates that the utility did find an INDEX record with no matching SYSDATA record. Such “orphan” INDEX records may appear in the History User Report List file as the result of situation described in message CLH943W.

The variables in this message are:

• jobName
• odate
• recordId

The INDEX record and its related index file are deleted.

Corrective Action: Investigate the cause of this occurrence. It should not happen in a proper Control-D operation, except for the situation described in message CLH943W.

CLHG8FI USER RECORD NOT FOUND FOR SYSDATA RECORD jobName ID jobId ODATE=odate RID=recordId

Explanation: Running with parameter NOSYS=S, the CTDCLHST utility found an “orphan” SYSDATA record in the History User Report List file. This means that a SYSDATA record is not referred to by any USER record in the file.

The variables in this message are:

• jobName - the name of the job to which the orphaned SYSDATA record belongs
• jobId - the MVS identifier of the job to which the orphaned SYSDATA record belongs
• odate - originating date of the report to which the orphaned SYSDATA record belongs
• recordId - the unique key of the orphaned SYSDATA record

The orphaned SYSDATA record will be removed from the History User Report List file in the next utility execution.

Corrective Action: No action is required.