Active Jobs file

The Control‑M active environment contains copies of the ordered job scheduling definitions and the status of those jobs. Accessible using option 3 in the IOA Primary Option menu.

The Active Jobs file must not be placed under the control of a product that does not support BDAM file structure, such as Hiperbatch or DLF.

Journal files

The Journal files include the log of Control‑M events (JRNL) and base images of files at the time of the New Day Procedure (CKPJNL and CNDJNL). Together, the Journal files enable you to restore your Active Jobs files in case of a problem.

Job Statistics file

Job execution statistics, such as elapsed time for each job. Updated using utility CTMJSA. Accessible using option S in the Active Environment screen, which is accessed using option 3 in the IOA Primary Option menu.

Job Network file

Dependency information about jobs in the Active Jobs file. Accessible using option N in the Active Environment screen, which is accessed using option 3 in the IOA Primary Option menu.

Resources file (RES)

The Control‑M Resources file contains information on the status and availability of resources system wide. Resources and conditions can be viewed using option 4 in the IOA Primary Option menu. The following types of resources are included in this file:

Quantitative

Quantity of a resource in the system. Different jobs may require different quantities of specific resources. For example, a job may require two tape drives.

Specification of Quantitative resource requirements for a job provides a solution for the allocation of quantitative computer resources, including, for example, cartridge drives, CPU utilization, database access rate. Specification of Quantitative resource requirements increases computer throughput by controlling access to these resources, thus preventing execution bottlenecks.

Control

Shared or Exclusive usage of a specific resource. Some jobs may require a resource to be in a specific mode. For example, a backup job may require exclusive access to a specific dataset.

Specification of Control resource requirements for a job or mission provides a solution for the problem of resource sharing between different jobs. The Exclusive or Shared mode in which a Control resource is required by a job is also specified.

IOA considers the mode of resource usage required when allocating Control resources and prevents jobs whose resource usage is incompatible from executing simultaneously.

Active Missions file

The Control‑D and Control‑V active environment contains copies of pending, executing and recently executed missions, and mission status. Accessible using option A in the IOA Primary Option menu. Managed by the IOA Access Method.

User Report List files

Information about reports sent to a specific user. Reports can be selected for Online Viewing, deleted, and transferred to other users. Accessible using option U in the IOA Primary Option menu. Managed by the IOA Access Method.

Types of User Report List files:

Permanent

A list of all reports defined to Control‑D.

Active

Recently or soon to be processed reports.

Migrated

Reports migrated from DASD to various storage devices (Control‑V only).

History

Reports backed up on tape or cartridge.

Active Transfer file

Information about packets that are scheduled for transfer to a PC. Only relevant for sites with Control‑D/WebAccess Server. Accessible using option F in the IOA Primary Option menu.

Message Statistics file

List of all messages and commands detected in the system, and various information about messages. Examples include frequency, and whether the messages were suppressed. Accessible using option OM in the IOA Primary Option menu.

Automation log

Automation information about all input available to Control‑O:

• Console, IMS, and CICS messages and commands.
• Control‑O internal messages.
• Control‑O rule traces.

The Automation log can be accessed using option OL in the IOA Primary Option menu.

Global Variables library

List of all user‑defined Global variables. The members of this library are loaded when Control‑O is started These members can be defined or updated using various operator commands. A backup sequential file with the .COPY suffix also exists under the name of the specified Global Variables library.

Global Variables Database

List of all user-defined Global variables. The pools are stored in the IOA Global Variables Database files and are loaded when Control-O is started These databases can be defined or updated using various operator commands. See IOA Core.

Active Balancing file

List of all Control‑M/Analyzer missions loaded during the Control‑M/Analyzer New Day procedure and information about rule status. Accessible using option BB in the IOA Primary Option menu.

Control‑M/
Analyzer
Report file

Detailed information (Balancing report) about each invoked Control‑M/Analyzer rule. Accessed using option R in the Rule Activity screen (option BA).

Database files

Information about each Control-M/Analyzer Database variable. The Database tracks the generations, or previous and current values, of each variable.

Media Database

Information on all datasets and volumes managed by Control‑M/Tape.

Trace file

Record of activities in the Control‑M/Tape environment. Used primarily for recovery of the Media Database.

Stacking Database

Statistical information on each dataset that is used by Control‑M/Tape to estimate the amount of space required for that dataset. Information about previous generations of the dataset is used to calculate space requirements for storage of each dataset as well as to calculate the average life span of the dataset (non-specific retention criteria). Information used to calculate the average life span of the dataset include catalog, date since last access, and so on.