MONITOR LINK command - Revision history

ELowell at 23:07, 28 March 2017

2017-03-28T23:07:12Z

← Older revision		Revision as of 23:07, 28 March 2017
Line 3:		Line 3:

	==Output==		==Output==
	<p>The output of MONITOR LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>		<p>The output of <var>MONITOR LINK</var>, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>
	<table>		<table>
	<caption>MONITOR LINK summary line</caption>		<caption>MONITOR LINK summary line</caption>
Line 104:		Line 104:

	</table>		</table>
	<p>The lower line of MONITOR LINK headings are for details of each bound session. Detail line headings are shown in the table below.</p>		<p>The lower line of <var>MONITOR LINK</var> headings are for details of each bound session. Detail line headings are shown in the table below.</p>
	<table>		<table>
	<caption>MONITOR LINK detail line</caption>		<caption>MONITOR LINK detail line</caption>
Line 170:		Line 170:
	==Examples==		==Examples==
	===Horizon for VTAM link===		===Horizon for VTAM link===
	<p> The following is an example of a MONITOR LINK display for a Horizon link: </p>		<p> The following is an example of a <var>MONITOR LINK</var> display for a Horizon link: </p>
	<p class="code"><nowiki>MONITOR LINK HEADQTRS		<p class="code"><nowiki>MONITOR LINK HEADQTRS
	LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO		LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO
Line 224:		Line 224:

	===Horizon for TCP/IP link===		===Horizon for TCP/IP link===
	<p>The following is an example of a MONITOR LINK display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) </p>		<p>The following is an example of a <var>MONITOR LINK</var> display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) </p>
	<p class="code"><nowiki>MONITOR LINK TCPSQL		<p class="code"><nowiki>MONITOR LINK TCPSQL
	LOCAL I.D.		LOCAL I.D.
Line 237:		Line 237:
	REMOTE ID: ::FFFF:10.204.204.116		REMOTE ID: ::FFFF:10.204.204.116
	</nowiki></p>		</nowiki></p>
	<p>In ~~the previous~~ example:</p>		<p>In this example:</p>
	<ul>		<ul>
	<li>		<li>
Line 277:		Line 277:
	<p> </p>		<p> </p>
	===TPROCESS link===		===TPROCESS link===
	<p>The following is an example of a MONITOR LINK display for a CICS TPROCESS link: </p>		<p>The following is an example of a <var>MONITOR LINK</var> display for a CICS TPROCESS link: </p>
	<p class="code"><nowiki>MONITOR LINK LK4CICS		<p class="code"><nowiki>MONITOR LINK LK4CICS
	LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO		LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO

ELowell at 22:47, 28 March 2017

2017-03-28T22:47:06Z

← Older revision		Revision as of 22:47, 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 LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>		<p>The output of MONITOR LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>
	<table>		<table>
	<caption>MONITOR LINK summary line</caption>		<caption>MONITOR LINK summary line</caption>

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

	<tr> <th><var>		<tr> <th><var>
	<p>LOCAL I.D. </p>		<p>LOCAL I.D. </p>
Line 83:		Line 76:
	<p>TRAN/PROTO </p>		<p>TRAN/PROTO </p>
	</var></th> <td>		</var></th> <td>
	<p>Communications transmission method and protocol. Possible transport values are:</p>		<p>Communications transmission method and protocol. Possible transport values are:</p>
	<ul>		<ul>
	<li>CRAM </li>		<li>CRAM </li>
Line 115:		Line 108:
	<caption>MONITOR LINK detail line</caption>		<caption>MONITOR LINK 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>

ELowell at 22:28, 28 March 2017

2017-03-28T22:28:29Z

← Older revision		Revision as of 22:28, 28 March 2017
Line 3:		Line 3:
	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 LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>		<p>The output of MONITOR LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>

ELowell: /* Overview */

2017-03-28T22:20:09Z

Overview

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

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

			===Output===

	<p>The output of MONITOR LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>		<p>The output of MONITOR LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>
	<table>		<table>
