MONITOR command: Subsystems: Difference between revisions

From m204wiki
Jump to navigation Jump to search
m (Automatically generated page update)
 
mNo edit summary
Line 6: Line 6:
<dd>Displays a list of active subsystems and information about those subsystems.
<dd>Displays a list of active subsystems and information about those subsystems.
</dl>
</dl>
==Syntax==
==Syntax==
<p class="syntax"><b>M</b>ONITOR <b>SUBSYS</b>TEM [(<i>option</i> [[,] <i>option</i>]...)]  
<p class="syntax"><b>M</b>ONITOR <b>SUBSYS</b>TEM [(<i>option</i> [[,] <i>option</i>]...)]  
Line 16: Line 17:
<tr>
<tr>
<th>name</th>
<th>name</th>
<td> displays the specified information for the named subsystem.</td>
<td>The name of a subsystem.</td>
</tr>
</tr>
   
   
<tr>
<tr>
<th>location</th>
<th>location</th>
<td>, to display information about Parallel Query Option/204 service subsystems, is the value of the client CCAIN LOCATION parameter. location is also the value of the CLNT field in the LOGWHO command output. </td>
<td>In information about Parallel Query Option/204 service subsystems, the value of the client CCAIN <var>LOCATION</var> parameter. <var class="term">location</var> is also the value of the <var>CLNT</var> field in the <var>LOGWHO</var> command output. </td>
</tr>
</tr>
   
   
<tr>
<tr>
<th><var>LIKE pattern</var></th>
<th nowrap><var>LIKE</var> pattern</th>
<td> displays the specified information for subsystems whose names match the designated pattern. The pattern must be enclosed in single quotes. An asterisk (*) finds all. See the <var class="product">Model&nbsp;204</var> User Language Manual for information about pattern-matching capabilities.</td>
<td>Displays the specified information for subsystems whose names match the designated pattern. The [[Record retrievals#Pattern matching|pattern]] must be enclosed in single quotes. An asterisk (<tt>*</tt>) finds all. </td>
</tr>
</tr>
   
   
<tr>
<tr>
<th>loc-pattern</th>
<th>loc-pattern</th>
<td>, to display 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. </td>
<td>In information about PQO service subsystems, matches a client CCAIN <var>LOCATION</var> parameter. An asterisk (<tt>*</tt>), meaning all nonlocal locations, is a valid value for <var class="term">loc-pattern</var>. 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. </td>
</tr>
</tr>
   
   
<tr>
<tr>
<th>option</th>
<th>option</th>
<td> is a term from the following table (options must be enclosed in parentheses).</td>
<td>A term from the "MONITOR SUBSYSTEM options" table, below (options must be enclosed in parentheses).</td>
</tr>
</tr>  
</table>
</table>
==Usage notes==
==Usage notes==
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>
<li><code>FROM location</code> looks only for server subsystems.</li>
<p>[FROM location] looks only for server subsystems.</p>
</li>
   
   
<li>
<li>A name only or <var class="term">loc pattern</var> looks only for client or local systems.</li>
<p>A name only or 'loc pattern' looks only for client or local systems.</p>
</ul>
</li>
 
</ul>
<table>
<table>
<caption>MONITOR SUBSYSTEM options</caption>
<caption>MONITOR SUBSYSTEM options</caption>
      
      
<tr> <th>
<tr class="head"> <th>Option</th>  
<p>Option</p>
<th>Displays the following information...</th> </tr>
</th> <th>
<p>Displays the following information...</p>
</th> </tr>
    
    
<tr> <th><var>
<tr> <th><var>LIKE *</var></th>  
<p>LIKE *</p>
<td>Name of each subsystem.</td> </tr>
</var></th> <td>
<p>Name of each subsystem.</p>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>STATUS</var></th>  
<p>STATUS</p>
<td><p class="syntax">SUBSYSTEM: <span class="term">subsysname</span> STATUS: <span class="term">status</span> NUMBER OF USERS: <span class="term">n</span> </p>
</var></th> <td>
<p>
<p>SUBSYSTEM: subsysname   STATUS: status   NUMBER OF USERS: n</p>
where <i>status</i> can be:</p>
<p>where <i>status</i> can be:</p>
<p>
<p>ACTIVE, Subsystem is active STOPPED, Subsystem is stopped STOPPING, Subsystem is being stopped TEST, Subsystem is in test mode</p>
ACTIVE, Subsystem is active </p>
<p>
STOPPED, Subsystem is stopped </p>
<p>
STOPPING, Subsystem is being stopped </p>
<p>
TEST, Subsystem is in test mode</p>
</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>FILELIST</var></th>  
<p>FILELIST</p>
<td>Name of each subsystem with the name of each file within each subsystem.</td> </tr>
</var></th> <td>
<p>Name of each subsystem with the name of each file within each subsystem.</p>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>FILESTATUS</var></th>  
<p>FILESTATUS</p>
<td><p class="syntax">SUBSYSTEM: <span class="term">subsysname</span> FILE: <span class="term">filename</span>, STATUS=<span class="term">status</span>, NUSERS=<span class="term">n</span>, DFRD UPDATE=<span class="term">x</span>, MANDATORY or OPTIONAL, AUTOMATIC or MANUAL </p>
</var></th> <td>
<p>
<p>SUBSYSTEM: subsysname   FILE: filename,STATUS=status,NUSERS=n,   DFRD UPDATE=x, MANDATORY or OPTIONAL,   AUTOMATIC or MANUAL</p>
where:</p>
<p>where:</p>
<p><i>filename</i> includes AT <i>location</i> for PQO remote files.</p>
<p><i>filename</i> includes AT <i>location</i> for PQO remote files</p>
<p><i>status</i> can be: </p>
<p><i>status</i> can be: OPEN, file is open CLOSED, file is closed STOPPING, Subsystem is being stopped and the file is closing</p>
<p>OPEN, file is open. </p>
<p><i>DFRD UPDATE</i> indicates whether the file is a deferred update file and <i>x </i>= Y (yes) or N (no).</p>
<p>CLOSED, file is closed. </p>
<p><i>MANDATORY</i> or <i>OPTIONAL</i> indicates whether the file is required.</p>
<p>STOPPING, Subsystem is being stopped and the file is closing.</p>
<p><i>AUTOMATIC</i> or <i>MANUAL</i> indicates whether the file is opened automatically at subsystem activation or must be opened explicitly with OPEN or OPENC.</p>
<p>DFRD UPDATE, whether the file is a deferred update file, and <i>x </i>= Y (yes) or N (no).</p>
<p>MANDATORY or OPTIONAL, whether the file is required.</p>
<p>AUTOMATIC or MANUAL, whether the file is opened automatically at subsystem activation or must be opened explicitly with <var>OPEN</var> or <var>OPENC</var>.</p>
</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>PROCCT</var></th>  
<p>PROCCT</p>
<td><p class="syntax">SUBSYSTEM: <span class="term">subsysname</span><br>NUMBER OF PRECOMPILABLE PROCEDURES (SAVED): <span class="term">n</span><br>NUMBER OF PRECOMPILABLE PROCEDURES (NOT SAVED): <span class="term">n</span><br>NUMBER OF NON-PRECOMPILABLE PROCEDURES: <span class="term">n</span><br>NUMBER OF REQUESTS MADE RESIDENT: <span class="term">n</span><br>NUMBER OF ELIGIBLE REQUESTS NOT RESIDENT: <span class="term">n</span><br>STORAGE USED FOR RESIDENT REQUESTS: <span class="term">n</span><br>NUMBER OF RESIDENT PROCEDURE EVALS: <span class="term">n</span><br>NUMBER OF SWITCHES FROM RESIDENT MODE: <span class="term">n</span> </p>
</var></th> <td>
<p>
<p>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 </p>
For information about the PQO display, see the <i>Parallel Query Option/204 User's Guide</i>. </p>
<p>For information about the PQO display, see the <i>Parallel Query Option/204 User's Guide</i>. </p>
</td> </tr>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>USER</var></th>  
<p>USER</p>
<td>User number, ID, and terminal ID for each user in the subsystem.</td> </tr>
</var></th> <td>
<p>User number, ID, and terminal ID for each user in the subsystem.</p>
</td> </tr>
   
   
<tr> <th><var>
<tr> <th><var>ALL</var></th>  
<p>ALL</p>
<td>Information for options: <var>LIST</var>, <var>STATUS</var>, <var>FILELIST</var>, <var>FILESTATUS</var>, <var>PROCCT</var>, and <var>USER</var>. </td> </tr>  
</var></th> <td>
<p>Information for options: LIST, STATUS, FILELIST, FILESTATUS, PROCCT, and USER. </p>
</td> </tr>
 
</table>
</table>
[[Category: System administrator commands]]
[[Category: System administrator commands]]
[[Category:Commands]]
[[Category:Commands]]

Revision as of 22:12, 15 April 2014

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 Parallel Query Option/204 User's Guide.

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