MONITOR PROCESSGROUP command - Revision history

ELowell at 22:59, 28 March 2017

2017-03-28T22:59:38Z

← Older revision		Revision as of 22:59, 28 March 2017
Line 1:		Line 1:
	==Overview==		==Overview==

	For the summary, syntax, and usage notes, see [[MONITOR command: Intersystem network entities]].		For the summary, syntax, and usage notes, see [[MONITOR command: Intersystem network entities]].

	==Output==		==Output==
	<p>The output of MONITOR PROCESSGROUP is a display with two lines of headings and multiple lines of values. The upper line of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of the headings in the table below.</p>		<p>The output of <var>MONITOR PROCESSGROUP</var> is a display with two lines of headings and multiple lines of values. The upper line of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of the headings in the table below.</p>
	<table>		<table>
	<caption>MONITOR PROCESSGROUP summary line</caption>		<caption>MONITOR PROCESSGROUP summary line</caption>
Line 20:		Line 19:
	<p>One of the following:</p>		<p>One of the following:</p>
	<p>Remote LU name (blank, for CRAM SQL and IUCV SQL)</p>		<p>Remote LU name (blank, for CRAM SQL and IUCV SQL)</p>
	<p>Remote node address specified on DEFINE PROCESSGROUP</p>		<p>Remote node address specified on <var>DEFINE PROCESSGROUP</var></p>
	</td> </tr>		</td> </tr>

Line 58:		Line 57:

	</table>		</table>
	<p>The lower line of MONITOR PROCESSGROUP headings are for details of each active conversation. Detail line headings, which depend on the intersystem facility monitored, are a subset of the headings in the table below.</p>		<p>The lower line of <var>MONITOR PROCESSGROUP</var> headings are for details of each active conversation. Detail line headings, which depend on the intersystem facility monitored, are a subset of the headings in the table below.</p>
	<table>		<table>
	<caption>MONITOR PROCESSGROUP detail line</caption>		<caption>MONITOR PROCESSGROUP detail line</caption>
Line 111:		Line 110:

	</table>		</table>
	===Obsolete processgroups===		==Obsolete processgroups==
	<p>When a processgroup with an active conversation is stopped and redefined, and the new version of the processgroup is allocated to another conversation before the first one ends, there can temporarily be more than one processgroup having the same name. The following scenario results in this condition: </p>		<p>When a processgroup with an active conversation is stopped and redefined, and the new version of the processgroup is allocated to another conversation before the first one ends, there can temporarily be more than one processgroup having the same name. The following scenario results in this condition: </p>
	<ol>		<ol>
Line 119:		Line 118:

	<li>		<li>
	<p>The processgroup is stopped (STOP PROCESSGROUP command), and the conversation has not ended.</p>		<p>The processgroup is stopped (<var>STOP PROCESSGROUP</var> command), and the conversation has not ended.</p>
	</li>		</li>

	<li>		<li>
	<p>The processgroup definition is changed (DEFINE PROCESSGROUP command).</p>		<p>The processgroup definition is changed (<var>DEFINE PROCESSGROUP</var> command).</p>
	</li>		</li>

	<li>		<li>
	<p>The processgroup is started (START PROCESSGROUP command). </p>		<p>The processgroup is started (<var>START PROCESSGROUP</var> command). </p>
	</li>		</li>
	</ol>		</ol>
	<p>Now the processgroup with the active conversation is obsolete, since it no longer reflects the current definition. Any new conversations that are started with that processgroup result in the creation of another processgroup having the same name but the more current set of attributes. </p>		<p>Now the processgroup with the active conversation is obsolete, since it no longer reflects the current definition. Any new conversations that are started with that processgroup result in the creation of another processgroup having the same name but the more current set of attributes. </p>
	<p>Until the conversation with the obsolete processgroup ends, the MONITOR PROCESSGROUP command produces separate reports for each processgroup. Obsolete processgroups can be identified by an X flag in their summary line.</p>		<p>Until the conversation with the obsolete processgroup ends, the <var>MONITOR PROCESSGROUP</var> command produces separate reports for each processgroup. Obsolete processgroups can be identified by an X flag in their summary line.</p>
	==Examples==		==Examples==
	===Example of Horizon for VTAM processgroup===		===Example of Horizon for VTAM processgroup===
	<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for VTAM processgroup: </p>		<p>The following is an example of <var>MONITOR PROCESSGROUP</var> output for a Horizon for VTAM processgroup: </p>
	<p class="code"><nowiki>MONITOR PROCESSGROUP DENVER		<p class="code"><nowiki>MONITOR PROCESSGROUP DENVER
	LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS		LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS
Line 169:		Line 168:
	</ul>		</ul>
	===Example of Horizon for TCP/IP processgroup===		===Example of Horizon for TCP/IP processgroup===
	<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for TCP/IP processgroup, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.)</p>		<p>The following is an example of <var>MONITOR PROCESSGROUP</var> output for a Horizon for TCP/IP processgroup, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.)</p>
	<p class="code"><nowiki>MONITOR PROCESSGROUP ANY10		<p class="code"><nowiki>MONITOR PROCESSGROUP ANY10
	REMOTE I.D.		REMOTE I.D.
Line 199:		Line 198:
	<ul>		<ul>
	<li>		<li>
	<p>INCNLI is the current inbound conversation limit, as set on the INLIMIT parameter of DEFINE PROCESSGROUP. </p>		<p>INCNLI is the current inbound conversation limit, as set on the INLIMIT parameter of <var>DEFINE PROCESSGROUP</var>. </p>
	</li>		</li>

	<li>		<li>
	<p>OTCNLI is the current outbound conversation limit, set on the OUTLIMIT parameter of DEFINE PROCESSGROUP. </p>		<p>OTCNLI is the current outbound conversation limit, set on the OUTLIMIT parameter of <var>DEFINE PROCESSGROUP</var>. </p>
	</li>		</li>
	</ul>		</ul>
	<p>Both values may have been altered from the original INLIMIT/OUTLIMIT values by MODIFY PROCESSGROUP commands.</p>		<p>Both values may have been altered from the original INLIMIT/OUTLIMIT values by <var>MODIFY PROCESSGROUP</var> commands.</p>
	</li>		</li>

Line 218:		Line 217:

	<li>		<li>
	<p>A mask is used on the REMOTEID value of DEFINE PROCESSGROUP (see asterisk in upper line FLGS field). The mask value is 255.255.255.0. </p>		<p>A mask is used on the REMOTEID value of <var>DEFINE PROCESSGROUP</var> (see asterisk in upper line FLGS field). The mask value is 255.255.255.0. </p>
	</li>		</li>

Line 226:		Line 225:
	</ul>		</ul>
	===Example of TPROCESS processgroup===		===Example of TPROCESS processgroup===
	<p>The following is an example of MONITOR PROCESSGROUP output for a CICS TPROCESS processgroup: </p>		<p>The following is an example of <var>MONITOR PROCESSGROUP</var> output for a CICS TPROCESS processgroup: </p>
	<p class="code"><nowiki>MONITOR PROCESSGROUP PGP4CICS		<p class="code"><nowiki>MONITOR PROCESSGROUP PGP4CICS
	LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS		LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS

ELowell at 22:35, 28 March 2017

2017-03-28T22:35:43Z

← Older revision		Revision as of 22:35, 28 March 2017
Line 1:		Line 1:
			==Overview==

			For the summary, syntax, and usage notes, see [[MONITOR command: Intersystem network entities]].

			==Output==
	<p>The output of MONITOR PROCESSGROUP is a display with two lines of headings and multiple lines of values. The upper line of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of the headings in the table below.</p>		<p>The output of MONITOR PROCESSGROUP is a display with two lines of headings and multiple lines of values. The upper line of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of the headings in the table below.</p>
	<table>		<table>
	<caption>MONITOR PROCESSGROUP summary line</caption>		<caption>MONITOR PROCESSGROUP summary line</caption>

	<tr> <th>		<tr class="head"> <th>Display heading</th> <th>Meaning</th> </tr>
	<p>Display heading~~</p>~~
	</th> <th>
	<p>Meaning~~</p>~~
	</th> </tr>

	<tr> <th><var>		<tr> <th><var>
	<p>LINKNAME </p>		<p>LINKNAME </p>
Line 62:		Line 62:
	<caption>MONITOR PROCESSGROUP detail line</caption>		<caption>MONITOR PROCESSGROUP detail line</caption>

	<tr> <th>		<tr class="head"> <th>Display heading</th> <th>Meaning</th> </tr>
	<p>Display heading~~</p>~~
	</th> <th>
	<p>Meaning~~</p>~~
	</th> </tr>

	<tr> <th><var>		<tr> <th><var>
Line 115:		Line 111:

	</table>		</table>
	====Obsolete processgroups====		===Obsolete processgroups===
	<p>When a processgroup with an active conversation is stopped and redefined, and the new version of the processgroup is allocated to another conversation before the first one ends, there can temporarily be more than one processgroup having the same name. The following scenario results in this condition: </p>		<p>When a processgroup with an active conversation is stopped and redefined, and the new version of the processgroup is allocated to another conversation before the first one ends, there can temporarily be more than one processgroup having the same name. The following scenario results in this condition: </p>
	<ol>		<ol>
