ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzaii_5.4.0.1/rzaiimst28.htm

93 lines
5.4 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="task" />
<meta name="DC.Title" content="Establish client/server communications" />
<meta name="abstract" content="Learn the process for starting and ending communication between clients and host servers." />
<meta name="description" content="Learn the process for starting and ending communication between clients and host servers." />
<meta name="DC.Relation" scheme="URI" content="rzaiimst27.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiimstsvrprtnum.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiistrhostsvr.htm" />
<meta name="DC.Relation" scheme="URI" content="rzaiiendinghost.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzai2/rzai2kickoff.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaiimst28" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Establish client/server communications</title>
</head>
<body id="rzaiimst28"><a name="rzaiimst28"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Establish client/server communications</h1>
<div><p>Learn the process for starting and ending communication between
clients and host servers.</p>
<div class="section"><p>This topic also includes each server's port numbers, and a description
of server daemons and their role in communication.</p>
<p>Client/Server communication
is established in the following steps:</p>
</div>
<ol><li><span>To initiate a server job that uses sockets communications support,
the client system connects to a particular server's port number.</span></li>
<li><span>A server daemon must be started (with the STRHOSTSVR command) to
listen for and accept the client's connection request. Upon accepting the
connection request, the server daemon issues an internal request to attach
the client's connection to a server job.</span></li>
<li><span>This server job may be a prestarted job or, if prestart jobs are
not used, a batch job that is submitted when the client connection request
is processed. The server job handles any further communications with the client.
The initial data exchange includes a request that identifies authentication
tokens that are associated with the client user. A user profile and password,
or a Kerberos ticket, are examples of these tokens.</span></li>
<li><span>Once the authentication tokens are validated, the server job switches
to use the i5/OS™ user
profile associated with those tokens, and changes the job by using many of
the attributes defined for the user profile, such as accounting code and output
queue.</span></li>
</ol>
<div class="section"><p><strong>Server to client communications</strong></p>
<p>iSeries™ Access
for Windows<sup>®</sup> uses
TCP/IP to communicate with the iSeries system servers. The optimized
servers use i5/OS sockets
support to communicate with clients. The i5/OS sockets support is compatible with
Berkeley Software Distributions 4.3 sockets over TCP/IP. Sockets support is
provided with the 5722-TC1 product that is installed on the iSeries server.</p>
<p>See
the TCP/IP Configuration and Reference manual for more information about communications.</p>
<p>For
more information, see:</p>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rzaiimstsvrprtnum.htm">Host Servers port numbers</a></strong><br />
Each type of server has its own server daemon, which listens on a port for incoming client connection requests.</li>
<li class="ulchildlink"><strong><a href="rzaiistrhostsvr.htm">Start host servers</a></strong><br />
To start Host Servers, use the <span class="cmdname">STRHOSTSVR</span> CL
command. </li>
<li class="ulchildlink"><strong><a href="rzaiiendinghost.htm">End host servers</a></strong><br />
To end Host servers, use the ENDHOSTSVR CL command.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiimst27.htm" title="Describes the client/server communication process, and how to manage it. Additionally, this topic lists relevant iSeries system values and subsystems, and describes how to identify, display and manage server jobs on the iSeries.">Use i5/OS host servers</a></div>
</div>
<div class="relinfo"><strong>Related information</strong><br />
<div><a href="../rzai2/rzai2kickoff.htm">TCP/IP setup</a></div>
</div>
</div>
</body>
</html>