Space announcement

   

This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

OUTPUT option descriptions

BMC AMI Recover provides options for use with the OUTPUT command. The options are described in the order in which they are shown in the OUTPUT syntax diagram.

OUTPUT name

Use OUTPUT name to introduce a new output descriptor name. BMC AMI Recover creates the named descriptor by using the options specified in the OUTPUT command statement. The value for name must not exceed eight characters.

DSNAME dataSetName

Specify DSNAME and a data set name (dataSetName) to specify a data set name or model to use.

DSNAME is not required if you use the OUTCOPYDSN keyword (OUTCOPYDDN specification), or the RECOVERYDSN keyword (RECOVERYDDN specification), or both in the OUTCOPY specification on the RECOVER command statement.

You can constructdataSetName by using the symbolic variables in Using symbolic variables.

Common options specification description

This topic describes options that you can use for output data sets written to disk or tape.

UNIT name

Specify UNIT and a new tape or disk unit name when you want to override an existing default unit. The BMC AMI Recover default is SYSALLDA.

BMC AMI Recover can dynamically determine whether a unit is tape or disk.

CATLG

Specify CATLG to indicate whether to redefine the operating system catalog directive for the named descriptor.

CATLG YES

CATLG YES is the default and redefines the operating system catalog directive for the named descriptor.

If any SMS option (STORCLAS, DATACLAS, or MGMTCLAS) is used, BMC AMI Recover forces CATLG YES.

CATLG NOCATLG NO does not redefine the operating system catalog directive for the named descriptor.


MODELDCB dataSetName

Specify MODELDCB and a cataloged data set name (dataSetName) to redefine the model data control block (DCB) for the named descriptor.

To specify that no model DCB be used, use MODELDCB NONE.

The specified model data set must be allocated on a mounted direct access volume. BMC AMI Recover copies the DCB information from the data set label.

You can construct dataSetName by using any of the symbolic variables in Using symbolic variables.

VOLCNT integer

To set VOLCNT integer for the named descriptor, specify the largest number of volumes that you expect BMC AMI Recover to process when copying a single data set. For both tape and disk data sets, integer must be equal to or greater than the number of volumes produced for the single largest output copy, whether or not you use stacked output. The default is 25. To use the operating system default, set VOLCNT to 0.

Note

If you are using SMS in your system, BMC recommends that you use VOLCNT 0.

UNITCNT integer

Use UNITCNT to specify the unit count used for dynamic allocation. Valid values are 0 (zero) to 59. The value 0, the default, means that the unit count is not specified for the allocation.

Specifying UNITCNT 2 for tape output allocates two tape drives. When a tape volume is at the end of tape, BMC AMI Recover begins writing on the second drive immediately. This eliminates time spent waiting for tape rewind.

The total number of tape drives allowed in use at one time is specified by the MAXDRIVES option, either as coded in the OPTIONS command statement or from the MAXDRIVE installation option. If the value for UNITCNT is greater than one and would cause the total number of tape drives in use to exceed MAXDRIVES, BMC AMI Recover decrements UNITCNT to prevent the allocation from exceeding that limit.

DATACLAS name

Specify DATACLAS name when you want to provide an SMS data class name for the named descriptor. The value of name must be a valid SMS data class name, not exceeding eight characters.

BMC AMI Recover forces CATLG=YES when you specify DATACLAS.


MGMTCLAS name

Specify MGMTCLAS name when you want to provide an SMS management class name for the named descriptor. The value of name must be a valid SMS management class name, not exceeding eight characters.

BMC AMI Recover forces CATLG=YES when you specify MGMTCLAS.


STORCLAS name

Specify STORCLAS name when you want to provide an SMS storage class name for the named descriptor. The value of name must be a valid SMS storage class name, not exceeding eight characters.

BMC AMI Recover forces CATLG=YES when you specify STORCLAS. For more information, see STORCLAS.

Disk options specification description

This topic describes options that apply only to output data sets written to disk devices.

SPACE (primarysecondary) allocation unit

