MONITOR command: Subsystems

From m204wiki
Revision as of 18:31, 30 October 2017 by JAL (talk | contribs) (misc formatting)
Jump to navigation Jump to search

Summary

Privileges
System administrator
Function
Displays a list of active subsystems and information about those subsystems.

Syntax

MONITOR SUBSYSTEM [(option [[,] option]...)] { name [FROM location] | LIKE 'pattern' [FROM 'loc-pattern'] }

Where:

name The name of a subsystem.
location In information about Parallel Query Option/204 service subsystems, the value of the client CCAIN LOCATION parameter. location is also the value of the CLNT field in the LOGWHO command output.
LIKE pattern Displays the specified information for subsystems whose names match the designated pattern. The pattern must be enclosed in single quotes. An asterisk (*) finds all.
loc-pattern In information about PQO service subsystems, matches a client CCAIN LOCATION parameter. An asterisk (*), meaning all nonlocal locations, is a valid value for loc-pattern. If you use this pattern matching, you must specify a pattern for both the subsystem name and location, and you can only match remote location names.
option A term from the "MONITOR SUBSYSTEM options" table, below (options must be enclosed in parentheses).

Usage notes

If you have both client and server subsystems, you can monitor both, but only one at a time:

  • FROM location looks only for server subsystems.
  • A name only or loc pattern looks only for client or local systems.
MONITOR SUBSYSTEM options
Option Displays the following information...
LIKE * Name of each subsystem.
STATUS

SUBSYSTEM: subsysname STATUS: status NUMBER OF USERS: n

where status can be:

ACTIVE, Subsystem is active

STOPPED, Subsystem is stopped

STOPPING, Subsystem is being stopped

TEST, Subsystem is in test mode

FILELIST Name of each subsystem with the name of each file within each subsystem.
FILESTATUS

SUBSYSTEM: subsysname FILE: filename, STATUS=status, NUSERS=n, DFRD UPDATE=x,
MANDATORY or OPTIONAL, AUTOMATIC or MANUAL

where:

filename includes AT location for PQO remote files.

status can be:

OPEN, file is open.

CLOSED, file is closed.

STOPPING, Subsystem is being stopped and the file is closing.

DFRD UPDATE, whether the file is a deferred update file, and x = Y (yes) or N (no).

MANDATORY or OPTIONAL, whether the file is required.

AUTOMATIC or MANUAL, whether the file is opened automatically at subsystem activation or must be opened explicitly with OPEN or OPENC.

PROCCT

SUBSYSTEM: subsysname
NUMBER OF PRECOMPILABLE PROCEDURES (SAVED): n
NUMBER OF PRECOMPILABLE PROCEDURES (NOT SAVED): n
NUMBER OF NON-PRECOMPILABLE PROCEDURES: n
NUMBER OF REQUESTS MADE RESIDENT: n
NUMBER OF ELIGIBLE REQUESTS NOT RESIDENT: n
STORAGE USED FOR RESIDENT REQUESTS: n
NUMBER OF RESIDENT PROCEDURE EVALS: n
NUMBER OF SWITCHES FROM RESIDENT MODE: n

For information about the PQO display, see the PQO topics.

USER User number, ID, and terminal ID for each user in the subsystem.
ALL Information for options: LIST, STATUS, FILELIST, FILESTATUS, PROCCT, and USER.