Invalid state changes for BWO attributes

CICS®, DFSMSdfp, DFSMSdss, and an SMSVSAM server can all update the BWO attributes in the ICF catalog.

To prevent errors, DFSMSdss fails a BWO backup if one of the following state changes is attempted during the backup:
  • From ‘BWO enabled and VSAM split in progress’ to ‘BWO enabled’. This state change could be attempted if:
    1. At the start of data set backup processing, a request is issued to change the ‘BWO enabled and VSAM split occurred’ state to the ‘BWO enabled’ state.
    2. But then, before the ‘BWO enabled’ state is set, a VSAM split occurs and sets the ‘BWO enabled and VSAM split in progress’ state.

    DFSMSdfp must now disallow the pending change to ‘BWO enabled’ (and DFSMSdss must fail the backup) because, if the split did not finish before the end of the backup, the invalid backup would not be discarded.

  • From ‘BWO disabled and VSAM split occurred’ to ‘BWO enabled’. This state change could be attempted if:
    1. At the start of data set backup processing, a request is issued to change the ‘BWO enabled and VSAM split occurred’ state to the ‘BWO enabled’ state.
    2. But then, before the ‘BWO enabled’ state is set, CICS closes the last file opened for update, and the data set becomes ineligible for BWO. CICS sets the ‘BWO disabled and VSAM split occurred’ state to ensure that the BWO backup is discarded and that no more BWO backups are taken.

    DFSMSdfp must now disallow the pending change to ‘BWO enabled’ (and DFSMSdss must fail the backup) to prevent the possibility of a BWO backup being taken during a subsequent batch window.



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