Networking concepts and terminology: Difference between revisions

From m204wiki
Jump to navigation Jump to search
(Created page with "==Overview== This topic presents terminology used when referring to Model 204 intersystem communication. Because the meaning of networking terms could be different in a Model...")
 
m (misc formatting)
 
(16 intermediate revisions by 2 users not shown)
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> &mdash; PCs and workstations (nodes A, B, and C) &mdash; 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>
<p class="figure">
<p class="figure">[[File:SQL_Connect_Guide_fig_1-1.gif]]</p>
<IMG SRC="SQL_Connect_Guide_fig_1-1.gif"></p>


===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 &mdash; the PCs and the workstations &mdash; are also end users. An <i>end user</i> is defined as a user connected to a Model&nbsp;204 terminal thread. </li>
 
<li>For each end user in a Model&nbsp;204 TCP/IP (Horizon) network, its operation is transparent.</li>
</ul>
</ul>


Line 42: Line 44:


===IP===
===IP===
<p>The <i>internet protocol</i> (IP) provides the routing mechanism for the data. The internet protocol creates a virtual network view and acts as a layer to hide the underlying physical network. </p>
<p>
The <i>internet protocol</i> (IP) provides the routing mechanism for the data. The internet protocol creates a virtual network view and acts as a layer to hide the underlying physical network. </p>
<p>
<p>
The <i>IP address</i> is a 32-bit address, usually represented in dotted decimal form. The internet protocol uses an IP address to specify two logical addresses:</p>
The <i>IP address</i> is a 32-bit address, usually represented in dotted decimal form. The internet protocol uses an IP address to specify two logical addresses:</p>
<ul>
<ul>
<li>
<li><i>Network address</i> represents the physical network within the internet</li>
<i>Network address</i> represents the physical network within the internet</li>
 
<li>
<li><i>Local address</i> specifies an individual host within the physical network</li>
<i>Local address</i> specifies an individual host within the physical network</li>
</ul>
</ul>


===Ports===
===Ports===
<p>A <i>port</i> is an identifier used by TCP/IP to distinguish one client node from another in a network connecting many client nodes to a single host (or server).</p>
<p>
A <i>port</i> is an identifier used by TCP/IP to distinguish one client node from another in a network connecting many client nodes to a single host (or server).</p>


===Identifying Model 204 to TCP/IP===
===Identifying Model 204 to TCP/IP===
<p>In setting up a client node for the Model 204 TCP/IP (Horizon) network, you provide an IP address and port number combination to identify Model 204. This example shows a valid IP address/port number combination:</p>
<p>
In setting up a client node for the Model 204 TCP/IP (Horizon) network, you provide an IP address and port number combination to identify Model 204. This example shows a valid IP address/port number combination:</p>


<code>192.35.46.128:1003</code>
<code>192.35.46.128:1003</code>
Line 66: Line 70:
<td>Is the dotted decimal notation address</td>
<td>Is the dotted decimal notation address</td>
</tr>
</tr>
<tr>
<tr>
<td>1003</td>
<td>1003</td>
Line 82: Line 87:
==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&nbsp;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&nbsp;204 database management system (DBMS) operations, and provides a combination of Model&nbsp;204 and SQL database functionality. Its main components are:    </p>
<table>
<table>
<tr>
<tr>
Line 92: Line 97:
<td>Compiles SQL syntax strings, checks SQL semantics, optimizes database access, generates code to accomplish SQL requests, and executes the generated code. Each SQL statement generates data, status information, or both for the requesting application.</td>
<td>Compiles SQL syntax strings, checks SQL semantics, optimizes database access, generates code to accomplish SQL requests, and executes the generated code. Each SQL statement generates data, status information, or both for the requesting application.</td>
</tr>
</tr>
<tr>
<tr>
<td>SQL Server Front End (SSFE)</td>
<td>SQL Server Front End (SSFE)</td>
Line 98: Line 104:
</table>
</table>
<p>
<p>
The Model 204 SQL Server provides full SQL processing in one of these locations: </p>
The Model&nbsp;204 SQL Server provides full SQL processing in one of these locations: </p>
<ul>
<ul>
<li>
<li>Address space (z/OS)</li>
Address space (z/OS)</li>
 
