B.3 LDXU Messages

Following are explanations, possible causes and actions for LDXU messages.

LDXU000I Log File Utility started on mm/dd/yyyy at hh:mm:ss.

Explanation: The Log File utility has initialized.

Message Destination: SYSPRINT.

Action: Informational only. No action is required.

LDXU001W Message log disabled, SYSPRINT DD missing.

Explanation: During initialization, the Log File utility was unable to open the SYSPRINT DD statement. The Log File utility continues processing, but no messages are written to SYSPRINT.

Message Destination: WTO.

Possible Cause: The SYSPRINT DD statement is missing from the JCL for the Log File utility.
Action: Ensure that a SYSPRINT DD statement is present in the JCL and that it defines a file that the Log File utility can write to.

LDXU002I Execute statement parameters: parm-values

Explanation: During initialization, the Log File utility found the listed parameters present on the EXEC statement PARM parameter.

Message Destination: SYSPRINT.

Action: Informational only. No action is required.

LDXU003E Open failed for log file.

Explanation: The Log File utility could not open the Change Log data set.

Message Destination: SYSPRINT.

Possible Cause: The LOGFILE DD statement is missing from the JCL for the Log File utility.
Action: Ensure that a LOGFILE DD statement is present in the JCL and that it defines a data set that the Log File utility can write to.

LDXU004I Log file blocksize: blksize

Explanation: The Log File utility is initializing the Change Log data set with a blocksize of blksize

Message Destination: SYSPRINT.

Action: Informational only. No action is required.

LDXU005I Log file blocks written: block-count

Explanation: While initializing the Change Log data set, the Log File utility has written block-count blocks of empty records.

Message Destination: SYSPRINT.

Action: Informational only. No action is required.

LDXU006E Open failed for LOADIN file.

Explanation: The Log File utility Load function could not open the LOADIN ddname.

Message Destination: SYSPRINT.

Possible Cause: The LOADIN DD statement is missing from the JCL for the Log File utility.
Action: Ensure that a LOADIN DD statement is present in the JCL and that it defines a file that the Log File utility can read.

LDXU007E Unrecognized or missing execute statement parameter.

Explanation: The Log File utility found an unknown parameter in the EXEC statement PARM parameter.

Processing ends.

Message Destination: SYSPRINT.

Possible Cause: The EXEC statement PARM value is missing or does not contain one of the following functions:

  • INITIALIZE

  • DUMP

  • LOAD

Action: Correct the PARM value and resubmit the job.

LDXU008I Log file events loaded: event-count

Explanation: The Log File utility Load function has successfully loaded event-count events into the Change Log data set from the input file.

Message Destination: SYSPRINT.

Action: Informational only. No action is required.

LDXU009E Add event failed, error code code

Explanation: The Log File utility Load function was unable to add an event record to the Change Log data set. The LDXLADD LDXIOERR code was code.

Message Destination: SYSPRINT.

Possible Cause: Internal system error.
Action: Contact software support. Be ready to provide the job log and SYSPRINT data set with the exact contents of the message received.

LDXU010E Read header failed, error code code

Explanation: The Log File utility Dump function was unable to read the header record of the Change Log data set. The LDXLGETE LDXIOERR code was code.

Message Destination: SYSPRINT.

Possible Cause: Internal system error.
Action: Contact software support. Be ready to provide the job log and SYSPRINT data set with the exact contents of the message received.

LDXU011E Read event failed, error code code

Explanation: The Log File utility Dump function was unable to read an event record from the Change Log data set. The LDXLGETE LDXIOERR code was code.

Message Destination: SYSPRINT.

Possible Cause: Internal system error.
Action: Contact software support. Be ready to provide the job log and SYSPRINT data set with the exact contents of the message received.

LDXU990I Open BDAM log succeeded.

Explanation: The Log File utility has initialized the Change Log data set with empty records and has successfully opened it to complete the initialization by updating the header information.

Message Destination: SYSPRINT.

Action: Informational only. No action is required.

LDXU991E Open BDAM log failed.

Explanation: The Log File utility has initialized the Change Log data set with empty records, but could not reopen it to complete the initialization by updating the header information.

Message Destination: SYSPRINT.

Possible Cause: Internal system error.
Action: Contact software support. Be ready to provide job logs and the console log with the exact contents of the messages received.

LDXU999I Log File Utility ended on mm/dd/yyyy at hh:mm:ss

Explanation: The Log File utility has completed processing.

Message Destination: SYSPRINT.

Action: Informational only. No action is required.