85 lines
5.7 KiB
HTML
85 lines
5.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="reference" />
|
||
|
<meta name="DC.Title" content="Parameter list example for DDM" />
|
||
|
<meta name="abstract" content="The commands in this topic are in a CL program that a user named KAREN on the source server (NEWYORK) is using. The remote location configuration of the target server (CHICAGO) specifies SECURELOC(*YES) for the NEWYORK source server. This action indicates that user IDs are to be sent and that a user profile for KAREN exists on the target server." />
|
||
|
<meta name="description" content="The commands in this topic are in a CL program that a user named KAREN on the source server (NEWYORK) is using. The remote location configuration of the target server (CHICAGO) specifies SECURELOC(*YES) for the NEWYORK source server. This action indicates that user IDs are to be sent and that a user profile for KAREN exists on the target server." />
|
||
|
<meta name="DC.subject" content="parameter list, example" />
|
||
|
<meta name="keywords" content="parameter list, example" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rbae5exitpgm.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="rbae5parameterlist" />
|
||
|
<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>Parameter list example for DDM</title>
|
||
|
</head>
|
||
|
<body id="rbae5parameterlist"><a name="rbae5parameterlist"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Parameter list example for DDM</h1>
|
||
|
<div><p>The commands in this topic are in a CL program that a user named
|
||
|
KAREN on the source server (NEWYORK) is using. The remote location configuration
|
||
|
of the target server (CHICAGO) specifies SECURELOC(*YES) for the NEWYORK source
|
||
|
server. This action indicates that user IDs are to be sent and that a user
|
||
|
profile for KAREN exists on the target server.</p>
|
||
|
<div class="section"><p>The program used by KAREN accesses a DDM file named LOCFILEX that
|
||
|
opens a remote file named RMTFILEX on the target server in Chicago. Both servers
|
||
|
are <span class="keyword">iSeries™ server</span>s. The file is
|
||
|
being opened for input.</p>
|
||
|
</div>
|
||
|
<div class="section"><div class="p"> <pre>CRTDDMF FILE(LOCFILEX) RMTFILE(LIBX/RMTFILEX)
|
||
|
RMTLOCNAME(CHICAGO)
|
||
|
|
||
|
Open Database File (OPNDBF) FILE(LOCFILEX) OPTION(*INP)
|
||
|
Monitor Message (MONMSG) MSGID(CPF0000) EXEC(GOTO EXIT)
|
||
|
|
||
|
CLOF OPNID(LOCFILEX)
|
||
|
EXIT: End Program (ENDPGM)</pre>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="section"><div class="p">When the <span class="cmdname">Open Database File (OPNDBF)</span> command
|
||
|
is run on the NEWYORK source server, the DDM file named LOCFILEX is opened.
|
||
|
DDM sends a request to the target server to open RMTFILEX in LIBX for input
|
||
|
operations. From this information, the target server builds the following
|
||
|
parameter list to be used by the user exit program for verification: <pre>KAREN *DDM OPEN RMTFILEX LIBX *N 0 24 CHICAGO NEWYORK 1000</pre>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="section"><p>This parameter list shows only the significant characters that
|
||
|
would be sent in each field; all the padded blanks and zeros are not shown.
|
||
|
For example, the field containing KAREN is padded with five blanks because
|
||
|
it is a 10-character field. This parameter list is sent only for the open
|
||
|
operation, although several input operations might be performed on RMTFILEX.</p>
|
||
|
</div>
|
||
|
<div class="section"><p>This parameter list is sent to the user exit program specified
|
||
|
on the DDMACC parameter of the <span class="cmdname">Change Network Attributes (CHGNETA)</span> command.
|
||
|
The user exit program determines if user KAREN is authorized to open RMTFILEX.
|
||
|
If she is authorized, the program returns a 1 in the return code field, and
|
||
|
she can open the file and perform read operations. If the program returns
|
||
|
a 0 in the return code field, user KAREN receives a message in the job log
|
||
|
indicating that she is not authorized to use the file.</p>
|
||
|
</div>
|
||
|
<div class="section"><p>When all the input operations are completed, the <span class="cmdname">Close
|
||
|
File (CLOF)</span> command runs on the source server, and DDM sends the
|
||
|
request to close the file.</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>
|
||
|
</body>
|
||
|
</html>
|