<li>
<li>Virtual machine (VM)</li>
Virtual machine (VM)</li>
 
<li>
<li>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&nbsp;204 software:  </p>
<table>
<table>
<tr>
<tr>
Line 115: Line 121:
<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 124: Line 132:
</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>
<table>
<table>
<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>
<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>
Line 139: Line 150:
==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&nbsp;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">&#9733;</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">&#9733;</span> Suite for Model&nbsp;204 drivers. You can configure Model&nbsp;204 z/OS, z/VM, or z/VSE TCP/IP connections to workstation clients.</p>


===Application program interfaces===
===Application program interfaces===
Line 147: Line 158:
Connect<span class="superstar">&#9733;</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">&#9733;</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">&#9733;</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">&#9733;</span> Suite for Model&nbsp;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>
<p class="caption" id="SQL_proc_transport">Model 204 SQL processing transport methods </p>
<p class="caption">Model 204 SQL processing transport methods </p>
<p class="figure">[[File:SQL_Connect_Guide_fig_1-2.gif]]</p>
<p class="figure"><IMG SRC="SQL_Connect_Guide_fig_1-2.gif"></p>
<!-- Note <div> above -->


==Model 204 TCP/IP (Horizon)==
==Model 204 TCP/IP (Horizon)==
<p>
<p>
Model 204 contains a TCP/IP intersystem processing facility that enables Model 204 applications to participate in program-to-program processing through the Connect<span class="superstar">&#9733;</span> Suite using the TCP/IP type of connection.</p>
Model&nbsp;204 contains a TCP/IP intersystem processing facility that enables Model&nbsp;204 applications to participate in program-to-program processing through the Connect<span class="superstar">&#9733;</span> Suite using the TCP/IP type of connection.</p>
<p>
<p>
Connect<span class="superstar">&#9733;</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">&#9733;</span> requires that Model&nbsp;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&nbsp;204 TCP/IP (Horizon) supplies a connection to TCP/IP software on workstations. </p>


===Windows Sockets (winsocket) support===
===Windows Sockets (winsocket) support===
<p>
<p>
A <i>socket</i> is a function that makes it possible for an application to access a communications protocol. Windows provides such a function, a Windows Sockets (winsocket) connection. </p>
A <b>socket</b> is a function that makes it possible for an application to access a communications protocol. Windows provides such a function, a Windows Sockets (winsocket) connection. </p>
<p>
<p>
The Connect<span class="superstar">&#9733;</span> Suite provides winsocket connection support, which lets you connect to Model 204 using Connect<span class="superstar">&#9733;</span> and a Windows TCP/IP package that supports winsocket calls.</p>
The Connect<span class="superstar">&#9733;</span> Suite provides winsocket connection support, which lets you connect to Model 204 using Connect<span class="superstar">&#9733;</span> and a Windows TCP/IP package that supports winsocket calls.</p>


===Interface product to support Windows Sockets===
===Interface product to support Windows Sockets===
<p>To use Model 204 TCP/IP (Horizon), you need installed and running on your PC or workstation an interface product that supports Windows Sockets.  </p>
<p>
To use Model&nbsp;204 TCP/IP (Horizon), you need installed and running on your PC or workstation an interface product that supports Windows Sockets.  </p>


===Other requirements===
===Other requirements===
<p>To complete the TCP/IP connection, you must also make sure that your system meets these requirements:</p>
<p>
To complete the TCP/IP connection, you must also make sure that your system meets these requirements:</p>
<ul>
<ul>
<li>
<li>IBM/TCP-IP is running on the mainframe</li>
IBM/TCP-IP is running on the mainframe</li>
 
<li>
<li>PCs are able to "talk to" the mainframe
PCs are able to "talk to" the mainframe
<p>Use the <var>ping</var> command to check the network connection and make sure that each PC and workstation is communicating with the mainframe. </p>
<p>Use the <var>ping</var> command to check the network connection and make sure that each PC and workstation is communicating with the mainframe. </p>
</li>
</li>
</ul>
</ul>
===Procedures for defining the network===
===Procedures for defining the network===
<p>
<p>
The Rocket Model 204 documentation wiki command pages describe the [[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]] commands that you use to define the TCP/IP network to Model 204 for PCs and workstations.</p>
<var>[[DEFINE LINK command: Horizon for TCP/IP|DEFINE LINK]]</var>, <var>[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM|DEFINE PROCESS]]</var>, and <var>[[DEFINE PROCESSGROUP command: Horizon for TCP/IP|DEFINE PROCESSGROUP]]</var> are the commands that you use to define the TCP/IP network to Model&nbsp;204 for PCs and workstations.</p>


====For more information====
====For more information====
<p>
<p>
For more information about installing Connect<span class="superstar">&#9733;</span> on a PC or workstation running Windows and TCP/IP software, consult the appropriate section in the <var class="book">Connect<span class="superstar">&#9733;</span> Installation and Programming Guide</var>.
For more information about installing Connect<span class="superstar">&#9733;</span> on a PC or workstation running Windows and TCP/IP software, see the [[:Category:Connect*|Connect<span class="superstar">&#9733;</span> wiki pages]].</p>
</p>


==Information to be gathered==
==Information to be gathered==
Line 196: Line 206:


==Tasks summary==
==Tasks summary==
<p>The following table summarizes the general tasks that you perform to set up Model 204 intersystem communication.</p>
<p>
The following table summarizes the general tasks that you perform to set up Model&nbsp;204 intersystem communication.</p>
<table>
<table>
<p class="caption">List of general tasks</p>
<p class="caption">List of general tasks</p>
<th>Step</th>
<tr class="head"><th>Step</th>
<th>Task</th>
<th>Task</th>
<th>See...</th>
<th>See...</th></tr>
 
