DFHFC4700 applid {An unexpected | A VSAM | A length | A lock | A timeout | An unexpected delete} error has occurred during file backout. (Module DFHFCFR has returned reason code (X'xx'), access method code (X'cccccccc') and length error code (X'yy').)

Explanation

File backout has called module DFHFCFR as part of its processing, and an error has been returned which should not be possible during backout. The message text includes the type of error that has occurred.

Additional diagnostic information is provided by: the reason code xx returned from DFHFCFR, the code cccccccc which was returned to DFHFCFR from the access method that it called, and the length error code yy.

The length error code is normally either X'00', indicating that length errors are not applicable to the type of request which was in error, or X'01', indicating that there was no length error. A value greater than X'01' occurs when the message text indicates that the type of error is a length error.

System action

An exception trace point is written, and a system dump is taken.

The error is processed as a backout failure. Unless a user exit program enabled at the XFCBFAIL exit point bypasses backout failure processing, message DFHFC4701 or DFHFC4702 follows and gives details of the file and data set involved.

CICS continues. Message DFHME0116, which contains the symptom string for this problem, is produced.

User response

Inform the system programmer. This indicates a possible error in CICS, VSAM or BDAM code. The severity of its impact depends on whether the backout can be successfully retried.

If the data set being backed out is a VSAM data set, you can retry the backout. Message DFHFC4701 names the data set, and the failed backout can be retried using SET DSNAME RETRY. If the problem is due to some transient condition which has since cleared, the backout will now succeed.

If the data set being backed out is a BDAM data set, the backout cannot be retried. The data is committed and the locks are released, unless an exit program enabled at the XFCBFAIL exit point terminates CICS, in which case data integrity can be preserved by performing an emergency restart.

If the backout cannot be successfully retried, then take action depending on the type of error indicated in the message text:

  • An unexpected error

    This probably indicates either a corruption of storage or an error within CICS code. It might also indicate an error within the access method called to process the request (VSAM or BDAM).

    The reason code xx is the reason code from the DFHFCFR parameter list and has been included as additional documentation in case you need further help from IBM.

    The access method code cccccccc is information returned to file control in the VSAM RPL if the error was detected by VSAM, or the BDAM DECB if the error was detected by BDAM. For VSAM, the first byte is the VSAM return code and the second byte is the VSAM reason code; the third and fourth bytes may contain additional VSAM diagnostics (for more information, see z/OS DFSMS Macro Instructions for Data Sets). For BDAM, the access method code is the 4-byte exception codes field from the DECB (for more information, see z/OS DFSMS Using Data Sets).

  • A VSAM error

    This indicates that an error has occurred within VSAM.

    The access method code cccccccc is information returned to file control in the VSAM RPL. The first byte is the VSAM return code and the second byte is the VSAM reason code; the third and fourth bytes may contain additional VSAM diagnostics (for more information, see z/OS DFSMS Macro Instructions for Data Sets).

  • A length error

    When a length error is reported, the length error code yy will be greater than X'01'. This normally indicates a serious error in CICS, VSAM, or BDAM processing. If it occurs for a BDAM data set, check the FCT and DCB definitions in case there is a mismatch between, for example, the blocksizes, which would result in a length error.

  • A lock error

    This indicates that backout processing has encountered a LOCKED response on attempting to acquire a lock on a record which is held as a retained lock by another unit of work. This should not be possible because the record should be locked by the unit of work being backed out. If this error occurs for a file being accessed in RLS mode, then it probably indicates an error in the SMSVSAM server. If this error occurs for a file being accessed in non-RLS mode, then it probably indicates an error in CICS enqueue processing.

  • A timeout error

    This indicates that backout processing has timed out attempting to acquire an RLS lock. This should not be possible during backout because the record should already be locked by the unit of work being backed out. If this error occurs then it probably indicates an error in the SMSVSAM server.

  • An unexpected delete error

    This indicates that the request to be backed out was a delete request, but that the file type is one for which deletes are not supported (VSAM ESDS or BDAM). The most likely cause of this error would be some corruption of the data set, although it might also indicate an error within CICS, or a storage corruption.

You may need assistance from IBM to resolve this problem. See IBM problem support for guidance on how to proceed.

Module

DFHFCRC

XMEOUT parameters/Message inserts

  1. applid
  2. Value chosen from the following options:
  3. X'xx'
  4. X'cccccccc'
  5. X'yy'

Destination

Console