You can specify the EATTR value when allocating a data set to define
whether the data set can have extended attributes (format 8 and 9
DSCBs) and optionally reside in EAS. In the event that a data set
is being directed to a pre-allocated data set on a RECOVER or ARECOVER
function, the system uses the EATTR value of the pre-allocated data
rather than the EATTR value specified for the data set source recovery
data.
ARECOVER and EATTR considerations
The following methods can be used to allow the EATTR information
from the ABACKUP site to be restored, along with the dataset:
- Use the DSCONFLICT(RENAMETARGET) parameter on the ARECOVER command,
then manually delete the existing dataset. Since the ARECOVER resolved
the conflict by renaming the existing dataset before restoring the
ABARS copy, both copies will have their own EATTR. You only need to
get rid of the renamed existing dataset.
- Use the DSCONFLICT(BYPASS) parameter on the ARECOVER command,
manually delete the existing dataset and existing conflict resolution
data set, then rerun the ARECOVER. Only the datasets that were bypassed
or failed for some other reason on the first ARECOVER will be processed.
Since no conflict exists anymore, you will get the ABARS copy, complete
with its EATTR.
For more information, see EATTR parameter of
the ALLOCATE command in z/OS DFSMS Access Method Services Commands.