Monitor Defaults

This document covers the following topics:

Setting Defaults for the Monitor

You can define defaults for the Entire Operations Monitor. The defaults must be set before the first start of the Monitor.

Start of instruction setTo set the Monitor Defaults

  1. In the object workspace, select Administration.

  2. From the context menu, select Monitor Defaults.

    A Monitor Defaults window similar to the example below opens:

    graphics/monitordefaults_administration.png

    The fields on the tabbed page General are explained in Fields: Monitor Defaults - General.

    • The read-only fields on the tabbed page Monitor Files show the default database IDs (DBID) and file numbers (FNR) of Entire Operations files currently used by the Monitor.

      Example:

      graphics/monitordefaults_files.png

  3. Make your definitions on each of the tabbed pages and choose OK.

  4. Choose OK.

    The defaults are set and become active by starting the Monitor the next time.

Fields: Monitor Defaults - General

The following table explains the modifiable fields on the tabbed page General of the Monitor Defaults window:

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.
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: Ennnnn01.

where nnnnn is the Monitor node. This field is not used, if the Monitor node is a UNIX node or Windows node.

Note:
On z/OS and BS2000 systems, this User ID must be a defined system user ID.

Prefix 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 E01 and the task number is 2, the task name will be EORE0102.

Default for the task prefix: EOR

For further information, see also Task Names in the section Entire Operations Monitor.

Notes:

  1. If you want to run several Entire Operations Monitors under one Entire System Server, you must define a different Monitor task prefix for each monitor.
  2. Monitor tasks of the same Monitor use the same prefix, but different task numbers.
  3. For z/OS, the Entire System Server event names also use these subtask names.

z/OS Event Name Syntax:

EORpppnn

where ppp is the subtask prefix, as defined in this case. The default is EOR. nn is the task number within the monitor.

Example: Monitor 1 has an empty task prefix. The events are then EOREOR01 through EOREOR99.

Monitor 2 has the task prefix A01. The events are then EORA0101 through EORA0199.

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:

This value is a default for all monitor tasks. An individual wait time can be defined for each task. These individual wait times can also be modified while the monitor tasks are running, and for the current monitor session only. For details, see Fields: Monitor Defaults - Monitor Task Profile.
Log Monitor Activity If you select this check box, additional information about Monitor activities, in particular about the activities of each Monitor task, is written to the Log periodically. Default: not selected.

Note:
The above option increases the amount of Log data.

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 selection options:

User ID of the Entire Operations monitor 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.
Network owner Network owner.
Job's submit user ID 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.

Job's submit user ID, no replace for 'DUM' Similar to Job's submit user ID, but no user ID replacement for DUM jobs.
Submit user ID same as the network owner Submit user ID must be the same as for the network owner.
Submit user ID same as the last mod. user Submit user ID must be the same as for the last modifying user.

Note:
With User ID of the Entire Operations monitor, no specific security profiles are possible for the submitted jobs. This setting is a global default. You may define the submit security user type individually for any node, if this is necessary.

Using the Monitor Task Profile

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.

Start of instruction set To assign Monitor functions

  1. In the Monitor Defaults window, open the tabbed page Monitor Task Profile.

    A matrix table with a list of all Monitor functions and tasks is displayed as shown in the example below:

    graphics/monitordefaults_task_prof.png

  2. Select each function in the Task # column you want to assign to the Monitor.

    For details, see Fields: Monitor Defaults - Monitor Task Profile.

  3. Select Task Reconfiguration and choose Apply or OK if you want the changes to take immediate effect.

    Otherwise, the changes take effect at the next Monitor start.

This section covers the following topics:

Fields: Monitor Defaults - Monitor Task Profile

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.

Suspended Normally, each function is assigned to a task. If required, for example, for disaster recovery, you can disable a function in the Suspended column by selecting the check box next to the required function (see 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:
In this case, you modify the default settings only. If you want to modify the settings of the current monitor session, you must do this in the Monitor Status window (see Display Monitor Task Status).

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).
Task Reconfiguration Select this check box (default) to immediately change the Monitor defaults.

Otherwise, the changes take effect at the next Monitor start.

Using Tasks

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 NATNUMSUB in 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.

Note:
All tasks use the same database files.

For more information, see Display Monitor Task Status.