Limited support

   

BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.

BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI System Administration for IMS 2.9.

Limiting access to DELTA IMS

By default, access to many DELTA IMS functions is unlimited.

To restrict product usage, you must take steps to protect the functions that you want to restrict.

Under most circumstances, you do not have to set security when initially installing DELTA IMS. Therefore, you may want to defer setting security until you have reviewed the various security methods.

DELTA IMS allows you to secure product features through either of the following methods:

  • A System Authorization Facility (SAF) interface to RACF or an equivalent product

    For more information, see the DELTA IMS User Guide.

    Note

    If you are going to restrict access to product functions via the SAF security interface, you must define the ACTIVATE resource before SAF will activate. The ACTIVATE resource provides a method to quickly activate and deactivate the interface. Users must have READ access to the ACTIVATE resource to access the product main menu. You should not define the ACTIVATE resource until you define all other resources.

    Warning

    If your site is running ACF2 and you elect not to install the SAF security interface, you must add the following SAFDEF entry to your ACF2 parameters:

             FUNCRET(4) FUNCRSN(0) ID(DELTA IMS) MODE(IGNORE)
             RACROUTE(REQUEST=AUTH CLASS=DLA#) RETCODE(4)

    Failure to add this SAFDEF entry may cause you to receive the following error message when attempting to perform any product function:

    BMCDLAnnnnnn NOT AUTHORIZED TO USE DELTA IMS

    Adding this SAFDEF entry will ensure that your existing internal product security will be used. If you decide to use the SAF security interface at a later time, you must delete this SAFDEF entry from your ACF2 parameters.

  • User access profiles

    For more information, see Implementing user access profiles.



Was this page helpful? Yes No Submitting... Thank you

Comments