59 lines
4.3 KiB
HTML
59 lines
4.3 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="reference" />
|
||
|
|
<meta name="DC.Title" content="User exit program considerations for DDM" />
|
||
|
|
<meta name="abstract" content="There are some considerations that you should understand before using user exit programs for DDM." />
|
||
|
|
<meta name="description" content="There are some considerations that you should understand before using user exit programs for DDM." />
|
||
|
|
<meta name="DC.subject" content="command, RCVMSG (Receive Message), Receive Message (RCVMSG), command, CL, Receive Message (RCVMSG), message, receiving, command, CL" />
|
||
|
|
<meta name="keywords" content="command, RCVMSG (Receive Message), Receive Message (RCVMSG), command, CL, Receive Message (RCVMSG), message, receiving, command, CL" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5exitpgm.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5perfcon.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rbae5uepcsd" />
|
||
|
|
<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>User exit program considerations for DDM</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5uepcsd"><a name="rbae5uepcsd"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">User exit program considerations for DDM</h1>
|
||
|
|
<div><p>There are some considerations that you should understand before
|
||
|
|
using user exit programs for DDM.</p>
|
||
|
|
<div class="section"><p>If the user exit program is a CL program that creates an <span class="keyword">i5/OS™</span> exception, an inquiry message
|
||
|
|
is sent to the server operator on the target server if, for the target job,
|
||
|
|
the job attribute INQMSGRPY is *RQD (the default) or *SYSRPYL with no value
|
||
|
|
in the reply list for this message. The user exit program waits for a response
|
||
|
|
to the message on the target server, which causes the source job to wait also.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>There are other potential situations in which waiting could occur.
|
||
|
|
For example, if lengthy wait values are specified on the WAIT parameter of
|
||
|
|
the <span class="cmdname">Allocate Object (ALCOBJ)</span> or <span class="cmdname">Receive
|
||
|
|
Message (RCVMSG)</span> command, both the source and target jobs wait up
|
||
|
|
to the maximum time specified for an object lock to be obtained or a message
|
||
|
|
to be received by the target job.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5exitpgm.htm" title="Customers who use menu-level security, which is accomplished by restricting the user's access to functions on the server, are likely to have a large number of public files. Public files are those files to which the public has some or all authority. A user exit program allows you to restrict each DDM user's access to public files and to private files.">DDM server access control exit program for additional security</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rbae5perfcon.htm" title="These topics provide information to help you improve performance when using DDM and also provide some information about when to use something other than DDM to accomplish some functions.">Performance considerations for DDM</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|