106 lines
6.6 KiB
HTML
106 lines
6.6 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="Timing considerations" />
|
||
|
|
<meta name="abstract" content="Timing considerations during startup can affect network communications." />
|
||
|
|
<meta name="description" content="Timing considerations during startup can affect network communications." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakustrnwk.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1997, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1997, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakutiming" />
|
||
|
|
<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>Timing considerations</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakutiming"><a name="rzakutiming"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Timing considerations</h1>
|
||
|
|
<div><p>Timing considerations during startup can affect network communications.</p>
|
||
|
|
<div class="section"><p>i5/OS™ has the capability to automatically start the
|
||
|
|
necessary subsystems, the TCP/IP stack, lines, interfaces, and servers at
|
||
|
|
the appropriate times during IPL. In most situations, your network communications
|
||
|
|
will start smoothly using this automatic startup process.</p>
|
||
|
|
<div class="p">However, depending
|
||
|
|
on your unique hardware and software configuration you might have problems
|
||
|
|
starting the network communication due to timing problems during IPL. Timing
|
||
|
|
problems can occur for several different reasons. For example: <ul><li>The processing speed and the number of input-output processors (IOPs)
|
||
|
|
can affect the startup of the network hardware resource. If your hardware
|
||
|
|
resource is slow to start, it might not be ready when TCP/IP tries to start.
|
||
|
|
Your network communications fail because the TCP/IP interfaces cannot be started.</li>
|
||
|
|
<li>You might encounter timing problems if you have customized your server
|
||
|
|
so that you are using subsystems other than the IBM-supplied subsystems. Many
|
||
|
|
subsystems are typically started by the IPL startup program. However, if you
|
||
|
|
are using customized subsystems that are not recognized by the IPL startup
|
||
|
|
program, they will not be automatically started at IPL. Your network communications
|
||
|
|
fail because these subsystems have not been started.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>If these types of timing problems occur, you can automatically
|
||
|
|
start the subsystems, the TCP/IP stack, interfaces, and servers in the correct
|
||
|
|
order by <a href="../rzal2/rzal2chgiplstartup.htm">creating
|
||
|
|
a customized IPL startup program</a>. You might need to put delays in the
|
||
|
|
startup program to ensure that each step of the startup process is initiated
|
||
|
|
at the appropriate time. For example, the subsystems should be started before
|
||
|
|
the TCP/IP stack, and the interfaces should be started after the communications
|
||
|
|
resources are available.</p>
|
||
|
|
<p>To change from using the default IPL startup
|
||
|
|
program to using a customized startup program, follow these steps:</p>
|
||
|
|
</div>
|
||
|
|
<ol><li class="stepexpand"><span>Create a customized startup program.</span> Things to consider
|
||
|
|
when creating a new startup program:<div class="note"><span class="notetitle">Note:</span> These steps are defined to ensure
|
||
|
|
that all required resources are active before the next step. </div>
|
||
|
|
<ul><li>Start the subsystems.</li>
|
||
|
|
<li>Allow delays after the subsystems start.</li>
|
||
|
|
<li>Use the <a href="../apis/qwdrsbsd.htm">Retrieve Subsystem Information (QWDRSBSD)</a> API to ensure
|
||
|
|
that the subsystems are active. Although this API is not required, it can
|
||
|
|
help you avoid timing problems.</li>
|
||
|
|
<li>Start TCP/IP specifying STRSVR *NO, STRIFC *NO and STRPTPPRF(*NO).<div class="note"><span class="notetitle">Note:</span> You
|
||
|
|
will start TCP/IP for both IPv4 and IPv6 by performing this step. If you do
|
||
|
|
not want start IPv6, specify STRIP6 (*NO) on the STRTCP command.</div>
|
||
|
|
</li>
|
||
|
|
<li>Start the interfaces with STRTCPIFC *AUTOSTART. Remember that TCP/IP should
|
||
|
|
vary on your <a href="rzakuvryon.htm#vryon">communication lines, controllers,
|
||
|
|
and devices</a>.</li>
|
||
|
|
<li>Allow delays to ensure the required interfaces are active.</li>
|
||
|
|
<li>Start the TCP/IP point-to-point session jobs with STRTCPPTP *AUTOSTART.</li>
|
||
|
|
<li>Start the servers with STRTCPSVR *AUTOSTART.</li>
|
||
|
|
<li>Start any other servers that are not started with the STRTCPSVR command.
|
||
|
|
Use STRHOSTSVR *ALL.</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li class="stepexpand"><span>Test the customized startup program by calling the program. To
|
||
|
|
properly test the program you need to end TCP/IP and the subsystems. However,
|
||
|
|
be aware this can terminate the connections that other users are using. Plan
|
||
|
|
accordingly to test when the system is dedicated to the test.</span></li>
|
||
|
|
<li class="stepexpand"><span>Change the QSTRUPPGM system value to point to your customized start-up
|
||
|
|
program. It is not recommended to directly change QSTRUP.</span></li>
|
||
|
|
<li class="stepexpand"><span>Change the IPL attribute to no longer start TCP/IP automatically
|
||
|
|
when the system is started. To change the IPL attribute, follow these steps:</span><ol type="a"><li><span>At the command line, type <samp class="codeph">CHGIPLA</samp> (Change IPL
|
||
|
|
Attributes), and press F4.</span></li>
|
||
|
|
<li><span>For the <em>Start TCP/IP</em> prompt, type <samp class="codeph">*NO</samp>.
|
||
|
|
This prevents TCP/IP from starting at IPL, letting your startup program control
|
||
|
|
the startup.</span></li>
|
||
|
|
</ol>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakustrnwk.htm" title="Learn how to start subsystems, TCP/IP, interfaces, and servers in the correct order and learn how to locate problems associated with startup.">Verify system startup considerations for networking</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|