ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddm_5.4.0.1/rbae5mbraccess.htm

80 lines
5.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="Access members with DDM" />
<meta name="abstract" content="Members are supported for database I/O operations only if the target server is an iSeries server or a System/38. Members are not supported if the target server is neither an iSeries server nor a System/38." />
<meta name="description" content="Members are supported for database I/O operations only if the target server is an iSeries server or a System/38. Members are not supported if the target server is neither an iSeries server nor a System/38." />
<meta name="DC.subject" content="member access, considerations" />
<meta name="keywords" content="member access, considerations" />
<meta name="DC.Relation" scheme="URI" content="rbae5ddmop.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5expmbrs.htm" />
<meta name="DC.Relation" scheme="URI" content="rbae5exspec.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="rbae5mbraccess" />
<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 members with DDM</title>
</head>
<body id="rbae5mbraccess"><a name="rbae5mbraccess"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Access members with DDM</h1>
<div><p>Members are supported for database I/O operations only if the target
server is an <span class="keyword">iSeries™ server</span> or a <span class="keyword">System/38™</span>. Members are not supported
if the target server is neither an <span class="keyword">iSeries server</span> nor
a <span class="keyword">System/38</span>.</p>
<div class="section"><p>Members can be locked before use, using the <span class="cmdname">Allocate
Object (ALCOBJ)</span> command if the target server is an <span class="keyword">iSeries server</span> or
a <span class="keyword">System/38</span>.</p>
</div>
<div class="section"><p>The DDM file itself does not have members like a database file.
However, if a member is identified on the source server (for example, using
the <span class="cmdname">Override with Database File (OVRDBF)</span> command) and the
target server is an <span class="keyword">iSeries server</span> or
a <span class="keyword">System/38</span>, that member name
is used to identify a member in the target server's file. When the target
server is neither an <span class="keyword">iSeries server</span> nor
a <span class="keyword">System/38</span>, and if the member
name is specified as *FIRST, or in some cases *LAST, or the file name is the
same as the member name, then the RMTFILE parameter values in the DDM file
are sent without change. This allows file access on servers that do not support
members.</p>
</div>
<div class="section"><p>If the member name is other than *FIRST or in some cases *LAST,
or the file name is different from the member name (for example, when the
file is opened) and the target server does not support members, an error message
is sent to the requesting program and the function is not performed.</p>
</div>
</div>
<div>
<ul class="ullinks">
<li class="ulchildlink"><strong><a href="rbae5expmbrs.htm">Example: Access DDM remote members (iSeries server only)</a></strong><br />
These examples show how access to a DDM file becomes an indirect
reference (by using DDM) to a member of a file on a remote <span class="keyword">iSeries server</span>.
These examples are <span class="keyword">iSeries server</span>-to-<span class="keyword">iSeries server</span> examples.</li>
<li class="ulchildlink"><strong><a href="rbae5exspec.htm">Example: DDM file that opens a specific member</a></strong><br />
A specific file member can be specified in the RMTFILE parameter,
which is used only on the <span class="cmdname">Create DDM File (CRTDDMF)</span> and <span class="cmdname">Change
DDM File (CHGDDMF)</span> commands, by using the *NONSTD value followed
by the file, library, and member name.</li>
</ul>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5ddmop.htm" title="This topic provides task-oriented information and examples that describe various aspects of DDM operation considerations.">Operating considerations for DDM</a></div>
</div>
</div>
</body>
</html>