Identifying security system for your runtime environment

Use the RTE_SECURITY_USER_LOGON parameter to identify the security system for your runtime environment.

The following types of security are supported:
  • RACF®, ACF2: Causes the corresponding external security package to start, which can be RACF, CA-ACF2 or TSS CA-Top Secret
  • SAF: Starts the System Authorization Facility. If you specify ACF2 as your security system, enter the fully qualified data set name of the ACF2 macro library currently in use at your site. This data set name is used to assemble the ACF2 security exit. If this field is not supplied, the default security value is set to the global value supplied for this runtime environment.

If no global value is specified, the default setting is NONE.

See Common parameters in the Reference section of OMEGAMON shared documentation, Version 6.3.0 Fix Pack 2 and above for more information about RTE_SECURITY_USER_LOGON.

After you complete and verify the configuration of your runtime environment, you can enable security, which is described in Reference: OMEGAMON security decisions.

Using the KOISUPDI member in the TKANSAM library

The KOISUPDI member in the TKANSAM library is a sample default command security table. It is used by the PARMGEN RTE batch configuration job streams, $PARSE/$PARSESV, to build the default command security table in the RKANMODU library. It can also be used in the WKANSAMU/RKANSAMU library to update a runtime environment command security table for sample job KOISUPD.

WARNING: To change the command security table for a runtime environment, copy the KOISUPDI member from the TKANSAM library to the RKANSAMU library in your runtime environment and edit it there. The KOISUPDI member in the RKANSAMU library can be used as the source input to update the runtime environment command security table in the RKANMODU library.

See more details about the security table in The OMEGAMON for IMS Classic Realtime Monitor security facility.