Line 136:		Line 132:
	<p>Now the processgroup with the active conversation is obsolete, since it no longer reflects the current definition. Any new conversations that are started with that processgroup result in the creation of another processgroup having the same name but the more current set of attributes. </p>		<p>Now the processgroup with the active conversation is obsolete, since it no longer reflects the current definition. Any new conversations that are started with that processgroup result in the creation of another processgroup having the same name but the more current set of attributes. </p>
	<p>Until the conversation with the obsolete processgroup ends, the MONITOR PROCESSGROUP command produces separate reports for each processgroup. Obsolete processgroups can be identified by an X flag in their summary line.</p>		<p>Until the conversation with the obsolete processgroup ends, the MONITOR PROCESSGROUP command produces separate reports for each processgroup. Obsolete processgroups can be identified by an X flag in their summary line.</p>
	====Example of Horizon for VTAM processgroup====		==Examples==
			===Example of Horizon for VTAM processgroup===
	<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for VTAM processgroup: </p>		<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for VTAM processgroup: </p>
	<p class="code"><nowiki>MONITOR PROCESSGROUP DENVER		<p class="code"><nowiki>MONITOR PROCESSGROUP DENVER
Line 171:		Line 168:
	</li>		</li>
	</ul>		</ul>
	====Example of Horizon for TCP/IP processgroup====		===Example of Horizon for TCP/IP processgroup===
	<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for TCP/IP processgroup, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.)</p>		<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for TCP/IP processgroup, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.)</p>
	<p class="code"><nowiki>MONITOR PROCESSGROUP ANY10		<p class="code"><nowiki>MONITOR PROCESSGROUP ANY10
Line 228:		Line 225:
	</li>		</li>
	</ul>		</ul>
	====Example of TPROCESS processgroup====		===Example of TPROCESS processgroup===
	<p>The following is an example of MONITOR PROCESSGROUP output for a CICS TPROCESS processgroup: </p>		<p>The following is an example of MONITOR PROCESSGROUP output for a CICS TPROCESS processgroup: </p>
	<p class="code"><nowiki>MONITOR PROCESSGROUP PGP4CICS		<p class="code"><nowiki>MONITOR PROCESSGROUP PGP4CICS
Line 251:		Line 248:
	<p>The process name is PS4CICS. Conversation physical sends and receives (SENDS, RECVS) are not counted. </p>		<p>The process name is PS4CICS. Conversation physical sends and receives (SENDS, RECVS) are not counted. </p>
	</li>		</li>
	</ul>		</ul>
	[[Category:Commands]]		[[Category:Commands]]

ELowell at 19:16, 28 March 2017

2017-03-28T19:16:36Z

← Older revision		Revision as of 19:16, 28 March 2017
Line 138:		Line 138:
	====Example of Horizon for VTAM processgroup====		====Example of Horizon for VTAM processgroup====
	<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for VTAM processgroup: </p>		<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for VTAM processgroup: </p>
	<p class="code">MONITOR PROCESSGROUP DENVER		<p class="code"><nowiki>MONITOR PROCESSGROUP DENVER
	LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS		LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS
	-------- ----------- ------ ------- ------- ----		-------- ----------- ------ ------- ------- ----
Line 152:		Line 152:
	----- -------- ----- ----- ----		----- -------- ----- ----- ----
	3 PROCESS1 5 4 BI		3 PROCESS1 5 4 BI
	</p>		</nowiki></p>
	<p>In the previous example:</p>		<p>In the previous example:</p>
	<ul>		<ul>
Line 173:		Line 173:
	====Example of Horizon for TCP/IP processgroup====		====Example of Horizon for TCP/IP processgroup====
	<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for TCP/IP processgroup, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.)</p>		<p>The following is an example of MONITOR PROCESSGROUP output for a Horizon for TCP/IP processgroup, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.)</p>
	<p class="code">MONITOR PROCESSGROUP ANY10		<p class="code"><nowiki>MONITOR PROCESSGROUP ANY10
	REMOTE I.D.		REMOTE I.D.
	---------------------------------------------		---------------------------------------------
Line 195:		Line 195:
	9 CCARSQL 5 5 BI 10.204.204.116 16136		9 CCARSQL 5 5 BI 10.204.204.116 16136
	> (with LOCALID=ANY on DEFINE LINK)		> (with LOCALID=ANY on DEFINE LINK)
	</p>		</nowiki></p>
	<p>In the previous example:</p>		<p>In the previous example:</p>
	<ul>		<ul>
