ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamv_5.4.0.1/rzamvrevcomm.htm

60 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="Review communications entries and remote location names" />
<meta name="abstract" content="Ensure that the communications entries are secure." />
<meta name="description" content="Ensure that the communications entries are secure." />
<meta name="DC.Relation" scheme="URI" content="rzamvmonsubsystem.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="revcomm" />
<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>Review communications entries and remote location names</title>
</head>
<body id="revcomm"><a name="revcomm"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Review communications entries and remote location names</h1>
<div><p>Ensure that the communications entries are secure.</p>
<div class="p">When a communications job enters your system, the system uses the communications
entries and the remote location name entries in the active subsystem to determine
how the communications job will run. Look at the following for these entries:<ul><li>All subsystems are capable of running communications jobs. If a subsystem
that you intend for communications is not active, a job that is trying to
enter your system might find an entry in another subsystem description that
meets its needs. You need to look at the entries in all subsystem descriptions. </li>
<li>A communications entry contains a job description. The job description
may contain request data that runs a command or program. Look at your communications
entries and their associated job descriptions to ensure that you understand
how jobs will start. </li>
<li>A communications entry also specifies a default user profile that the
system uses in some situations. Make sure that you understand the role of
default profiles. If your system contains default profiles, you should ensure
that they are profiles with minimal authority. </li>
</ul>
</div>
<p>You can use the Print Subsystem Description (<span class="cmdname">PRTSBSDAUT</span>)
command to identify communications entries that specify a user profile name.</p>
<p>For additional information about the permissions assigned to default user
profiles, see: <a href="rzamvappcjobs.htm">Target system
assignment of user profiles for jobs</a>.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvmonsubsystem.htm" title="This article provides suggestions for reviewing the subsystem descriptions that currently exist on your system.">Monitor subsystem descriptions</a></div>
</div>
</div>
</body>
</html>