Configuring › System Extensions (SARXTD) › Activating System Extensions

Activating System Extensions

To activate the system extensions on a processor (or to reactivate those features that have been deactivated), issue the following command:

S SARXTD [,PARM='parameters']

Where

parameters specify one or more optional parameters used to override those in the start procedure JCL.

Note: For more information about activating system extensions, see System Extensions Parameters.

Note the following information:

• Add the S SARXTD command to member COMMNDxx of SYS1.PARMLIB to start the system extensions task automatically at each IPL.
• The data set security feature is activated only when its parameter is specified in the parameter field used to start system extensions.
• The automatic report archival feature is activated only when its parameters are specified in the parameter field used to start system extensions.
• The accounting data capture feature is activated only when the SARACT DD statement for the accounting file is included in the JCL procedure used to start system extensions.
• You can use the following dummy DD statements with the SARXTD program:

  //NOSVC99  DD DUMMY
  

  Dynamic deallocation (SVC 99) of SYSOUT data sets is bypassed during subsystem close processing. The result causes the SYSOUT data sets produced by automatic report archival to be unavailable to the CA View started task until job termination. If this DD statement is not present, each report is available when it is closed, potentially causing a separate entry for it in the CA View database.

  //NOTERM   DD DUMMY
  

  The SARXTD started task remains active and responds to MODIFY commands as they are received through the operator console. The started task terminates, regardless of whether this DD statement is present, when all system extensions have been deactivated.

  //SUBSYSn  DD DUMMY
  

  More than one set of system extensions can be implemented concurrently by specifying a unique subsystem identifier (n) in this DD statement.

  //NOCONF   DD DUMMY
  

  The SARXTD started task does not issue message SARXTD01 to authorize changes to SARXTD.

If you want to use multiple SARXTDs, be aware of the following information:

• If you want to use job accounting in a single CPU environment, accounting is done in only one SARXTD. If more than one SARXTD is used, accounting data is double posted.
• If you want to use job accounting in a multiple-CPU environment, the accounting data set can be shared only across systems within the same multi access spool complex. Furthermore, SARXTD records accounting data only for jobs run on a CPU on which you have requested SARXTD accounting. Therefore, to record accounting data on all CPUs, run SARXTD accounting on all CPUs.
• For automatic report archival, processing is performed based on the alphanumeric order of the subsystem identifier. For example, if SUBSYS2 and SUBSYS6 request automatic archival for the same SYSOUT, only the SUBSYS2 request is honored—even if SUBSYS2 was started after SUBSYS6.