108 lines
7.8 KiB
HTML
108 lines
7.8 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="Non-iSeries target restrictions and considerations for DDM" />
|
|
<meta name="abstract" content="In addition to the restrictions that apply when the target server is an iSeries server, the restrictions in this topic also might apply when the target server is not an iSeries server or a System/38." />
|
|
<meta name="description" content="In addition to the restrictions that apply when the target server is an iSeries server, the restrictions in this topic also might apply when the target server is not an iSeries server or a System/38." />
|
|
<meta name="DC.subject" content="performance considerations, operations delay" />
|
|
<meta name="keywords" content="performance considerations, operations delay" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5compile.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ovrdbf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5cpyfcmd.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5mbrcmds.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5srccmds.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="rbae5nonres" />
|
|
<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>Non-iSeries target restrictions
|
|
and considerations for DDM</title>
|
|
</head>
|
|
<body id="rbae5nonres"><a name="rbae5nonres"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Non-<span class="keyword">iSeries</span> target restrictions
|
|
and considerations for DDM</h1>
|
|
<div><p>In addition to the restrictions that apply when the target server
|
|
is an <span class="keyword">iSeries™ server</span>, the restrictions
|
|
in this topic also might apply when the target server is not an <span class="keyword">iSeries server</span> or
|
|
a <span class="keyword">System/38™</span>.</p>
|
|
<div class="section"><p> Whether they apply depends on what the target server supports.
|
|
You should refer to that server's documentation for more information.</p>
|
|
<ul><li>Only field data types that are common to the source and target servers
|
|
can normally be processed by HLL applications. Floating-point data is an example
|
|
of a data type that might not be common. Records can be transmitted that contain
|
|
floating-point data, but the representation of floating-point data sent between
|
|
servers might differ. <p>The packed signs sent between systems might differ;
|
|
for example, one server might use a C and another server might use an F.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> It
|
|
is possible for you to write your application program so that it interprets
|
|
the byte string for a record processed through a DDM file in any way that
|
|
you want. However, whenever you do this, it is your responsibility
|
|
to ensure that the data is handled correctly.</div>
|
|
</li>
|
|
<li>Any operations that request a delay period before returning, such as for
|
|
record lock wait times, might be rejected or changed to a zero wait time by
|
|
the target server.</li>
|
|
<li>Lock requests can be changed by the target server to a more restrictive
|
|
lock. This might prevent some operations from occurring at the same time that
|
|
can otherwise be performed on the local <span class="keyword">iSeries server</span>.
|
|
See <a href="rbae5alcobj.htm#rbae5alcobj">ALCOBJ (Allocate Object) command</a> for more information.</li>
|
|
<li>Some <span class="keyword">iSeries</span> parameters
|
|
are ignored or cause errors if they are used during remote file processing
|
|
on non-<span class="keyword">iSeries</span> target servers.
|
|
Examples are the FRCRATIO and FMTSLR parameters on some of the file commands.
|
|
For more information, see OVRDBF (Override with Database File) command and
|
|
see Copy commands with DDM.</li>
|
|
<li>Member names are not supported in the DDM architecture. When the target
|
|
server is not an <span class="keyword">iSeries server</span> or
|
|
a <span class="keyword">System/38</span>, CL commands that
|
|
have a MBR parameter, such as the <span class="cmdname">Clear Physical File Member (CLRPFM)</span> command,
|
|
must be changed if the parameter specifies a member name that is different
|
|
than the file name. If the member name is different, an error occurs if the
|
|
command is used for a non-<span class="keyword">iSeries</span> remote
|
|
file. For some commands, MBR(*FIRST) or MBR(*LAST) is also valid. See Member-related
|
|
commands with DDM for a list of all the CL commands related to file members,
|
|
and for those that are not valid for accessing files on non-<span class="keyword">iSeries</span> target
|
|
servers. <div class="note"><span class="notetitle">Note:</span> MBR(*LAST) is not supported by <span class="keyword">System/38</span>.</div>
|
|
</li>
|
|
<li>If a parameter on a CL command requires the name of a source file, then
|
|
the names of the DDM files that refer to non-<span class="keyword">iSeries</span> target
|
|
files cannot be specified. An <span class="keyword">iSeries server</span> cannot
|
|
determine whether a remote file on a non-<span class="keyword">iSeries</span> target
|
|
is in fact a source file. (See Source file commands for a list of all the
|
|
CL commands related to source files.)</li>
|
|
<li>Certain <span class="keyword">iSeries</span> commands
|
|
that are valid for <span class="keyword">iSeries</span> or <span class="keyword">System/38</span> target servers are not valid
|
|
for other targets. See DDM-related CL command lists for the lists of commands
|
|
that are not supported when the target is not an <span class="keyword">iSeries server</span> or
|
|
a <span class="keyword">System/38</span>.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5compile.htm" title="Remote files can be accessed by iSeries application programs written in the HLL and control language.">Program modification requirements for DDM</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rbae5ovrdbf.htm" title="The Override with Database File (OVRDBF) command can be used with DDM to override (replace) a local database file named in the program with a DDM file; the DDM file causes the associated remote file to be used by the program instead of the local database file.">OVRDBF (Override with Database File) command</a></div>
|
|
<div><a href="rbae5cpyfcmd.htm" title="This topic describes the DDM implications of these CL commands.">Copy commands with DDM</a></div>
|
|
<div><a href="rbae5mbrcmds.htm" title="Database file operations that apply to a member can be used by DDM.">Member-related commands with DDM</a></div>
|
|
<div><a href="rbae5srccmds.htm" title="If the target server is an iSeries server or a System/38, these CL commands can support a DDM file as a source file (on the SRCFILE parameter).">Source file commands</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |