DFHFC4701    date time applid Backout failed for transaction tranid, VSAM file filename, unit of work X'local_uowid', task task_number, base base_dsname, path path_dsname, failure code X'bfail_code'.

Explanation

File backout has been unable to backout an uncommitted change made to a VSAM data set via file filename, that was made by the unit of work local_uowid.

The file is associated with the data set path_dsname. This is either a base cluster data set if the path_dsname and base_dsname given in the message are the same, or is a path data set whose base cluster is the base_dsname given in the message if the two names differ.

The change that is being backed out was originally made by task task_number servicing transaction code tranid, running under the unit of work local_uowid The current task number will differ from the original one that is given in the message if this backout is itself a retry of an earlier backout which also failed, or is a backout being carried out following resolution of an indoubt situation, and the current transaction code will differ from the original one if the transaction has been disabled.

The failure code X'bfail_code' indicates the reason for the failure.

System action

The system continues normally.

Backing out of the unit of work continues, but no further attempts to backout updates made by this unit of work to the base_dsname named in the message are made.

When the unit of work has been backed out as far as is possible, those updates which could not be backed out are deferred (shunted) until the backout can be retried.

It is possible for other work to continue to access the base cluster data set, but the records in that data set that were changed by this unit of work are locked by retained locks. This ensures that any attempt to access these records results in a LOCKED response being returned to the application. The records must remain locked until the backout has been successfully retried in order to preserve data integrity.

If, when the backout is retried, it fails again for either the same or another reason, this message is issued again, with the failure code indicating the reason for the failure on this occasion.

User response

You may decide to leave the data set online for any of the errors indicated by X'bfail_code', especially if you believe that the backout failure may have been due to some transient situation, and that the backout may succeed if retried. You can manually drive retry of the backout using the SET DSNAME RETRY command, or alternatively wait until some event triggers retries of the shunted backouts in the system.

As a last resort, and at the cost of losing data integrity, you could bypass the deferred backout of uncommitted changes to this data set using the SET DSNAME RESETLOCKS command.

The user response depends on the value of the failure code X'bfail_code'.

10

The backout attempted to add a duplicate key value to a unique alternate index. The backout can never be carried out unless you can delete the existing record with this alternate key value, then retry the backout using SET DSNAME RETRY. This failure can only occur for a file being accessed in non-RLS mode.

20

The data set ran out of storage while the request was being processed. You should reallocate the data set with more space, then retry the backout using SET DSNAME RETRY. Do not forward recover the data set. If you accessed the file in RLS mode, there are extra steps required to ensure that the retained locks remain associated with the data set. These are explained in the Administering recovery and restart information.

24

An I/O error has occurred on the data set. You should consider the possibility that the data set needs restoring, especially if there have been a large number of these messages referring to the same base cluster data set, or if there have also been I/O errors issued during request processing for that data set.

If you do decide to restore the data set, you should take the following steps:

  1. Prevent access to the data set

  2. Restore a backup copy and forward recover the data set (for example, using CICSVR)

  3. Reallow access to the data set

  4. Retry deferred backouts.

For an RLS mode data set, prevent access by issuing a SET DSNAME QUIESCED command which closes all open files throughout the sysplex and prevents further RLS opens. Reallow access by issuing a SET DSNAME UNQUIESCED command, which also retries deferred backouts automatically.

For a non-RLS mode data set, prevent access by issuing a SET DSNAME UNAVAILABLE command to prevent further non-RLS opens and issue SET FILE CLOSED commands for all open files. Reallow access by issuing a SET DSNAME AVAILABLE command, and retry deferred backouts using SET DSNAME RETRY.

40

Logical delete for an ESDS data set was not performed because the XFCLDEL exit either chose not to carry out the logical delete, or was not enabled.

41

A DFSMSdss non-BWO backup is in progress for the data set. The backout will be automatically retried when the backup completes.

B0

A deadlock was detected. This can only happen for files opened in non-RLS mode. Since this is a transient condition, you should just retry the backout using SET DSNAME RETRY.

C0

A failure of the VSAM RLS server was detected by this request. The backout is automatically retried when the server becomes available again.

C1

VSAM RLS access is disabled because the server is unavailable. The backout is automatically retried when the server becomes available again.

C2

The VSAM RLS server has recycled (failed and restarted) whilst a record was being backed out. This is a very rare occurrence since the failure and restart must have taken place after the record to be backed out was read for update, and before it was rewritten or deleted. A retry of the backout should be successful, but because the server has already become available, backout will not be automatically retried. You should use SET DSNAME RETRY to drive backout retry.

C3

The VSAM RLS cache structure to which the data set was bound has either failed or has lost connectivity, and VSAM has been unable either to rebuild the failed cache structure, or to bind the data set to an alternative cache structure in the cache set. The backout is automatically retried when the cache structure becomes available again.

C4

VSAM has returned a response indicating that the RLS lock structure in the coupling facility is full. Allocate a larger lock structure, rebuild into it and retry the backout using set dsname retry. See , (GC28-1779) and z/OS DFSMSdfp Storage Administration, (SC26-4920) for further information on how to allocate, and build into, larger lock structures.

F0

There was no space to add another alternate key value to a non-unique alternate index. You should rebuild the data set with a larger alternate index data CI size (unless you are already at the maximum), and then retry the backout using SET DSNAME RETRY. If you accessed the file in RLS mode, there are extra steps required to ensure that the retained locks remain associated with the data set. These are explained in the Administering recovery and restart information. Do not forward recover the data set.

FB

An error occurred when opening the file for backout. Determine why the file would not open, and if it is possible to correct it, do so and then issue SET DSNAME RETRY to retry the backout. If the error occurred because the data set was quiesced, the backout is automatically retried when the data set is unquiesced. If the error occurred because the VSAM RLS server was not available, the backout is automatically retried when it becomes available again.

FE

An error occurred which is not expected to be possible during backout. An exception trace point is written, message DFHFC4700 is issued and a system dump is taken. Use these to determine the cause of the error. It might be worth retrying the backout, using SET DSNAME RETRY, since the problem could have been some transient condition which has since cleared.

Module

DFHFCRC

XMEOUT parameters/Message inserts

  1. date
  2. time
  3. applid
  4. tranid
  5. filename
  6. X'local_uowid'
  7. task_number
  8. base_dsname
  9. path_dsname
  10. X'bfail_code'

Destination

CSFL and Console



DFHFC4701.html | Timestamp icon Last updated: Sunday, 4 June 2017