Starting the AKDMAIN started task

1. Change the STEPLIB to point to the library that contains the Advanced Audit load modules.
2. Change the PARMLIB to point to the library that contains the Advanced Audit parameter members.
   • If the product parameters are distributed across multiple data set members, then specify the parameter as follows in EXEC statement: PARM=’MEMBER=(AKDCMD00, AKDCMD01,..., AKDCMDnn)’If this parameter is omitted in EXEC statement, then AKDCMD00 is considered as PARMLIB dataset member for product parameter.
   • For the MEMBER keyword values, specify appropriate member names that are separated by commas and enclosed within parentheses. In situations where the same parameter was specified in multiple members, Advanced Audit uses the first occurrence of the parameter specification that it encounters. The specifications for the same parameter that appear in subsequent members that were specified for the MEMBER keyword are ignored.
   • If the product parameters are distributed across multiple data sets, change the parameter library to point to a concatenation of the appropriate data set names.
3. Add the customized start up JCL to a system procedure library. This JCL can also be run as a batch job, but it is recommended that you run it as an address space.

At this point in the configuration process, you must start the AKDMAIN started task.

• Start AKDMAIN on every system on which users will access the Advanced Audit for DFSMShsm ISPF interface.