Line 173:		Line 178:
	</td> </tr>		</td> </tr>
	</table>		</table>

	==Examples==		==Examples==
	===Horizon for VTAM link===		===Horizon for VTAM link===

ELowell at 20:11, 28 March 2017

2017-03-28T20:11:26Z

← Older revision		Revision as of 20:11, 28 March 2017
Line 1:		Line 1:
			==Overview==
	<p>The output of MONITOR LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>		<p>The output of MONITOR LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.</p>
	<table>		<table>
Line 171:		Line 172:
	</ul>		</ul>
	</td> </tr>		</td> </tr>

	</table>		</table>
	====~~Example of~~ Horizon for VTAM link====		==Examples==
			===Horizon for VTAM link===
	<p> The following is an example of a MONITOR LINK display for a Horizon link: </p>		<p> The following is an example of a MONITOR LINK display for a Horizon link: </p>
	<p class="code"><nowiki>MONITOR LINK HEADQTRS		<p class="code"><nowiki>MONITOR LINK HEADQTRS
Line 227:		Line 228:
	</ul>		</ul>

	===~~=Example of~~ Horizon for TCP/IP link====		===Horizon for TCP/IP link===
	<p>The following is an example of a MONITOR LINK display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) </p>		<p>The following is an example of a MONITOR LINK display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) </p>
	<p class="code"><nowiki>MONITOR LINK TCPSQL		<p class="code"><nowiki>MONITOR LINK TCPSQL
Line 280:		Line 281:
	</ul>		</ul>
	<p> </p>		<p> </p>
	===~~=Example of~~ TPROCESS link====		===TPROCESS link===
	<p>The following is an example of a MONITOR LINK display for a CICS TPROCESS link: </p>		<p>The following is an example of a MONITOR LINK display for a CICS TPROCESS link: </p>
	<p class="code"><nowiki>MONITOR LINK LK4CICS		<p class="code"><nowiki>MONITOR LINK LK4CICS
Line 320:		Line 321:
	</li>		</li>
	</ul>		</ul>
	====Monitoring a CNOS link====		==Monitoring a CNOS link==
	<p>~~Starting in Version 3.2, the~~ value of the TRAN/PROTO option for CNOS is LU62. A link definition does disclose whether a link is CNOS or not. However, when there are sessions on the link, a CNOS session is denoted by an X in the FLGS column, as shown in the following example: </p>		<p>The value of the TRAN/PROTO option for CNOS is LU62. A link definition does disclose whether a link is CNOS or not. However, when there are sessions on the link, a CNOS session is denoted by an X in the FLGS column, as shown in the following example: </p>
	<p class="code"><nowiki>MONITOR LINK LULK1		<p class="code"><nowiki>MONITOR LINK LULK1
	LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO		LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO

ELowell: /* Example of Horizon for VTAM link */

2017-03-27T22:07:44Z

Example of Horizon for VTAM link

← Older revision		Revision as of 22:07, 27 March 2017
Line 183:		Line 183:
	3 PROCESS1 5 4 BI DENVER DENVM204 OBSOLETE		3 PROCESS1 5 4 BI DENVER DENVM204 OBSOLETE
	4 PROCESS1 5 4 BI DENVER DENVM204		4 PROCESS1 5 4 BI DENVER DENVM204

	</nowiki></p>		</nowiki></p>
	<p>In this example: </p>		<p>In this example: </p>
Line 227:		Line 226:
	</li>		</li>
	</ul>		</ul>

	====Example of Horizon for TCP/IP link====		====Example of Horizon for TCP/IP link====
	<p>The following is an example of a MONITOR LINK display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) </p>		<p>The following is an example of a MONITOR LINK display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) </p>

ELowell at 22:47, 25 June 2013

2013-06-25T22:47:44Z

