BMC AMI Utilities work data set control


The following topics describe the work data sets that BMC AMI Utilities use, as well as the parameters that name them and control how long they are remain on a mainframe system:

BMC AMI Utilities work data sets

Related topic

BMC AMI Utilities do not use the SYSREC, SORTWORK and SYSUT work files and uses four VSAM work files which are dynamically allocated. The four BMC AMI Utilities work files are:

  • WK 
  • RGTS 
  • INFO  
  • OUT

Work file allocation can be controlled and manipulated in the XSUTDBMG automation control point.  Additional WK and RGTS work files might be pre-allocated if desired by setting the DSNUM variable value in the XSUTDBMG automation control point.  This can be useful and more efficient to pre-allocate the files if running many very large objects in a single utility.  For more information about how to pre-allocate the work files, see XSUTDBMG-database-manager-automation-control-point.

All four work files are necessary for restart and available when restarting a failed BMC AMI Utilities. The INFO and OUT must also be available for QUICKEXIT in case the BMC AMI Utility is cancelled. The workfiles are not needed for a FORCEID of a utility.

We recommend that BMC AMI Utilities work files be allocated on EA enabled devices otherwise there could be space issues with the work files.

Work file data set naming qualifiers are defined by the +WORKPREFIX parameter value and are suffixed as .WK#####, .RGTS####, .INFO### and .OUT###.

With +CONTROLPREFIX parameter, you can prefix the .INFO and .OUT work files differently than the .WK and .RGTS files. This is useful if allocation of these files to alternate DASD pools or devices is desired.

WK 

Used for sorting RIDs internally by BMC AMI Utilities.  Specific allocation of the data set can be set and controlled in the XSUTDBMG automation control point.  If necessary, BMC AMI Utilities automatically and dynamically allocate a .WK00002, .WK00003.

RGTS 

Used to hold image copy data for the table spaces being reorganized. Being the largest work file used by BMC AMI Reorg , the file contains all the image copy data excluding the free space for everything that is processed at a given time. The file must be as large as the largest combination of objects being processed concurrently at any given time. As image copies are written and objects are completed, the space is made available and can be reused in the work file.  Specific allocation of this data set can be set and controlled in the XSUTDBMG automation control point.  If necessary, BMC AMI Utilities automatically and dynamically allocate a .RGTS0002, .RGTS0003.

INFO

Used internally by BMC AMI Utilities to keep track of UIDs and their statuses.  INFO is also accessed by the servers as work is initiated and completed.  The utility dynamically allocates the work file to you and is not very big.  Dynamic allocation using the shipped defaults should be sufficient for the work file.

OUT 

Used for all utility related output including journal output. The file is not very big. Dynamic allocation using the shipped defaults should be sufficient for the work file.

Work file cleanup is done using +parms and can be automatic upon successful completion of BMC AMI Utilities or can be retained for a duration before deletion. The primary means of controlling cleanup of the work files are CLEANUP, DELETEOUTPUT, and OUTPUTAGE

Naming the BMC AMI Utilities work data sets

All the BMC AMI Utilities work data sets are qualified by the HLQ that you supply in WORKPREFIX. However, to keep the INFO and OUT data sets, which are kept for a few days, in a separate pool, use the CONTROLPREFIX global parameter to provide a separate HLQ for them.

 

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