Entire Operations consists of the following components:
This document covers the following topics:
All definitions and information concerning any user, job network, job, and scheduling information are stored on the master database. The master database is an Adabas file. This automatically provides features such as user synchronization, data integrity, data compression, auto-extension and auto-restart capability. The stored objects can be maintained online in any environment such as Com-plete, CICS, IMS TM, TSO, TIAM and openUTM as well as on UNIX. These objects are:
User profiles;
Job network definitions;
Job definitions;
Input and output conditions;
Resource definitions;
Schedule tables;
Calendars;
Symbol tables.
Entire Operations can integrate JCL unchanged into job networks and the JCL can even remain in its original location. On z/OS, sequential data sets and PDS, LMS and z/VSE libraries are supported as well as the Natural and CA-LIBRARIAN storage types. On BS2000, the JCL can be located in SAM and ISAM files, or in LMS libraries. On UNIX operating systems, shell scripts can be included into job control by Entire Operations. On Windows, BAT files can be used.
The IMPORT function allows you to copy the JCL to the Master Database. This should always be used when required by particular backup criteria (access is then only possible through Natural Security) or if the JCL resides in the Master Database and is backed up with it.
When a job network is activated (see the User's Guide), it is copied to the active database. A network is activated (see the User's Guide) either automatically by the Entire Operations Monitor according to its scheduled date, or manually by the user on demand. The active database may thus contain several copies of the same job network, each identified by a different run number.
The following information is stored:
Current definition of scheduled job networks and their current symbol tables;
Active JCL library (this means that all JCL information is copied from external storage media such as PDS, LMS, VSE-LIBRARIAN or UNIX files to the active database)
Current status of input and output conditions;
Current job status.
The active database can be accessed and its information modified in the same way as the master database. Changes to any object in the active database are only valid for the current run of the network and do not affect the network and job definitions stored on the master database. This enables you to make modifications which are valid only for a specific production cycle.
At this point, all jobs are ready for execution according to their dependencies. They are said to be in the active database. However, not all jobs in the active database become operating system jobs: for example, dummy-type jobs or Natural programs are Entire Operations jobs which are not submitted to the operating system but executed by the Entire Operations.
You can distinguish between the following groups of jobs:
Jobs in the Entire Operations master database
(inactive Entire Operations jobs);
Jobs in the Entire Operations active database
(including jobs not submitted to the operating system);
Operating system jobs
(including jobs not defined to Entire Operations).
The orange circle contains all jobs started and controlled by Entire Operations. The blue circle contains all jobs defined to Entire Operations but not started. Entire Operations cannot control jobs that are not defined to it, and that are not started by it.
The intersection of the orange and blue circle indicates Entire Operation jobs that are ready to be started by Entire Operations.
Jobs outside Entire Operations (contained in the grey circle) run on the computer outside the control of the Entire Operations Monitor. On the other hand, Entire Operations holds information on jobs that run outside the control of the operating system.
The intersection of the grey and orange circle indicate Entire Operations jobs submitted to the operating system.
The active database is located on the Entire Operations active database and contains all operational information of the current run of the activated job networks.
You can access the active database to maintain active networks and jobs, including logical conditions, resources and scheduling parameters.
The following chapters describe how you can maintain active job networks and individual active jobs.
The Monitor is the heart of Entire Operations. The Entire Operations Monitor is a complex program that is activated periodically and checks the definitions stored in the master database for any work to do. It activates and processes networks and jobs according to their prerequisites and controls running job networks, even if they reside on the nodes of different computers.
The Monitor performs the following functions:
Automatically activates scheduled networks (copies them to the active database);
Checks time windows for job or job network execution;
Checks input conditions and resources;
Submits jobs according to their (internal) priority;
Keeps track of jobs in the various queues of the operating system;
Analyses end-of-job status, determines which events have occurred and triggers appropriate system actions (set logical conditions, send messages, start programs);
Logs all important information.
The functions of the Entire Operations Monitor can be distributed to various subfunctions (subtasks). Using subtasking, certain processing steps can run in parallel and multi-processor environments can thus be used to optimize performance. Distributing typical Monitor functions is the responsibility of the system administrator.
For further information, refer to the section Monitor Defaults in the Administration documentation.
Entire Operations initiates job processing on the underlying operating systems: jobs, tasks, scripts or Natural programs are started. Several operating systems can be served simultaneously by one Entire Operations Monitor.
The Monitor sends the appropriate requests to the Entire System Server execution node. With Entire Net-Work, the Monitor can do this across the whole network.
Entire Operations provides a logging facility which records every event during network processing. It also records all manual changes to active jobs, such as JCL corrections or updates of symbol tables. This information is available online and can be used for reporting and statistical purposes.
The log information can be selected according to job network and job, as well as according to dates and times, or even users. The log reports can also be exported into a sequential file, thus providing the opportunity for further analysis with any other tool and according to any criteria.
It is possible to define logging of JCL, job protocol and/or job-related messages for all or for some jobs.
For more information, refer to the section Log Information in the User's Guide.
A reporting facility provides a wide range of system information useful for keeping track of operations, for making scheduling decisions or even for planning future production cycles.
Reports are available on the basis of log information. They can be requested for all jobs or selected for a given date/time range, either for all terminated jobs or for abended jobs.
Descriptions of job networks are available in a brief outline and more detailed form.
A list of all jobs scheduled for a specific date can also be displayed. This makes it possible to forecast any future production date in advance.
All reports can be viewed online or printed for archiving purposes.
For more information, refer to the section Reporting in the User's Guide.
Entire Operations includes an adapted version of the Software AG Editor which can be used to create, display or modify any of the following:
JCL in the master database, either in an external file or Natural member;
JCL in the active database;
Natural programs and user exits;
Online documentation of networks, jobs and any events (e.g. scratch pad information);
Job protocols and output (in browse mode).
The Entire Operations editor allows you to handle all these data types in the same way in any operating system and run-time environment supported.