DWW260I

INVALID REDO LOG RECORD TYPE SPECIFIED FOR cccc LOGGING. SPHERE NAME: VSAM_sphere_name RETURN CODE (IN HEX): rc REASON CODE (IN HEX): rsnc

Explanation

The CICS VR VSAM batch logger has detected an incorrect record type in the VSAM request.

In the message text:
cccc
logging type(REDO or UNDO).
VSAM_sphere_name
The name of the VSAM sphere that encountered the rror..
rc
The reason code.
rsnc
The reason code.
RETURN CODE 36
Reason Code Description
X'717053D3' Explanation: Unexpected logging request detected during VSAM REDO logging REDO logging might have been requested due to a VSAM get request, which is not allowed.

Programmer Response: Check the RPL request and the FRLOG value in the catalog entry for the VSAM sphere listed in the message text.

X'717053D8' Explanation: Unexpected logging request detected during VSAM UNDO logging. UNDO logging might have been requested due to a VSAM ERASE request, which is not allowed.

Programmer Response: Check the RPL request and the FRLOG value in the catalog entry for the VSAM sphere listed in the message text.

X'717053EI' Explanation: Unexpected logging request detected during VSAM UNDO logging. UNDO logging might have been requested due to VSAM PUT UPDATE request, which is not allowed.

Programmer Response: Check the RPL request and the FRLOG value in the catalog entry for the VSAM sphere listed in the message text.

X'717053E2' Explanation: Unexpected logging request detected during VSAM REDO logging. REDO logging might have been requested due to a VSAM GET UPDATE request, which is not allowed.

Programmer Response: Check the RPL request and the FRLOG value in the catalog entry for the VSAM sphere listed in the message text.

X'717053E0' Explanation: Unexpected error occurred during VSAM batch logging.

Programmer Response: Check the RPL request and the FRLOG value in the catalog entry for the VSAM sphere listed in the message text.

Source: DHSMS (IDA019BL or IDABLVBB)

System action

CICS VR VSAM batch logging terminates. The system continues processing.

Operator response

Contact your IBM Support Center.