← Older revision		Revision as of 22:47, 25 June 2013
Line 143:		Line 143:
	</var></th> <td>		</var></th> <td>
	<p>Session status flags; possible values are:</p>		<p>Session status flags; possible values are:</p>
	<p>B (bind or connection established)</p>		<ul>
	<p>F (first speaker)</p>		<li>B (bind or connection established)</li>
	<p>I (inbound)</p>		<li>F (first speaker)</li>
	<p>L (local bid is in progress)</p>		<li>I (inbound)</li>
	<p>O (outbound)</p>		<li>L (local bid is in progress)</li>
	<p>R (remote bid has been accepted)</p>		<li>O (outbound)</li>
	<p>S CNOS source (<var class="product">Model 204</var> initiated the connection)</p>		<li>R (remote bid has been accepted)</li>
	<p>T CNOS target (partner initiated the connection)</p>		<li>S CNOS source (<var class="product">Model 204</var> initiated the connection)</li>
	<p>X CNOS control session</p>		<li>T CNOS target (partner initiated the connection)</li>
			<li>X CNOS control session</li>
			</ul>
	</td> </tr>		</td> </tr>

Line 164:		Line 166:
	</var></th> <td>		</var></th> <td>
	<p>One of the following:</p>		<p>One of the following:</p>
	<p>Remote partner LU name (blank, for CRAM SQL and IUCV SQL), with the word OBSOLETE appearing to the right if the session belongs to an obsolete processgroup</p>		<ul>
	<p>Internet address of partner remote node</p>		<li>Remote partner LU name (blank, for CRAM SQL and IUCV SQL), with the word OBSOLETE appearing to the right if the session belongs to an obsolete processgroup</li>
			<li>Internet address of partner remote node</li>
			</ul>
	</td> </tr>		</td> </tr>

Line 171:		Line 175:
	====Example of Horizon for VTAM link====		====Example of Horizon for VTAM link====
	<p> The following is an example of a MONITOR LINK display for a Horizon link: </p>		<p> The following is an example of a MONITOR LINK display for a Horizon link: </p>
	<p class="code">MONITOR LINK HEADQTRS		<p class="code"><nowiki>MONITOR LINK HEADQTRS
	LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO		LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO
	---------- ------ ------ ----- ---- ----------		---------- ------ ------ ----- ---- ----------
Line 180:		Line 184:
	4 PROCESS1 5 4 BI DENVER DENVM204		4 PROCESS1 5 4 BI DENVER DENVM204

	</p>		</nowiki></p>
	<p>In this example: </p>		<p>In this example: </p>
	<ul>		<ul>
Line 225:		Line 229:
	====Example of Horizon for TCP/IP link====		====Example of Horizon for TCP/IP link====
	<p>The following is an example of a MONITOR LINK display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) </p>		<p>The following is an example of a MONITOR LINK display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) </p>
	<p class="code">MONITOR LINK TCPSQL		<p class="code"><nowiki>MONITOR LINK TCPSQL
	LOCAL I.D.		LOCAL I.D.
	----------		----------
Line 236:		Line 240:
	13 CCARCL 3 4 BI CTCP10		13 CCARCL 3 4 BI CTCP10
	REMOTE ID: ::FFFF:10.204.204.116		REMOTE ID: ::FFFF:10.204.204.116
	</p>		</nowiki></p>
	<p>In the previous example:</p>		<p>In the previous example:</p>
	<ul>		<ul>
Line 278:		Line 282:
	====Example of TPROCESS link====		====Example of TPROCESS link====
	<p>The following is an example of a MONITOR LINK display for a CICS TPROCESS link: </p>		<p>The following is an example of a MONITOR LINK display for a CICS TPROCESS link: </p>
	<p class="code">MONITOR LINK LK4CICS		<p class="code"><nowiki>MONITOR LINK LK4CICS
	LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO		LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO
	---------- ------ ------ ----- ---- ----------		---------- ------ ------ ----- ---- ----------
Line 285:		Line 289:
	----- -------- ----- ----- ---- ----------		----- -------- ----- ----- ---- ----------
	5 PS4CICS 0 0 BFO PGP4CICS		5 PS4CICS 0 0 BFO PGP4CICS
	</p>		</nowiki></p>
	<p>In this example: </p>		<p>In this example: </p>
	<ul>		<ul>
Line 318:		Line 322:
	====Monitoring a CNOS link====		====Monitoring a CNOS link====
	<p>Starting in Version 3.2, the value of the TRAN/PROTO option for CNOS is LU62. A link definition does disclose whether a link is CNOS or not. However, when there are sessions on the link, a CNOS session is denoted by an X in the FLGS column, as shown in the following example: </p>		<p>Starting in Version 3.2, the value of the TRAN/PROTO option for CNOS is LU62. A link definition does disclose whether a link is CNOS or not. However, when there are sessions on the link, a CNOS session is denoted by an X in the FLGS column, as shown in the following example: </p>
	<p class="code">MONITOR LINK LULK1		<p class="code"><nowiki>MONITOR LINK LULK1
	LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO		LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO
	---------- ------ ------ ----- ---- ----------		---------- ------ ------ ----- ---- ----------
Line 326:		Line 330:
	0 0 B CICSRE5		0 0 B CICSRE5
	0 0 BX CICSRE5		0 0 BX CICSRE5
	</p>		</nowiki></p>
	[[Category:Commands]]		[[Category:Commands]]

ELowell at 22:04, 25 June 2013

2013-06-25T22:04:33Z

← Older revision		Revision as of 22:04, 25 June 2013
Line 13:		Line 13:
	</var></th> <td>		</var></th> <td>
	<p>One of the following:</p>		<p>One of the following:</p>
	<p>Local LU name (from SNA Communications Server APPL definition) </p>		<ul>
	<p>CRAM or IUCV channel name</p>		<li>Local LU name (from SNA Communications Server APPL definition) </li>
	<p>Host machine's internet address or, if multiple addresses available, ANY</p>		<li>CRAM or IUCV channel name</li>
	<p>Blank (no meaning)</p>		<li>Host machine's internet address or, if multiple addresses available, ANY</li>
			<li>Blank (no meaning)</li>
			</ul>
	</td> </tr>		</td> </tr>

Line 23:		Line 25:
	</var></th> <td>		</var></th> <td>
	<p>One of the following:</p>		<p>One of the following:</p>
	<p>Maximum number of sessions (connections, for CRAM/IUCV) allowed</p>		<ul>
	<p>Maximum number of threads allowed (DB2THRD parameter value)</p>		<li>Maximum number of sessions (connections, for CRAM/IUCV) allowed</li>
			<li>Maximum number of threads allowed (DB2THRD parameter value)</li>
			</ul>
	</td> </tr>		</td> </tr>

Line 37:		Line 41:
	</var></th> <td>		</var></th> <td>
	<p>One of the following:</p>		<p>One of the following:</p>
	<p>Number of currently bound sessions (connections, for CRAM and IUCV)</p>		<ul>
	<p>Number of threads currently in use or on the chain</p>		<li>Number of currently bound sessions (connections, for CRAM and IUCV)</li>
			<li>Number of threads currently in use or on the chain</li>
			</ul>
	</td> </tr>		</td> </tr>

Line 51:		Line 57:
	</var></th> <td>		</var></th> <td>
	<p>One of the following:</p>		<p>One of the following:</p>
	<p>Number of active conversations</p>		<ul>
	<p>Threads currently active to DB2</p>		<li>Number of active conversations</li>
			<li>Threads currently active to DB2</li>
			</ul>
	</td> </tr>		</td> </tr>

Line 59:		Line 67:
	</var></th> <td>		</var></th> <td>
	<p>Link status flags; possible values are:</p>		<p>Link status flags; possible values are:</p>
	<p>A (active) S (stopped) C (being closed)</p>		<ul>
			<li>A (active) </li>
			<li>S (stopped) </li>
			<li>C (being closed)</li>
			</ul>
	</td> </tr>		</td> </tr>

