Implementing CA-ACF2 security

If you have enabled security on the hub and specified CA-ACF2 as the security system, you must take additional steps to implement it.

1. If your Tivoli Enterprise Monitoring Server is running, stop it by entering the following command:

   P cccccccc

   where cccccccc is the name of your Tivoli Enterprise Monitoring Server started task.

2. Follow the instructions in KLVA2NEV to assemble and link KLVA2NEV. Change the -RHILEV- and -THILEV- variables as directed.

   Member KLVA2NEV in thilev.TKANSAM is the product-supplied interface to CA-ACF2. The product-supplied member KLV@ASM, in rhilev.rte.RKANSAMU (for PARMGEN) or rPlibHilev.rte_name.SECEXITS (for Configuration Manager), contains sample assembly JCL. This gets assembled into the runtime environment-specific rhilev.rte.RKANMODU data set (for PARMGEN) and rHilev.rte_name.SECEXITS (for Configuration Manager) by running the respective jobs (for PARMGEN) or GENERATE action (for Configuration Manager).

3. Define the Tivoli Enterprise Monitoring Server started task as a MUSASS to CA-ACF2:
   1. Log on to TSO. At the READY prompt, type ACF and press Enter.
   2. At the ACF prompt, type SET LID and press Enter.
   3. At the LID prompt, type the following commands:

      CH cccccccc MUSASS

      where cccccccc is the name of the Tivoli Enterprise Monitoring Server started task.
   4. Press Enter.
   5. At the LID prompt, type END and press Enter.
   If your site has a large numbers of users, you might have to increase the value assigned to the RESERVE parameter, which is KDS_X_TEMS_STORAGE_RESERVE_PRI, of member KDSSYSIN in the rhilev.rte.RKANPARU library. After making a change, as usual, you will need to regenerate RKANPARU members accordingly. However, do this with extreme caution as this member is not normally altered in any way.
4. Restart your Tivoli Enterprise Monitoring Server by entering the following command:

   S cccccccc

   where cccccccc is the name of your Tivoli Enterprise Monitoring Server started task.