Setting up for ACS Trace Facility

The following items are required prior to starting and using the ACS Trace Facility.

1. Customize ACSTRSTC Member in BBSAMP  Trace uses the ACS Service Started Task. MVSRM SAMPLIB data set (hlq.BBSAMP) contains member ACSTRSTC. That member needs to be copied, customized and placed into your system PROCLIB concatenation. The name used for the Started Task is determined by your site standards.
2. Update SMMSYSxx (ACSTR_PROC=): Specify the name of the  ACS Trace Service Started Task using the ACSTR_PROC parameter in the active SMMSYSxx member in SVOS.  The name used in the customization of the service Started Task in step one should be specified in this parameter.  Example: ACSTR_PROC=ACSTRSTC
3. Update SMMSYSxx (ACSTR_OINDX=): The ACS Trace Facility creates, uses and deletes work data sets in its processing. It also uses static test SCDS data sets (the SCDS data set contains object code created from the ACS source members). The work data sets are dynamically allocated and deleted during processing. The test SCDS data sets are created using JCL supplied in MVSRM SAMPLIB (the creation of the SCDS is in the following steps). Both the work data sets and the SCDS data sets require a high-level qualifier (HLQ) to be specified in SMMSYSxx. The ACSTR_OINDX parameter is used to specify the HLQ. The HLQ can have a maximum length of 19 characters of your choosing (using your site standards) . The low-level qualifiers (LLQ) of the data sets are predetermined. The LLQ for the work data set will be “.SVACSTR.Dnnnnnn.Tnnnnnnn” (n=creation date and time).  The low-level qualifier for the test SCDS data sets are .SVACSTR.TSTSCDS1 and .SVACSTR.TSTSCDS2.   These low-level qualifiers are appended to the high-level qualifier supplied in the ACSTR_OINDX parameter to create the fully qualified data set names used during processing.  Example: ACSTR_OINDX=SYS2.SVOS will become SYS2.SVOS.SVACSTR.D200506.T9022949 / SYS2.SVOS.SVACSTR.TSTSCDS1
4. Update SMMSYSxx (ACSTR_OUNIT=) (Optional): The creation of the work data sets can be directed to a unit and volume. If you want these data sets to be allocated on a specific unit you can specify ACSTR_OUNIT=unit, if coded ACSTR_OVOL is required. If not specified, the data sets are allocated using SYSALLDA for the unit and the creation of the data sets will default to the site specified rules for that esoteric unit name. Example: ACSTR_OUNIT=3390
5. Update SMMSYSxx (ACSTR_OVOL=) (Optional): The creation of the work data sets can be directed to a volume and unit. If you want these data sets to be allocated on a specific volume you can specify ACSTR_OVOL=volume, if coded ACSTR_OUNIT is required. Example: ACSTR_OVOL=SYS001 
6. Update and submit ACSTRSCD member in BBSAMP: The ACS Trace facility utilizes SCDS data sets. The SAMPLIB member (in hlq.BBSAMP) ACSTRSCD contains sample JCL to create the test SCDS data sets. Copy, customize and submit the JCL to create these test SCDS data sets. During the customization of the JCL you will be asked to update the high-level qualifier used for the SCDS data set, you have to use the same name for the HLQ in this this JCL that you used in the ACSTR_OINDX= parameter and you cannot change the low-level qualifier names for the SCDS data sets that are coded in the sample JCL. If the LLQ’s are changed or the HLQ doesn’t match the parameter in SMMSYSxx member, the ACS Trace Facility will issue error messages and fail to process.
7. Security for the data sets used by the Trace Facility must be updated to allow the SVOS started task to read the input ACS source files and JCL test data set.  Alter access must be granted to the test SCDS data sets and the related work data sets that are utilized during the process.