DEFINE LINK command: Horizon for VTAM - Revision history

DCameron: /* Usage notes */

2019-02-12T14:05:41Z

Usage notes

← Older revision		Revision as of 14:05, 12 February 2019
Line 102:		Line 102:
	</li>		</li>
	</ul>		</ul>
	<p>If you are to have multiple links open simultaneously, you must make sure the value of the <var class="product">Model 204</var> User 0 parameter NSUBTKS is sufficiently large. Each open link requires an increment to NSUBTKS: 2 for z/OS, 4 for CMS.</p>		<p>If you are to have multiple links open simultaneously, you must make sure the value of the <var class="product">Model 204</var> User 0 parameter <var>[[NSUBTKS_parameter\|NSUBTKS]]</var> is sufficiently large. Each open link requires an increment to NSUBTKS: 2 for z/OS, 4 for CMS.</p>
	<p>For more information about a Horizon network and entities, see [[Horizon network management]].</p>		<p>For more information about a Horizon network and entities, see [[Horizon network management]].</p>

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

DCameron: /* Usage notes */

2019-02-12T14:04:32Z

Usage notes

← Older revision		Revision as of 14:04, 12 February 2019
Line 82:		Line 82:
	==Usage notes==		==Usage notes==
	The names for the link and processgroup entities for a given link are system-specific and are not pointed to by other systems in the network, unlike the LOCALID value of DEFINE LINK and the REMOTEID value of DEFINE PROCESSGROUP. Thus, you may assign the link and processgroup entities any names you choose, even names that are used on other systems. Also, they need not be changed if, for example, the LOCALID value of DEFINE LINK or the REMOTEID value of DEFINE PROCESSGROUP is changed.		The names for the link and processgroup entities for a given link are system-specific and are not pointed to by other systems in the network, unlike the LOCALID value of DEFINE LINK and the REMOTEID value of DEFINE PROCESSGROUP. Thus, you may assign the link and processgroup entities any names you choose, even names that are used on other systems. Also, they need not be changed if, for example, the LOCALID value of DEFINE LINK or the REMOTEID value of DEFINE PROCESSGROUP is changed.
	<p>The DEFINE LINK command can be issued only if the named link is not open. <var class="product">Model 204</var> rejects a DEFINE LINK command for an open link. If the link is open, the CLOSE LINK command must be issued for the DEFINE LINK to complete successfully.</p>		<p>The DEFINE LINK command can be issued only if the named link is not open. <var class="product">Model 204</var> rejects a DEFINE LINK command for an open link. If the link is open, the <var>[[CLOSE_LINK_command\|CLOSE LINK]]</var> command must be issued for the DEFINE LINK to complete successfully.</p>
	<p>A single link may be shared by: </p>		<p>A single link may be shared by: </p>
	<ul>		<ul>

DCameron: /* Syntax */

2019-02-12T14:00:32Z

Syntax

← Older revision		Revision as of 14:00, 12 February 2019
Line 49:		Line 49:
	<th><var>SESSIONS</var></th>		<th><var>SESSIONS</var></th>
	<td>specifies the maximum number of concurrent sessions that can be activated for the link. A session is activated when a conversation is initiated. The valid range of values is 1 to 32767.		<td>specifies the maximum number of concurrent sessions that can be activated for the link. A session is activated when a conversation is initiated. The valid range of values is 1 to 32767.
	<p>For CNOS, the SESSIONS parameter value should include two extra control sessions per remote. These sessions are not used for application conversations, and they are defined automatically by <var class="product">Model 204</var>. Since a single Horizon link can support both CNOS and non-CNOS conversations, you are not required to specify an additional DEFINE LINK and DEFINE PROCESS command for CNOS if you also have non-CNOS sessions.</p>		<p>For CNOS, the SESSIONS parameter value should include two extra control sessions per remote. These sessions are not used for application conversations, and they are defined automatically by <var class="product">Model 204</var>. Since a single Horizon link can support both CNOS and non-CNOS conversations, you are not required to specify an additional DEFINE LINK and [[DEFINE_PROCESS_command:_Overview_of_intersystem_network_process\|DEFINE PROCESS]] command for CNOS if you also have non-CNOS sessions.</p>
	</td>		</td>
	</tr>		</tr>

DCameron: /* Syntax */

2019-02-12T13:56:49Z

Syntax

← Older revision		Revision as of 13:56, 12 February 2019
Line 38:		Line 38:
	<tr>		<tr>
	<th><var>TRANSPORT</var></th>		<th><var>TRANSPORT</var></th>
	<td>is the physical communication transmission method. For Horizon, the transport must be SNA Communications Server.</td>		<td>is the physical communication transmission method. For [[Model_204_intersystem_processing#Horizon\|Horizon]], the transport must be SNA Communications Server.</td>
	</tr>		</tr>

DCameron: /* Syntax */

2019-02-12T13:55:41Z

Syntax

← Older revision		Revision as of 13:55, 12 February 2019
Line 23:		Line 23:
	<tr>		<tr>
	<th><var class="term">name</var></th>		<th><var class="term">name</var></th>
	<td>refers to the link entity and is used on DEFINE PROCESSGROUP commands to refer to this connection to the network. The length of <var class="term">name</var> must be eight characters or fewer. <var>ALL</var> is a reserved keyword and cannot be used.</td>		<td>refers to the link entity and is used on <var>[[DEFINE_PROCESSGROUP_command:_Horizon_for_VTAM\|DEFINE PROCESSGROUP]]</var> commands to refer to this connection to the network. The length of <var class="term">name</var> must be eight characters or fewer. <var>ALL</var> is a reserved keyword and cannot be used.</td>
	</tr>		</tr>

ELowell: /* Summary */

2016-03-17T16:10:26Z

Summary

← Older revision		Revision as of 16:10, 17 March 2016
Line 4:		Line 4:
	<dd>System manager, User 0		<dd>System manager, User 0
	<dt>Function		<dt>Function
	<dd>Defines a connection from <var class="product">Model 204</var> to the network ~~that specifies~~ a node name to be used when <var class="product">Model 204</var> connects to the SNA network and ~~indicates~~ the transport type and protocol		<dd>Defines a connection from <var class="product">Model 204</var> to the network, specifying a node name to be used when <var class="product">Model 204</var> connects to the SNA network and indicating the transport type and protocol
	</dl>		</dl>

	==Syntax==		==Syntax==
	<p class="syntax">DEFINE LINK <span class="term">name</span> [LIKE <span class="term">previousname</span>] WITH		<p class="syntax">DEFINE LINK <span class="term">name</span> [LIKE <span class="term">previousname</span>] WITH

ELowell: /* Syntax */

2016-03-17T16:07:04Z

Syntax

← Older revision		Revision as of 16:07, 17 March 2016
Line 22:		Line 22:
	<tr>		<tr>
	<th><var class="term">name</var></th>		<th><var class="term">name</var></th>
	<td>~~is referred~~ to as the link entity~~. It~~ is used on DEFINE PROCESSGROUP commands to refer to this connection to the network. The length of name must be eight characters or fewer. <var>ALL</var> is a reserved keyword and cannot be used.</td>		<td>refers to the link entity and is used on DEFINE PROCESSGROUP commands to refer to this connection to the network. The length of <var class="term">name</var> must be eight characters or fewer. <var>ALL</var> is a reserved keyword and cannot be used.</td>
	</tr>		</tr>

ELowell: /* Syntax */

2016-03-17T15:55:32Z

Syntax

← Older revision		Revision as of 15:55, 17 March 2016
Line 7:		Line 7:
	</dl>		</dl>
	==Syntax==		==Syntax==
	<p class="syntax">DEFINE LINK name [LIKE previousname] WITH		<p class="syntax">DEFINE LINK <span class="term">name</span> [LIKE <span class="term">previousname</span>] WITH
	SCOPE=SYSTEM		SCOPE=SYSTEM
	TRANSPORT=VTAM		TRANSPORT=VTAM
	PROTOCOL=LU62		PROTOCOL=LU62
	SESSIONS=num		SESSIONS=<span class="term">num</span>
	INBUFSIZE=size		INBUFSIZE=<span class="term">size</span>
	LOCALID=applid		LOCALID=<span class="term">applid</span>
	[PSWD \| NOPSWD]		[PSWD \| NOPSWD]
	[GCSID=vmid]		[GCSID=<span class="term">vmid</span>]
	</p>		</p>

Line 21:		Line 21:
	<table>		<table>
	<tr>		<tr>
	<th>name</th>		<th><var class="term">name</var></th>
	<td> ~~is that which~~ is referred to as the link entity. It is used on DEFINE PROCESSGROUP commands to refer to this connection to the network. The length of name must be eight characters or ~~less~~. ALL is a reserved keyword and cannot be used.</td>		<td>is referred to as the link entity. It is used on DEFINE PROCESSGROUP commands to refer to this connection to the network. The length of name must be eight characters or fewer. <var>ALL</var> is a reserved keyword and cannot be used.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th><var>LIKE</var></th>		<th><var>LIKE</var></th>
	<td> gives the current link the attributes of the link entity referred to by previousname. If you use LIKE, you must also specify WITH SCOPE=SYSTEM. If you also do not specify a new LOCALID value, the DEFINE LINK command will be valid but you cannot open both links.</td>		<td>gives the current link the attributes of the link entity referred to by <var class="term">previousname</var>. If you use LIKE, you must also specify WITH SCOPE=SYSTEM. If you also do not specify a new LOCALID value, the DEFINE LINK command will be valid but you cannot open both links.</td>
	</tr>		</tr>

Line 37:		Line 37:
	<tr>		<tr>
	<th><var>TRANSPORT</var></th>		<th><var>TRANSPORT</var></th>
	<td> is the physical communication transmission method. For Horizon, the transport must be SNA Communications Server.</td>		<td>is the physical communication transmission method. For Horizon, the transport must be SNA Communications Server.</td>
	</tr>		</tr>

	<tr>		<tr>
	<th><var>PROTOCOL</var></th>		<th><var>PROTOCOL</var></th>
	<td> identifies the conversation protocol. LU62 specifies the SNA LU~~ ~~6.2 protocol. This option supports basic LU 6.2 and also supports parallel sessions, namely CNOS. </td>		<td>identifies the conversation protocol. LU62 specifies the SNA LU 6.2 protocol. This option supports basic LU 6.2 and also supports parallel sessions, namely CNOS. </td>
	</tr>		</tr>

	<tr>		<tr>
	<th><var>SESSIONS</var></th>		<th><var>SESSIONS</var></th>
	<td> specifies the maximum number of concurrent sessions that can be activated for the link. A session is activated when a conversation is initiated. The valid range of values is 1 to 32767.		<td>specifies the maximum number of concurrent sessions that can be activated for the link. A session is activated when a conversation is initiated. The valid range of values is 1 to 32767.
	<p>For CNOS, the SESSIONS parameter value should include two extra control sessions per remote. These sessions are not used for application conversations, and they are defined automatically by <var class="product">Model 204</var>. Since a single Horizon link can support both CNOS and non-CNOS conversations, you are not required to specify an additional DEFINE LINK and DEFINE PROCESS command for CNOS if you also have non-CNOS sessions.</p>		<p>For CNOS, the SESSIONS parameter value should include two extra control sessions per remote. These sessions are not used for application conversations, and they are defined automatically by <var class="product">Model 204</var>. Since a single Horizon link can support both CNOS and non-CNOS conversations, you are not required to specify an additional DEFINE LINK and DEFINE PROCESS command for CNOS if you also have non-CNOS sessions.</p>
	</td>		</td>
Line 54:		Line 54:
	<tr>		<tr>
	<th><var>INBUFSIZE</var></th>		<th><var>INBUFSIZE</var></th>
	<td> specifies the size of the Horizon receiving buffer, the buffer into which each unit of data transferred over the session is received. In SNA, data is sent and received in units called Request Units (RUs).		<td>specifies the size of the Horizon receiving buffer, the buffer into which each unit of data transferred over the session is received. In SNA, data is sent and received in units called Request Units (RUs).
	<p>You should set INBUFSIZE to the value of the SNA Communications Server MODETAB table parameter RUSIZES, the maximum RU a session partner is allowed to send. It is recommended that both RUSIZES values be set to 2K. For a discussion about setting RUSIZES to a value other than 2K, see [[SNA Communications Server tuning for Horizon]].</p>		<p>You should set INBUFSIZE to the value of the SNA Communications Server MODETAB table parameter RUSIZES, the maximum RU a session partner is allowed to send. It is recommended that both RUSIZES values be set to 2K. For a discussion about setting RUSIZES to a value other than 2K, see [[SNA Communications Server tuning for Horizon]].</p>
	<p>Set INBUFSIZE to the value of the SNA Communications Server MODETAB table parameter RUSIZES (2K recommended). The valid range of INBUFSIZE values is 256 to 32767.</p>		<p>Set INBUFSIZE to the value of the SNA Communications Server MODETAB table parameter RUSIZES (2K recommended). The valid range of INBUFSIZE values is 256 to 32767.</p>
Line 60:		Line 60:
	</td>		</td>
	</tr>		</tr>

	</table>		</table>

ELowell: /* Syntax */

2016-02-04T20:45:11Z

Syntax

← Older revision		Revision as of 20:45, 4 February 2016
Line 55:		Line 55:
	<th><var>INBUFSIZE</var></th>		<th><var>INBUFSIZE</var></th>
	<td> specifies the size of the Horizon receiving buffer, the buffer into which each unit of data transferred over the session is received. In SNA, data is sent and received in units called Request Units (RUs).		<td> specifies the size of the Horizon receiving buffer, the buffer into which each unit of data transferred over the session is received. In SNA, data is sent and received in units called Request Units (RUs).
	<p>You should set INBUFSIZE to the value of the SNA Communications Server MODETAB table parameter RUSIZES, the maximum RU a session partner is allowed to send. It is recommended that both RUSIZES values be set to 2K. For a discussion about setting RUSIZES to a value other than 2K, see ~~<var>Rocket Model 204~~ Horizon~~: Intersystem Processing Guide~~.~~</var>~~ </p>		<p>You should set INBUFSIZE to the value of the SNA Communications Server MODETAB table parameter RUSIZES, the maximum RU a session partner is allowed to send. It is recommended that both RUSIZES values be set to 2K. For a discussion about setting RUSIZES to a value other than 2K, see [[SNA Communications Server tuning for Horizon]].</p>
	<p>Set INBUFSIZE to the value of the SNA Communications Server MODETAB table parameter RUSIZES (2K recommended). The valid range of INBUFSIZE values is 256 to 32767.</p>		<p>Set INBUFSIZE to the value of the SNA Communications Server MODETAB table parameter RUSIZES (2K recommended). The valid range of INBUFSIZE values is 256 to 32767.</p>
	<p>INBUFSIZE and the DEFINE PROCESS command parameter DATALEN are independent; they refer to different buffers.</p>		<p>INBUFSIZE and the DEFINE PROCESS command parameter DATALEN are independent; they refer to different buffers.</p>
Line 62:		Line 62:

	</table>		</table>

	==Example==		==Example==
	The following standard Horizon link definitions identify <var class="product">Model 204</var> as an LU to the network (setting LOCALID to a SNA Communications Server applid), specify the TRANSPORT and PROTOCOL options, indicate the maximum number of available sessions, and specify the size of the receive buffer (INBUFSIZE):		The following standard Horizon link definitions identify <var class="product">Model 204</var> as an LU to the network (setting LOCALID to a SNA Communications Server applid), specify the TRANSPORT and PROTOCOL options, indicate the maximum number of available sessions, and specify the size of the receive buffer (INBUFSIZE):

ELowell: /* Usage notes */

2016-02-04T20:34:39Z

Usage notes

← Older revision		Revision as of 20:34, 4 February 2016
Line 101:		Line 101:
	</li>		</li>
	</ul>		</ul>
	<p>If you are to have multiple links open simultaneously, you must make sure the value of the <var class="product">Model 204</var> User 0 parameter NSUBTKS is sufficiently large. Each open link requires an increment to NSUBTKS: 2 for z/OS, 4 for CMS.</p>		<p>If you are to have multiple links open simultaneously, you must make sure the value of the <var class="product">Model 204</var> User 0 parameter NSUBTKS is sufficiently large. Each open link requires an increment to NSUBTKS: 2 for z/OS, 4 for CMS.</p>
	<p>For more information about Horizon network and entities, see ~~the <var>Model 204~~ Horizon~~: Intersystem Processing Guide~~.~~</var>~~</p>		<p>For more information about a Horizon network and entities, see [[Horizon network management]].</p>

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