IBM SC34-7012-01 manual Logical delete not performed, Open error, SMSVSAM server failure

Models: SC34-7012-01

1 268
Download 268 pages 41.5 Kb
Page 93
Image 93

It might be worth initially deciding to leave a data set online for some time after a backout failure, to evaluate the level of impact the failures have on users.

To recover from a media failure, re-create the data set by applying forward recovery logs to the latest backup. The steps you take depend on whether the data set is opened in RLS or non-RLS mode:

vFor data sets opened in non-RLS mode, set the data set offline to all CICS applications by closing all open files against the data set.

Perform forward recovery using a forward recovery utility.

When the new data set is ready, use the CEMT (or EXEC CICS) SET DSNAME RETRY command to drive backout retry against the data set for all the units of work in backout-failed state.

vFor data sets opened in RLS mode, use the CEMT (or EXEC CICS) SET DSNAME QUIESCED command to quiesce the data set.

Perform forward recovery using CICSVR as your forward recovery utility.

CICS regions are notified through the quiesce protocols when CICSVR has completed the forward recovery. This causes backout to be automatically retried. The backout retry fails at this attempt because the data set is still quiesced, and the UOWs are again shunted as backout-failed.

Unquiesce the data set as soon as you know that forward recovery is complete. Completion of the unquiesce is notified to the CICS regions, which causes backout to be automatically retried again, and this time it should succeed.

This mechanism, in which the backout retry is performed within CICS, supersedes the batch backout facility supported by releases of CICSVR earlier than CICSVR 2.3. You do not need a batch backout utility.

Logical delete not performed

This error occurs if, during backout of a write to an ESDS, the XFCLDEL logical delete exit was either not enabled, or requested that the backout be handled as a backout failure.

You can correct this by enabling a suitable exit program and manually retrying the backout. There is no need to take the data set offline.

Open error

Investigate the cause of any error that occurs in a file open operation. A data set is normally already open during dynamic backout, so an open error should occur only during backout processing if the backout is being retried, or is being carried out following an emergency restart. Some possible causes are:

vThe data set has been quiesced, in which case the backout is automatically retried when the data set is unquiesced.

vIt is not possible to open the data set in RLS mode because the SMSVSAM server is not available, in which case the backout is automatically retried when the SMSVSAM server becomes available.

For other cases, manually retry the backout after the cause of the problem has been resolved. There is no need to take the data set offline.

SMSVSAM server failure

This error can occur only for VSAM data sets opened in RLS access mode. The failure of the SMSVSAM server might be detected by the backout request, in which case CICS file control starts to close the failed SMSVSAM control ACB

Chapter 8. Unit of work recovery and abend processing 81

Page 93
Image 93
IBM SC34-7012-01 manual Logical delete not performed, Open error, SMSVSAM server failure