DEFINE SESSIONGROUP command - Revision history

ELowell: /* Syntax notes */

2017-04-06T21:42:40Z

Syntax notes

← Older revision		Revision as of 21:42, 6 April 2017
Line 55:		Line 55:
	</table>		</table>
	===Syntax notes===		===Syntax notes===
	You can specify multiple sessiongroups with the same remote, but each must have a different mode name.		You can specify multiple sessiongroups with the same remote, but each must have a different mode name.

			<p>For general syntax and usage notes that apply to all forms of the <var>DEFINE</var> command, see <var>[[DEFINE command]]</var>.</p>

	==Example==		==Example==
	<p class="code">DEFINE SESSIONGROUP SESS1 WITH -		<p class="code">DEFINE SESSIONGROUP SESS1 WITH -

ELowell: /* Usage notes */

2016-02-04T21:36:49Z

Usage notes

← Older revision		Revision as of 21:36, 4 February 2016
Line 69:		Line 69:
	<p>The values you specify for MAXIMUM and WINNERS are maximums. CNOS negotiation rules determine the actual session limits and allotment of first-speaker sessions between the LUs sharing the sessions. Also, the two reserved CNOS control sessions are not included in CNOS session limit negotiation and should not influence your MAXIMUM and WINNERS specifications.</p>		<p>The values you specify for MAXIMUM and WINNERS are maximums. CNOS negotiation rules determine the actual session limits and allotment of first-speaker sessions between the LUs sharing the sessions. Also, the two reserved CNOS control sessions are not included in CNOS session limit negotiation and should not influence your MAXIMUM and WINNERS specifications.</p>
	<p>It is an error to issue DEFINE SESSIONGROUP for a sessiongroup defined previously during the run. </p>		<p>It is an error to issue DEFINE SESSIONGROUP for a sessiongroup defined previously during the run. </p>
	<p>For more information ~~about~~ Horizon CNOS connections~~, see the <var>Model 204 Horizon: Intersystem Processing Guide</var>~~. </p>		<p>For more information, see [[Horizon CNOS connections]].</p>

	[[Category: System manager commands]]		[[Category: System manager commands]]
	[[Category:Commands]]		[[Category:Commands]]

Alex: Automatically generated page update

2013-02-28T01:04:50Z

Automatically generated page update

New page

==Summary==
<dl>
<dt>Privileges
<dd>User 0 or system manager
<dt>Function
<dd>Defines a group of parallel sessions and associates the group with the CNOS remote and SNA Communications Server mode name specified in this command
</dl>
==Syntax==
DEFINE SESSIONGROUP name WITH
SCOPE=SYSTEM
REMOTE=rmtname
MODENAME=modent
MAXIMUM=xx
WINNERS=yy


Where:
<table>
<tr>
<th>name</th>
<td> is the locally known name for this entity. It is used on DEFINE PROCESSGROUP commands to refer to this sessiongroup. The length of the name must be eight characters or less. ALL is a reserved word and cannot be used.</td>
</tr>

<tr>
<th><var>SCOPE=SYSTEM</var></th>
<td> indicates that the definition is available to all users of the <var class="product">Model 204</var> system for the entire run. </td>
</tr>

<tr>
<th><var>REMOTE</var></th>
<td> specifies the name of the remote with which this sessiongroup is associated. This name must be the same as the remote name specified on a local DEFINE REMOTE command.</td>
</tr>

<tr>
<th><var>MODENAME</var></th>
<td> refers to the SNA Communications Server mode table entry that identifies this sessiongroup. modent must be an entry in a SNA Communications Server mode table that the local LU (DEFINE LINK LOCALID) associated with this sessiongroup is authorized to search.
If you specify multiple sessiongroups for a given remote LU (that is, with the same REMOTE value), you must specify a unique MODENAME value for each one. Each sessiongroup is, therefore, distinguished by its unique pairing of remote LU and mode entry.
You cannot name your entry SNASVCMG; this name is reserved for CNOS control sessions between the local and remote LUs.
</td>
</tr>

<tr>
<th><var>MAXIMUM</var></th>
<td> specifies the maximum number of concurrent sessions that can be active between the local LU and the target remote LU. MAXIMUM must be greater than zero, greater than or equal to the value of WINNERS, and less than or equal to 32,767. </td>
</tr>

<tr>
<th><var>WINNERS</var></th>
<td> specifies the maximum number of sessions for which this LU has the right to request an application conversation without permission (also called first-speaker sessions).
WINNERS must be greater than or equal to zero, less than or equal to the value of MAXIMUM, and less than or equal to 32,767.
The maximum number of sessions in which the remote node can be first speaker is equal to the difference between the values of MAXIMUM and WINNERS. 
</td>
</tr>

</table>
===Syntax notes===
You can specify multiple sessiongroups with the same remote, but each must have a different mode name.
==Example==
DEFINE SESSIONGROUP SESS1 WITH -
SCOPE=SYSTEM -
REMOTE=RMT1 -
MODENAME=LU62C -
MAXIMUM=10 -
WINNERS=5

==Usage notes==
You can specify multiple sessionsgroups with the same remote, but each must have a different mode name. 
Sessions in a sessiongroup use the CNOS session management protocol and have the same network properties (from a common remote and link) and the same session characteristics (from a common SNA Communications Server logmode entry).
The values you specify for MAXIMUM and WINNERS are maximums. CNOS negotiation rules determine the actual session limits and allotment of first-speaker sessions between the LUs sharing the sessions. Also, the two reserved CNOS control sessions are not included in CNOS session limit negotiation and should not influence your MAXIMUM and WINNERS specifications.
It is an error to issue DEFINE SESSIONGROUP for a sessiongroup defined previously during the run. 
For more information about Horizon CNOS connections, see the <var>Model 204 Horizon: Intersystem Processing Guide</var>. 
[[Category: System manager commands]]
[[Category:Commands]]