Configuring Your Product › Step 6: Set Up Security for Operator Commands (Optional)

Step 6: Set Up Security for Operator Commands (Optional)

To prevent unauthorized users from issuing CA PMO operator commands, do the following:

• Your security administrator must activate the OPERCMDS class and define the command profiles (PMO.command name) for each command you want to protect.
• Authorized users should be given READ access; all others should be given an access of NONE.
• You can also protect the STOP PMO (or P PMO) command by using the profile name PMO.STOP.

  Note: If a command has no profile, CA PMO assumes that anyone may issue it. Review the CMDSECUR member of SAMP for sample RACF commands for enabling this security.

• Specify CMDSECUR=YES to activate security. If your security package is not set up to use the system authorization facility (SAF), you must specify CMDSECUR=NO. For more information on the CMDSECUR parameter, see the chapter "Using Parameters" in the CA PMO Systems Programmer Guide.

Note: CA PMO uses the RACROUTE macro and SAF to ensure only authorized users are issuing CA PMOcommands.