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.

EOR{task-prefix}{task-number}

EORpppnn

Special PF Keys: Monitor Defaults

Using Monitor Tasks

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

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

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

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:

Columns: Monitor Defaults - Suspensions

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