ibm-information-center/dist/eclipse/plugins/i5OS.ic.ifs_5.4.0.1/rzaaxos4comm.htm

94 lines
6.1 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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="reference" />
<meta name="DC.Title" content="Communications in the QFileSvr.400 file system" />
<meta name="abstract" content="The QFileSvr.400 file system communicates in the following ways." />
<meta name="description" content="The QFileSvr.400 file system communicates in the following ways." />
<meta name="DC.Relation" scheme="URI" content="rzaaxrfsfs.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzaaxos4comm" />
<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>Communications in the QFileSvr.400 file system</title>
</head>
<body id="rzaaxos4comm"><a name="rzaaxos4comm"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Communications in the QFileSvr.400 file system</h1>
<div><p><span>The QFileSvr.400 file system communicates
in the following ways.</span></p>
<div class="section"><ul><li>TCP connections with the file server on a target server can be established
only if the QSERVER subsystem on the target server is active.</li>
<li>SNA LU 6.2 connections are attempted only if there is a locally controlled
session that is not in use (for example, a session specifically established
for use by the LU 6.2 connection). When establishing LU 6.2 connections,
the QFileSvr.400 file system uses a mode of BLANK. On the target system, a
job named QPWFSERV is submitted to the QSERVER subsystem. The user profile
of this job is defined by the communications entry for the BLANK mode. For
more information about LU 6.2 communications, see <a href="../books/sc415443.pdf" target="_blank">APPC Programming</a> <img src="wbpdf.gif" alt="Link to PDF" />.
</li>
<li>File server requests that use TCP as the communications protocol are performed
within the context of the job that is issuing the request. File server requests
that use SNA as the communications protocol are performed by the <span class="keyword">i5/OS™</span> system job Q400FILSVR.</li>
<li>If a connection is not yet established with the target server,
the QFileSvr.400 file system assumes that the first-level directory represents
a TCP/IP host name. The QFileSvr.400 file system goes through the following
steps to establish a connection with the target server: <ol><li>Resolve the remote location name to an IP address.</li>
<li>Connect to the host server's server mapper on well-known port 449 using
the resolved IP address. Then send a query to the server mapper for the service
name <span class="q">"as-file."</span> One of the following occurs as result of the query: <ul><li>If <span class="q">"as-file"</span> is in the service table on the target server, the server
mapper returns the port on which the <span class="keyword">i5/OS</span> file
server daemon is listening.</li>
<li>If the server mapper is not active on the target server, the default port
number for <span class="q">"as-file"</span> (8473) is used.</li>
</ul>
<p>The QFileSvr.400 file system then tries to establish a TCP connection
with the <span class="keyword">i5/OS</span> file server
daemon on the target server. When the connection is established, QFileSvr.400
exchanges requests and replies with the file server. Within the QSERVER subsystem,
the QPWFSERVSO prestart requests take control of the connection. Each prestart
job runs under its own user profile.</p>
</li>
<li>If the remote location name is not resolved to an IP address, the first-level
directory is assumed to be an SNA LU 6.2 name. Therefore, an attempt is made
to establish an APPC connection with the <span class="keyword">i5/OS</span> file
server.</li>
</ol>
</li>
<li>The QFileSvr.400 file system periodically (every 2 hours) checks to determine
if there are any connections that are not being used (for example, no opened
files associated with the connection) and those connections had no activity
during a 2-hour period. If such a connection is found, the connection is ended.</li>
<li>The QFileSvr.400 file system cannot detect loops. The following path name
is an example of a loop: <pre> /QFileSvr.400/Remote2/QFileSvr.400/Remote1/QFileSvr.400/Remote2/...</pre>
<p>where <samp class="codeph">Remote1</samp> is the local system. When the path name that contains a loop is specified,
the QFileSvr.400 file system returns an error after a brief period of time.
The error indicates that a time-out has occurred.</p>
<p>The QFileSvr.400
file system will use an existing free session when communicating over SNA.
It is necessary to start the mode and establish a session for the QFileSvr.400
to successfully connect to the remote communications system.</p>
</li>
</ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxrfsfs.htm" title="The QFileSvr.400 file system provides transparent access to other file systems that reside on remote iSeries servers. It is accessed through a hierarchical directory structure.">i5/OS file server file system (QFileSvr.400)</a></div>
</div>
</div>
</body>
</html>