Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
How security works with BMC AMI Ops products
The BMC AMI Ops environment provides an interface to ESMs (such as IBM RACF, Top Secret for z/OS, or ACF2) by using standard System Authorization Facility (SAF) calls. Two types of security are available for BMC AMI Ops products, depending on the product interface:
Additional security is available for Alternate Access, which provides access to products through VTAM and EXCP interfaces without TSO communication support. Security for Alternate Access is independent of other product security. If your site uses Alternate Access, see Controlling-Alternate-Access.
How security is defined for BMC AMI Ops SYSPROG Services, is different from other BMC AMI Ops products. The BBSEC member that contains the TYPE=SYSPROG statement must reside in SYS1.PARMLIB or the logical PARMLIB concatenation. For more information about the TYPE=SYSPROG statement, see the comments in the sample BBSEC member and TYPE=SYSPROG statement.
