99 lines
6.5 KiB
HTML
99 lines
6.5 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="concept" />
|
|
<meta name="DC.Title" content="System request processing scenarios" />
|
|
<meta name="abstract" content="These scenarios explain how system request processing works with multiple types of systems." />
|
|
<meta name="description" content="These scenarios explain how system request processing works with multiple types of systems." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiwscenariocascade.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="rzaiwreqprocscen" />
|
|
<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>System request processing scenarios</title>
|
|
</head>
|
|
<body id="rzaiwreqprocscen"><a name="rzaiwreqprocscen"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">System request processing scenarios</h1>
|
|
<div><p>These scenarios explain how system request processing works with
|
|
multiple types of systems.</p>
|
|
<div class="section"><h4 class="sectiontitle">Scenario 1</h4><p>All servers are iSeries™ servers. System request processing
|
|
works normally.</p>
|
|
<p>The image depicts the following setup: Home system A
|
|
in New York connects to intermediate system B in Chicago, which connects to
|
|
intermediate system C in Los Angeles, which connects to end system D in Houston. </p>
|
|
<p><br /><a name="rzaiwreqprocscen__rzaiw513"><!-- --></a><img id="rzaiwreqprocscen__rzaiw513" src="rzaiw513.gif" alt="Cascaded systems" /><br /> </p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Scenario 2</h4><p>The New York system is a non-iSeries
|
|
server using 3270 or VTxxx Telnet. </p>
|
|
<p>The image depicts the following
|
|
setup: System A in New York, a non-iSeries server, connects to home system
|
|
B in Chicago, which connects to intermediate system C in Los Angeles, which
|
|
connects to end system D in Houston. <br /><a name="rzaiwreqprocscen__rzaiw516"><!-- --></a><img id="rzaiwreqprocscen__rzaiw516" src="rzaiw516.gif" alt="Cascaded systems" /><br /> </p>
|
|
<p>The system request
|
|
processing works like the first scenario except that Chicago is considered
|
|
as the home system. All system requests sent to the home system process on
|
|
the Chicago system.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Scenario 3</h4><p>The Houston system is a non-iSeries servers
|
|
using 3270 or VTxxx Telnet. </p>
|
|
<p>The image depicts the following setup:
|
|
Home system A in New York connects to intermediate system B in Chicago, which
|
|
connects to intermediate system C in Los Angeles, which connects to end system
|
|
D, a non-iSeries server in Houston. <br /><a name="rzaiwreqprocscen__rzaiw517"><!-- --></a><img id="rzaiwreqprocscen__rzaiw517" src="rzaiw517.gif" alt="Cascaded systems" /><br /></p>
|
|
<p>The system request
|
|
processing works like the first scenario except that Los Angeles is considered
|
|
as the end system for all system request processing. If you press the System
|
|
Request key and then press the Enter key, the System Request menu for Los
|
|
Angeles displays.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">Scenario 4</h4><p>The Los Angeles system is a non-iSeries
|
|
server using 3270 or VTxxx Telnet. </p>
|
|
<p>Home system A in New York connects
|
|
to end system B in Chicago, which connects to non-iSeries server system C
|
|
in Los Angeles, which connects to home system D in Houston, which connects
|
|
to end system E in Tokyo. <br /><a name="rzaiwreqprocscen__rzaiw518"><!-- --></a><img id="rzaiwreqprocscen__rzaiw518" src="rzaiw518.gif" alt="Cascaded systems" /><br /></p>
|
|
<p>The system request processing works
|
|
like the first scenario except that the Chicago system is considered as the
|
|
end system for system request processing. If you press the System Request
|
|
key and then press the Enter key, the System Request menu for Chicago displays.</p>
|
|
<p>If
|
|
you want to send a system request to the Tokyo system, you can map a function
|
|
key on the Houston system to the System Request key. If you map this function,
|
|
then the Tokyo system is the end system, and Houston is the home system.</p>
|
|
<p>The
|
|
image depicts the following setup: System A in New York connects to system
|
|
B in Chicago, which connects to non-iSeries server C in Los Angeles, which
|
|
connects to home system D in Houston, which connects to end system E in Tokyo.</p>
|
|
<br /><a name="rzaiwreqprocscen__rzaiw519"><!-- --></a><img id="rzaiwreqprocscen__rzaiw519" src="rzaiw519.gif" alt="Cascaded systems" /><br /><p>As an example of this mapping function for an iSeries 3270
|
|
Telnet server, the default keyboard mapping identifies the System Request
|
|
key as a 3270 PF11 key. For an iSeries 3270 Telnet client, the F11 key
|
|
is mapped to the 3270 PF11 key. If the Los Angeles system is a system that
|
|
uses the 3270 data stream, then pressing F11 maps the Los Angeles system to
|
|
the System Request key on the Houston system. The system request transmits
|
|
to the Tokyo system, and the System Request menu for Tokyo displays.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> This
|
|
mapping function is complex especially if you are using the VTxxx data stream
|
|
and are mapping between block data and character data.</div>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiwscenariocascade.htm" title="This scenario demonstrates the ability to start Telnet sessions while you are still in a Telnet session. After you have been connected, you can move between systems using system request values.">Telnet scenario: Cascaded Telnet sessions</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |