Reviewing NetView security for Access NV operator IDs

In Creating-DSIPARM-member-NAIOPT00, you added OPER01= through OPERxx= statements, which are operator IDs defined to NetView and that NetView uses to run commands and EXECs that originate from the following sources:

  • EXECs running in BMC AMI Ops Automation PAS that include the IMFEXEC NETVIEW command
  • BMC AMI OpsA Rules that specify a NV command as part of the defined Action Specification for the Rule

Related topic

Implementing-BMC-AMI-Ops-Automation-Access-NV

You must authorize these operator IDs that are defined to NetView to run any commands or EXECs that originate from BMC AMI OpsA. You must also authorize the operator IDs to use the STOP and START commands because these commands may be used internally by BMC AMI OpsA without specifying them as a NetView Command or that may be used within a NetView EXEC.

In other words, these operator IDs must be defined to have enough NetView authority to perform any command requested from BMC AMI OpsA.

Important

When NetView is accessed from a TS session, the NetView operator ID is the same as the TS user ID. Standard NetView security applies to the operator ID.

When NetView is accessed from a BMC AMI OpsA EXEC (IMFEXEC NetView), the NetView operator ID is chosen by using a least-recently used algorithm from the pool of OPERxx IDs defined in DSIPARM member NAIOPT00. Standard NetView security applies to the operator ID.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*