65 lines
4.2 KiB
HTML
65 lines
4.2 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="Control remote commands and batch jobs" />
|
||
|
|
<meta name="abstract" content="Several options are available to help you control which remote commands and jobs can run on your system." />
|
||
|
|
<meta name="description" content="Several options are available to help you control which remote commands and jobs can run on your system." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzamvappcsetup.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="appcremotecmd" />
|
||
|
|
<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>Control remote commands and batch jobs</title>
|
||
|
|
</head>
|
||
|
|
<body id="appcremotecmd"><a name="appcremotecmd"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Control remote commands and batch jobs</h1>
|
||
|
|
<div><p>Several options are available to help you control which remote
|
||
|
|
commands and jobs can run on your system.</p>
|
||
|
|
<p>You can use the network job action (JOBACN) network attribute to prevent
|
||
|
|
network jobs from being submitted or to prevent them from running automatically.</p>
|
||
|
|
<div class="p">If your system uses distributed data management (DDM), you can do the following:<ul><li>Restrict access to DDM files to prevent users from using the Submit Remote
|
||
|
|
Command (<span class="cmdname">SBMRMTCMD</span>) command from another system. To use
|
||
|
|
the SBMRMTCMD, the user must be able to open a DDM file. You also need to
|
||
|
|
restrict the ability to create DDM files.</li>
|
||
|
|
<li>Specify an exit program for the DDM request access (DDMACC) system value.
|
||
|
|
In the exit program, you can evaluate all DDM requests before allowing them.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>You can specify explicitly which program requests can run in a communications
|
||
|
|
environment by removing the PGMEVOKE routing entry from subsystem descriptions.
|
||
|
|
The PGMEVOKE routing entry allows the requester to specify the program that
|
||
|
|
runs. When you remove this routing entry from subsystem descriptions, such
|
||
|
|
as the QCMN subsystem description, you must add routing entries for the communications
|
||
|
|
requests that need to run successfully. </p>
|
||
|
|
<p>For each request that you want to allow, you can add a routing entry with
|
||
|
|
the compare value and the program name both equal to the program name. When
|
||
|
|
you use this method, you need to understand the work management environment
|
||
|
|
on your system and the types of communications requests that occur on your
|
||
|
|
system. If possible, you should test all types of communications requests
|
||
|
|
to ensure that they work properly after you change the routing entries. When
|
||
|
|
a communications request does not find an available routing entry, you receive
|
||
|
|
a CPF1269 message. Another alternative is to set the public authority to *EXCLUDE
|
||
|
|
for the transaction programs that you do not want to run on your system. </p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamvappcsetup.htm" title="This group of articles discuss various aspects of setting up security for APPC sessions.">Set up APPC security</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|