MONITOR REMOTE command: Difference between revisions
m (Automatically generated page update) |
|||
| Line 95: | Line 95: | ||
====Example of Horizon CNOS remote==== | ====Example of Horizon CNOS remote==== | ||
<p>The following is an example of MONITOR REMOTE output for a Horizon CNOS remote:</p> | <p>The following is an example of MONITOR REMOTE output for a Horizon CNOS remote:</p> | ||
<p class="code">MONITOR REMOTE RMT1 | <p class="code"><nowiki>MONITOR REMOTE RMT1 | ||
LINK REMOTE I.D. BNDSES SECURITY | LINK REMOTE I.D. BNDSES SECURITY | ||
-------- ----------- ------ -------- | -------- ----------- ------ -------- | ||
| Line 104: | Line 104: | ||
SESS1 LU62C 10 5 5 0 0 0 | SESS1 LU62C 10 5 5 0 0 0 | ||
SESS2 LU62D 10 5 5 0 0 0 | SESS2 LU62D 10 5 5 0 0 0 | ||
</p> | </nowiki></p> | ||
<p>In the previous example:</p> | <p>In the previous example:</p> | ||
<ul> | <ul> | ||
Revision as of 21:07, 27 March 2017
The output of MONITOR REMOTE is a display with two lines of headings and multiple lines of values. The upper line of headings is a summary line. Its headings are a subset of those shown in the following table.
|
Display heading |
Display of summary value... |
|---|---|
|
LINK |
Name of associated link |
|
REMOTE I.D. |
Remote LU name |
|
BNDSES |
Number of currently bound sessions |
|
SECURITY |
Whether LOGIN security accepts trusted users |
The lower line of MONITOR REMOTE headings are for details of each active sessiongroup. Detail line headings are shown in the table below.
|
Display heading |
Display of detail line... |
|---|---|
|
SGROUP |
Name of associated sessiongroup |
|
MODENAME |
Name of SNA Communications Server log mode entry that specifies session characteristics |
|
MAXSES |
Maximum number of sessions allowed |
|
MINWIN |
Minimum number of guaranteed first-speaker sessions |
|
MINLOS |
Minimum number of sessions in which the remote partner is the first speaker |
|
BNDSES |
Number of currently bound sessions |
|
BNDWIN |
Number of currently bound first-speaker sessions |
|
BNDLOS |
Number of currently bound sessions in which the remote partner is the first-speaker |
Example of Horizon CNOS remote
The following is an example of MONITOR REMOTE output for a Horizon CNOS remote:
MONITOR REMOTE RMT1 LINK REMOTE I.D. BNDSES SECURITY -------- ----------- ------ -------- LINK1 CICSRE3 1 N SGROUP MODENAME MAXSES MINWIN MINLOS BNDSES BNDWIN BNDLOS -------- -------- ------ ------ ------ ------ ------ ------ SNASVCMG 2 1 1 1 1 0 SESS1 LU62C 10 5 5 0 0 0 SESS2 LU62D 10 5 5 0 0 0
In the previous example:
-
Link LINK1 has a CNOS session established with remote node CICSRE3 over which trusted logins are not accepted.
-
The SNA Communications Server mode table entry SNASVCMG is reserved for the two CNOS control sessions (MAXSES=2) between this LU and CICSRE3. The local LU is the first speaker for one of these control sessions (MINWIN) and CICSRE3 is first speaker for the other (MINLOS).
-
SESS1 and SESS2 have no bound sessions (BNDWIN=0, BNDLOS=0). Only a control session is active (BNDSES=1 for MODENAME=SNASVCMG), and the local LU is considered first speaker in this session.
-
Sessiongroup SESS1 allows a maximum of ten sessions (MAXSES), and on five of these it is the first speaker (MINWIN). None of the sessions is in use. The session characteristics are specified in SNA Communications Server mode table entry LU62C (MODENAME).
-
Sessiongroup SESS2 allows a maximum of ten sessions (MAXSES), and on five of these it is the first speaker (MINWIN). None of the sessions is in use. The session characteristics are specified in SNA Communications Server mode table entry LU62C.