EATTR=

You cannot use an image copy made to the cylinder-managed portion of an extended address volume (EAV) under z/OS Version 1.11 on z/OS Version 1.10 because z/OS Version 1.10 does not support sequential data sets in the cylinder-managed portion of an EAV.

z/OS Version 1.11 or later supports the EATTR option. For earlier versions of z/OS, you must set EATTR= (or EATTR=NONE).

You can set EATTR to OPT or NO in the JCL.

When you create an OUTCOPY (OUTCOPY specification) and want to force the copy to the cylinder-managed space of an EAV, specify the SPACE keyword.

Valid values for EATTR are:

• Specifying no value for EATTR (EATTR=), the default, allows the value for EATTR to be set by an SMS DATACLAS. (EATTR= is the same as specifying EATTR=NONE.)

  Using the default value allows you to have your environment set up to use extended attributes.

• OPT specifies that extended attributes are optional for the data set.

  You must set EATTR=OPT to allocate an extended format sequential data set. By using EATTR=OPT, BMC AMI Recover supports sequential data sets in the cylinder-managed portion of EAVs.

  If you specify EATTR=OPT, BMC AMI Recover specifies the EATTR attribute when it dynamically allocates the output data set and overrides the EATTR option in the SMS DATACLAS, if one exists.

  Extended format sequential data sets must be allocated on SMS-managed volumes and the size of the data set must be greater than the EAV break point, which is typically 10 cylinders.

• NO specifies that the data set cannot have extended attributes.

  If you specify EATTR=NO, BMC AMI Recover specifies the EATTR attribute when it dynamically allocates the output data set and overrides the EATTR option in the SMS DATACLAS, if one exists.

By using the EATTR syntax option in an OUTPUT statement at runtime, you can override the value set during installation. (See EATTR.)