Acs tracing of alternate ACS routines - syncsort_allocation_control_center

SMS/Debug ACS tracing can be performed using either the active ACS routines (the ACS routines used by DFSMS and residing in the SMS Active Control Data Set (ACDS)), or an alternate set of ACS routines that has not yet been made active.

By default, SMS/Debug ACS tracing uses the currently active ACS routines.

To perform a trace using a different set of ACS routines, the routines must have been translated by ISMF and must reside in an SMS Source Control Dataset (SCDS).

Tip: This SCDS does not need to be the SCDS that was copied to the ACDS at activation time, and it does not need to have been validated (although validation is recommended).

The ACS routines source that is to be tested must have been successfully translated; otherwise, the routines will not be present in the SCDS. This SCDS must be allocated to the DIF started task with a DDNAME of SCDSxx.

Up to 99 different SCDSs may be allocated to the DIF started task. The particular SCDS that contains the alternate ACS routines to be traced is specified on the SCDSNAME= keyword in the JCL.

If only a single alternate set of ACS routines is allocated to the DIF started task, or the SCDSNAME= keyword is not used, the DD name may simply be //SCDS.

The sample below shows a DIF started task with 11 SCDSs allocated to it. This allows users to perform ACS tracing using any one of 11 different sets of ACS routines.

Identifying ACS routine logic


            //*********************************************************************
            //*                                                                   *
            //* DTS SOFTWARE DYNAMIC INSTALL FACILITY (DIF)                       *
            //*                                                                   *
            //*********************************************************************
            //DIF PROC P=
            //DIF EXEC PGM=DIF,DYNAMNBR=20,TIME=1440,REGION=4M,
            // PARM='CMDCHAR=%,&P'
            //STEPLIB  DD DISP=SHR,DSN=DIF.LOAD.LIBRARY
            //PARMLIB  DD DISP=SHR,DSN=DTS.PARMLIB
            //LPALIB   DD DISP=SHR,DSN=SYS1.LPALIB
            //SCDS     DD DISP=SHR,DSN=SYS1.SCDS
            //SCDS01   DD DISP=SHR,DSN=TEST.SCDS01.SCDS
            //SCDS02   DD DISP=SHR,DSN=SYSX.TEST.SCDS
            //SCDS03   DD DISP=SHR,DSN=TEST.PROD.SCDS
            //SCDS05   DD DISP=SHR,DSN=TEST.SCDS05.SCDS
            //SCDS06   DD DISP=SHR,DSN=TEST.SCDS06.SCDS
            //SCDS07   DD DISP=SHR,DSN=TEST.SCDS07.SCDS
            //SCDS08   DD DISP=SHR,DSN=TEST.SCDS08.SCDS
            //SCDS09   DD DISP=SHR,DSN=TEST.SCDS09.SCDS
            //SCDS10   DD DISP=SHR,DSN=TEST.SCDS10.SCDS
            //*MLPALIB DD DISP=SHR,DSN=MLPA.LIBRARY
            //SYSPRINT DD SYSOUT=A
            //SYSABEND DD SYSOUT=A
            //*SYSEXEC DD DISP=SHR,DSN=REXX.LIBRARY
            //*SYSPROC DD DISP=SHR,DSN=CLIST.LIBRARY
            //*SYSTSPRT DD UNIT=VIO,SPACE=(CYL,1)
            //*SYSTSIN DD DUMMY
            // PEND

Identifying ACS routine logic

When an alternate set of ACS routines is being traced, the logic trace for each set of ACS routines is preceded by message ACC80210 and ACC08300. These messages serve to separate and identify the logic for each set of ACS routines. Message ACC08300 'USING SCDS scdsname' will identify the SCDS. For the active ACS routines, scdsname will be ACTIVE. If both active and alternate ACS routines are being traced, the active routines are run last, so that the dataset can be allocated without error.

Acs tracing of alternate ACS routines - syncsort_allocation_control_center - Latest

Syncsort™ Storage Management Sms/Debug User Guide

Identifying ACS routine logic

Identifying ACS routine logic