Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recovery Manager for Db2 13.1.

Work file option descriptions

You can specify sort and work file options that might be required when extracted keys are sorted during index rebuilds or when using the CHECK DATA and CHECK INDEX utilities.

This information is used for the following purposes:

  • As the data set sizing default (primarily allocation values) when BMC AMI Recovery Manager cannot determine data set sizes using information from the Db2 or ICF catalog
  • When generating the Log Master (ALPMAIN) step during disaster recovery (only available with the Recovery Management for Db2 solution)

Important

If you are using the Recovery Management for Db2 solution, the Log Master step generates the file that contains the SQL statements that you use to return the data collection information from the recovery site to the local site. (For more information, see the Recovery Management for Db2 documentation.)

The work file fields are listed alphabetically in the following table along with the corresponding BMC AMI Recovery Manager defaults.

Field

Default

Description

Allocation type

Cylinder

Specifies whether the primary and secondary allocation quantities are expressed in cylinders or tracks

Max primary allocation

0

Limits the amount of primary allocation space to be used for sort work space

Valid values are 0 - 9999, where 0 indicates no limit.

Warning

Ensure that you use a maximum primary value that fits on your DASD devices. If the maximum primary value exceeds the capacity of a volume, the job will fail. For capacity guidelines, see Capacity of typical DASD devices.

Max primary allocation affects the following values:

  • Primary Allocation, Dynamic Sortworks, and WORKDDN Sizing

    BMC AMI Recovery Manager compares the maximum primary allocation to the calculated primary allocation value and selects the smaller of the two. If the maximum primary value is selected, the primary space allocation is set to that value, and the secondary space allocation is set to 1/15 of that value. The same calculations are used for the sort work files.

  • Unit Count (for DSNUTILB COPY)

    The unit count for DSNUTILB COPY is based on the maximum primary value. If the space required for the copy is greater than the maximum primary allocation, BMC AMI Recovery Manager calculates the required unit count. The unit parameter is UNIT=(work_unit,n) where n is the calculated number of units up to a maximum of 59. If the maximum primary value is 0, no unit count is calculated. (See BMC-AMI-Copy-backup-options.)

Primary allocation

10

Specifies the primary allocation quantity when BMC AMI Recovery Manager is unable to estimate the quantity due to problems or when the Data Set Sizing option in the Recovery Options Specification panel is set to Default

You can limit the primary allocation value by specifying the Max primary allocation.

Secondary allocation

20

Specifies the secondary allocation quantity when BMC AMI Recovery Manager is unable to estimate the quantity due to problems or when the Data Set Sizing option in the Recovery Options Specification panel is set to Default.

Work prefix

Not specified

Specifies the high-level name to use when allocating sort and work files.

  • If you specify a work prefix in the object set options, BMC AMI Recovery Manager uses that work prefix.
  • If you do not specify work prefix in the object set options, BMC AMI Recovery Manager uses the value of Work File Prefix in ARM$OPTS (see page 755).
  • If WORKPREFIX has no value in ARM$OPTS, BMC AMI Recovery Manager uses the user ID.

Work unit

SYSALLDA

Specifies a disk file for use when dynamically allocating work files.

Tip

To determine the size of the work file, run DSN1LOGP with SUMMARY(ONLY) and allocate the output to a disk file.

WORKDDN

NO

Directs the sorting of extracted index keys in index recoveries.

NO (the default) sorts the keys without writing them to SYSUT1 and omits that file from the recovery JCL.

YES writes extracted index keys to a work file (SYSUT1) before sorting.

You can limit the amount of space allocated for the work file by specifying the Max primary allocation.

BMC AMI Recovery Manager ignores this option if you specify a value greater than 1 for Maximum Key Sorts (MAXKSORT).

You must ensure that the value that you specify for the Maximum primary value fits on your DASD devices. If the maximum primary value exceeds the capacity of a volume, the job will fail. The following table gives examples of the capacity of some typical DASD devices:

Physical data for 3380

(per device)

Physical data for 3390

(per device)

Physical data for 9345

(per device)

Single Density (Models D & J)

Tracks: 3,275

Cyls: 885

Model 1 (Single)

Tracks: 16,695

Cyls: 1,113

Model 1

Tracks: 21,600

Cyls: 1,440

Double Density (Model E)

Tracks: 26,550

Cyls: 1,770

Model 2 (Double)

Model 3

Tracks: 33,390

Cyls: 2,226

Model 2

Tracks: 32,340

Cyls: 2,156

Triple Density (Model K)

Tracks: 39,825

Cyls: 2,655

(Triple)

Tracks: 50,085

Cyls: 3,339

Not applicable

Not applicable

Not applicable

Not applicable

Model 9

(Mod 9)

Tracks: 150,255

Cyls: 10,017

Not applicable

Not applicable


Related topics

Backing-up-and-recovering-the-Db2-catalog-and-directory

Recovering object sets



 

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