Monitor Defaults

#### Search Results

Search

# Monitor Defaults

This document covers the following topics:

- Setting Defaults for the Monitor

- Using Monitor Tasks

- Defining a Monitor Task Profile

- Defining Filters to Suspend Entire Operations Functions

## 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.

To set defaults for the Monitor

- From the System Services Menu, select the Monitor Defaults option and press ENTER.

  A Monitor Defaults screen like the example below appears with a table of all current defaults:

       18.09.21                ***** Entire Operations *****                11:49:02
       Owner EXAMPLE                  Monitor Defaults
      -------------------------------------------------------------------------------
        NOP Monitor Files      DBID   FNR              Monitor Node ==> 146__ N0146
          NOP System File ==>     9    18
                  SAT Log ==>     9    28           Monitor User ID ==> NOPDEV______
               Accounting ==>     9    27       Monitor Task Prefix ==> 55D
          SAT Event Store ==>     9    50
       Entire Output Mgmt ==>     9   251    Global Monitor Wait Time ==> ___10 sec.
                                                 Log Monitor Activity ==> N
                     FNAT ==>     9   107
                    FUSER ==>     9   124
                     FSEC ==>     9   125

              Monitor JCL ==> ______________________________________________________

           OS Spool Class ==> X_______      Node Security User Type ==> U

       Command => ____________________________________________________________
      Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
            Help        End         Save                    Tasks Susp        Menu

  The fields and special PF keys on the screen are explained in the Fields: Monitor Defaults and Special PF Keys: Monitor Defaults.

### Fields: Monitor Defaults

The following table explains the fields on the Monitor Defaults screen.

Field | Description
--- | ---
NOP Monitor Files | Read-only information. Entire Operations files currently used by the Monitor. The files are explained in Entire Operations Files.
DBID | Read-only information. Database ID (DBID) of an Entire Operations file currently used by the Monitor.
FNR | Read-only information. File number (FNR) of an Entire Operations file currently used by the Monitor.
Monitor Node | Node under which the Entire Operations Monitor runs. The node can be the same as the default Entire System Server node.
Monitor User ID | User ID used for Monitor actions which are not dependent on any jobs. If not specified, the Default User ID of the Monitor node will be used. If both are specified, the Default User ID of the Monitor node supersedes the Monitor User ID. This field is not used if the Monitor node is a UNIX or Windows node. Notes: If specified, this user ID must be a valid operating system user ID on the machine of the Monitor node. This field is mandatory for Monitor nodes on UNIX (Linux) or Windows.
Monitor Task Prefix | Prefix used for the internal generation of Monitor subtask names. Entire Operations Monitor subtask names use the following syntax:
    EOR{task-prefix}{task-number}
where `task-prefix` is the character string entered in this field and `task-number` the number of a defined task. 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: 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. Monitor tasks of the same Monitor use the same prefix, but different task numbers. 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. The default is `EOR`. `nn` is the task number within the Monitor. Examples: 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 | Wait time (in seconds) between two Monitor cycles. This parameter sets the Monitor frequency. Valid values: 1 to 99999 seconds. Default: 30. (The Monitor waits 30 seconds until it begins the next cycle.) Note: This value is the 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 Task Profile.
Log Monitor Activity | Write information about Monitor activities, in particular, about the activities of each Monitor task, to the log periodically. Note: This option increases the amount of log data. Possible values:
`Y` | Log additional information.
`N` | Do not log additional information (default).
Monitor JCL | For UNIX only. 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. Spool class to be used by the Monitor for all background printouts.
Node Security User Type | The Monitor performs an Entire System Server logon to this user ID. This option allows you to specify which user ID is to be taken. Possible values:
`M` | User ID of the Monitor (default). See also the field Monitor User ID.
`O` | Network owner.
`U` | Submit user ID. User ID of the user 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` | Like `U` (submit user ID), but `DUM` jobs are assigned the user ID of the Monitor in the Entire Operations log.
`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: With `M`, 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 necessary.

### Special PF Keys: Monitor Defaults

PF Key | Name | Function
--- | --- | ---
PF9 | Tasks | Define a Monitor task profile.
PF10 | Susp | Define filters to suspend Entire Operations functions.

## Using Monitor Tasks

A Monitor task defines a function to be performed by the Entire Operations Monitor.

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

Monitor tasks are defined in the Monitor Task Profile.

This section covers the following topics:

- Execution of Monitor Tasks using Entire System Server

- Dynamic Task Profile Reconfiguration

### Execution of Monitor Tasks using Entire System Server

Monitor tasks must be enabled in the Entire System Server as a subtask in the address space (z/OS) or as a pseudo subtask, that is, standalone task (BS2000).

The execution of Monitor (sub)tasks is internally controlled by the Entire System Server view `NATURAL-SUB-TASK`.

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 the 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.

In z/OS, 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, choose PF9 (Tasks) in the Entire Operations Monitor window.

Note
All tasks use the same database files.

For more information, see Status of the Entire Operations Monitor.

### Dynamic Task Profile Reconfiguration

The tasks defined in the task profile can be modified 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.

## Defining a Monitor Task Profile

To define Monitor tasks

