DFHFC4702 date time applid Backout failed for transaction tranid, BDAM file filename, unit of work X'local_uowid', task task_number.
Explanation
File backout has been unable to backout an uncommitted change made to a BDAM data set via file filename, that was made by the unit of work local_uowid.
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. However, if this backout is being attempted after waiting for an indoubt situation to be resolved, the current task number will be different from the original one given in the message, and transaction code will be different from the original one if the transaction has been disabled.
System action
The system continues normally.
Backing out of the unit of work continues, and any further failures to backout changes made to this BDAM data set result in the message being reissued.
Unless a program invoked at the backout failure exit point, XFCBFAIL, took some action to prevent it, it is possible for other work to continue to access the BDAM data set, but data integrity is compromised because the changes have not been backed out.
User response
Unless you are prepared to continue using the data set in spite of the loss of data integrity, you should take some action to correct matters, such as closing all files that are using the data set and backing out the uncommitted changes offline.
One possible cause of a BDAM backout failure is that a logical delete could not be performed because the XFCLDEL exit either chose not to carry out the logical delete or was not enabled. If this is the case then you may want to ensure that a suitable exit program is enabled at the XFCLDEL exit point, so that any future attempts at backing out writes made to BDAM data sets will succeed.
Module
XMEOUT parameters/Message inserts
- date
- time
- applid
- tranid
- filename
- X'local_uowid'
- task_number
Destination
CSFL and Console