This section covers the following topics:
The Monitor is that component of Entire Output Management which performs all the work of generating, printing and distributing reports and bundles.
It runs as a Natural subtask under Entire System Server or as a batch job.
To invoke Monitor Management:
Enter 6 in the command line of the
System Administration menu.
The Monitor Management screen is displayed:
17:01:46 **** ENTIRE OUTPUT MANAGEMENT **** 2018-11-20
User ID XYZ - Monitor Management -
Status / Tasks active Idle
at 17:00:12 2018-11-20
S Start Monitor Section
C Close Monitor
L Display Monitor Log
D Display Monitor Log by Date/Time
P Purge Monitor Buffer Pool
E Purge a single Buffer Pool Entry
+-------------------------------------------------+
: ---------- Main Task Parameters ----------- :
: Monitor Node ........ Monitor 40 :
: Minimum Wait ........ 2___ seconds :
: Maximum Wait ........ 300_ seconds :
: Wait Increment ...... 1___ seconds :
: Current Wait ........ 169 seconds :
+-------------------------------------------------+
Command => ___________________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help Exit Flip Tasks Stat Wake Menu
|
It shows the Monitor status and the date/time when the Monitor was last active.
If more than one task is active, the Status field shows the task number which are currently active. For more task information, you press PF8 (see Managing the Monitor Tasks)
The available functions are described below.
You can change the Main Task Parameters as described under Modifying the Monitor Parameters.
The Monitor status can be one of the following:
Abended
Analyzing report sources
Analyzing Unix nodes
Cataloging Natural srce.
Checking defined events
Closed
Controlling print jobs
Controlling print tasks
Creating active reports
Deleting report sources
Exporting objects
Idle
Inactive
Initializing
Loading sources into DB
Processing bundles
Processing printouts
Processing spool queue
Purging expired archives
Purging expired bundles
Purging expired logs
Purging exprd. printouts
Purging expired reports
Purging NAT buffer pool
Reactivating susp. nodes
Restaring after error
Scheduler active
Shutting down
Starting archiving
Starting condensing
Starting monitor cycle
Starting Natural subtask
Starting reviving
To modify the monitor parameters:
Enter 6 in the command line of the
System Administration menu.
The Monitor Management screen is displayed, showing the monitor parameter settings.
These main task parameters are explained below. You can change their settings as desired.
| Parameter | Explanation |
|---|---|
| Monitor Node | The node under which Entire Output Management is running. |
| Minimum Wait | The minimum time (in seconds) the Monitor is to wait between two consecutive monitoring cycles. You can modify this value by entering a new value. |
| Maximum Wait | The maximum time (in seconds) the Monitor is to wait between two consecutive monitoring cycles. You can modify this value by entering a new value. |
| Wait Increment | The number of seconds by which the wait time increases. If there is no activity during the minimum wait time, the wait time is increased by this value, until the maximum is reached. When activity occurs, the wait time returns to the minimum. You can modify this value by entering a new value. |
| Current Wait | The wait time in effect for the current cycle (in seconds). |
See also Wait Factor under Monitor Defaults.
To start the Monitor, the Entire System Server node specified for start must be active.
To start the Monitor:
Enter S in the command line.
A message confirms the start, and the Monitor status changes accordingly.
The corresponding console messages will be displayed:
NOM1510 Monitor initialization completed successfully. NOM1603 Monitor NOMXTS dbid fnr on node node started.
To activate the Monitor before the next scheduled activity cycle, see Wait parameters under Main Task Parameters.
To activate the Monitor:
Press PF10 (Wake) on the Monitor Management screen.
The Monitor is activated.
When you press ENTER, the at field (see above) displays the time when the Monitor became active.
If there was any pending work, the Monitor status changes. When the activity cycle is completed, the Monitor status changes back to "Idle".
To close the Monitor:
Enter C in the command line of
the Monitor Management screen.
A window is displayed, in which you enter
SHUTDOWN to confirm the shutdown.
The Monitor status changes to "Shutdown In Progress". This means that the Monitor has not yet detected the close, since it is in wait status. The next time it is active, the Monitor detects the close and performs the normal close. The status then changes to "Closed".
The corresponding console message will be displayed:
NOM1515 Monitor shutdown completed.
Note:
For a user without administrator status to use this function, the
option "Display Monitor Log" must be set to "Y" on his/her User Profile
Definition screen.
To display the monitor log:
Enter one of the following commands in the command line of the Monitor Management screen:
L - to display the monitor log
records in descending chronological order (most recent event first).
D - to display the monitor log
records in ascending chronological order (oldest event first).
A list of all monitor log records is displayed.
If you have invoked the list with
D, you can make date/time specifications on the
screen to restrict the range of records listed.
To display more information about a log entry, enter the
command IN in the command line preceding the
entry.
See also LO under
Commonly Used
Line Commands in the User's
Guide.
The monitor log can also be retrieved in batch mode using the utility NOMLOG.
To do so:
Create a batch job, start Natural, and log on to the library SYSNOM.
Invoke the NOMLOG utility with the following parameters:
NOMLOG <yyyymmdd> <hhmm> <YYYYMMDD> <HHMM> <L> <T> <H> [<text>]
| Parameter | Explanation |
|---|---|
<yyyymmdd> |
From year (yyyy) month
(mm) day (dd).
|
<hhmm> |
From hour (hh) minute
(mm).
|
<YYYYMMDD> |
To year (YYYY) month
(MM) day (DD).
|
<HHMM> |
To hour (HH) minute
(MM).
|
<L> |
Language (1 = English, 2
= German).
|
<T> |
L = Log data only, T =
Trace data only, B = Both log and trace data.
|
<H> |
Write titles (Y/N). Specify
N if you want to subsequently process the output with user
utilities.
|
<text> |
A word for full text research (optional); only the messages containing this word will be printed. |
To purge the monitor buffer pool:
Enter P in the command line of the
Monitor Management screen.
All entries in the Natural Buffer Pool are purged.
To purge a single buffer pool entry:
Enter E in the command line of the
Monitor Management screen.
A window is displayed.
In this window, you enter the data for the object to be purged:
| Field | Explanation |
|---|---|
| Library | Enter the name of the library where the object to be purged is located. |
| Object | Enter the name of the object to be purged. |
| DBID | Enter the ID of the database where the object to be purged is located. |
| FNR | Enter the file number of the object to be purged. |
The object specified will be purged from the Monitor Buffer Pool.
As monitor performance is significantly worse when tracing is active, you should only activate it under the direction of Software AG Support personnel.
To start the monitor activity trace:
Enter the command TRACE ON or
T+ in the command line of the Monitor
Management screen.
A message is written to the monitor's output file to record that tracing was started.
The number of program levels to be traced is determined by the trace
level specified in the job cards of the Monitor Defaults. If the job
cards contain no level restriction, the trace activated by TRACE
ON or T+ will be across all
levels.
To stop the monitor activity trace:
Enter the command TRACE OFF or
T- in the command line of the Monitor
Management screen.
A message is written to the monitor's output file to record that tracing was stopped.
This function is used to see the current status of the monitor tasks.
To list the monitor tasks:
Press PF8 (Tasks) on the Monitor Management screen.
The Monitor Task Management screen will be displayed, showing the following information on the monitor tasks:
| Field | Explanation | |
|---|---|---|
| # | Task number. | |
| Task Status | Current task status. | |
| Action | Processing performed by the task. | |
| Last Active | Date and time the task was last active. | |
| Wait Factors (Min, Max, Incr, Curr) | The Minimum, Maximum, Increment and Current wait times for the task. You can change these values (except Current) by pressing PF8 and then overwriting the values. | |
See also Monitor Tasks under Monitor Defaults.
The following line commands can be entered in the Cmd field next to a task:
| Command | Function |
|---|---|
| C | Close the task.
If you close Task 1, all subtasks will be closed. If you close any other subtask, Task 1 will take over its work. |
| W | Wake the task to perform its processing cycle. |
| P | Purge the Natural buffer pool of the task. |
| E | Purge a single object from the Natural buffer pool of the task. |
| L | Display log entries for the task. |
| + | Activate monitor trace for the task. |
| - | Deactivate monitor trace for the task. |
This function is used to see the current activities of all monitor tasks.
To display the monitor activities:
Press PF9 (Stat) on the Monitor Management screen.
The Monitor Activities screen will be displayed, showing the following information on the monitor tasks
| Field | Explanation | |
|---|---|---|
| Monitor node / status / wait time / at | The node and status of the main task. | |
| Current data node | The node from which the print data are read. | |
| System / Spool type | The operating system and spool type of the current node. | |
| NPR user ID (MF nodes) | The user ID which is logged on the Entire System Server node (if it is a mainframe node). | |
| Next orders: Action | The current action which is active or queued. | |
| Report | The report (or other object) processed by the action. | |
| By | The number of the task which processes the action. | |
| Schd. | The time when the action is scheduled. | |
| Rtry | The number of retries if the action is executed repeatedly. | |