This section describes special global functions, control and recovery functions provided for system administrators.
Note:
Some of these functions should be used only as recovery for
uncommon situations.
Außerdem behandelt dieses Kapitel, wie Sie ein Monitor-Start-Netzwerk anlegen und benutzen können.
In addition, this section describes how to define and use a monitor start network.
(Administrator rights for owner SYSDBA required)
You can define a job network to be executed after each Monitor start and before the activation of any other job.
This section covers the following topics:
If a job network with the name MON-START is defined
under the owner SYSDBA, this network is executed exclusively at each Monitor
startup. This is called the Monitor start network.
No other job network is started until the start network is terminated correctly.
The last job of the start network must not set any condition
(but can reset conditions). During execution of the start network, the absolute
condition MON-START-RUNNING (owner SYSDBA) is set.
If any job of the start network ends not OK, this
condition remains true and blocks any other Monitor action. The condition can
be reset manually to free continuation of other processing. While the absolute
condition is active, the message Start Network still
running appears in the log and on the system console during each
Monitor pass.
The start network is intended to run exclusively before any
other network. Therefore, the absolute condition MON-START-RUNNING
(owner SYSDBA) is set at activation time.
The setting of this condition is automatically taken over by the first job of the start network. This job sets no conditions during End-of-Job checking and actions.
Note:
The absolute condition MON-START-RUNNING is to
be reset, only if the whole start network ends normally. Any other activity of
the Monitor is blocked during execution of the start network. If any error
occurs in the start network, the whole processing of other networks is blocked
until there is a manual intervention. To force the normal processing to start,
reset the condition MON-START-RUNNING manually.
You can define a job network to be executed at the start of each day (when the date changes) and before the activation of any other job. If the Monitor is not active at this time, it is executed at Monitor start time.
If a network with the name DAY-START is defined
under the owner SYSDBA, it is executed at Monitor start time.
The start network is intended to run exclusively before any
other network. Therefore, the absolute condition DAY-START-RUNNING
(owner SYSDBA) is set at activation time.
The setting of this condition is automatically taken over by the first job of the start network. This job sets no conditions during End-of-Job checking and actions.
Note:
The absolute condition DAY-START-RUNNING is to
be reset only if the whole start network ends normally. Any other activity of
the Monitor is blocked during execution of the start network. If any error
occurs in the start network, the whole processing of other networks is blocked
until there is a manual intervention. To force the normal processing to start,
reset the condition DAY-START-RUNNING manually.
The considerations in this section apply to the Monitor start network and the day start network.
While a start network is running, a warning message is repeatedly written to the log.
During the execution of the start network, the following Monitor activities are blocked:
Schedule extraction
Activation (except start network)
Cleanup
Note:
The Monitor start network and the day start network can
execute in parallel.
Some possibilities for the use of the start network are:
Preparation of symbol tables for other networks;
Activation of other networks;
Condition setting;
Any Entire System Server functions.
To access special functions
From the System Services Menu, select the Special Functions option and press ENTER.
A Special Function Selection screen appears:
16-08-30 ***** Entire Operations ***** 14:10:50
Special Function Selection
------------------------------------------------------------------------------
Cmd Function
_ Global Schedule Extraction
_ Cleanup of the Active Database
_ Control of Activity Monitoring
_ Removal of all Monitor Commands
_ Deactivation in Foreground
_ System File Adaptations for new Version
_ JCL File Password: Global Exchange
_ Force prerequisite check for jobs in Passive Wait
_ Pending Tasks
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End |
The columns on the Special Function Selection screen are explained in the following table:
| Column | Meaning |
|---|---|
| Cmd | Line command input
field.
Enter any character next to the function you want to use, and press ENTER. |
| Function | A short description of the function. |
The Entire Operations Monitor performs the following steps to activate networks:
Extracts schedules at the beginning of a new day by default.
Activates extracted job networks at or shortly before the earliest start time of the network.
Examination of schedules can be forced at any time by using the Global Schedule Extraction feature. Several schedule extractions on the same day have no influence on already extracted activations.
Note:
Any modification to a schedule automatically implies an
activation extraction for the networks linked to this schedule.
This section covers the following topics:
To add an activation date and time for schedule
extraction
On the Special Function Selection screen, mark Global Schedule Extraction with any character and press ENTER.
A Next Global Extractions window like the example below opens:
+-----------------------------------------------------------------------+ | | | Owner Network | | Next Global Extractions | | | | Cmd Date Act. Start Type | | _ 15.10.18 15:22 Global | | | | | | | | | | | | | | | | | | | | | | D Deactivate M Start Time | | PF1 Help PF2 Add PF3 End PF7 Up PF8 Down | +-----------------------------------------------------------------------+ |
The columns and line commands available in the window are explained in Columns/Fields: Global Schedule Extraction.
Choose PF2 (Add).
A Schedule Activation Extraction window opens. The fields are explained in Columns/Fields: Global Schedule Extraction.
Enter the required date and time and choose PF3 (End).
See also Date and Time Formats in the User's Guide.
The window closes, and the new date and time are listed in the Next Global Extractions window.
To modify an activation date and time for schedule
extraction
In the Next Global
Extractions window, enter the line command M
(Start Time) next to the date and time you want to change, and press
ENTER.
A Start Time Modification window opens. The fields are explained in Columns/Fields: Global Schedule Extraction.
Enter the required new date and time and choose
PF3 (End).
To delete an activation date and time for schedule
extraction
In the Next Global
Extractions window, enter the line command D
(Deactivate) next to the date and time you want to delete, and press
ENTER.
The following table describes the columns and fields contained in the Next Global Extractions and related subordinate windows.
| Column/Fields | Meaning | |
|---|---|---|
| Next Global Extractions window: | ||
| Cmd | Line command input
field.
For possible line commands, see Line Commands: Global Schedule Extraction. |
|
| Date | Date of the activation
extraction.
See also Date and Time Formats in the User's Guide. |
|
| Act. | Time of the activation
extraction.
See also Date and Time Formats in the User's Guide. |
|
| Start | Time at which the job network was started in the operating system. | |
| Type | Status of network
activation processing.
Possible status values:
Global schedule, active on demand |
|
| Schedule Activation Extraction window: | ||
| Date/Time | Date and time to be
used for activation extraction.
See also Date and Time Formats in the User's Guide. |
|
| Start Time Modification window: | ||
| Start planned/new | The planned (old) start
time previously set and the new start time to be used instead.
For valid input values, see Date and Time Formats in the User's Guide. |
|
| Keep predefined Job Time Frames | Adapt the job time
frames.
Possible values: |
|
N |
All job time frames are adapted (default). | |
Y |
Jobs with master time frame definitions are not adapted. | |
| Line Command | Description |
|---|---|
D |
Deactivate.
Cancel the planned or scheduled network activation. |
M |
Start time.
Opens the Start Time Modification window to change the network start time. |
Normally, the active database is cleaned automatically every time the Entire Operations Monitor starts up or at the beginning of a new day.
An immediate cleanup of the active database can be triggered at any time. It is executed by the Entire Operations Monitor (in the background). This cleanup removes expired active job entries, pending tasks, log records, and related material from the Entire Operations database file. The retention periods of the Entire Operations default settings (see Default Setting (1)) are used.
Alternatively, the cleanup of the active database can be performed in batch mode. See Cleanup of the Active Database in Batch Mode described in the User's Guide.
All operations performed during the cleanup are recorded in the Entire Operations log.
To clean up the active database
On the Special Function Selection screen, mark Cleanup of the Active Database with any character and press ENTER.
A window like the following opens:
+-------------------------------------------------------------+ | | | Please confirm | | Active Database Cleanup | | by entering CLEANUP | | ==> ______________________________ | | PF3 End | +-------------------------------------------------------------+ |
Confirm the cleanup by entering
CLEANUP and pressing ENTER.
This function allows interaction with non-conversational Entire Operations activity monitoring displays started on other terminals. They can be stopped, or the interval time can be modified.
This section covers the following topics:
To view and change the activity monitoring settings
On the Special Function Selection screen, mark Control of Activity Monitoring with any character and press ENTER.
An Entire Operations Activity Monitoring window like the following opens:
+------------------------------------------+ ! ! ! Entire Operations Activity Monitoring ! ! ! ! on Terminal ==> DAEFTCG1 ! ! ! ! Stop ==> _ (mark) ! ! ! ! Start at ==> 05.11.08 14:37:08 ! ! Interval ==> 10_____ Seconds ! ! ! ! PF3 End PF10 Delete Entry ! +------------------------------------------+ |
If required, changes the entries. The input fields are explained in Fields: Entire Operations Activity Monitoring.
Press ENTER to confirm all entries.
The fields in the Entire Operations Activity Monitoring window are explained in the following table:
| Field | Meaning |
|---|---|
| on Terminal | Terminal to be handled.
Enter an asterisk ( |
| Stop | Mark this field with any character to stop activity monitoring for the selected terminal. |
| Start at | Modify the date and
time to specify when the display of activities will restart.
For valid input values, see Date and Time Formats in the User's Guide. |
| Interval | Interval, in seconds, between updates of the automatic display for the selected terminal. |
See Monitoring Entire Operation Activities in the User's Guide for details.
This function removes all internal commands from the internal Entire Operations Monitor command queue.
 |
Warning: Use this function only in case of emergency and with extreme care. |
To remove all Monitor commands
On the Special Function Selection screen, mark Removal of all Monitor Commands with any character and press ENTER.
A window like the following opens:
+-------------------------------------------------------------+ | | | Please confirm | | Monitor Command Cleanup | | by entering MONITOR COMMAND | | ==> ______________________________ | | PF3 End | +-------------------------------------------------------------+ |
Confirm the removal by entering MONITOR
COMMAND and pressing ENTER.
Usually, job deactivation is triggered in the foreground and executed by the Entire Operations Monitor in the background.
|
Warning: Use this function to deactivate active jobs in the foreground only in case of emergency, and if the Entire Operations Monitor is not active. |
To deactivate jobs
On the Special Function Selection screen, mark Deactivation in Foreground with any character and press ENTER.
A window like the following opens:
+-------------------------------------------------------------+ | | | Please confirm | | Job Deactivation | | by entering DEACTIVATION | | ==> ______________________________ | | PF3 End | +-------------------------------------------------------------+ |
Confirm deactivation by entering
DEACTIVATION and pressing ENTER.
The Entire Operations system file is usually automatically modified to the needs of a new version of Entire Operations at the first startup of the Entire Operations Monitor. The modification can be forced online by this function.
To perform data adaptation
On the Special Function Selection screen, mark System File Adaptations for new Version with any character and press ENTER.
A window like the following opens:
+----------------------------------------------+ ! ! ! Please confirm ! ! Data Adaption ! ! by entering SYSTEM FILE ! ! ==> ______________________________ ! ! PF3 End ! +----------------------------------------------+ |
Confirm system file adaptation by entering
SYSTEM FILE and pressing ENTER.
The JCL File Password: Global Exchange function allows the system administrator to exchange the file password for all definitions of a given file. This function should be used after the modification of a file password on the operating system level.
To exchange the JCL file password
On the Special Function Selection screen, mark JCL File Password: Global Exchange with any character and press ENTER.
A window like the following opens:
+-----------------------------------------------------------------------+ | | | Global File Password Exchange | | | | JCL Node ===> _____ | | File ===> ______________________________________________________ | | Password ===> | | | | PF1 Help PF3 End | +-----------------------------------------------------------------------+ |
Enter the required values. The input fields are explained in Fields: Global File Password Exchange.
This section covers the following topics:
| Field | Meaning |
|---|---|
| JCL Node | Number of the Entire System Server node on which the file can be accessed. |
| File | The password for the file specified here will be exchanged in all job definitions. |
| Password | The new replacement
password (invisible when entered).
This password must then be used when editing or selecting members, as well as for JCL loading of the Monitor. |
This function forces an active prerequisite check for all jobs which have been set to the status passive wait.
To force a prerequisite check
On the Special Function Selection screen, mark Force prerequisite check for jobs in Passive Wait with any character and press ENTER.
A window like the following opens:
+-------------------------------------------------------------+ | | | Please confirm | | Force prerequisite check | | by entering FORCE | | ==> ______________________________ | | PF3 End | +-------------------------------------------------------------+ |
Confirm the prerequisite check forcing by entering
FORCE and pressing ENTER.
This function shows pending file delete requests.
The main reason for pending delete states are file in
use errors during a delete attempt.
Pending tasks are deleted during the next database cleanup (see the relevant section).
To view all pending tasks
On the Special Function Selection screen, mark Pending Tasks with any character and press ENTER.
If any tasks are pending, a Pending Tasks screen appears with a list of all pending tasks.
Otherwise, a message is returned indicating that no tasks are found.
The screen columns are explained in Columns: Pending Tasks.
The columns of the Pending Tasks screen are described in the following table:
| Column | Meaning | |
|---|---|---|
| Owner | Owner of the affected network. | |
| Network | Network that contains the affected job. | |
| Run | Run number of the affected job. | |
| Job | Job that references the affected file. | |
| Type | Type of delete request. Possible values: | |
O |
Online or Monitor request. | |
B |
Batch cleanup. | |
| Hours Wait | Hours since the delete request is pending. | |
| File | File affected by the delete request. | |