This document covers the following topics:
You can define defaults for the Entire Operations Monitor. The defaults must be set before the first start of the Monitor.
To set defaults for the Monitor
Select the option Monitor Defaults from the System Services Menu.
The Monitor Defaults screen appears with a table of all current defaults:
29.09.15 ***** Entire Operations ***** 16:16:38
Owner EXAMPLE Monitor Defaults
-------------------------------------------------------------------------------
NOP Monitor Files DBID FNR Monitor Node ==> /FS/M N0146
NOP System File ==> 9 17
SAT Log ==> 9 23 Monitor Userid ==> ON/HOME/SAG/
Accounting ==> 9 25 Monitor Task Prefix ==> BIN
SAT Event Store ==> 9 50
Entire Output Mgmt ==> 9 251 Global Monitor Wait Time ==> /MONT sec.
Con-nect ==> Log Monitor Activity ==> E
FNAT ==> 9 107
FUSER ==> 9 124
FSEC ==> 9 125
Monitor JCL ==> /FS/mon/home/sag/bin/montest.bsh________________
OS Spool Class ==> X_______ Submit Security User Type ==> V
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Tasks Menu |
The database IDs (DBID) and file numbers (FNR) of Entire Operations files at the top left of the screen are for your information and cannot be modified.
| Key | Name | Function |
|---|---|---|
| PF9 | Tasks | Define a Monitor task profile. |
The following table explains the modifiable fields of the Monitor Defaults screen:
| Field | Description | |
|---|---|---|
| Monitor Node | The Entire Operations Monitor runs under this node. The node can be the same as the default Entire System Server node. | |
| Monitor User ID | This user ID will be used for
Monitor actions which are not dependent from any job. If the field is empty,
the default will be inserted.
Default: where Note: |
|
| Monitor Task | This prefix is used for the
internal generation of Monitor subtask names.
The Entire Operations Monitor subtask names are now using the syntax (explained in Direct Command Syntax): EOR{task-prefix}{task-number}
Example: If the task prefix is Default for the task prefix: For further information, see also Task Names in the section Entire Operations Monitor. Notes:
z/OS Event Name Syntax: EORpppnn where Example: Monitor 1 has an empty task prefix. The events are then
Monitor 2 has the task prefix |
|
| Global Monitor Wait Time | The Wait Time between two monitor
cycles. This parameter sets the monitor frequency.
Example: 30. The monitor will wait 30 seconds until it will begin the next cycle. Note: |
|
| Log Monitor Activity | If you enter
Y, additional
information about Monitor activities, in particular about the activities of
each Monitor task, is written to the Log periodically. Default:
N.
Note: |
|
| Monitor JCL | For UNIX only.
The full path name of the shell script to be used for starting the Monitor. Usually the script generated during the installation procedure should be used for this purpose. File selection by wildcard is possible. |
|
| OS Spool Class | For z/OS only.
The Spool Class to be used by the Monitor for all background printouts. |
|
| Submit Security User Type | The Monitor performs an Entire
System Server logon to the submit user ID. This parameter allows you to specify
which user ID is to be taken.
Possible values: |
|
M |
Default. User ID of Entire Operations Monitor.
If the field Monitor Subtask User ID (above) is left blank and M
is specified in this case, then
SYSEORnnn1 is taken as submit user ID.
|
|
O |
Network owner. | |
U |
Submit user ID.
User ID of the person who defined the job or who made the last modification (even in the active queue). See also the sections Operating System User IDs and Default User ID Determination. |
|
V |
Similar
to U (submit user ID), but no user ID
replacement for DUM jobs.
|
|
A
|
Submit user ID must be the same as for the network owner. | |
B
|
Submit user ID must be the same as for the last modifying user. | |
|
Note: |
||
Note:
If you want to run the Entire Operations Monitor in several tasks on
z/OS and BS2000 systems, you must start the monitor as a subtask.
You can divide the Monitor into several tasks in order to:
perform some Monitor actions in parallel,
execute Natural jobs (NAT-type jobs) asynchronously.
If you want to run the Entire Operations Monitor in several tasks, you must define how the Monitor functions are to be distributed on the different Monitor tasks.
To assign Monitor functions
Press PF9 (Tasks) on the Monitor Defaults screen.
A matrix table with a list of all Monitor functions and tasks is displayed as shown in the example below:
16.09.15 ***** Entire Operations ***** 11:03:43
Monitor Task Profile
------------------------------------------------------------------------------
Task # 1 2 3 4 5 6 7 8 9 10
Schedule Extraction X _ _ _ _ _ _ _ _ _
Activation _ _ X _ _ _ _ _ _ _
JCL Loading _ X _ _ _ _ _ _ _ _
Prerequisite Check _ X _ _ _ _ _ _ _ _
Submission _ _ X _ _ _ _ _ _ _
Submission, SAP _ _ _ _ _ _ _ _ _ _ < suspended
Job Execution _ X _ _ _ _ _ _ _ _
EOJ Check X _ _ _ _ _ _ _ _ _
EOJ Actions X _ _ _ _ _ _ _ _ _
Message Sending X _ _ _ _ _ _ _ _ _
Special Actions X _ _ _ _ _ _ _ _ _
Cleanup X _ _ _ _ _ _ _ _ _
Deactivation _ _ X _ _ _ _ _ _ _
Task wait time (sec.) ___ ___ ___ ___ ___ ___ ___ ___ ___ ___ global 20
Max. Number of Natural Tasks ===> __5
Max. Idle Time of a Natural Task ===> __3 min.
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Menu |
Mark each function in the Task # column you want to assign to the Monitor.
For details, see Fields: Monitor Task Profile.
Press PF5 to save your changes.
The changes take effect at the next Monitor start.
This section covers the following topics:
| Field/Column | Meaning |
|---|---|
| Task # | The Task # column lists
all functions you can assign to the Monitor and the task number to which they
are assigned.
The default for all functions is the main task, Task 1. All tasks are performed when you start the Monitor. All tasks available are described in Using Tasks. |
Normally, each function is assigned to a task.
If required, for example, for disaster recovery, you can
disable a function by removing the mark in the corresponding Task
# column as indicated by suspended in the
previous
example. The selected function is then disabled until you
assign the task again.
|
|
| Task Wait Time (sec.) | The Wait Time between two
monitor task cycles.
This value can be defined individually for each monitor task. The value Global Monitor Wait Time from the Monitor Defaults will be used if no value is specified here. Note: |
| Max. Number of Natural Tasks | This is the maximum number of tasks for the parallel execution of asynchronous Natural programs (NAT-type). Increase this number if you want to run longer Natural programs in parallel. Default = 0 : (Natural programs are executed synchronously by Task 1). |
| Max. Idle Time of a Natural Task | A Natural task can remain active for some time after it has performed the last Natural program in its queue. This can be useful if there are many Natural programs with short execution times, and it eliminates some overhead for the starting and stopping of (sub)tasks. Default = 0 : (A Natural task terminates immediately if its queue is empty). |
| global | The global monitor wait time. |
- Main Task, Task 1
Task 1 is a general-purpose task and must always exist. It performs all functions for which no other task is defined. It is the only task which can start other tasks.
- Other General-Purpose Tasks, 2 - 50
The other tasks in the top row (Numbers 2 to 50) are called general purpose tasks. This means that each of them is capable of performing all functions. These tasks are all started at Monitor startup time. Each function can and must be performed by exactly one task.
Do not define too many Monitor tasks. If Task 1 is not sufficient for your needs, then the figure above offers an example of a possible alternative. You should not exceed 2 to 4 tasks, since resources for administration of the individual tasks must always be considered.
- Natural Tasks, 51 - 89
Natural programs (NAT-type jobs; Numbers 51 to 89) can be performed asynchronously in their own dedicated tasks. In the field Max. Number of Natural Tasks, you can specify how many of them can be active in parallel. In the field Max. Idle Time of a Natural Task, you can specify how long they should remain idle if their input queue is empty. These tasks are started if necessary.
Note:
Asynchronous end-of-job check (EJC) exits and end-of-job action (EJA) exits will be executed in the Natural Tasks too.- OGC RPC Service Task, 90
The task 90 performs background functions for the Entire Operations GUI Client (OGC). It is started automatically during monitor startup. It cannot be configured by the administrator.
- Task Names
The (sub)task names are SYSEORttnnn, where tt is the task number and nnn is the Entire System Server node number.
- Monitor Tasks and NPR
Before you specify several Monitor tasks or allow several Natural tasks, you should check the value of
NATNUMSUBin the Entire System Server startup parameters.If not enough (sub)tasks are allowed for Entire System Server, a message will be issued by Entire Operations after an attempted task start, and the task activity is taken over by the main task (Task 1). This can decrease Monitor performance.
- Dynamic Task Profile Reconfiguration
The task profile can be modified (in the Task definition), while the Monitor is running. All tasks stop briefly, then the unused tasks are stopped and the newly-defined tasks are started.
This permits adaptation to different workloads in the running Monitor.
- How Monitor Tasks Are Executed
The execution of Monitor (sub)tasks is internally controlled by the Entire System Server view Natural-SUB-TASK.
In z/OS and z/VSE, subtasks run under the Monitor Entire System Server node.
In BS2000, one batch job is run for each Monitor task.
In UNIX, each Monitor task uses a separate process.
Each task has an internal control record in the database. To display the current status of the tasks, press PF9 (Tasks) in the Entire Operations Monitor window.
Note:
All tasks use the same database files.For more information, see Display Monitor Task Status.