70 lines
4.7 KiB
HTML
70 lines
4.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="Access intents" />
|
||
|
|
<meta name="abstract" content="When a program opens a file, it must specify how it intends to work with the records in the file: read, add, update, delete, or a combination of these." />
|
||
|
|
<meta name="description" content="When a program opens a file, it must specify how it intends to work with the records in the file: read, add, update, delete, or a combination of these." />
|
||
|
|
<meta name="DC.subject" content="access intent, data authority, security, access intents" />
|
||
|
|
<meta name="keywords" content="access intent, data authority, security, access intents" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5amc.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="rbae5accessintents" />
|
||
|
|
<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>Access intents</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5accessintents"><a name="rbae5accessintents"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Access intents</h1>
|
||
|
|
<div><p>When a program opens a file, it must specify how it intends to
|
||
|
|
work with the records in the file: read, add, update, delete, or a combination
|
||
|
|
of these.</p>
|
||
|
|
<div class="section"><p>Of course, to successfully perform these operations, the job,
|
||
|
|
user or both running the program must have the corresponding data authorities.
|
||
|
|
The <span class="keyword">iSeries™ server</span> does not check
|
||
|
|
to make sure all data authorities exist when the file is opened, but it does
|
||
|
|
check for each required data authority when the corresponding I/O operation
|
||
|
|
is done using the file. The <span class="keyword">System/36™</span> does
|
||
|
|
check these data authorities at open time; therefore, a program may no longer
|
||
|
|
work using a remote file on a <span class="keyword">System/36</span>,
|
||
|
|
even though the requester's data authorities to the remote file are the same
|
||
|
|
as for a local file (which will work).</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>For example, assume that a program is used by two groups of users
|
||
|
|
on an <span class="keyword">iSeries server</span> to access the
|
||
|
|
same local <span class="keyword">iSeries</span> file. Group
|
||
|
|
A has only *READ authority, while group B has *READ, *ADD, and *UPDATE. The
|
||
|
|
program always opens the file for *READ, *ADD, and *UPDATE. But it has a <em>read
|
||
|
|
only</em> logic path that is used when a member of group A calls the program.
|
||
|
|
In this way, no authority exceptions are encountered, even though exceptions
|
||
|
|
would be created if members of group A attempted to add or update records.
|
||
|
|
Now, if this program is redirected to a remote <span class="keyword">System/36</span> file
|
||
|
|
to which members of both user groups have the same data authorities as they
|
||
|
|
had to the local <span class="keyword">iSeries</span> file,
|
||
|
|
the program might not work for members of group A. This is because
|
||
|
|
the <span class="keyword">System/36</span> may reject requests
|
||
|
|
to open the file when the requester does not have data authorities matching
|
||
|
|
those specified in the access intent list accompanying the open request.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5amc.htm" title="Access methods control what subsets of functions can be performed after a particular remote file is opened. This might mean that an iSeries program, or a group of programs sharing a non-iSeries file, cannot do all the same operations that are possible using a file that is on the local iSeries server.">Work with access methods for DDM</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|