47 lines
3.7 KiB
HTML
47 lines
3.7 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="Basic elements of APPC communications" />
|
|
<meta name="abstract" content="APPC provides the ability for a user on one system to perform work on another system." />
|
|
<meta name="description" content="APPC provides the ability for a user on one system to perform work on another system." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvappcsecurity.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="appcelement" />
|
|
<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>Basic elements of APPC communications</title>
|
|
</head>
|
|
<body id="appcelement"><a name="appcelement"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Basic elements of APPC communications</h1>
|
|
<div><p>APPC provides the ability for a user on one system to perform work on another system.</p>
|
|
<p>The system from which the request starts is called any of the following: <span class="uicontrol">source system</span>, <span class="uicontrol">local system</span>, or <span class="uicontrol">client</span>.</p>
|
|
<p>The system that receives the request is called any of the following: <span class="uicontrol">target system</span>, <span class="uicontrol">remote system</span>, or <span class="uicontrol">server</span>.</p>
|
|
<div class="p">From the perspective of a security administrator, the following must happen before a user on one system (SYSTEMA) can perform meaningful work on another system (SYSTEMB):<ul><li>The source system (SYSTEMA) must provide a path to the target system (SYSTEMB). This path is called an <span class="uicontrol">APPC session</span>.</li>
|
|
<li>The target system must identify the user and associate the user with a user profile. The target system must support the encryption algorithm of the source system.</li>
|
|
<li>The target system must start a job for the user with an appropriate environment (work management values).</li>
|
|
</ul>
|
|
</div>
|
|
<p>The security administrator on the target system has primary responsibility for ensuring that APPC users do not violate security. However, when the security administrators on both systems work together, the job of managing APPC security is much easier.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvappcsecurity.htm" title="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.">Plan APPC security</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |