Horizon TCP/IP - Revision history

JAL: /* DEFINE commands */ typo

2017-03-24T20:34:01Z

DEFINE commands: typo

← Older revision		Revision as of 20:34, 24 March 2017
Line 32:		Line 32:
	==DEFINE commands==		==DEFINE commands==
	In Model 204 terminology, the Model 204 SQL Server is the server process, or program, that communicates through a conversation with a client partner (SQL application). The Model 204 DEFINE commands specify the physical and logical characteristics of the conversation and name the clients that can access the SQL Server.		In Model 204 terminology, the Model 204 SQL Server is the server process, or program, that communicates through a conversation with a client partner (SQL application). The Model 204 DEFINE commands specify the physical and logical characteristics of the conversation and name the clients that can access the SQL Server.
	<p>The DEFINE commands--[[DEFINE LINK command: Horizon for TCP/IP\|DEFINE LINK]], [[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]], and [[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|DEFINE PROCESSGROUP]]--are all necessary to define a Horizon for TCP/IP connection.</p>		<p>The DEFINE commands — [[DEFINE LINK command: Horizon for TCP/IP\|DEFINE LINK]], [[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]], and [[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|DEFINE PROCESSGROUP]] — are all necessary to define a Horizon for TCP/IP connection.</p>

	===Issuing DEFINE commands===		===Issuing DEFINE commands===
	The DEFINE commands are typically stored in a SOUL procedure that is invoked by the Model 204 Online job or EXEC at runtime or coded in the Online job or EXEC CCAIN stream. For example,		The DEFINE commands are typically stored in a SOUL procedure that is invoked by the Model 204 Online job or EXEC at runtime or coded in the Online job or EXEC CCAIN stream. For example,
Line 49:		Line 50:
	<th>TCP/IP client specification</th>		<th>TCP/IP client specification</th>
	</tr>		</tr>

	<tr>		<tr>
	<td>Server node (Model 204 SQL) address</td>		<td>Server node (Model 204 SQL) address</td>
Line 55:		Line 57:
	<td>Host (Server) Name or IP Address parameter in ODBC, JDBC or .NET connection string</td>		<td>Host (Server) Name or IP Address parameter in ODBC, JDBC or .NET connection string</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Server port number</td>		<td>Server port number</td>
Line 61:		Line 64:
	<td>Port number parameter in ODBC, JDBC or .NET connection string</td>		<td>Port number parameter in ODBC, JDBC or .NET connection string</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Client node (TCP/IP Workstation) address</td>		<td>Client node (TCP/IP Workstation) address</td>
Line 68:		Line 72:
	</td>		</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Model 204 user ID and password for client user (might not be required)</td>		<td>Model 204 user ID and password for client user (might not be required)</td>
Line 94:		Line 99:
	<td>Points to the link (with LINK) and points to the client node (with REMOTEID and, optionally, MASK)</td>		<td>Points to the link (with LINK) and points to the client node (with REMOTEID and, optionally, MASK)</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Process</td>		<td>Process</td>
Line 99:		Line 105:
	</tr>		</tr>
	</table>		</table>
	<p>The following figure shows the parameters with which the commands point to each other and to the client partner. Descriptions of the individual entity definitions with all their parameters are provided in previous sections of this topic.</p>		<p>
			The following figure shows the parameters with which the commands point to each other and to the client partner. Descriptions of the individual entity definitions with all their parameters are provided in previous sections of this topic.</p>

	<p class="caption">Interconnecting parameters of network entity definitions </p>		<p class="caption">Interconnecting parameters of network entity definitions </p>

ELowell at 23:59, 11 October 2016

2016-10-11T23:59:41Z

← Older revision		Revision as of 23:59, 11 October 2016
Line 107:		Line 107:
	After you have issued the required entity definition commands, you must issue the [[OPEN LINK command]] to enable processing.		After you have issued the required entity definition commands, you must issue the [[OPEN LINK command]] to enable processing.
	<p>The OPEN LINK command prepares a port to accept connection requests. Connection requests are accepted and processed only if the address they come from matches the (masked) address in a processgroup definition that points to an open link.</p>		<p>The OPEN LINK command prepares a port to accept connection requests. Connection requests are accepted and processed only if the address they come from matches the (masked) address in a processgroup definition that points to an open link.</p>

			==See also==
			{{Template:SQL connectivity topic list}}

	[[Category: SQL connectivity]]		[[Category: SQL connectivity]]
	[[Category: Horizon]]		[[Category: Horizon]]

ELowell at 19:40, 14 October 2015

