Explanation: The cross memory queue access routine in a RACF exit found events in the cross memory queue that have been unprocessed for at least fifteen minutes. During normal operation, the Change Log Started Task processes events from the queue immediately.

Message Destination: WTO.

Possible Cause: The Change Log Started task is not running.

Action: Ensure that the Change Log Started Task is running.

Explanation: An unexpected return code was received from z/OS Name/Token Services by a RACF Event Subsystem component.

Message Destination: WTO.

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 message received.

Explanation: The LDXSERV command contained invalid operands, and LDXSERV was unable to prompt for correct information.

Message Destination: SYSTSPRT.

Action: Correct the syntax of the LDXSERV command and reissue it.

If the command was issued by the driver shim, contact software support. Be ready to provide driver logs and logs for the Telnet session showing the faulty command.

Explanation: An LDXSERV MARKDONE command was missing the required event token operand.

Message Destination: SYSTSPRT.

Possible Cause: Internal error in driver shim.

Action: If the command was issued by the driver shim, contact software support. Be ready to provide driver logs and logs for the Telnet session for the Telnet session showing the faulty command.

Explanation: An unexpected error occurred in the LDXSERV command. The message contains a description of the problem.

Message Destination: SYSTSPRT.

Possible Cause: Internal error.

Action: Contact software support. Be ready to provide driver logs and logs for the Telnet session.

Explanation: LDXSERV was unable to open the Change Log data set.

Message Destination: SYSTSPRT.

Possible Cause: The user ID running the LDXSERV command does not have access to the Change Log data set.

Action: Check the TSO session log and message files for additional messages concerning the failure.

If you are unable to determine and correct the cause of the error, contact software support. Be ready to provide driver logs and logs for the Telnet session.

Explanation: The LDXSERV command was unable to find the Change Log data set because there was no LOGFILE DD statement and there was no valid LDX environment. The LDX environment is created when either of the RACF exits is invoked for the first time after an IPL or when the Change Log Started Task first starts.

Message Destination: SYSTSPRT.

Action: Ensure that you are logged on to a system where the RACF Event Subsystem is installed and that the RACF exits have been properly installed and are active.

If you are unable to determine and correct the cause of the error, contact software support. Be ready to provide driver logs and logs for the Telnet session.

Explanation: The LDXSERV command was unable to find the Change Log data set because there was no LOGFILE DD statement and the Change Log Started Task was not active.

Message Destination: SYSTSPRT.

Action: If you are unable to determine and correct the cause of the error, contact software support. Be ready to provide driver logs and logs for the Telnet session.

Explanation: The LDXSERV command was unable to dynamically allocate the Change Log data set. The dynamic allocation return code and reason codes are given in the message by rc and err respectively.

Dynamic allocation return codes and reason codes are documented in the IBM publication MVS Programming: Authorized Assembler Services Guide.

Message Destination: SYSTSPRT.

Action: If you are unable to determine and correct the cause of the error, contact software support. Be ready to provide driver logs and logs for the Telnet session.