98 lines
6.9 KiB
HTML
98 lines
6.9 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="Rules for specifying target server file names for DDM" />
|
|
<meta name="abstract" content="The rules for specifying the name of a DDM file (on the local iSeries server) are the same as for any other file type on an iSeries server. The rules, however, for specifying the name of a remote file depend on the type of target server." />
|
|
<meta name="description" content="The rules for specifying the name of a DDM file (on the local iSeries server) are the same as for any other file type on an iSeries server. The rules, however, for specifying the name of a remote file depend on the type of target server." />
|
|
<meta name="DC.subject" content="target DDM (TDDM), specifying file names, TDDM (target DDM), DDM target considerations" />
|
|
<meta name="keywords" content="target DDM (TDDM), specifying file names, TDDM (target DDM), DDM target considerations" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5fac.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5ddmtargetnames.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5noninames.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5locationnames.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5differences36.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5differences38.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="rbae5namecon" />
|
|
<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>Rules for specifying target server file names for DDM</title>
|
|
</head>
|
|
<body id="rbae5namecon"><a name="rbae5namecon"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Rules for specifying target server file names for DDM</h1>
|
|
<div><p>The rules for specifying the name of a DDM file (on the local <span class="keyword">iSeries™ server</span>) are the same as for any other
|
|
file type on an <span class="keyword">iSeries server</span>. The
|
|
rules, however, for specifying the name of a remote file depend on the type
|
|
of target server.</p>
|
|
<div class="section"><p>A remote file name can be specified only on the RMTFILE parameter
|
|
of the <span class="cmdname">Create DDM File (CRTDDMF)</span> and <span class="cmdname">Change DDM
|
|
File (CHGDDMF)</span> commands. The following list is the maximum number
|
|
of characters that can be used on the RMTFILE parameter to specify a remote
|
|
file name:</p>
|
|
<ul><li>For the <span class="keyword">iSeries server</span> (database
|
|
management): 33 characters. This maximum can occur when a full name is specified
|
|
that includes a library qualifier and a member name. For example: <pre>LIBRARY123/FILE123456(MEMBER1234)</pre>
|
|
The
|
|
value DM can be added to the name to specify that this is a data management
|
|
file. There can be one or more blanks between the name and DM. This is the
|
|
default.</li>
|
|
<li>For the <span class="keyword">iSeries server</span> (folder
|
|
management services): 76 characters. This maximum can occur when a fully qualified
|
|
path name (consisting of 76 characters) is specified. For example: <pre>/Path123/Path223/Path323/Path423/
|
|
Path523/Path623/Path723/Path823/Path923/DOC1 FMS</pre>
|
|
The value
|
|
FMS specifies that this is a folder management object. There can be one or
|
|
more blanks between the name and FMS.</li>
|
|
<li>For <span class="keyword">System/38™</span>: 33 characters.
|
|
This maximum can occur when a full name is specified that includes a library
|
|
qualifier and a member name. For example: <pre>FILE123456.LIBRARY123(MEMBER1234)</pre>
|
|
</li>
|
|
<li>For <span class="keyword">System/36™</span> and CICS<sup>®</sup>: 8 characters.
|
|
For example: <pre>FILE1234</pre>
|
|
</li>
|
|
<li>For other systems: 255 characters is the maximum length allowed by the
|
|
DDM architecture. The actual maximum length and syntax are determined by the
|
|
target server.</li>
|
|
</ul>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rbae5ddmtargetnames.htm">Target iSeries file names for DDM</a></strong><br />
|
|
As with local files, every <span class="keyword">iSeries</span> remote
|
|
file, library name, or member must begin with an alphabetic character (A through
|
|
Z, $, #, or @) and can be followed by no more than 9 alphanumeric characters:
|
|
A through Z, 0 through 9, $, #, @, _, or period (.). No name can exceed 10
|
|
characters. Blanks are not allowed in <span class="keyword">iSeries</span> names.</li>
|
|
<li class="ulchildlink"><strong><a href="rbae5noninames.htm">Target non-iSeries file names for DDM</a></strong><br />
|
|
For non-<span class="keyword">iSeries</span> remote
|
|
file names, the name must be in the form required by the target server. </li>
|
|
<li class="ulchildlink"><strong><a href="rbae5locationnames.htm">Use location-specific file names for commonly named files for DDM</a></strong><br />
|
|
When multiple servers are involved in a network, naming DDM files with location-specific file names can reduce confusion about which target server is being accessed for a file that has a commonly used name.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5fac.htm" title="These topics describe the types of files supported by an iSeries server, when the DDM file and remote file must exist, and how to specify the names of remote files. Also included are examples and considerations for iSeries-to-iSeries and iSeries-to-System/36 file accessing.">Access files with DDM</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="rbae5differences36.htm" title="This topic consists of a list of differences between the iSeries server and System/36.">iSeries server and System/36 DDM differences</a></div>
|
|
<div><a href="rbae5differences38.htm" title="This topic consists of a list of differences between the iSeries server and System/38.">iSeries server and System/38 DDM differences</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |