58 lines
3.9 KiB
HTML
58 lines
3.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="Use location-specific file names for commonly named files for DDM" />
|
|
<meta name="abstract" content="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." />
|
|
<meta name="description" content="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." />
|
|
<meta name="DC.subject" content="location-specific file name, remote system, location-specific file names" />
|
|
<meta name="keywords" content="location-specific file name, remote system, location-specific file names" />
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5namecon.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="rbae5locationnames" />
|
|
<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>Use location-specific file names for commonly named files
|
|
for DDM</title>
|
|
</head>
|
|
<body id="rbae5locationnames"><a name="rbae5locationnames"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Use location-specific file names for commonly named files
|
|
for DDM</h1>
|
|
<div><p>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.</p>
|
|
<div class="section"><p>For example, for an inventory file that may be named INVEN on
|
|
multiple servers, using location-specific names such as NYCINVEN, STLINVEN,
|
|
and DALINVEN for the DDM files on the local server to access files in New
|
|
York City, St. Louis, and Dallas helps you to access the correct file.</p>
|
|
</div>
|
|
<div class="section"><p>Using an abbreviation or code that identifies the destination
|
|
target server as part of the DDM file names makes it easier to remember where
|
|
the desired remote file is located.</p>
|
|
</div>
|
|
<div class="section"><p>For non-<span class="keyword">iSeries™</span> remote
|
|
files that have record formats, using the same name for the DDM file as for
|
|
the record format can also be useful.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5namecon.htm" title="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.">Rules for specifying target server file names for DDM</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |