72 lines
4.6 KiB
HTML
72 lines
4.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="concept" />
|
||
|
|
<meta name="DC.Title" content="Plan APPC security" />
|
||
|
|
<meta name="abstract" content="Use this information to understand how Advanced Program-to-Program Communication (APPC) works and how you can set up the appropriate security for APPC on your system." />
|
||
|
|
<meta name="description" content="Use this information to understand how Advanced Program-to-Program Communication (APPC) works and how you can set up the appropriate security for APPC on your system." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvplansecstrat.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvappcterms.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvappcelement.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvappctarget.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="appcsecurity" />
|
||
|
|
<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>Plan APPC security</title>
|
||
|
|
</head>
|
||
|
|
<body id="appcsecurity"><a name="appcsecurity"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Plan APPC security</h1>
|
||
|
|
<div><p>Use this information to understand how Advanced Program-to-Program
|
||
|
|
Communication (APPC) works and how you can set up the appropriate security
|
||
|
|
for APPC on your system.</p>
|
||
|
|
<p>APPC allows programs on i5/OS™ to communicate with programs on other systems
|
||
|
|
having compatible communications support. Display station passthrough, distributed
|
||
|
|
data management, personal computers, and iSeries™ Access for Windows<sup>®</sup> can
|
||
|
|
use APPC communications.</p>
|
||
|
|
<p>When your system participates in a network with other systems, a new set
|
||
|
|
of doors and windows to your system becomes available. As security administrator,
|
||
|
|
you should be aware of the options that you can use to control the entrances
|
||
|
|
to your system in an APPC environment.</p>
|
||
|
|
<p><span class="uicontrol">Tip:</span> Many methods for connecting PCs to your system
|
||
|
|
servers depend on communications, such as APPC or TCP/IP. Be sure to consider
|
||
|
|
the security issues for connecting to both other systems and to PCs. When
|
||
|
|
you plan your network protection, make sure that you do not adversely affect
|
||
|
|
the PCs that are attached to your system.</p>
|
||
|
|
<div class="p">These links provide additional information:<ul><li><a href="../books/sc415443.pdf" target="_blank">APPC
|
||
|
|
Programming</a></li>
|
||
|
|
<li><a href="../rzahj/rzahj000.pdf" target="_blank">APPC,
|
||
|
|
APPN, and HPR</a></li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzamvappcterms.htm">Example: A basic APPC session</a></strong><br />
|
||
|
|
In an APPC environment, when a user or application on one system requests access to another system, the two systems set up a session. To establish the session, the systems must link two matching APPC device descriptions.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzamvappcelement.htm">Basic elements of APPC communications</a></strong><br />
|
||
|
|
APPC provides the ability for a user on one system to perform work on another system.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzamvappctarget.htm">APPC user access to the target system</a></strong><br />
|
||
|
|
The topics that follow describe the elements that determine how an APPC user gains entrance to the target system.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvplansecstrat.htm" title="This topic describes various aspects of planning a security strategy.">Plan your security strategy</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|