Output descriptor options for disk data sets

The following options can be used only for disk data sets.

For more information about these options, see OUTPUT-syntax-options-reserved-for-disk-data-sets. 

Related topics

Copy-data-set-output-descriptor-options

OUTPUT-syntax-options-reserved-for-disk-data-sets

SPACE=CYL

Use SPACE to specify that the disk data set output is to be allocated in cylinders. Specify SPACE=TRK to allocate the output in tracks. The value of this option can be overridden at runtime by using the SPACE syntax option in an OUTPUT statement. 

PCTPRIM=100

Use PCTPRIM to specify that 100% of the disk space should be allocated as primary space. Any integral value from 1 through 100 is valid. The value can be overridden at runtime by using the PCTPRIM syntax option in an OUTPUT statement.

Important

For large table spaces, it is possible for the primary allocation calculated by PCTPRIM to be too large. However, you can use the MAXPRIM installation option to override the calculated value.

MAXPRIM=559

Use MAXPRIM to specify the maximum amount of disk space (in the units specified by SPACE) that can be allocated as primary space. A value of 0 specifies no limit, while a nonzero value establishes an upper limit on the value calculated by PCTPRIM. The default value is 559 (16 extents * 559 cylinders would provide 8944 cylinders). Valid values are 0 through 65535. A value specified during installation can be overridden at runtime by using the MAXPRIM syntax option in an OUTPUT statement. 

NBRSECD=10

Use NBRSECD to specify the number of disk space secondary allocations. After the primary allocation is calculated, the remaining space is secondary space and can be divided into from one to fifteen parts, specified by the value in the range 1 to 15 used for NBRSECD. The default is 10. A value specified during installation can be overridden at runtime by using the NBRSECD syntax option in an OUTPUT statement.

The size of the secondary allocation is never allowed to be less than 10% of the primary allocation. 

VOLUMES=

Use VOLUMES to specify a default list of disk volumes for the LPVOLS, LBVOLS, RPVOLS, and RBVOLS installation options. The number of entries in the list must not exceed the default value of VOLCNT, which is 25. If the data set is uncataloged, the list recorded in SYSIBM.SYSCOPY is truncated to reflect the actual volumes used. Use VOLUMES only when you are not using SMS and want to direct the copy data set output to specific volumes.

A list specified during installation can be overridden at runtime by using the VOLUMES syntax option in an OUTPUT statement.

Specify the list in the form (vol1,vol2,...). 

LPVOLS=

Use LPVOLS to specify a default list of disk volumes for storing local site primary copy data sets. The number of entries in the list must not exceed the default value of VOLCNT. If the data set is uncataloged, the list recorded in SYSIBM.SYSCOPY is truncated to reflect the actual volumes used.

A list specified during installation can be overridden at runtime by using the LPVOLS syntax option in an OUTPUT statement.

Specify the list in the form (vol1,vol2,...). 

LBVOLS=

Use LBVOLS to specify a default list of disk volumes for storing local site backup copy data sets. The number of entries in the list must not exceed the default value of VOLCNT. If the data set is uncataloged, the list recorded in SYSIBM.SYSCOPY is truncated to reflect the actual volumes used.

A list specified during installation can be overridden at runtime by using the LBVOLS syntax option in an OUTPUT statement.

Specify the list in the form (vol1,vol2,.......voln). 

RPVOLS=

Use RPVOLS to specify a default list of disk volumes for storing recovery site primary copy data sets. The number of entries in the list must not exceed the default value of VOLCNT. If the data set is uncataloged, the list recorded in SYSIBM.SYSCOPY is truncated to reflect the actual volumes used.

A list specified during installation can be overridden at runtime by using the RPVOLS syntax option in an OUTPUT statement.

Specify the list in the form (vol1,vol2,...). 

RBVOLS=

Use RBVOLS to specify a default list of disk volumes for storing recovery site backup copy data sets. The number of entries in the list must not exceed the default value of VOLCNT. If the data set is uncataloged, the list recorded in SYSIBM.SYSCOPY is truncated to reflect the actual volumes used.

A list specified during installation can be overridden at runtime by using the RBVOLS syntax option in an OUTPUT statement.

Specify the list in the form (vol1,vol2,...). 

DISKEXPD=

Use DISKEXPD with dynamic allocation to specify the expiration date for a disk copy data set. The date must be in the format YYDDD or YYYYDDD, where YY is the last two digits of the year, YYYY is the four-digit year, and DDD is the 3-digit Julian day (001 through 366).

Important

A date with a two-digit year is passed as is to dynamic allocation. For years beyond 1999, depending on your environment, this might not produce the appropriate result. We recommend using a four-digit year.

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

Important

When you specify the DISKEXPD option, DISKEXPD takes precedence over DISKRETN.

DISKRETN=0

Use DISKRETN with dynamic allocation to specify the retention period in days for a disk copy data set. The number of days must be in the range 0 through 9999. The default value, 0, indicates there is no retention of the disk copy data set.

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

Important

When you specify the DISKEXPD option, DISKEXPD takes precedence over DISKRETN.

EATTR=

Use EATTR to specify whether a data set supports extended attributes or not. If EATTR is not specified, which is the default, an SMS DATACLAS can provide the value.

Valid values for EATTR are NONE, OPT, and NO:

  • 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 Copy supports sequential data sets in the cylinder-managed portion of EAVs.

    If you specify EATTR=OPT, BMC AMI Copy 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 Copy 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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*