Skip to Content

Using the ACS Trace Facility

ACS routines can be used to determine the SMS classes and storage groups for data sets and objects in an SMS complex. The ACS Trace facility is used to trace the ACS rules that determine the destination of data set allocations. The output from the ACS Trace facility displays the comparisons that occur within the ACS rule and identifies the success or failure of the comparison. It can also identify the line number in the source where the SET action was taken during processing. Knowing the location in the rule where the action takes place makes it easy to determine why a rule is or is not providing the expected result.

Related topic

Using-BMC-AMI-Storage-Allocation

Information related to the Read/Write variables used in ACS processing can be identified by using the SMSACSTE function in MVSRM. For more information about the SMSACSTE function See, Global-parameter-for-SMSACSTE. Both the ACS Trace Facility and the SMSACSTE function require a license for BMC AMI Storage Allocation.

Following are the five elements to the ACS Trace Facility:

  • The batch job that allocates the data sets being traced.
  • The ACS source member that contains the ACS rules.
  • The SVACSTR component
  • The ACSTRSTC Service Task.
  • The user interface (MVSRM Dialog) that coordinates the trace. 

The batch job that is submitted by the trace process provides the data sets to be traced and also contain the trace output data.

The ACS source member provides the rules that determine the destination of the data sets being allocated. The ACSTRSTC Service Task is used to translate the rule source to object form. The ACSTRSTC component provides access to SMS and the Dialog controls the process.

The following information explains how to use the ACS Trace Facility:

 

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

BMC AMI Storage Allocation 8.2