75 lines
4.9 KiB
HTML
75 lines
4.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="Create a DDM file using RDB directory entry information" />
|
||
|
|
<meta name="abstract" content="You can create a DDM file that uses the remote location information from a relational database (RDB) directory entry." />
|
||
|
|
<meta name="description" content="You can create a DDM file that uses the remote location information from a relational database (RDB) directory entry." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5partfile.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5jobasp.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaly/rzalydmkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../ddp/rbal1kickoff.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="rbae5crtrdb" />
|
||
|
|
<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>Create a DDM file using RDB directory entry information</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5crtrdb"><a name="rbae5crtrdb"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Create a DDM file using RDB directory entry information</h1>
|
||
|
|
<div><p>You can create a DDM file that uses the remote location information
|
||
|
|
from a relational database (RDB) directory entry.</p>
|
||
|
|
<div class="section"><p>Each DDM file that uses an RDB directory entry contains the following
|
||
|
|
information.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">DDM file value and description of values</h4><dl><dt class="dlterm">DDM file name</dt>
|
||
|
|
<dd>The name of the DDM file on the source server that is used to identify
|
||
|
|
a specific remote file.</dd>
|
||
|
|
<dt class="dlterm">Remote file name</dt>
|
||
|
|
<dd>The actual file name of the remote file; that is, the name by which it
|
||
|
|
is known on the target server.</dd>
|
||
|
|
<dt class="dlterm">Remote location name</dt>
|
||
|
|
<dd>Specify *RDB to indicate that the remote location information is taken
|
||
|
|
from an RDB directory entry.</dd>
|
||
|
|
<dt class="dlterm">Relational database</dt>
|
||
|
|
<dd>The name of the relational database entry used for the remote location
|
||
|
|
information. The remote location information in the RDB directory entry is
|
||
|
|
used to establish the data link to the target server (remote location), over
|
||
|
|
which a DDM conversation is established when the DDM file is accessed.</dd>
|
||
|
|
</dl>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>You need to specify an RDB directory
|
||
|
|
entry associated with an auxiliary storage pool (ASP) group for the DDM file's
|
||
|
|
remote location information to access that ASP group.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rbae5jobasp.htm">Effect of job description on ASP group selection</a></strong><br />
|
||
|
|
When the target DDM server is configured to use ASP groups, and the DDM file specifies a relational database name, the relational database entry specified in the DDM file on the client is used to establish the ASP group for the target job.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5partfile.htm" title="A system object with type *FILE exists on the source server to identify a remote file. It combines the characteristics of a device file and a database file. As a device file, the DDM file refers to a remote location name, local location name, device name, mode, and a remote network ID to identify a remote server as the target server. The DDM file appears to the application program as a database file and serves as the access device between a source server program and a remote file.">Parts of DDM: DDM file</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzaly/rzalydmkickoff.htm">Disk management</a></div>
|
||
|
|
<div><a href="../ddp/rbal1kickoff.htm">Distributed database programming</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|