Horizon network management - Revision history

ELowell at 22:04, 13 October 2017

2017-10-13T22:04:15Z

← Older revision		Revision as of 22:04, 13 October 2017
Line 22:		Line 22:
	Model 204 Online configuration preparation		Model 204 Online configuration preparation
	<p>		<p>
	Online configuration preparation involves the following modification of system input (CCAIN): allotting Horizon inbound threads (IODEV=27) and adding to the ~~NSUBTSKS~~ parameter value for LU 6.2/SNA Communications Server pseudo subtasks.</p>		Online configuration preparation involves the following modification of system input (CCAIN): allotting Horizon inbound threads (IODEV=27) and adding to the NSUBTKS parameter value for LU 6.2/SNA Communications Server pseudo subtasks.</p>
	</li>		</li>
	<li>		<li>
Line 587:		Line 587:
	==Preparing the ONLINE configuration==		==Preparing the ONLINE configuration==
	<p>		<p>
	This section describes CCAIN stream parameters the system manager must set appropriately for Horizon to function successfully. The parameters discussed here are the system input (CCAIN) parameters IODEV and NSUBTKS. ONLINE configuration preparation includes allotting Horizon inbound threads (IODEV=27) and adding to the ~~NSUBTSKS~~ parameter value for LU 6.2/SNA Communications Server pseudo subtasks.</p>		This section describes CCAIN stream parameters the system manager must set appropriately for Horizon to function successfully. The parameters discussed here are the system input (CCAIN) parameters IODEV and NSUBTKS. ONLINE configuration preparation includes allotting Horizon inbound threads (IODEV=27) and adding to the NSUBTKS parameter value for LU 6.2/SNA Communications Server pseudo subtasks.</p>

	===IODEV specification for Horizon inbound threads===		===IODEV specification for Horizon inbound threads===

JAL: link repair

2017-03-28T19:07:41Z

link repair

← Older revision		Revision as of 19:07, 28 March 2017
Line 56:		Line 56:
	<tr>		<tr>
	<td nowrap>SNA Communications Server</td>		<td nowrap>SNA Communications Server</td>
	<td>[[#Defining the ~~Network~~ to SNA Communications Server\|Defining the ~~Network~~ to SNA Communications Server]]</td>		<td>[[#Defining the network to SNA Communications Server\|Defining the network to SNA Communications Server]]</td>
	</tr>		</tr>
	</table>		</table>
Line 377:		Line 377:
	An entry in a mode table is required to specify the particular set of SNA protocols (the session mode) desired for a session between two Horizon LUs. In this case the protocols are characteristic of LU type 6.2.</p>		An entry in a mode table is required to specify the particular set of SNA protocols (the session mode) desired for a session between two Horizon LUs. In this case the protocols are characteristic of LU type 6.2.</p>
	<p>		<p>
	The [[#APPL statements for network definition\|APPL statements for network definition]] and [[#Coding the mode table entry for SNA Communications Server network definition\|Coding the mode table entry for SNA Communications Server network definition]] sections describe how to code the APPL statements and the mode table entries to define the SNA Communications Server network.</p>		The [[#APPL statements for network definition\|APPL statements for network definition]] and [[#Coding the mode table entry for SNA Communications Server network definition\|Coding the mode table entry for SNA Communications Server network definition]] sections that follow describe how to code the APPL statements and the mode table entries to define the SNA Communications Server network.</p>

	===APPL statements for network definition===		===APPL statements for network definition===

JAL: misc formatting

2017-03-28T18:59:35Z

misc formatting

← Older revision		Revision as of 18:59, 28 March 2017
Line 33:		Line 33:
	==Defining the Network to Model 204==		==Defining the Network to Model 204==
	<p>		<p>
	Before partner programs can converse over Horizon, the network, including the programs and their interconnections, must be defined to Model 204. In addition, the network must be defined to SNA Communications Server, which supports Horizon. Each Model 204 system in the network provides a definition of the link, processgroup, and process entities using respectively the DEFINE LINK, DEFINE PROCESS, and DEFINE PROCESSGROUP commands. </p>		Before partner programs can converse over Horizon, the network, including the programs and their interconnections, must be defined to Model 204. In addition, the network must be defined to SNA Communications Server, which supports Horizon. Each Model 204 system in the network provides a definition of the link, processgroup, and process entities using respectively the <var>DEFINE LINK</var>, <var>DEFINE PROCESS</var>, and <var>DEFINE PROCESSGROUP</var> commands. </p>
	<table>		<table>
	<tr>		<tr class="head">
	<th>		<th>Defining the network to</th>
	Defining the network to</th>		<th>Is described in</th>
	<th>
	Is described in</th>
	</tr>		</tr>

	<tr>		<tr>
	<td>Model 204</td>		<td>Model 204</td>
	<td>		<td>This topic, as well as these:
	~~<ul>~~
	~~<li~~>This topic~~.</li>~~
	~~<li>These topics~~:
	<ul>		<ul>
	<li>[[DEFINE LINK command: Horizon for TCP/IP]] and [[DEFINE LINK command: Horizon for VTAM]]</li>		<li>[[DEFINE LINK command: Horizon for TCP/IP]] and [[DEFINE LINK command: Horizon for VTAM]]</li>
Line 55:		Line 51:
	<br>[[DEFINE PROCESSGROUP command: Horizon for TCP/IP]]		<br>[[DEFINE PROCESSGROUP command: Horizon for TCP/IP]]
	<br>[[DEFINE PROCESSGROUP command: Horizon for VTAM]]</li>		<br>[[DEFINE PROCESSGROUP command: Horizon for VTAM]]</li>
	~~</ul></li>~~
	</ul>		</ul>
	</td></tr>		</td></tr>
Line 61:		Line 56:
	<tr>		<tr>
	<td nowrap>SNA Communications Server</td>		<td nowrap>SNA Communications Server</td>
	<td>		<td>[[#Defining the Network to SNA Communications Server\|Defining the Network to SNA Communications Server]]</td>
	[[#Defining the Network to SNA Communications Server\|Defining the Network to SNA Communications Server]]
	</td>
	</tr>		</tr>
	</table>		</table>

JAL: misc formatting

2017-03-28T18:50:42Z

misc formatting

Show changes

ELowell: /* IODEV specification for Horizon inbound threads */

2016-06-15T19:03:04Z

IODEV specification for Horizon inbound threads

← Older revision		Revision as of 19:03, 15 June 2016
Line 606:		Line 606:
	To guarantee that there is no shortage of Horizon inbound threads and that all incoming conversation requests can be processed, set the NOTERM parameter to the total of INLIMIT values on all DEFINE PROCESSGROUP commands for the server system.</p>		To guarantee that there is no shortage of Horizon inbound threads and that all incoming conversation requests can be processed, set the NOTERM parameter to the total of INLIMIT values on all DEFINE PROCESSGROUP commands for the server system.</p>
	<p>		<p>
	For more information about IODEV 27, see [[Defining the user environment (CCAIN)#Horizon (IODEV=27)]].</p>		For more information about IODEV 27, see [[Defining the user environment (CCAIN)#Horizon (IODEV=27)\|Defining the user environment (CCAIN)]].</p>

	===Modifying the NSUBTKS parameter===		===Modifying the NSUBTKS parameter===

JAL: link repair

2016-02-01T22:21:17Z

link repair

← Older revision		Revision as of 22:21, 1 February 2016
Line 581:		Line 581:
	[[OPEN LINK command\|OPEN LINK]]</li>		[[OPEN LINK command\|OPEN LINK]]</li>
	<li>		<li>
	[[CLOSE LINK command: CNOS ~~Link~~\|CLOSE LINK (CNOS)]]</li>		[[CLOSE LINK command: CNOS link\|CLOSE LINK (CNOS)]]</li>
	<li>		<li>
	[[CLOSE LINK command: Model 204 non-CNOS intersystem link\|CLOSE LINK (non-CNOS)]]</li>		[[CLOSE LINK command: Model 204 non-CNOS intersystem link\|CLOSE LINK (non-CNOS)]]</li>
Line 593:		Line 593:
	[[MODIFY SESSIONGROUP command\|MODIFY SESSIONGROUP]]</li>		[[MODIFY SESSIONGROUP command\|MODIFY SESSIONGROUP]]</li>
	</ul>		</ul>

	==Preparing the ONLINE configuration==		==Preparing the ONLINE configuration==
	<p>		<p>

JAL: link repair

2015-10-13T22:45:36Z

link repair

← Older revision		Revision as of 22:45, 13 October 2015
Line 46:		Line 46:
	<ul>		<ul>
	<li>This topic.</li>		<li>This topic.</li>
	<li>~~The~~ <~~var~~>[[DEFINE LINK command\|DEFINE LINK]]</~~var~~>, <~~var~~>[[DEFINE PROCESS command~~\|DEFINE PROCESS~~]]</~~var~~>~~, and~~ <~~var~~>[[DEFINE PROCESSGROUP command\|DEFINE PROCESSGROUP]]</~~var~~> ~~topics.~~</li>		<li>These topics:
			<ul>
			<li>[[DEFINE LINK command: Horizon for TCP/IP]] and [[DEFINE LINK command: Horizon for VTAM]]</li>

			<li>[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM]]</li>

			<li>[[DEFINE PROCESSGROUP command: Horizon CNOS]]
			<br>[[DEFINE PROCESSGROUP command: Horizon for TCP/IP]]
			<br>[[DEFINE PROCESSGROUP command: Horizon for VTAM]]</li>
			</ul></li>
	</ul>		</ul>
	</td>		</td></tr>
	</tr>
	<tr>		<tr>
	<td>SNA Communications Server</td>		<td nowrap>SNA Communications Server</td>
	<td>		<td>
	[[#Defining the Network to SNA Communications Server\|Defining the Network to SNA Communications Server]]		[[#Defining the Network to SNA Communications Server\|Defining the Network to SNA Communications Server]]
Line 73:		Line 82:

	<p class="note"><b>Note:</b> CNOS connections require the definition of two additional definition commands: <var>[[DEFINE REMOTE command\|DEFINE REMOTE]]</var> and <var>[[DEFINE SESSIONGROUP command\|DEFINE SESSIONGROUP]]</var>. See [[Horizon CNOS connections]] for more information.</p>		<p class="note"><b>Note:</b> CNOS connections require the definition of two additional definition commands: <var>[[DEFINE REMOTE command\|DEFINE REMOTE]]</var> and <var>[[DEFINE SESSIONGROUP command\|DEFINE SESSIONGROUP]]</var>. See [[Horizon CNOS connections]] for more information.</p>
	~~<p>~~
	See also <var>[[DEFINE LINK command\|DEFINE LINK]]</var>, <var>[[DEFINE PROCESSGROUP command\|DEFINE PROCESSGROUP]]</var>, <var>[[DEFINE PROCESS command\|DEFINE PROCESS]]</var>, DEFINE REMOTE, and DEFINE SESSIONGROUP.</p>

	==Creating a Horizon network==		==Creating a Horizon network==

JAL: link repair

2015-10-13T21:49:56Z

link repair

← Older revision		Revision as of 21:49, 13 October 2015
Line 199:		Line 199:
	This is an example of tuning RETAIN and OUTLIMIT values so that it is possible not to run out of available sessions. See the discussion of RETAIN in [[#Defining a Horizon network\|Defining a Horizon network]] for more information about sharing sessions and network resource use.</p>		This is an example of tuning RETAIN and OUTLIMIT values so that it is possible not to run out of available sessions. See the discussion of RETAIN in [[#Defining a Horizon network\|Defining a Horizon network]] for more information about sharing sessions and network resource use.</p>
	<p>		<p>
	The sessions are allocated on a first come, first served basis. They remain allocated to a remote node unless the link is closed, a <var>[[~~STOP LINK command~~\|STOP LINK]]</var> or <var>[[STOP ~~PROCESSGROUP~~ command\|STOP PROCESSGROUP]]</var> command is issued, or the session is ended by the remote node. The effects of STOP LINK and STOP PROCESSGROUP are described further in [[STOP command: Stopping a Horizon or Model 204 SQL link or processgroup]].</p>		The sessions are allocated on a first come, first served basis. They remain allocated to a remote node unless the link is closed, a <var>[[STOP_command: Stopping a Horizon or Model 204 SQL link or processgroup\|STOP LINK]]</var> or <var>[[STOP command: Stopping a Horizon or Model 204 SQL link or processgroup\|STOP PROCESSGROUP]]</var> command is issued, or the session is ended by the remote node. The effects of STOP LINK and STOP PROCESSGROUP are described further in [[STOP command: Stopping a Horizon or Model 204 SQL link or processgroup]].</p>
	<p>		<p>
	The session used by each outbound conversation with PGCLI2 is released as soon as the conversation ends, as specified by the RETAIN value of zero in PGCLI2's processgroup definition.</p>		The session used by each outbound conversation with PGCLI2 is released as soon as the conversation ends, as specified by the RETAIN value of zero in PGCLI2's processgroup definition.</p>

JAL: link repair

2015-10-13T21:45:17Z

link repair

← Older revision		Revision as of 21:45, 13 October 2015
Line 17:		Line 17:
	Network security		Network security
	<p>		<p>
	Network security involves using DEFINE command security parameters in conjunction with Application Subsystem security to provide the desired protection for network resources. Network security is described in [[Horizon security]].</p>		Network security involves using DEFINE command security parameters in conjunction with Application Subsystem security to provide the desired protection for network resources. Network security is described in [[Horizon network security]].</p>
	</li>		</li>
	<li>		<li>

JAL: link repair

2015-10-13T21:33:34Z

link repair

← Older revision		Revision as of 21:33, 13 October 2015
Line 535:		Line 535:
	The COS= parameter in the mode table entry may also need to be modified to meet system and application requirements.</p>		The COS= parameter in the mode table entry may also need to be modified to meet system and application requirements.</p>
	<p>		<p>
	The situations requiring such modifications are discussed in [[SNA ~~communications server~~ tuning for Horizon]].</p>		The situations requiring such modifications are discussed in [[SNA Communications Server tuning for Horizon]].</p>
	<p>		<p>
	Modifications for parallel session connections are discussed in [[Horizon CNOS connections#Defining CNOS support to SNA Communications Server\|Defining CNOS support to SNA Communications Server]]. In particular, the PSERVIC value must be different.</p>		Modifications for parallel session connections are discussed in [[Horizon CNOS connections#Defining CNOS support to SNA Communications Server\|Defining CNOS support to SNA Communications Server]]. In particular, the PSERVIC value must be different.</p>