Operations on IOA Conditions and Control-M Resources

Whenever a user attempts to perform an operation on IOA conditions or Control‑M resources (for example, Add, Delete), or when the operation is performed automatically, the user’s authority is checked. The following IOA conditions and Control‑M resources are checked:

• Prerequisite conditions – common IOA facilities that control tracking of conditions that must be met before activities such as job submissions are performed.
• Control resources – common Control‑M facilities that Control resource sharing between jobs.
• Quantitative resources – common Control‑M facilities that control allocation of computer resources such as tapes, CPUs, and so on, to maximize system throughput.

The security interface checks every type of operation to verify that the specified user is authorized to access a specific entity, as defined in your security product. The name of the entity is derived from the name of the condition or resource being accessed, and optionally, from the type of operation requested by the user.

For example, to access a condition called SYSCOND1 in Basic Definition mode, the user must be authorized to access the entity $$IOARES.qname.SYSCOND1. To delete a resource named SYSTAPE1 in Extended Definition mode, the user must be authorized to access the entity $$DELRES.qname.SYSTAPE1.

The IOASE07 IOA security module is invoked to verify the user’s authorization to

• Add or delete a prerequisite condition to or from the IOA Conditions file.
• Add or delete a Control resource to or from the Control‑M Resources file.
• Add, delete, or change a Quantitative resource to, from, or in the Control‑M Resources file.
• Add a prerequisite condition to the IOA Manual Conditions file.

For more information about these elements, see Basic Definition Security Calls and Extended Definition Security Calls.