Subsequent files opened when use count is zero

The following processing is done when a subsequent file is opened for update against a VSAM base cluster data set and the update use count in the DSNB for the base cluster is zero.

This situation could exist in the following cases:
  • After a warm or emergency restart of CICS®, because the BACKUPTYPE attribute in the DSNB is cataloged in the global catalog and is restored at CICS restart
  • When all files that are open against a base cluster are closed, and then one or more are reopened
CICS checks the BACKUPTYPE attributes in the FCT and the DSNB. If they are inconsistent, the file-open operation fails with error messages. Either correct the CEDA definition, or REMOVE the DSNB after closing all files that are open against the base cluster data set. If the BACKUPTYPE attributes are consistent, CICS uses the DFSMSdfp IGWABWO callable service to inquire on the BWO attributes in the ICF catalog.
  • If the file was defined with BACKUPTYPE(DYNAMIC), IGWABWO makes the data set eligible for BWO and sets the recovery point to the current time.

    However, if the ICF catalog indicates that the data set is already eligible for BWO, IGWABWO resets the recovery point to the current time. CICS issues an attention message; you can discard any BWO backup copies already taken in a previous batch window.

  • If the file was defined with BACKUPTYPE(STATIC) and the ICF catalog indicates that the data set is already ineligible for BWO, the ICF catalog is not updated.

    However, if the ICF catalog indicates that the data set is currently eligible for BWO, IGWABWO makes it ineligible for BWO and sets the recovery point to the current time. CICS issues an attention message; you should discard any BWO backup copies already taken in a previous batch window.



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