File opening
Different processing is done for each of the three cases when a file is opened for an update.
The following processing takes place:
- First file opened for update against a cluster
- Subsequent file opened for update against a cluster while the previous file is still open (that is, the update use count in the DSNB is not zero)
- Subsequent file opened for update against a cluster after all previous files have been closed (that is, the update use count in the DSNB is zero)
In all three cases, CICS® issues warning message DFHFC5812 if BACKUPTYPE(DYNAMIC) is specified for a VSAM AIX data set that is being opened as a stand-alone base cluster data set. The AIX data set must default to the BACKUPTYPE already defined for the sphere.
Also, if the file-open operation fails during BWO processing, the ACB will be open. So CICS closes the ACB before indicating the file-open operation has failed. This affects CICS statistics.
If the file is opened for read-only, and the data set ICF catalog indicates that the data set is back-level, the file-open operation fails.
Back-level data sets
In all cases, a file-open operation fails with error messages if the ICF catalog indicates that
the data set is back-level. A back-level data set occurs as a result of the following:
- A data set has been restored from a backup copy, but not forward recovered.
- A data set has been forward recovered, but the forward recovery operation has not completed successfully.
- The ICF catalog indicates that a data set is corrupted.
Note: This check occurs irrespective of whether BACKUPTYPE(DYNAMIC)
or BACKUPTYPE(STATIC) is specified.