Line 230:		Line 230:
	====Example of TPROCESS processgroup====		====Example of TPROCESS processgroup====
	<p>The following is an example of MONITOR PROCESSGROUP output for a CICS TPROCESS processgroup: </p>		<p>The following is an example of MONITOR PROCESSGROUP output for a CICS TPROCESS processgroup: </p>
	<p class="code">MONITOR PROCESSGROUP PGP4CICS		<p class="code"><nowiki>MONITOR PROCESSGROUP PGP4CICS
	LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS		LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS
	-------- ----------- ------ ------- ------- ----		-------- ----------- ------ ------- ------- ----
Line 237:		Line 237:
	----- -------- ----- ----- ----		----- -------- ----- ----- ----
	5 PS4CICS 0 0 BFO		5 PS4CICS 0 0 BFO
	</p>		</nowiki></p>
	<p>In the previous example:</p>		<p>In the previous example:</p>
	<ul>		<ul>

Alex: Automatically generated page update

2013-02-28T01:05:14Z

Automatically generated page update

New page

The output of MONITOR PROCESSGROUP is a display with two lines of headings and multiple lines of values. The upper line of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of the headings in the table below.
<table>
<caption>MONITOR PROCESSGROUP summary line</caption>

<tr> <th>
Display heading
</th> <th>
Meaning
</th> </tr>

<tr> <th><var>
LINKNAME 
</var></th> <td>
Name of associated link
</td> </tr>

<tr> <th><var>
REMOTE I.D. 
</var></th> <td>
One of the following:
Remote LU name (blank, for CRAM SQL and IUCV SQL)
Remote node address specified on DEFINE PROCESSGROUP
</td> </tr>

<tr> <th><var>
BNDSES
</var></th> <td>
Number of bound sessions
</td> </tr>

<tr> <th><var>
CONNEC
</var></th> <td>
Number of established connections
</td> </tr>

<tr> <th><var>
INCONVS 
</var></th> <td>
Number of active inbound conversations
</td> </tr>

<tr> <th><var>
OTCONVS 
</var></th> <td>
Number of active outbound conversations 
</td> </tr>

<tr> <th><var>
FLGS 
</var></th> <td>
Processgroup status flags; possible values are:
A (active)
S (stopped)
X (obsolete)
* (remote address is masked)
</td> </tr>

</table>
The lower line of MONITOR PROCESSGROUP headings are for details of each active conversation. Detail line headings, which depend on the intersystem facility monitored, are a subset of the headings in the table below.
<table>
<caption>MONITOR PROCESSGROUP detail line</caption>

<tr> <th>
Display heading
</th> <th>
Meaning
</th> </tr>

<tr> <th><var>
USER 
</var></th> <td>
External user number
</td> </tr>

<tr> <th><var>
PROCESS 
</var></th> <td>
Process name
</td> </tr>

<tr> <th><var>
SENDS 
</var></th> <td>
Number of physical sends
</td> </tr>

<tr> <th><var>
RECVS 
</var></th> <td>
Number of physical receives
</td> </tr>

<tr> <th><var>
FLGS
</var></th> <td>
Session (or connection) status flags; possible values are:
B (bound)
F (first speaker)
I (inbound)
O (outbound) 
</td> </tr>

<tr> <th><var>
REMOTE ADDRESS
</var></th> <td>
Internet address of client user
</td> </tr>

<tr> <th><var>
PORT#
</var></th> <td>
Port number of client user
</td> </tr>

</table>
====Obsolete processgroups====
When a processgroup with an active conversation is stopped and redefined, and the new version of the processgroup is allocated to another conversation before the first one ends, there can temporarily be more than one processgroup having the same name. The following scenario results in this condition: 
<ol>
<li>
A processgroup has an active conversation.
</li>

<li>
The processgroup is stopped (STOP PROCESSGROUP command), and the conversation has not ended.
</li>

<li>
The processgroup definition is changed (DEFINE PROCESSGROUP command).
</li>

<li>
The processgroup is started (START PROCESSGROUP command). 
</li>
</ol>
Now the processgroup with the active conversation is obsolete, since it no longer reflects the current definition. Any new conversations that are started with that processgroup result in the creation of another processgroup having the same name but the more current set of attributes. 
Until the conversation with the obsolete processgroup ends, the MONITOR PROCESSGROUP command produces separate reports for each processgroup. Obsolete processgroups can be identified by an X flag in their summary line.
====Example of Horizon for VTAM processgroup====
The following is an example of MONITOR PROCESSGROUP output for a Horizon for VTAM processgroup: 
MONITOR PROCESSGROUP DENVER
LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS
-------- ----------- ------ ------- ------- ----
HEADQTRS DENVM204 2 1 0 A
USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
4 PROCESS1 7 3 BI
MONITOR PROCESSGROUP DENVER
LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS
-------- ----------- ------ ------- ------- ----
HEADQTRS DENVM204 2 1 0 AX
USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
3 PROCESS1 5 4 BI

