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.
SET RESOURCE(CMF)
COMP
$KEY($$CTBEDM.qname) TYPE(CMF)
UID(USERA) ALLOW
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.
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 |