Step 1 Implement Control-O Security

Follow the steps below to implement Control‑O 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‑O Security Definitions (Sample)" and "Functions Security Definitions (Sample)" to create two sample jobs.
Submit the jobs to define security to IOA and Control‑O.

Step 1.2 Customize Security Parameters

Table 58 Security Parameters

Parameter	Description
DEFMCHKO	When choosing a definition mode as COND to any of the Control‑O 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.
SECTOLO	Determine which action to perform if your security product is inactive or a specific resource is not defined in 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 Control‑O security modules: COND — Conditional Definition mode. Default. BASIC — Basic Definition mode. EXTEND — Extended Definition mode.
DFMO01	Definition mode for the CTOSE01 Control‑O security module.
DFMO02	Definition mode for the CTOSE02 Control‑O security module.
DFMO03	Definition mode for the CTOSE03 Control‑O security module.
DFMO04	Definition mode for the CTOSE04 Control‑O security module.
DFMO08	Definition mode for the CTOSE08 Control‑O security module.
DFMO10	Definition mode for the CTOSE10 Control-O security module.
DFMO15	Definition mode for the CTOSE15 Control‑O security module.

Step 1.3 Save Security Parameters into Product

This step saves all the security parameters specified for Control‑O.

When this step completes, the Status column is automatically updated to COMPLETE.