In the previous example:
<ul>
<li>
Two PROCESSGROUP reports were produced; the second report is for an obsolete processgroup with which a conversation is still active (FLAGS=AX). 
</li>

<li>
Both processgroups currently have two bound sessions (BNDSES); one of these currently has an active, inbound conversation (INCONVS=1). No outbound conversations are active (OTCONVS=0).
</li>

<li>
The conversation in the first report is inbound (FLGS=BI) and it is being held with a program running as User 4. 
</li>

<li>
The process name is PROCESS1. In the course of the conversation, the process has issued a number of physical SNA Communications Server sends and receives (SENDS, RECVS) with its remote partner DENVM204 (REMOTE I.D.). 
</li>
</ul>
====Example of Horizon for TCP/IP processgroup====
The following is an example of MONITOR PROCESSGROUP output for a Horizon for TCP/IP processgroup, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.)
MONITOR PROCESSGROUP ANY10
REMOTE I.D.
---------------------------------------------
10.0.0.0
LINKNAME INCNLI OTCNLI CONNEC INCONVS OTCONVS FLGS
-------- ------ ------ ------ ------- ------- ----
TCPSQL 4 2 1 1 0 A*
USER PROCESS SENDS RECVS FLGS REMOTE ADDRESS PORT#
----- -------- ----- ----- ---- -------------- -----
41 CCARCL 6 7 BI 16163
REMOTE ID: ::FFFF:10.204.204.116
MONITOR PROCESSGROUP ANY10
REMOTE I.D.
---------------------------------------------
10.0.0.0
LINKNAME INCNLI OTCNLI CONNEC INCONVS OTCONVS FLGS
-------- ------ ------ ------ ------- ------- ----
TCPSQL 4 2 1 1 0 A*
USER PROCESS SENDS RECVS FLGS REMOTE ADDRESS PORT#
----- -------- ----- ----- ---- -------------- -----
9 CCARSQL 5 5 BI 10.204.204.116 16136
> (with LOCALID=ANY on DEFINE LINK)

In the previous example:
<ul>
<li>
The Remote ID is placed on a separate line because, if it is an IPv6 address, its length can be up to 45 characters. Its place on the detail line has been taken by INCNLI and OTCNLI. 
<ul>
<li>
INCNLI is the current inbound conversation limit, as set on the INLIMIT parameter of DEFINE PROCESSGROUP. 
</li>

<li>
OTCNLI is the current outbound conversation limit, set on the OUTLIMIT parameter of DEFINE PROCESSGROUP. 
</li>
</ul>
Both values may have been altered from the original INLIMIT/OUTLIMIT values by MODIFY PROCESSGROUP commands.
</li>

<li>
Processgroup ANY10 currently has one bound connection (CONNEC). 
</li>

<li>
The connection currently has an active, inbound conversation (INCONVS=1). 
</li>

<li>
A mask is used on the REMOTEID value of DEFINE PROCESSGROUP (see asterisk in upper line FLGS field). The mask value is 255.255.255.0. 
</li>

<li>
CCARSQL is the required <var class="product">Model 204</var> SQL process. In the course of the conversation, CCARSQL has issued a number of physical sends and receives (SENDS, RECVS) for user 9.
</li>
</ul>
====Example of TPROCESS processgroup====
The following is an example of MONITOR PROCESSGROUP output for a CICS TPROCESS processgroup: 
MONITOR PROCESSGROUP PGP4CICS
LINKNAME REMOTE I.D. BNDSES INCONVS OTCONVS FLGS
-------- ----------- ------ ------- ------- ----
LK4CICS 1 0 1 A
USER PROCESS SENDS RECVS FLGS
----- -------- ----- ----- ----
5 PS4CICS 0 0 BFO

In the previous example:
<ul>
<li>
The processgroup PGP4CICS has an established connection (BNDSES=1) over which there is an active conversation (FLAGS=A). The conversation was initiated by the User Language request and is considered outbound (OTCONVS=1, FLGS=BFO). 
</li>

<li>
The user thread number of the conversation is 5 (USER=5). 
</li>

<li>
The process name is PS4CICS. Conversation physical sends and receives (SENDS, RECVS) are not counted. 
</li>
</ul>
[[Category:Commands]]