1. Choose PF9 (Tasks) on the Monitor Defaults screen.

   A Monitor Task Profile screen like the example below appears:

       13.03.23                ***** Entire Operations *****                15:52:51
                                      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   _   _   _   _   _   _   _   _
         Job Execution            X   _   _   _   _   _   _   _   _   _
         EOJ Check                _   _   _   _   X   _   _   _   _   _
         EOJ Actions              _   _   _   _   X   _   _   _   _   _
         Message Sending          _   _   _   _   _   _   _   X   _   _
         Special Actions          _   _   X   _   _   _   _   _   _   _
         Cleanup                  _   _   X   _   _   _   _   _   _   _
         Deactivation             _   _   X   _   _   _   _   _   _   _

         Task wait time (sec.)  ___ ___ ___ ___ ___ ___ ___ ___ ___ ___  global    15

         Max. Number of Natural Tasks     ===> __7
         Max. Idle Time of a Natural Task ===> _30 min.
        Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
              Help        End         Save                                      Menu

   A matrix table with a list of all Monitor functions and tasks is displayed.

   The fields and columns on the page are explained in Fields: Monitor Task Profile.

2. In the Task # column, mark each function you want to assign to the Monitor.

   As soon as you select a task, the Task Reconfiguration option is activated.

3. Choose PF5 to save your changes.

   The changes take effect at the next Monitor start.

This section covers the following topics:

- Fields: Monitor Task Profile

- Available Monitor Tasks

### Fields: 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 are described in Available Monitor Tasks.
`suspended` | 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.) | Wait time (in seconds) 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 With this option, you modify the default settings only. If you want to modify the settings of the current Monitor session, you must do this on the Monitor Tasks screen.
Max. Number of Natural Tasks | 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 is `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 is `0`: A Natural task terminates immediately if its queue is empty.
global | Global Monitor Wait Time.

### Available Monitor 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 can perform 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 previous example shows 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

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

## Defining Filters to Suspend Entire Operations Functions

You can reduce the system workload after disaster recovery by defining object filters and determining Entire Operations functions to be suspended for the specified jobs.

For each filter, you can specify whether it is activated (enabled) immediately or only specified for future activation.

To list and define filters and suspended functions

1. On the Monitor Defaults screen, choose PF10 (Susp).

   A Suspensions screen like the example below appears:

       08.03.18                ***** Entire Operations *****                12:05:57
                                     Suspensions

              Filter for                    Suspendible
        Owner      Network     Job          Functions                   Enable

        ******************************   Top of Data    ******************************
        EXAMPLE___ *_________  JOB*______   * _ _ _ _ _ _ _ _ _ _ _ _   Y
        DEMO*_____ TEST>_____  T>________   A _ _ _ _ _ _ _ _ _ _ _ _   N
        SAGTEST___ SAGNET____  T<________   J S _ _ _ _ _ _ _ _ _ _ _   Y
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        __________ __________  __________   _ _ _ _ _ _ _ _ _ _ _ _ _   _
        ******************************* Bottom of Data *******************************

       Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
             Help        End   EnAll Save  DisAl Up    Down

   The screen lists all suspensions defined in your environment (empty if no suspensions exist).

2. Modify, add or remove a definition.

   The columns and valid input values are explained in Columns: Monitor Defaults - Suspensions.

   The special PF keys available are explained in Special PF Keys: Suspensions.

   You can delete a suspension by removing the relevant entries from the table row.

3. Choose PF5 to save your definitions.

   All enabled filters are evaluated by the Monitor when you choose PF3 and leave the function.

### Special PF Keys: Suspensions

The special PF keys available on the Suspensions screen are explained in the following table:

PF Key | Name | Function
--- | --- | ---
PF4 | EnAll | Enable (activate) all suspensions listed in the table. All entries in the Enable column change to `Y` (Yes).
PF6 | DisAl | Disable (deactivate) all suspensions listed in the table. All entries in the Enable column change to `N` (No).
PF7 | Up | Move up one row in the table.
PF8 | Down | Move down one row in the table.

### Columns: Monitor Defaults - Suspensions

The columns on the Suspensions screen are explained in the following table:

Column | Description
--- | ---
Owner | Name of an owner or a range of names. For valid range specifications, see Specifying Filter Criteria in the User's Guide.
Network | Name of a network or a range of names. For valid range specifications, see Specifying Filter Criteria in the User's Guide.
Job | Name of a job or a range of names. For valid range specifications, see Specifying Filter Criteria in the User's Guide.
Suspendible Functions | Function to be suspended. Possible values:
`A` | Activation Activate networks.
`J` | JCL loading Load JCL.
`P` | Prerequisite check Perform prerequisite checks.
`S` | Submission Submit jobs.
`U` | Job execution Execute jobs.
`E` | EOJ check Perform End-of-Job checking.
`O` | EOJ actions Perform End-of-Job actions.
`M` | Message sending Send messages.
`D` | Deactivation Deactivate networks.
`*` | All functions Perform all functions.
Enable | Enable (activate) or disable (deactivate) the functions entered in Suspendible Functions. Possible values:
`Y` | Enable function.
`N` | Disable function.
PF4 sets all filters to `Y`, PF6 sets all filters to `N`.

### On this page

- Setting Defaults for the Monitor
- Using Monitor Tasks
- Defining a Monitor Task Profile
- Defining Filters to Suspend Entire Operations Functions