Step 2.1 ControlM/Tape Security Definitions (optional)
Select this step to edit the CTTSRAC2 member in the IOA INSTWORK library.
Perform the following steps to define the required permissions.
RDEFINE FACILITY $$CTTEDM.qname UACC(NONE)
PERMIT $$CTTEDM.qname ID(USERA) CLASS(FACILITY) ACCESS(READ)
This job must be run under an administrator user ID who has authorization to enter these commands.
For information about entities and user authorizations, see Control-M/Tape Basic Definition Security Callsand Control-M/Tape Extended Definition Security Calls.
Example
To authorize USERA access to a given Control‑M/Tape entity, use the following command:
PERMIT $$CTTnnn.qname CLASS(FACILITY) ID(USERA) ACCESS(READ)
where CTTnnn is the name of the Control‑M/Tape entity to be accessed.
All entity names for each Control‑M/Tape protected element appear in Control-M/Tape Basic Definition Security Calls for Basic Definition mode and Control-M/Tape Extended Definition Security Calls for Extended Definition mode.
Step 2.2 Functions Security Definitions (Optional)
Select this step to edit the CTTSRAC3 member in the IOA INSTWORK library. This member contains definition samples for the various Control‑M/Tape entities. Modify the definitions according to the requirements of the site and submit the job.
Step 2.3 Control Program Access to Datasets (Optional)
Select this step to edit the CTTSRAC4 member in the IOA INSTWORK library. This member contains a sample of the definitions required to define Program Pathing access authorizations to Control‑M/Tape datasets. Review the definitions and modify to meet the requirements of your site.
WARNING: BMC recommends that the security administrator first read Limiting Access to Specific Programs.
Parent Topic |