MONITOR command: Subsystems: Difference between revisions
m (misc formatting) |
|||
Line 8: | Line 8: | ||
==Syntax== | ==Syntax== | ||
<p class="syntax"><b>M</b>ONITOR <b>SUBSYS</b>TEM [(< | <p class="syntax"><b>M</b>ONITOR <b>SUBSYS</b>TEM [(<span class="term">option</span> [[,] <span class="term">option</span>]...)] | ||
{< | { <span class="term">name</span> [FROM <span class="term"i>location</span>] | LIKE '<span class="term">pattern</span>' [FROM '<span class="term">loc-pattern'</span>] } | ||
</p> | </p> | ||
Line 44: | Line 43: | ||
If you have both client and server subsystems, you can monitor both, but only one at a time: | If you have both client and server subsystems, you can monitor both, but only one at a time: | ||
<ul> | <ul> | ||
<li><code>FROM location</code> looks only for server subsystems.</li> | <li><code>FROM <i>location</i></code> looks only for server subsystems.</li> | ||
<li>A name only or <var class="term">loc pattern</var> looks only for client or local systems.</li> | <li>A name only or <var class="term">loc pattern</var> looks only for client or local systems.</li> |
Revision as of 18:31, 30 October 2017
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.
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, 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 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. |