Line 66:		Line 78:
	</var></th> <td>		</var></th> <td>
	<p>Communications transmission method and protocol. Possible transport values are:</p>		<p>Communications transmission method and protocol. Possible transport values are:</p>
	<p>CRAM IUCV LOCL (local) TCP/IP (if CMS)</p>		<ul>
	<p>TCSE/IP (if z/OS)</p>		<li>CRAM </li>
	<p>TCVS/IP (if z/VSE)</p>		<li>IUCV </li>
	<p>TERM (terminal) SNA Communications Server</p>		<li>LOCL (local) </li>
	<p>Possible protocol values are:</p>		<li>TCP/IP (if CMS)</li>
	<p>MSTR, master (for CRAM SQL, IUCV SQL, and TPROCESS) XFER, transfer (for Transfer Control) LU62, LU 6.2 (for Horizon and Parallel Query Option/204) CAF, Call Attach Facility (for UL/DB2)</p>		<li>TCSE/IP (if z/OS)</li>
			<li>TCVS/IP (if z/VSE)</li>
			<li>TERM (terminal)</li>
			<li>SNA Communications Server</li>
			<li><p>Possible protocol values are:</p>
			<ul>
			<li>MSTR, master (for CRAM SQL, IUCV SQL, and TPROCESS)</li>
			<li>XFER, transfer (for Transfer Control)</li>
			<li>LU62, LU 6.2 (for Horizon and Parallel Query Option/204)</li>
			<li>CAF, Call Attach Facility (for UL/DB2)</li>
			</ul>
			</li>
			</ul>
	</td> </tr>		</td> </tr>

Alex: Automatically generated page update

2013-02-28T01:05:12Z

Automatically generated page update

New page

The output of MONITOR LINK, except for UL/DB2, is a display with two lines of headings and multiple lines of values. The upper line (the only line for UL/DB2) of headings is a summary line. Its headings, which depend on the intersystem facility monitored, are a subset of those shown in the table below.
<table>
<caption>MONITOR LINK summary line</caption>

<tr> <th>
Display heading
</th> <th>
Displays...
</th> </tr>

<tr> <th><var>
LOCAL I.D. 
</var></th> <td>
One of the following:
Local LU name (from SNA Communications Server APPL definition) 
CRAM or IUCV channel name
Host machine's internet address or, if multiple addresses available, ANY
Blank (no meaning)
</td> </tr>

<tr> <th><var>
MAXSES
</var></th> <td>
One of the following:
Maximum number of sessions (connections, for CRAM/IUCV) allowed
Maximum number of threads allowed (DB2THRD parameter value)
</td> </tr>

<tr> <th><var>
MAXCON
</var></th> <td>
Maximum number of concurrent connections allowed
</td> </tr>

<tr> <th><var>
BNDSES
</var></th> <td>
One of the following:
Number of currently bound sessions (connections, for CRAM and IUCV)
Number of threads currently in use or on the chain
</td> </tr>

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

<tr> <th><var>
CONVS
</var></th> <td>
One of the following:
Number of active conversations
Threads currently active to DB2
</td> </tr>

<tr> <th><var>
FLGS
</var></th> <td>
Link status flags; possible values are:
A (active) S (stopped) C (being closed)
</td> </tr>

<tr> <th><var>
TRAN/PROTO 
</var></th> <td>
Communications transmission method and protocol. Possible transport values are:
CRAM IUCV LOCL (local) TCP/IP (if CMS)
TCSE/IP (if z/OS)
TCVS/IP (if z/VSE)
TERM (terminal) SNA Communications Server
Possible protocol values are:
MSTR, master (for CRAM SQL, IUCV SQL, and TPROCESS) XFER, transfer (for Transfer Control) LU62, LU 6.2 (for Horizon and Parallel Query Option/204) CAF, Call Attach Facility (for UL/DB2)
</td> </tr>

<tr> <th><var>
PORT#
</var></th> <td>
Server port number that remote clients use to connect to the link
</td> </tr>

