Networking concepts and terminology - Revision history

JAL: misc formatting

2017-03-28T20:12:32Z

misc formatting

JAL: /* SQL processing transport methods */ replace "chapter"

2017-03-28T19:57:24Z

SQL processing transport methods: replace "chapter"

← Older revision		Revision as of 19:57, 28 March 2017
Line 146:		Line 146:
	==SQL processing transport methods==		==SQL processing transport methods==
	<p>		<p>
	Transport of the data between the SQL Server and its clients relies on the communication layer: Model 204 TCP/IP (Horizon). These interfaces, which define client to SQL Server connections, are described in this ~~chapter~~ and shown in [[#~~SQL_proc_transport~~\|Model 204 SQL processing transport methods]].</p>		Transport of the data between the SQL Server and its clients relies on the communication layer: Model 204 TCP/IP (Horizon). These interfaces, which define client to SQL Server connections, are described in this topic and shown in [[#SQL proc transport\|Model 204 SQL processing transport methods]].</p>
	<p>		<p>
	The figure includes the workstation clients that can be configured with the Connect<span class="superstar">★</span> Suite for Model 204 drivers. You can configure Model 204 z/OS, z/VM, or z/VSE TCP/IP connections to workstation clients.</p>		The figure includes the workstation clients that can be configured with the Connect<span class="superstar">★</span> Suite for Model 204 drivers. You can configure Model 204 z/OS, z/VM, or z/VSE TCP/IP connections to workstation clients.</p>

	===Application program interfaces===		===Application program interfaces===
Line 154:		Line 154:
	Connect<span class="superstar">★</span> application programming interfaces are shown in the following figure as elements in the client configurations. Brief descriptions of these interfaces follow the figure. </p>		Connect<span class="superstar">★</span> application programming interfaces are shown in the following figure as elements in the client configurations. Brief descriptions of these interfaces follow the figure. </p>
	<p>		<p>
	Workstation clients can use the following 32-bit Connect<span class="superstar">★</span> Suite for Model 204 drivers, which lets you use dynamic SQL statements in any Windows application that uses Microsoft Open Database Connectivity (ODBC), JDBC, or .NET Framework function calls. </p>		Workstation clients can use the following 32-bit Connect<span class="superstar">★</span> Suite for Model 204 drivers, which lets you use dynamic SQL statements in any Windows application that uses Microsoft Open Database Connectivity (ODBC), JDBC, or .NET Framework function calls. </p>
	<div id="SQL_proc_transport"></div>		<div id="SQL_proc_transport"></div>
	<p class="caption">Model 204 SQL processing transport methods </p>		<p class="caption">Model 204 SQL processing transport methods </p>

JAL: /* Overview of Model 204 SQL processing */ add link

2017-03-28T19:47:26Z

Overview of Model 204 SQL processing: add link

← Older revision		Revision as of 19:47, 28 March 2017
Line 84:		Line 84:
	==Overview of Model 204 SQL processing==		==Overview of Model 204 SQL processing==
	<p>		<p>
	This section briefly reviews the components involved in Model 204 SQL processing. SQL processing transport methods are described in [[#SQL processing transport methods\|SQL processing transport methods]]. For a more complete discussion of all SQL processing components and related concepts, see ~~the <var class="book">Rocket Model 204~~ SQL Server ~~User's Guide</var>~~.</p>		This section briefly reviews the components involved in Model 204 SQL processing. SQL processing transport methods are described in [[#SQL processing transport methods\|SQL processing transport methods]]. For a more complete discussion of all SQL processing components and related concepts, see [[SQL Server overview]].</p>

	===SQL Server===		===SQL Server===
	<p>		<p>
	Client/server architecture allows the Model 204 to act as an SQL Server on the host machine, to service clients' TCP/IP. The SQL Server invokes Model 204 database management system (DBMS) operations, and provides a combination of Model 204 and SQL database functionality. Its main components are: </p>		Client/server architecture allows the Model 204 to act as an SQL Server on the host machine, to service clients' TCP/IP. The SQL Server invokes Model 204 database management system (DBMS) operations, and provides a combination of Model 204 and SQL database functionality. Its main components are: </p>
	<table>		<table>
	<tr>		<tr>
Line 109:		Line 109:
	Partition (VSE)</li>		Partition (VSE)</li>
	</ul>		</ul>

	===SQL Server associated software===		===SQL Server associated software===
	<p>		<p>
	The SQL Server works in conjunction with the following Model 204 software: </p>		The SQL Server works in conjunction with the following Model 204 software: </p>
	<table>		<table>
	<tr>		<tr>
Line 117:		Line 118:
	<td>CCACAT is the Model 204 system file that houses the SQL catalog information for Model 204 files defined with SQL Data Definition Language (DDL).</td>		<td>CCACAT is the Model 204 system file that houses the SQL catalog information for Model 204 files defined with SQL Data Definition Language (DDL).</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>SQL communications interface</td>		<td>SQL communications interface</td>
	<td>Receives SQL requests from TCP/IP and passes them to the SQL Server Front End (SSFE). The interface receives result packets from the SSFE and routes them back to the client. This Model 204 module is used only for SQL processing.</td>		<td>Receives SQL requests from TCP/IP and passes them to the SQL Server Front End (SSFE). The interface receives result packets from the SSFE and routes them back to the client. This Model 204 module is used only for SQL processing.</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>SQL Client Front End (SCFE)</td>		<td>SQL Client Front End (SCFE)</td>
Line 126:		Line 129:
	</tr>		</tr>
	</table>		</table>

	===SQL Server supporting tools===		===SQL Server supporting tools===
	<p>These Model 204 tools support SQL Server processing: </p>		<p>These Model 204 tools support SQL Server processing: </p>
Line 133:		Line 137:
	<td>Model 204 subsystem ([[SQL DDL from the Table Specification Facility\|CCATSF]]) that provides an interactive, menu-driven facility for mapping existing Model 204 files to SQL tables and columns. The TSF is available on the mainframe only.</td>		<td>Model 204 subsystem ([[SQL DDL from the Table Specification Facility\|CCATSF]]) that provides an interactive, menu-driven facility for mapping existing Model 204 files to SQL tables and columns. The TSF is available on the mainframe only.</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>Catalog Reporting facility (CCACATREPT)</td>		<td>Catalog Reporting facility (CCACATREPT)</td>

JAL: /* Basic networking terms and concepts */ use — instead of hyphen pair

2017-03-28T19:40:36Z

Basic networking terms and concepts: use — instead of hyphen pair

← Older revision		Revision as of 19:40, 28 March 2017
Line 18:		Line 18:
	The following figure shows a hypothetical network that consists of three nodes. The software communication interface used is TCP/IP. </p>		The following figure shows a hypothetical network that consists of three nodes. The software communication interface used is TCP/IP. </p>
	<p>		<p>
	The transactions originate from the <i>client nodes</i>--PCs and workstations (nodes A, B, and C)--that request information from the <i>server node</i>, where the Model 204 SQL process runs.</p>		The transactions originate from the <i>client nodes</i> — PCs and workstations (nodes A, B, and C) — that request information from the <i>server node</i>, where the Model 204 SQL process runs.</p>

	<p class="caption">Network transactions</p>		<p class="caption">Network transactions</p>
Line 24:		Line 24:

	===Figure description===		===Figure description===
	<p>Essential elements shown in the previous figure are: </p>		<p>
			Essential elements shown in the previous figure are: </p>
	<ul>		<ul>
	<li>		<li>Exchange of data between two application programs at different nodes is referred to as a <i>conversation</i>. </li>
	Exchange of data between two application programs at different nodes is referred to as a <i>conversation</i>. </li>
	<li>Two programs that converse are referred to as <i>conversation partners</i>. </li>		<li>Two programs that converse are referred to as <i>conversation partners</i>. </li>
	<li>Client nodes--the PCs and the workstations--are also end users. An <i>end user</i> is defined as a user connected to a Model 204 terminal thread. </li>
	<li>For each end user in a Model 204 TCP/IP (Horizon) network, its operation is transparent.</li>		<li>Client nodes — the PCs and the workstations — are also end users. An <i>end user</i> is defined as a user connected to a Model 204 terminal thread. </li>

			<li>For each end user in a Model 204 TCP/IP (Horizon) network, its operation is transparent.</li>
	</ul>		</ul>

ELowell at 23:58, 11 October 2016

2016-10-11T23:58:39Z

← Older revision		Revision as of 23:58, 11 October 2016
Line 255:		Line 255:
	</tr>		</tr>
	</table>		</table>

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

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

ELowell: /* SQL Server supporting tools */

2016-09-13T19:58:14Z

SQL Server supporting tools

← Older revision		Revision as of 19:58, 13 September 2016
Line 132:		Line 132:
	<tr>		<tr>
	<td>Catalog Reporting facility (CCACATREPT)</td>		<td>Catalog Reporting facility (CCACATREPT)</td>
	<td>Model 204 subsystem that provides a menu-driven facility for generating DDL from and reports of the SQL catalog contents. With the CCACATREPT, you can review your SQL object definitions, names, and privileges or use the DDL that it generates to repopulate the SQL catalog. CCACATREPT is available on the mainframe only.</td>		<td>Model 204 subsystem that provides a menu-driven facility for generating DDL from and reports of the SQL catalog contents. With the [[SQL catalog reporting and querying\|CCACATREPT]], you can review your SQL object definitions, names, and privileges or use the DDL that it generates to repopulate the SQL catalog. CCACATREPT is available on the mainframe only.</td>
	</tr>		</tr>
	</table>		</table>

ELowell: /* SQL Server supporting tools */

2016-09-13T19:51:26Z

SQL Server supporting tools

← Older revision		Revision as of 19:51, 13 September 2016
Line 128:		Line 128:
	<tr>		<tr>
	<td>Table Specification facility (TSF)</td>		<td>Table Specification facility (TSF)</td>
	<td>Model 204 subsystem (CCATSF) that provides an interactive, menu-driven facility for mapping existing Model 204 files to SQL tables and columns. The TSF is available on the mainframe only.</td>		<td>Model 204 subsystem ([[SQL DDL from the Table Specification Facility\|CCATSF]]) that provides an interactive, menu-driven facility for mapping existing Model 204 files to SQL tables and columns. The TSF is available on the mainframe only.</td>
	</tr>		</tr>
	<tr>		<tr>

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

2016-02-04T20:31:02Z

Model 204 TCP/IP (Horizon)

← Older revision		Revision as of 20:31, 4 February 2016
Line 158:		Line 158:
	Connect<span class="superstar">★</span> requires that Model 204 TCP/IP (Horizon) be installed and running on the mainframe serving as the host machine in your network.</p>		Connect<span class="superstar">★</span> requires that Model 204 TCP/IP (Horizon) be installed and running on the mainframe serving as the host machine in your network.</p>
	<p>		<p>
	~~The <var class="book">Rocket Model 204~~ Horizon: ~~Intersystem Processing Guide</var> contains complete information about~~ Horizon. </p>		For more information about Horizon, see the [[:Category: Horizon\|Horizon]] wiki topics.</p>
	<p>		<p>
	Along with IBM/TCP-IP software on the mainframe, Model 204 TCP/IP (Horizon) supplies a connection to TCP/IP software on workstations. </p>		Along with IBM/TCP-IP software on the mainframe, Model 204 TCP/IP (Horizon) supplies a connection to TCP/IP software on workstations. </p>

ELowell: /* Tasks summary */

2015-07-20T16:55:19Z

Tasks summary

← Older revision		Revision as of 16:55, 20 July 2015
Line 234:		Line 234:
	<td>6.</td>		<td>6.</td>
	<td>Size SQL buffers.</td>		<td>Size SQL buffers.</td>
	<td>[[Runtime environment for SQL processing#Setting initial sizes for SQL buffers\|~~See~~ Setting initial sizes for SQL buffers]]</td>		<td>[[Runtime environment for SQL processing#Setting initial sizes for SQL buffers\|Setting initial sizes for SQL buffers]]</td>
	</tr>		</tr>

Line 240:		Line 240:
	<td>7.</td>		<td>7.</td>
	<td>Review network definition entities.</td>		<td>Review network definition entities.</td>
	<td>[[#~~Determining~~ the necessary connections\|~~Determining~~ the necessary connections]]</td>		<td>[[SQL network entities#Making the necessary connections\|Making the necessary connections]]</td>
	</tr>		</tr>

	<tr>		<tr>
	<td>8.</td>		<td>8.</td>
	<td>Using Model 204 TCP/IP (Horizon), issue DEFINE commands for:		<td>Using Model 204 TCP/IP (Horizon), issue DEFINE commands for link, processgroup, and process.</td>
	<ul>		<td>
	<li>[[DEFINE LINK command: Horizon for TCP/IP\|Link]]</li>		[[DEFINE LINK command: Horizon for TCP/IP\|Link]]<br />

	~~<li>~~[[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|Processgroup]]</li>		[[DEFINE PROCESSGROUP command: Horizon for TCP/IP\|Processgroup]]<br />

	~~<li>~~[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|Process]]</li>		[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM\|Process]]<br />
	~~</ul>~~</td>		</td>
	</tr>		</tr>
	</table>		</table>

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

ELowell: /* Tasks summary */

2015-07-20T16:39:14Z

Tasks summary

← Older revision		Revision as of 16:39, 20 July 2015
Line 204:		Line 204:
	<td>1.</td>		<td>1.</td>
	<td>Include SQL-specific files in your online environment.</td>		<td>Include SQL-specific files in your online environment.</td>
	<td>[[#SQL processing files\|SQL processing files]]</td>		<td>[[Runtime environment for SQL processing#SQL processing files\|SQL processing files]]</td>
	</tr>		</tr>

Line 210:		Line 210:
	<td>2.</td>		<td>2.</td>
	<td>Set CCAIN parameters to support Model 204 SQL processing.</td>		<td>Set CCAIN parameters to support Model 204 SQL processing.</td>
	<td>[[#CCAIN parameters to support Model 204 SQL processing\|CCAIN parameters to support Model 204 SQL processing]]</td>		<td>[[Runtime environment for SQL processing#CCAIN parameters to support Model 204 SQL processing\|CCAIN parameters to support Model 204 SQL processing]]</td>
	</tr>		</tr>

Line 216:		Line 216:
	<td>3.</td>		<td>3.</td>
	<td>Size the CCATEMP file.</td>		<td>Size the CCATEMP file.</td>
	<td>[[#CCATEMP file size\|CCATEMP file size]]</td>		<td>[[Runtime environment for SQL processing#CCATEMP file size\|CCATEMP file size]]</td>
	</tr>		</tr>

Line 222:		Line 222:
	<td>4.</td>		<td>4.</td>
	<td>Define SQL and RCL IODEV threads.</td>		<td>Define SQL and RCL IODEV threads.</td>
	<td>[[#Defining SQL and RCL IODEV threads\|Defining SQL and RCL IODEV threads]]</td>		<td>[[Runtime environment for SQL processing#Defining SQL and RCL IODEV threads\|Defining SQL and RCL IODEV threads]]</td>
	</tr>		</tr>

Line 228:		Line 228:
	<td>5.</td>		<td>5.</td>
	<td>Size the fixed server area and the variable server area.</td>		<td>Size the fixed server area and the variable server area.</td>
	<td>[[#Server area sizing\|Server area sizing]]</td>		<td>[[Runtime environment for SQL processing#Server area sizing\|Server area sizing]]</td>
	</tr>		</tr>

Line 234:		Line 234:
	<td>6.</td>		<td>6.</td>
	<td>Size SQL buffers.</td>		<td>Size SQL buffers.</td>
	<td>[[#~~See~~ Setting initial sizes for SQL buffers\|See Setting initial sizes for SQL buffers]]</td>		<td>[[Runtime environment for SQL processing#Setting initial sizes for SQL buffers\|See Setting initial sizes for SQL buffers]]</td>
	</tr>		</tr>