2015-10-14T19:40:28Z

← Older revision		Revision as of 19:40, 14 October 2015
Line 109:		Line 109:

	[[Category: SQL connectivity]]		[[Category: SQL connectivity]]
			[[Category: Horizon]]

ELowell: /* DEFINE commands */

2015-07-20T16:33:47Z

DEFINE commands

← Older revision		Revision as of 16:33, 20 July 2015
Line 32:		Line 32:
	==DEFINE commands==		==DEFINE commands==
	In Model 204 terminology, the Model 204 SQL Server is the server process, or program, that communicates through a conversation with a client partner (SQL application). The Model 204 DEFINE commands specify the physical and logical characteristics of the conversation and name the clients that can access the SQL Server.		In Model 204 terminology, the Model 204 SQL Server is the server process, or program, that communicates through a conversation with a client partner (SQL application). The Model 204 DEFINE commands specify the physical and logical characteristics of the conversation and name the clients that can access the SQL Server.
	<p>The commands--[[DEFINE LINK command: Horizon for TCP/IP\|DEFINE LINK]], [[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]], and [[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|DEFINE PROCESSGROUP]]--are all necessary to define a Horizon for TCP/IP connection.</p>		<p>The DEFINE commands--[[DEFINE LINK command: Horizon for TCP/IP\|DEFINE LINK]], [[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]], and [[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|DEFINE PROCESSGROUP]]--are all necessary to define a Horizon for TCP/IP connection.</p>
	===Issuing DEFINE commands===		===Issuing DEFINE commands===
	The DEFINE commands are typically stored in a SOUL procedure that is invoked by the Model 204 Online job or EXEC at runtime or coded in the Online job or EXEC CCAIN stream. For example,		The DEFINE commands are typically stored in a SOUL procedure that is invoked by the Model 204 Online job or EXEC at runtime or coded in the Online job or EXEC CCAIN stream. For example,
Line 44:		Line 44:
	<table>		<table>
	<p class="caption">Model 204 TCP/IP connection parameters</p>		<p class="caption">Model 204 TCP/IP connection parameters</p>
			<tr class="head">
	<th>Value provided</th>		<th>Value provided</th>
	<th>Model 204 DEFINE command parameter</th>		<th>Model 204 DEFINE command parameter</th>
	<th>TCP/IP client specification</th>		<th>TCP/IP client specification</th>
			</tr>
	<tr>		<tr>
	<td>Server node (Model 204 SQL) address</td>		<td>Server node (Model 204 SQL) address</td>
Line 77:		Line 79:

	===DEFINE command interconnections===		===DEFINE command interconnections===
	Specify a DEFINE command for each Horizon network entity. Each command has multiple parameters, some of which are optional. The Horizon network entities are:		Specify a DEFINE command for each Horizon network entity. Each command has multiple parameters, some of which are optional.

			The Horizon network entities are described in the following table.
	<table>		<table>
			<tr class="head">
			<th>Entity</th> <th>Description</th>
			</tr>
	<tr>		<tr>
	<td>Link</td>		<td>Link</td>

ELowell: /* Exchanging Horizon for TCP/IP connection parameters */

2015-07-14T18:15:57Z

Exchanging Horizon for TCP/IP connection parameters

← Older revision		Revision as of 18:15, 14 July 2015
Line 74:		Line 74:
	</tr>		</tr>
	</table>		</table>
	<p>For details about TCP/IP client specification, see ~~the~~ <~~var~~ class="~~book~~">~~Connect* Suite Installation and Programming Guide~~</~~var~~>.</p>		<p>For details about TCP/IP client specification, see [[Connect* installation requirements\|Connect<span class="superstar">★</span> installation requirements]].</p>

	===DEFINE command interconnections===		===DEFINE command interconnections===

ELowell: /* Connecting to Model 204 TCP/IP (Horizon) */

2015-07-14T18:12:09Z

Connecting to Model 204 TCP/IP (Horizon)

← Older revision		Revision as of 18:12, 14 July 2015
Line 11:		Line 11:

	==Connecting to Model 204 TCP/IP (Horizon)==		==Connecting to Model 204 TCP/IP (Horizon)==
	The following figure shows a Model 204 TCP/IP link with three connections to Connect* clients. Note the interrelated process, processgroup, and link that support TCP/IP connections.		The following figure shows a Model 204 TCP/IP link with three connections to Connect<span class="superstar">★</span> clients. Note the interrelated process, processgroup, and link that support TCP/IP connections.

	<p class="caption">Horizon for TCP/IP connection support</p>		<p class="caption">Horizon for TCP/IP connection support</p>