Specify SPACE to set the output allocation units (tracks or cylinders) for the named descriptor. Specify SPACE TRK to allocate the output in tracks. Specify SPACE CYL to allocate the output in cylinders. The default value for this option is CYL. Specify the values in parentheses, as in the following example: SPACE (200,100) CYL. If no SPACE specification is provided, the default is (5,5) CYL.

Note

You can use BMC AMI Recover to automatically size the OUTCOPY files generated by BMC AMI Recover. For more information, see Automatic sizing of output copies dynamically allocated on DASD.

VOLUMES (volume1volume2..........volumen)

Specify VOLUMES to provide a list of default volumes for the named descriptor. The number of entries in the list must not exceed the value specified by VOLCNT for the named descriptor (see VOLCNT integer). If the data set is uncataloged, BMC AMI Recover truncates the list recorded in SYSIBM.SYSCOPY to reflect the actual volumes used.

Warning

Enough space must exist on the first specified volume to allocate the primary space required for the output data set.

EATTR

Use EATTR to specify whether a data set supports extended attributes or not. If you do not specify EATTR on the OUTPUT command, BMC AMI Recover uses the value of the EATTR installation option (EATTR=). The EATTR installation option defaults to EATTR=, which is the equivalent of EATTR=NONE.

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

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.

You can also 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 (INCOPY specification).

Valid values for EATTR are:

  • NONE specifies no value for EATTR and allows the value for EATTR to be set by an SMS DATACLAS

    Using NONE 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.

    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.

MAXPRIM integer

Specifying MAXPRIM allows you to set a maximum amount of disk space (in the units specified by SPACE) to allocate as primary space. Valid values are 0 through 65535. A nonzero value for integer establishes an upper limit for primary space allocation, while a value of zero specifies no limit.

Note

Although this option is not required for use with the AUTOSIZE=YES option (AUTOSIZE), you might find it useful when you want to use dynamic space calculation of OUTCOPY files generated by BMC AMI Recover. For more information, see Automatic sizing of output copies dynamically allocated on DASD.

Tape options specification description

This topic describes the options that apply only to copies written to tape.

STACK

The STACK option tells BMC AMI Recover whether to stack the output copies from multiple RECOVER executions contiguously on the same tape volumes. For information about using tape stacking, see Stacking copies on tape.

STACK NO

STACK NO, the default, tells BMC AMI Recover not to stack output copies contiguously on tape.

STACK YES

STACK YES tells BMC AMI Recover to stack output copy data sets (of the same type) from multiple RECOVER command statements contiguously on the same tape.

Warning

If you are using Tape Mount Management (TMM), be aware that TMM intercepts any data set allocation whether dynamic or otherwise. If you want the copies on tape and use STACK YES with TMM, add the BMC AMI Recover program AFRMAIN to the TMM exclusion list. If BMC AMI Recover detects that the allocation has gone to disk instead of tape, it discontinues stacking.

TRTCH

The TRTCH option allows the use of Improved Data Recording Capability (IDRC) tape compression for the named descriptor.

TRTCH NONE

This value is the default and specifies the use of the system default for compression. TRTCH NONE is equivalent to not specifying TRTCH.

TRTCH COMP

TRTCH COMP specifies that IDRC compression is to be used for output files.

TRTCH NOCOMP

TRTCH NOCOMP specifies no IDRC compression for output files (even if the system default is TRTCH COMP).

RETPD integer

Specify RETPD integer to set a new retention period (in days) for the current output data set. The value of integer must be in the range of 1 through 9999.

Note

When EXPDT is specified, it takes precedence over RETPD.

EXPDT date

Specify EXPDT date to set a new expiration date for the current output data set. The default value of the EXPDT option is 99000, which indicates no expiration date.

Note

When it is specified, EXPDT takes precedence over RETPD.

The value of date must be in the format YYDDDYYYYDDD, or YYYY/DDD, where YYYY is the 4-digit year, YY is the last two digits of the year, and DDD is the 3-digit Julian day (001 through 366).

Note

A date with a two-digit year is passed as is to dynamic allocation. For years beyond 1999, depending on your environment, this date may not produce the desired result. BMC recommends using a four-digit year.

Was this page helpful? Yes No Submitting... Thank you

Comments