DFSMSdss actions resulting from dumping a data set are based on
the following conditions:
- Success or failure to acquire an exclusive enqueue for the resource
names of SYSDSN, SYSVSAM, and BWODSN.
- Backup-while-open status before the dump.
- Backup-while-open status indicators after the dump.
When DFSMSdss acquires all of the exclusive enqueues: The
data set is not open for update, even though it has a non-zero backup-while-open
status. The particular processing action is a direct result of the
initial backup-while-open status as follows:
- Status is 000; the data set is dumped. When it is restored, the
backup-while-open status is restored as 000.
- Status is 001. The data set is dumped and the backup-while-open
status is preserved and restored when the data set is subsequently
restored. This data set is in an indeterminate state because of an
incomplete forward recovery by CICSVR, which cannot forward-recover
the restored data set.
DFSMSdss lets you dump and restore this
data set for nonstandard recovery purposes. After restoring the data
set and correcting all errors in the data set, reset the BWO status
to 000 by using CICS-provided methods. The preferred action is for
you to restore an earlier dump of the data set and use CICSVR to do
forward-recovery processing. This maintains the integrity of the data.
- Status is 010. DFSMSdss did not dump the data set. Take
corrective action before using the data set by performing the following
actions:
- Determine if alternate indexes (AIX®)
are present for the sphere. If they are, do either of the following
tasks:
- Rebuild the AIXs from the base cluster, and reset the BWO status
to 000 by using the CICS' methods.
- Restore an earlier dump of the sphere, and use CICSVR to do forward-recovery
processing.
- If there are no AIXs, the data set is usable, as it is. Reset
the BWO status to 000 by using the CICS® methods.
- Status is 101. The data set is dumped and the backup-while-open
status is preserved and restored when the data set is subsequently
restored. This lets you process the data set with CICSVR before a
data base application uses it.
- Status is 011, 100, 110, 111. The backup-while-open status is
altered to 000 before the data set is dumped. When it is restored,
the backup-while-open status is restored as 000.
When DFSMSdss acquires an exclusive enqueue on
BWODSN (but not SYSDSN and SYSVSAM):Another program is using
the data set or the data set is open. The particular processing action
is a direct result of the initial backup-while-open status as follows:
- Status is 000. The data set is not eligible for backup-while-open.
The data set is not dumped unless SHARE or TOLERATE(ENQFAILURE) is
specified and the necessary conditions for those keywords are met.
- Status is 001, 010, 011, 101, or 111; the data set is not dumped.
- Status is 110; the backup-while-open status is altered to 100
and the data set is dumped.
- Status is 100. The data set is dumped, even though it is already
in use (including being open for update by another program). When
the data set is restored, the backup-while-open status is set to 101.
This ensures that CICSVR or DFSMStvs can process the data set, prior
to its use by a data base application. The dump is invalidated if
the backup-while-open indicators change while the data set is being
dumped. The chances of this invalidation occurring reduce significantly
when you use concurrent copy.