Following are explanations, possible causes and actions for LDXL messages.
LDXL000 LOGGING STARTED AT hh:mm:ss ON mm/dd/yyyy
Explanation:
The Change Log Started Task has initialized.
Message Destination: WTO.
Action:
Informational only. No action is required.
LDXL001 MESSAGE LOG DISABLED, SYSPRINT DD MISSING
Explanation:
During initialization, the Change Log Started Task was unable to open the SYSPRINT DD statement.
The Change Log Started Task 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 Change Log Started Task.
Action:
Ensure that a SYSPRINT DD statement is present in the JCL and that it defines a file that the Change Log Started Task can write to.
LDXL002 EXECUTE STATEMENT PARAMETERS: parm-values
Explanation:
During initialization, the Change Log Started Task found the listed parameters present on the EXEC statement PARM parameter.
Message Destination: SYSPRINT.
Action:
Informational only. No action is required.
LDXL003 START COMMAND PARAMETERS: parameters
Explanation:
During initialization, the Change Log Started Task found the listed parameters present on the START command.
Message Destination: SYSPRINT.
Action:
Informational only. No action is required.
LDXL004 STOP COMMAND RECEIVED.
Explanation:
An operator entered a STOP command for the Change Log Started Task. The Change Log Started Task ends.
Message Destination: SYSPRINT.
Action:
Informational only. No action is required.
LDXL005 MODIFY COMMAND PARAMETERS: parameters
Explanation:
An operator entered a MODIFY command for the Change Log Started Task with the listed parameters.
Message Destination: SYSPRINT.
Action:
Informational only. No action is required.
LDXL006 UNRECOGNIZED CIBVERB TYPE: X’hh’, COMMAND IGNORED
Explanation:
During processing, the Change Log Started Task received a command input buffer (CIB) with a verb other than STOP or MODIFY. Processing continues.
Message Destination: SYSPRINT.
Possible Cause:
Internal system error.
Action:
Contact software support. Be ready to provide the console log and the SYSPRINT data set with the exact contents of the message received.
LDXL007 OPERATOR CANCEL DETECTED, ATTEMPTING NORMAL SHUTDOWN
Explanation:
An operator has issued a CANCEL command without the DUMP parameter for the Change Log Started Task. The Change Log Started Task attempts a clean shutdown.
Message Destination: SYSPRINT.
Action:
Wait for the Change Log Started Task to end. If the Change Log Started Task does not end within a reasonable amount of time, issue another CANCEL command, specifying the DUMP parameter. If the cause of the failure to end normally is not evident, contact software support. Be ready to provide the contents of the system dump, job and console logs, and SYSPRINT data set.
NOTE:Use the STOP command for normal shutdown of the Change Log Started Task.
LDXL008 EVENT TRACING ENABLED.
Explanation:
An operator has issued a MODIFY command for TRACE ON to the Change Log Started Task.
Event tracing is turned on.
Message Destination: SYSPRINT.
Action:
Informational only. No action is required.
LDXL009 EVENT TRACING DISABLED.
Explanation:
An operator has issued a MODIFY command for TRACE OFF to the Change Log Started Task.
Event tracing is turned off.
Message Destination: SYSPRINT.
Action:
Informational only. No action is required.
LDXL010 MODIFY COMMAND IGNORED, INVALID OR MISSING PARAMETERS.
Explanation:
An operator has issued a MODIFY command to the Change Log Started Task, but the command parameters are not recognized.
The MODIFY command is ignored.
Message Destination: SYSPRINT.
Action:
Reissue the MODIFY command with the intended parameters.
LDXL011 EVENT RC( rc) DATA: event_data
Explanation:
Event tracing is turned on and an event has been processed.
The return code from ProcessEvent is rc. The content of the event record is event_data.
Processing continues.
Message Destination: SYSPRINT.
Action:
Informational only. No action is required.
LDXL012 TERMINATING BECAUSE LOGGING ALREADY ACTIVE.
Explanation:
Upon startup, the Change Log Started Task has detected that another Change Log Started Task is already running.
This instance of the Change Log Started Task terminates.
To detect this condition, the Change Log Started Task enqueues exclusively on qname “ldxlogr” rname “#LDXENVIRONTOKEN” when it initializes. If the enq macro fails, this message is issued. The Change Log Started Task dequeues this resource upon shutdown.
Message Destination: SYSPRINT.
Possible Cause:
A START command for the Change Log Started Task has been issued more than once.
Action:
Do not start more than one instance of the Change Log Started Task at a time.
LDXL013 LOGGING TO DATASET: dsname
Explanation:
The name of the Change Log data set in use is dsname.
Message Destination: SYSPRINT.
Action:
Informational only. No action is required.
LDXL999 LOGGING ENDED AT hh:mm:ss ON mm/dd/yyyy
Explanation:
The Change Log Started Task is ending.
Message Destination: SYSPRINT.
Possible Cause:
An operator entered a STOP command for the Change Log Started Task.
Action:
Informational only. No action is required.