<tr>
<tr>
<td>1.</td>
<td>1.</td>
<td>
<td>Include SQL-specific files in your online environment.</td>
<p>
<td>[[Runtime environment for SQL processing#SQL processing files|SQL processing files]]</td>
Include SQL-specific files in your online environment.</p>
</td>
<td>
<p>[[#SQL processing files|SQL processing files]]</p>
</td>
</tr>
</tr>
<tr>
<tr>
<td>2.
<td>2.</td>
</td>
<td>Set CCAIN parameters to support Model 204 SQL processing.</td>
<td>
<td>[[Runtime environment for SQL processing#CCAIN parameters to support Model 204 SQL processing|CCAIN parameters to support Model 204 SQL processing]]</td>
<p>Set CCAIN parameters to support Model 204 SQL processing.</p>
</td>
<td>
<p>[[#CCAIN parameters to support Model 204 SQL processing|CCAIN parameters to support Model 204 SQL processing]]</p>
</td>
</tr>
</tr>
<tr>
<tr>
<td>3.
<td>3.</td>
</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>
<tr>
<tr>
<td>4.</td>
<td>4.</td>
<td>
<td>Define SQL and RCL IODEV threads.</td>
Define 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>
<td>[[#Defining SQL and RCL IODEV threads|Defining SQL and RCL IODEV threads]]
</td>
</tr>
</tr>
<tr>
<tr>
<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>
<tr>
<tr>
<td>6.
<td>6.</td>
</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|Setting initial sizes for SQL buffers]]</td>
</tr>
</tr>
<tr>
<tr>
<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>
<td>Using Model 204 TCP/IP (Horizon), issue <var>DEFINE</var> commands for link, processgroup, and process.</td>
<p>
<td>[[DEFINE LINK command: Horizon for TCP/IP|Link]] <br />[[DEFINE PROCESSGROUP command: Horizon for TCP/IP|Processgroup]] <br />[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM|Process]]
Using Model 204 TCP/IP (Horizon), issue DEFINE commands for:</p>
<ul>
<li>
[[DEFINE LINK command: Horizon for TCP/IP|Link]]</li>
<li>
[[DEFINE PROCESSGROUP command: Horizon for TCP/IP|Processgroup]]</li>
<li>
[[DEFINE PROCESS command: Horizon for TCP/IP and VTAM|Process]]</li>
</ul>
</td>
</td>
<td />
</tr>
</tr>
</table>
</table>


[[Category: Networking]]
==See also==
[[Category: Model 204 SQL processing]]
{{Template:SQL connectivity topic list}}
 
[[Category: SQL connectivity]]

Latest revision as of 20:12, 28 March 2017

Overview

This topic presents terminology used when referring to Model 204 intersystem communication. Because the meaning of networking terms could be different in a Model 204 context, Technical Support recommends that all connectivity system administrators read this topic.

Basic networking terms and concepts

In this topic, a computer network is defined as a collection of nodes, connected at the software level by a communication interface.

Different types of nodes exist on a network: application nodes, terminal nodes, printer nodes, and so on. When the term "node" is used in this topic, however, it refers to an application node: the point of connection to the network for some system that supports application programs.

Some examples of communication interfaces are:

  • Virtual Telecommunication Access Method (VTAM)
  • Transmission Control Protocol/Internet Protocol (TCP/IP)

The following figure shows a hypothetical network that consists of three nodes. The software communication interface used is TCP/IP.

The transactions originate from the client nodes — PCs and workstations (nodes A, B, and C) — that request information from the server node, where the Model 204 SQL process runs.

Network transactions

Figure description

Essential elements shown in the previous figure are:

  • Exchange of data between two application programs at different nodes is referred to as a conversation.
  • Two programs that converse are referred to as conversation partners.
  • Client nodes — the PCs and the workstations — are also end users. An end user is defined as a user connected to a Model 204 terminal thread.
  • For each end user in a Model 204 TCP/IP (Horizon) network, its operation is transparent.

TCP/IP concepts and terminology

The Transmission Control Protocol/Internet Protocol (TCP/IP) is designed for building network interconnections.

TCP

The transmission control protocol (TCP) controls the transfer of the data. The TCP layer provides logical connections between pairs of processes. In TCP, a connection is defined by a pair of sockets, processes that are exchanging information, and a conversation is the communication link between the two processes. TCP provides reliability in data transmission and controls the data flow.

IP

The internet protocol (IP) provides the routing mechanism for the data. The internet protocol creates a virtual network view and acts as a layer to hide the underlying physical network.

The IP address is a 32-bit address, usually represented in dotted decimal form. The internet protocol uses an IP address to specify two logical addresses:

  • Network address represents the physical network within the internet
  • Local address specifies an individual host within the physical network

Ports

A port is an identifier used by TCP/IP to distinguish one client node from another in a network connecting many client nodes to a single host (or server).

Identifying Model 204 to TCP/IP

In setting up a client node for the Model 204 TCP/IP (Horizon) network, you provide an IP address and port number combination to identify Model 204. This example shows a valid IP address/port number combination:

192.35.46.128:1003

where:

192.35.46.128 Is the dotted decimal notation address
1003 Is the port number

Connections

A TCP/IP connection transports requests and responses between the client nodes and the server node.

A conversation occurs over a connection. In the SQL connectivity topics, descriptions of Model 204 TCP/IP (Horizon) use conversation and connection interchangeably, because a connection is dropped when a conversation ends.

The Model 204 server process (CCARSQL) receives information from the client nodes, completes the specified action, and returns data to the clients.

Overview of Model 204 SQL processing

This section briefly reviews the components involved in Model 204 SQL processing. SQL processing transport methods are described in SQL processing transport methods. For a more complete discussion of all SQL processing components and related concepts, see SQL Server overview.

SQL Server

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:

SQL Engine Compiles SQL syntax strings, checks SQL semantics, optimizes database access, generates code to accomplish SQL requests, and executes the generated code. Each SQL statement generates data, status information, or both for the requesting application.
SQL Server Front End (SSFE) Serves as the access layer to the SQL Engine, accepting client request packets, processing each packet's requests for the SQL Engine, and returning the SQL processing result to the client.

The Model 204 SQL Server provides full SQL processing in one of these locations:

  • Address space (z/OS)
  • Virtual machine (VM)
  • Partition (VSE)

SQL Server associated software

The SQL Server works in conjunction with the following Model 204 software:

SQL catalog CCACAT is the Model 204 system file that houses the SQL catalog information for Model 204 files defined with SQL Data Definition Language (DDL).
SQL communications interface 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.
SQL Client Front End (SCFE) Groups and sends client requests, and receives and distributes results to the client. The SCFE is platform independent.

SQL Server supporting tools

These Model 204 tools support SQL Server processing:

Table Specification facility (TSF) 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.
Catalog Reporting facility (CCACATREPT) 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.

SQL processing transport methods

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 Model 204 SQL processing transport methods.

The figure includes the workstation clients that can be configured with the Connect★ Suite for Model 204 drivers. You can configure Model 204 z/OS, z/VM, or z/VSE TCP/IP connections to workstation clients.

Application program interfaces

Connect★ application programming interfaces are shown in the following figure as elements in the client configurations. Brief descriptions of these interfaces follow the figure.

Workstation clients can use the following 32-bit Connect★ 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.

Model 204 SQL processing transport methods

Model 204 TCP/IP (Horizon)

Model 204 contains a TCP/IP intersystem processing facility that enables Model 204 applications to participate in program-to-program processing through the Connect★ Suite using the TCP/IP type of connection.

Connect★ requires that Model 204 TCP/IP (Horizon) be installed and running on the mainframe serving as the host machine in your network.

For more information about Horizon, see the Horizon wiki topics.

Along with IBM/TCP-IP software on the mainframe, Model 204 TCP/IP (Horizon) supplies a connection to TCP/IP software on workstations.

Windows Sockets (winsocket) support

A socket is a function that makes it possible for an application to access a communications protocol. Windows provides such a function, a Windows Sockets (winsocket) connection.

The Connect★ Suite provides winsocket connection support, which lets you connect to Model 204 using Connect★ and a Windows TCP/IP package that supports winsocket calls.

Interface product to support Windows Sockets

To use Model 204 TCP/IP (Horizon), you need installed and running on your PC or workstation an interface product that supports Windows Sockets.

Other requirements

To complete the TCP/IP connection, you must also make sure that your system meets these requirements:

  • IBM/TCP-IP is running on the mainframe
  • PCs are able to "talk to" the mainframe

    Use the ping command to check the network connection and make sure that each PC and workstation is communicating with the mainframe.

Procedures for defining the network

DEFINE LINK, DEFINE PROCESS, and DEFINE PROCESSGROUP are the commands that you use to define the TCP/IP network to Model 204 for PCs and workstations.

For more information

For more information about installing Connect★ on a PC or workstation running Windows and TCP/IP software, see the Connect★ wiki pages.

Information to be gathered

To set up the Model 204 TCP/IP (Horizon) network, you might need to obtain information from the TCP/IP administrator. See Model 204 TCP/IP connection parameters.

Tasks summary

The following table summarizes the general tasks that you perform to set up Model 204 intersystem communication.

List of general tasks

Step Task See...
1. Include SQL-specific files in your online environment. SQL processing files
2. Set CCAIN parameters to support Model 204 SQL processing. CCAIN parameters to support Model 204 SQL processing
3. Size the CCATEMP file. CCATEMP file size
4. Define SQL and RCL IODEV threads. Defining SQL and RCL IODEV threads
5. Size the fixed server area and the variable server area. Server area sizing
6. Size SQL buffers. Setting initial sizes for SQL buffers
7. Review network definition entities. Making the necessary connections
8. Using Model 204 TCP/IP (Horizon), issue DEFINE commands for link, processgroup, and process. Link
Processgroup
Process

See also

Retrieved from "https://m204wiki.rocketsoftware.com/index.php?title=Networking_concepts_and_terminology&oldid=102422"