Step 1 Implement Control-M/Analyzer Security

Follow the steps below to implement Control‑M/Analyzer security.

Step 1.1 Grant Access Permissions

Collect the data you need to define the INCONTROL entities and user authorizations to the security product.

In ICE, run the steps "Control‑M/Analyzer Security Definitions (Sample)" and "Functions Security Definitions (Sample)" to create two sample jobs.

Step 1.2 Customize Security Parameters

Table 67 Control‑M/Analyzer Modes

Mode	Definition
DEFMCHKB	When choosing a definition mode as COND to any of the Control‑M/Analyzer security modules, use qname together with the value given to this parameter as the high level qualifier, to determine the real definition mode to be used.
SECTOLB	Determine the action to perform if your security product is inactive or a specific resource is not defined to the security product.Valid values are: YES — Perform the action. NO — Do not perform the action.
Mode Definition	Specify one of the following values to determine the Definition mode for the Control‑M/Analyzer security modules: COND-Conditional Definition mode. Default. BASIC-Basic Definition mode. EXTEND-Extended Definition mode.
DFMB01	Definition mode for the CTBSE01 Control‑M/Analyzer security module.
DFMB03	Definition mode for the CTBSE03 Control‑M/Analyzer security module.
DFMB04	Definition mode for the CTBSE04 Control‑M/Analyzer security module.
DFMB08	Definition mode for the CTBSE08 Control‑M/Analyzer security module.

Step 1.3 Save Security Parameters into Product

This step saves all the security parameters specified for Control‑M/Analyzer.