</table>
The lower line of MONITOR LINK headings are for details of each bound session. Detail line headings are shown in the table below.
<table>
<caption>MONITOR LINK detail line</caption>

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

<tr> <th><var>
USER
</var></th> <td>
External user number (blank, if a conversation is not active)
</td> </tr>

<tr> <th><var>
PROCESS
</var></th> <td>
Process name (blank, if a conversation is not active)
</td> </tr>

<tr> <th><var>
SENDS
</var></th> <td>
Number of physical sends (zero, if a conversation is not active)
</td> </tr>

<tr> <th><var>
RECVS
</var></th> <td>
Number of physical receives (zero, if a conversation is not active)
</td> </tr>

<tr> <th><var>
FLGS 
</var></th> <td>
Session status flags; possible values are:
B (bind or connection established)
F (first speaker)
I (inbound)
L (local bid is in progress)
O (outbound)
R (remote bid has been accepted)
S CNOS source (<var class="product">Model 204</var> initiated the connection)
T CNOS target (partner initiated the connection)
X CNOS control session
</td> </tr>

<tr> <th><var>
PROCESSGRP 
</var></th> <td>
Processgroup name (the word OBSOLETE appears to the right if this is a connection that belongs to an obsolete processgroup) 
</td> </tr>

<tr> <th><var>
REMOTE I.D.
</var></th> <td>
One of the following:
Remote partner LU name (blank, for CRAM SQL and IUCV SQL), with the word OBSOLETE appearing to the right if the session belongs to an obsolete processgroup
Internet address of partner remote node
</td> </tr>

</table>
====Example of Horizon for VTAM link====
 The following is an example of a MONITOR LINK display for a Horizon link: 
MONITOR LINK HEADQTRS
LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO
---------- ------ ------ ----- ---- ----------
BOSTM204 4 2 2 A VTAM/LU62
USER PROCESS SENDS RECVS FLGS PROCESSGRP REMOTE I.D.
----- -------- ----- ----- ---- ---------- -----------
3 PROCESS1 5 4 BI DENVER DENVM204 OBSOLETE
4 PROCESS1 5 4 BI DENVER DENVM204


In this example: 
<ul>
<li>
HEADQTRS is defined to SNA Communications Server as BOSTM204. 
</li>

<li>
There can be as many as four bound sessions on this link (MAXSES=4). This limit was established by the SESSIONS parameter of the DEFINE LINK command. 
</li>

<li>
The transport mechanism is SNA Communications Server, and the communication protocol is LU 6.2 (TRAN/PROTO=VTAM/LU62).
</li>

<li>
The link is active (FLGS=A), and there are currently two bound sessions using the link (BNDSES=2), both of which have active conversations (CONVS=2).
</li>

<li>
Both sessions have active conversations using process PROCESS1. 
</li>

<li>
Each conversation has issued a number of physical SNA Communications Server sends and receives (SENDS, RECVS). 
</li>

<li>
Both conversations are inbound (FLGS=BI), and the processes belong to processgroup DENVER. That the conversations are inbound implies that process PROCESS1, which is used by these conversations, is a server process.
</li>

<li>
The HEADQTRS link is being used for conversations with the remote partner whose LU name is DENVM204 (REMOTE I.D.=DENVM204).
</li>

<li>
User 3 is running with an "obsolete" processgroup, meaning that the processgroup was stopped and a DEFINE PROCESSGROUP command was issued to change the processgroup definition for subsequent usage.
</li>

<li>
User 4 is running with the most recent version of the processgroup definition.
</li>
</ul>
====Example of Horizon for TCP/IP link====
The following is an example of a MONITOR LINK display for a Horizon for TCP/IP link, using IPv6 network addresses. (IPv6 addresses are supported on IBM z/OS systems only.) 
MONITOR LINK TCPSQL
LOCAL I.D.
----------
::
MAXCON CONNEC CONVS FLGS TRAN/PROTO PORT#
------ ------ ----- ---- ---------- -----
49 1 1 A TCSE/IP 6688
USER PROCESS SENDS RECVS FLGS PROCESSGRP REMOTE I.D.
----- -------- ----- ----- ---- ---------- -----------
13 CCARCL 3 4 BI CTCP10
REMOTE ID: ::FFFF:10.204.204.116

In the previous example:
<ul>
<li>
The Local ID has been placed on a separate line because, if IPv6, it can be up to 45 bytes in length.
</li>

<li>
There can be as many as 49 concurrent connections on this link (MAXCON=49). This limit was established by the CONNECTIONS parameter of the DEFINE LINK command. 
</li>

<li>
The transport mechanism is TCPSE, and the communication protocol is IP.
</li>

<li>
The link is active (FLGS=A), and one connection is currently established (CONNEC=1), which has an active conversation (CONVS=1).
</li>

<li>
The Horizon for TCP/IP link has a port number (PORT#) that clients use when connecting to the link.
</li>

<li>
CCARCL is the required <var class="product">Model 204</var> process. In the course of the conversations, CCARCL has issued a number of physical sends and receives (SENDS, RECVS) for user 13.
</li>

<li>
The connection has an active conversation using CCARCL. The conversation is inbound (FLGS=BI), and the process belongs to processgroup CTCP10. 
</li>

<li>
The remote address specified on the CTCP10 processgroup definition is ::FFFF:10.204.204.116. The remote ID is kept on the same line unless longer than 15 bytes, in which case it is put on a separate line.
</li>

<li>
The session partner address for user 13 is an IPv4 application, but it is held as an IPv4-mapped IPv6 address so that it can communicate with the IPv6 host.
</li>
</ul>
 
====Example of TPROCESS link====
The following is an example of a MONITOR LINK display for a CICS TPROCESS link: 
MONITOR LINK LK4CICS
LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO
---------- ------ ------ ----- ---- ----------
0 1 1 A TERM/MSTR
USER PROCESS SENDS RECVS FLGS PROCESSGRP
----- -------- ----- ----- ---- ----------
5 PS4CICS 0 0 BFO PGP4CICS

In this example: 
<ul>
<li>
TPROCESS entity definitions do not include LOCALID or REMOTEID parameters. A TPROCESS connection uses the existing terminal path (CRAM channel) between the CICS terminal and <var class="product">Model 204</var>. 
</li>

<li>
Only one connection at a time is allowed on this link. The DEFINE LINK command has no SESSIONS parameter (MAXSES=0). 
</li>

<li>
The link is active (FLGS=A), and there is currently an established connection (BNDSES=1), which has an active conversation (CONVS=1).
</li>

<li>
The user thread number (displayed in <var class="product">Model 204</var> journal/audit trail user statistics) of the conversation is 5 (USER=5).
</li>

<li>
The transport method is to use the existing CRAM channel to the CICS terminal, and the communication protocol is "Parent-Child" (TRAN/PROTO=TERM/MSTR). 
</li>

<li>
The conversation uses process PS4CICS. Conversation physical sends and receives (SENDS, RECVS) are not counted. 
</li>

<li>
In the conversation, the User Language request initiates ("first speaker") and is considered outbound (FLGS=BFO), and the process belongs to processgroup PGP4CICS. 
</li>
</ul>
====Monitoring a CNOS link====
Starting in Version 3.2, the value of the TRAN/PROTO option for CNOS is LU62. A link definition does disclose whether a link is CNOS or not. However, when there are sessions on the link, a CNOS session is denoted by an X in the FLGS column, as shown in the following example: 
MONITOR LINK LULK1
LOCAL I.D. MAXSES BNDSES CONVS FLGS TRAN/PROTO
---------- ------ ------ ----- ---- ----------
DVCNMB8 50 2 0 A VTAM/LU62
USER PROCESS SENDS RECVS FLGS PROCESSGRP REMOTE I.D.
----- -------- ----- ----- ---- ---------- -----------
0 0 B CICSRE5
0 0 BX CICSRE5

[[Category:Commands]]