Line 20:		Line 20:
	<p>		<p>
	In this chapter, descriptions of Model 204 TCP/IP use <i>conversation</i>		In this chapter, descriptions of Model 204 TCP/IP use <i>conversation</i>
	and <i>connection</i> interchangeably, because a connection is dropped when a conversation ends. Model 204 TCP/IP conversation exchanges are always initiated by the Connect* for an application program. CCARSQL is always the server.</p>		and <i>connection</i> interchangeably, because a connection is dropped when a conversation ends. Model 204 TCP/IP conversation exchanges are always initiated by the Connect<span class="superstar">★</span> for an application program. CCARSQL is always the server.</p>

	====Guidelines====		====Guidelines====

ELowell: /* Transparent operation */

2015-07-14T18:11:20Z

Transparent operation

← Older revision		Revision as of 18:11, 14 July 2015
Line 8:		Line 8:

	===Transparent operation===		===Transparent operation===
	Once the network is properly defined, the operation of Model 204 TCP/IP is transparent to Connect* users. For example, the execution of socket verbs is handled internally.		Once the network is properly defined, the operation of Model 204 TCP/IP is transparent to Connect<span class="superstar">★</span> users. For example, the execution of socket verbs is handled internally.

	==Connecting to Model 204 TCP/IP (Horizon)==		==Connecting to Model 204 TCP/IP (Horizon)==

ELowell at 17:25, 23 February 2015

2015-02-23T17:25:11Z

← Older revision		Revision as of 17:25, 23 February 2015
Line 101:		Line 101:
	<p>The OPEN LINK command prepares a port to accept connection requests. Connection requests are accepted and processed only if the address they come from matches the (masked) address in a processgroup definition that points to an open link.</p>		<p>The OPEN LINK command prepares a port to accept connection requests. Connection requests are accepted and processed only if the address they come from matches the (masked) address in a processgroup definition that points to an open link.</p>

	[[Category: SQL ~~Connectivity~~]]		[[Category: SQL connectivity]]

ELowell at 23:26, 20 February 2015

2015-02-20T23:26:01Z

← Older revision		Revision as of 23:26, 20 February 2015
Line 101:		Line 101:
	<p>The OPEN LINK command prepares a port to accept connection requests. Connection requests are accepted and processed only if the address they come from matches the (masked) address in a processgroup definition that points to an open link.</p>		<p>The OPEN LINK command prepares a port to accept connection requests. Connection requests are accepted and processed only if the address they come from matches the (masked) address in a processgroup definition that points to an open link.</p>

	[[Category: ~~Networking]]~~		[[Category: SQL Connectivity]]
	~~[[Category: Model 204~~ SQL ~~processing~~]]

ELowell: /* DEFINE commands */

2015-02-19T22:12:44Z

DEFINE commands

← Older revision		Revision as of 22:12, 19 February 2015
Line 32:		Line 32:
	==DEFINE commands==		==DEFINE commands==
	In Model 204 terminology, the Model 204 SQL Server is the server process, or program, that communicates through a conversation with a client partner (SQL application). The Model 204 DEFINE commands specify the physical and logical characteristics of the conversation and name the clients that can access the SQL Server.		In Model 204 terminology, the Model 204 SQL Server is the server process, or program, that communicates through a conversation with a client partner (SQL application). The Model 204 DEFINE commands specify the physical and logical characteristics of the conversation and name the clients that can access the SQL Server.
	<p>The commands--DEFINE LINK, DEFINE ~~PROCESSGROUP~~, and DEFINE ~~PROCESS~~--are all necessary to define a Horizon for TCP/IP connection. ~~These commands are documented in the Rocket Model 204 documentation wiki command pages:</p>~~		<p>The commands--[[DEFINE LINK command: Horizon for TCP/IP\|DEFINE LINK]], [[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|DEFINE PROCESS]], and [[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|DEFINE PROCESSGROUP]]--are all necessary to define a Horizon for TCP/IP connection.</p>
	~~<p>~~
	~~http://m204wiki.rocketsoftware.com/index.php/Category:Commands~~</p>

	===Issuing DEFINE commands===		===Issuing DEFINE commands===
	The DEFINE commands are typically stored in a SOUL procedure that is invoked by the Model 204 Online job or EXEC at runtime or coded in the Online job or EXEC CCAIN stream. For example,		The DEFINE commands are typically stored in a SOUL procedure that is invoked by the Model 204 Online job or EXEC at runtime or coded in the Online job or EXEC CCAIN stream. For example,