http://www.redbooks.ibm.com/redbooks/SG247768/wwhelp/wwhimpl/api.htm?href=4-3-3.htm
contains:
<IBM ITSO Documentation>
In z/OS V1.10, customers controlled whether VSAM data sets could reside in the
EAS by including or excluding EAVs in particular storage groups. For non-SMS
managed data sets, the customer controlled the allocation to a volume by
specifying a specific VOLSER or esoteric name.
This situation is different in z/OS V1.11 because V1.11 provides a new EATTR
data set attribute for controlling the allocation of VSAM and non-VSAM data sets
in regard to when extended attribute DSCBs and EAS can be used.
This new data set is used in AMS DEFINE and ALLOCATE, JCL, dynamic allocation,
and data class. IDCAMS AAMS [SIC] ALTER will modify this attribute in existing
data sets. There is no JCL override of the current EATTR value for existing data
sets. To change the EATTR value after a new allocation requires you to run the
AMS ALTER command.
The precedence order of EATTR is JCL, LIKE/REFDD, and Data Class. If there is no
data class, or the data class has no EATTR value, the processing defaults to the
default value based on data set type.
The EATTR value resides in the Format 1 and Format 8 DSCBs for VSAM and non-VSAM
data sets. It also resides in the primary VVR for VSAM data sets so that it is
associated with all components of the VSAM data set.
</IBM ITSO Documentation>
This suggests that IDCAMS ALTER can be used to change the EATTR value for an
existing data set. Really? How?
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
310-338-0400 x318
edja...@phoenixsoftware.com
http://www.phoenixsoftware.com/
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
