Modifying the security table

You must edit the security table manually to modify it. You can edit the control statements and run the job manually. You must repeat this task for each runtime environment that requires OMEGAMON security.

1. To modify the internal security table, complete the following steps for PARMGEN and Configuration Manager respectively:
   1. For PARMGEN, edit the control statements in the KOMSUPDI member of &rhilev.&rte.RKANSAMU.
   2. For Configuration Manager, edit the control statements in the KOMSUPDI member of &rhilev.&rte.SECEXITS.
      The SECEXITS dataset name is defined in CFM variable RTE_X_SECURITY_EXIT_LIB

   These control statements are described in OMEGAMON security control statements. Add the LIST=YES statement to create a complete listing of security information.

2. To switch from external security to internal security, complete the following steps:
   1. Add the RESET=MODULE command after your existing MODULE=xxxxxxxx command.
   2. Change commands marked EXTERNAL=YES to EXTERNAL=NO.
3. To update and report on the security table, complete the following steps:
   1. For PARMGEN, modify and submit the &rhilev.&rte.RKANSAMU(KOMSUPD) job.
   2. For Configuration Manager, submit GENERATE or you can perform configuration processing for security exits separately from the rest of the of GENERATE workflow with OPTION SECEXITS.

      For more information, refer to Setting up security exits in your runtime environment and GENERATE options

   If the update program flags statements as being in error, correct the statements and resubmit job KOMSUPD.

   See Security update program listing for instructions on interpreting the list of the control statement modifications. The changes do not affect the currently active sessions, but any session started after KOMSUPD is run uses the new security settings.

4. Move the KOMSUPDI member to a secured data set.
5. Modify the RKANSAMU(KOMSUPD) job to point to that new data set.