Previous Topic

Next Topic

Book Contents

Book Index

Step 4 ACF2 Security Definition Samples

Step 4.1 ControlM/Analyzer Security Definitions (Optional)

Step 4.2 Functions Security Definitions (Optional)

Step 4.3 Control Program Access to Datasets (Optional)

Select these steps to edit members CTBSSAF2, CTBSSAF3, or CTBSSAF4 in the IOA INSTWORK library.

Perform the following steps to define the required permissions.

  1. Associating users With Extended Definition Mode.
    1. Add the following ACF2 commands to define the $$CTBEDM.qname entity to ACF2, and authorize users to this entity.
    2. Define and authorize the entity: $$CTBEDM.qname to ACF2 using the following command:

      SET RESOURCE(CMF)
      COMP
      $KEY($$CTBEDM.qname) TYPE(CMF)
      UID(USERA) ALLOW

  2. Define entities and user authorizations to CA‑ACF2/SAF.

    For information about entities and user authorizations, see Control-M/Analyzer Basic Definition Security Calls, and Control-M/Analyzer Extended Definition Security Calls.

    Example

    To authorize USERA (the user ID of the Control‑M/Analyzer installer) access to a given Control‑M/Analyzer entity, use the following command:

    SET RESOURCE(CMF)
    COMP
    $KEY($$CTBnnn.qname) TYPE(CMF)
    UID(USERA) ALLOW

    where qname is the name used to assign different authorizations to different Control‑M/Analyzer environments (such as Test and Production). This parameter is specified during IOA installation.

    Set the USERA parameter to the UID string of the Control‑M/Analyzer installer.

    All entity names for each Control‑M/Analyzer protected element appear in Control-M/Analyzer Basic Definition Security Callsfor Basic Definition mode and Control-M/Analyzer Extended Definition Security Callsfor Extended Definition mode.

    For samples of user authorizations, review member CTBSSAF3 in the IOA INSTWORK library.

  3. Submit the Job

    This job must be run under a user of a ACF2/SAF administrator who has authorization to enter these ACF2 commands.

    Scan the output of the job for information and error messages produced by ACF2/SAF. All job steps must end with a condition code of 0.

Parent Topic

Implementing Control-M/Analyzer Security