ibm-information-center/dist/eclipse/plugins/i5OS.ic.cl_5.4.0.1/chgddmf.htm

722 lines
30 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<!doctype html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head><META http-equiv="Content-Type" content="text/html; charset=utf-8">
<title>Change DDM File (CHGDDMF)</title>
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body bgcolor="white">
<script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<a name="CHGDDMF.Top_Of_Page"></a>
<h2>Change DDM File (CHGDDMF)</h2>
<table width="100%">
<tr>
<td valign="top" align="left"><b>Where allowed to run: </b>All environments (*ALL)<br>
<b>Threadsafe: </b>No
</td>
<td valign="top" align="right">
<a href="#CHGDDMF.PARAMETERS.TABLE">Parameters</a><br>
<a href="#CHGDDMF.COMMAND.EXAMPLES">Examples</a><br>
<a href="#CHGDDMF.ERROR.MESSAGES">Error messages</a></td>
</tr>
</table>
<div> <a name="CHGDDMF"></a>
<p>The Change Distributed Data Management File (CHGDDMF) command changes, in the distributed data management file (DDM) description, one or more of the attributes of the specified DDM file. The DDM file is used as a reference file by programs on the iSeries system to access files located on any target system in the iSeries system DDM network.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div>
<h3><a name="CHGDDMF.PARAMETERS.TABLE">Parameters</a></h3>
<table border="1" cellpadding="4" cellspacing="0">
<!-- col1="10" col2="15" col3="30" col4="10" -->
<tr>
<th bgcolor="aqua" valign="bottom" align="left">Keyword</th>
<th bgcolor="aqua" valign="bottom" align="left">Description</th>
<th bgcolor="aqua" valign="bottom" align="left">Choices</th>
<th bgcolor="aqua" valign="bottom" align="left">Notes</th>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#CHGDDMF.FILE"><b>FILE</b></a></td>
<td valign="top">DDM file</td>
<td valign="top"><i>Qualified object name</i></td>
<td valign="top" rowspan="3">Required, Key, Positional 1</td>
</tr>
<tr>
<td valign="top">Qualifier 1: DDM file</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, <b><u>*LIBL</u></b>, *CURLIB</td>
</tr><tr>
<td valign="top" rowspan="5"><a href="#CHGDDMF.RMTFILE"><b>RMTFILE</b></a></td>
<td valign="top">Remote file</td>
<td valign="top">Single values: <b><u>*SAME</u></b><br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="5">Optional, Positional 2</td>
</tr>
<tr>
<td valign="top">Element 1: File</td>
<td valign="top">
Single values: <b><u>*NONSTD</u></b><br>Other values: <i>Qualified object name</i></td>
</tr>
<tr>
<td valign="top" style="padding-left:10pt">Qualifier 1: File</td>
<td valign="top"><i>Name</i></td>
</tr><tr>
<td valign="top" style="padding-left:10pt">Qualifier 2: Library</td>
<td valign="top"><i>Name</i>, *LIBL, *CURLIB</td>
</tr><tr>
<td valign="top">Element 2: Nonstandard file 'name'</td>
<td valign="top">
<i>Character value</i></td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#CHGDDMF.RMTLOCNAME"><b>RMTLOCNAME</b></a></td>
<td valign="top">Remote location</td>
<td valign="top">Single values: *RDB<br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="3">Optional, Positional 3</td>
</tr>
<tr>
<td valign="top">Element 1: Name or address</td>
<td valign="top">
<i>Character value</i>, <b><u>*SAME</u></b>, *DEVD</td>
</tr>
<tr>
<td valign="top">Element 2: Type</td>
<td valign="top">
<b><u>*SAME</u></b>, *SNA, *IP</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.LVLCHK"><b>LVLCHK</b></a></td>
<td valign="top">Record format level check</td>
<td valign="top"><b><u>*SAME</u></b>, *RMTFILE, *NO</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.RDB"><b>RDB</b></a></td>
<td valign="top">Relational database</td>
<td valign="top"><i>Name</i>, <b><u>*SAME</u></b></td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.TEXT"><b>TEXT</b></a></td>
<td valign="top">Text 'description'</td>
<td valign="top"><i>Character value</i>, <b><u>*SAME</u></b>, *BLANK</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="2"><a href="#CHGDDMF.DEV"><b>DEV</b></a></td>
<td valign="top">Device</td>
<td valign="top"><i>Element list</i></td>
<td valign="top" rowspan="2">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: APPC device description</td>
<td valign="top">
<i>Name</i>, <b><u>*SAME</u></b>, *LOC</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.LCLLOCNAME"><b>LCLLOCNAME</b></a></td>
<td valign="top">Local location</td>
<td valign="top"><i>Communications name</i>, <b><u>*SAME</u></b>, *LOC, *NETATR</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.MODE"><b>MODE</b></a></td>
<td valign="top">Mode</td>
<td valign="top"><i>Communications name</i>, <b><u>*SAME</u></b>, *NETATR</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.RMTNETID"><b>RMTNETID</b></a></td>
<td valign="top">Remote network identifier</td>
<td valign="top"><i>Communications name</i>, <b><u>*SAME</u></b>, *LOC, *NETATR, *NONE</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.PORT"><b>PORT</b></a></td>
<td valign="top">Port number</td>
<td valign="top">1-65535, <b><u>*SAME</u></b>, *DRDA</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top" rowspan="3"><a href="#CHGDDMF.ACCMTH"><b>ACCMTH</b></a></td>
<td valign="top">Access method</td>
<td valign="top">Single values: <b><u>*SAME</u></b>, *RMTFILE, *COMBINED<br>Other values: <i>Element list</i></td>
<td valign="top" rowspan="3">Optional</td>
</tr>
<tr>
<td valign="top">Element 1: Remote file attribute</td>
<td valign="top">
<b><u>*KEYED</u></b>, *ARRIVAL</td>
</tr>
<tr>
<td valign="top">Element 2: Local access method</td>
<td valign="top">
<b><u>*BOTH</u></b>, *RANDOM, *SEQUENTIAL</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.SHARE"><b>SHARE</b></a></td>
<td valign="top">Share open data path</td>
<td valign="top"><b><u>*SAME</u></b>, *NO, *YES</td>
<td valign="top">Optional</td>
</tr>
<tr>
<td valign="top"><a href="#CHGDDMF.PTCCNV"><b>PTCCNV</b></a></td>
<td valign="top">Protected conversation</td>
<td valign="top"><b><u>*SAME</u></b>, *NO, *YES</td>
<td valign="top">Optional</td>
</tr>
</table>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
</div>
<div> <a name="CHGDDMF.FILE"></a>
<h3>DDM file (FILE)</h3>
<p>Specifies the distributed data management (DDM) file to be changed.
</p>
<p>This is a required parameter.
</p>
<p><b>Qualifier 1: DDM file</b>
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the DDM file.
</dd>
</dl>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b><u>*LIBL</u></b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
</dl>
<dl>
<dt><b>*CURLIB</b></dt>
<dd>The current job library is used to locate the DDM file. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the library where the DDM file is located.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.RMTFILE"></a>
<h3>Remote file (RMTFILE)</h3>
<p>Specifies the name of the remote file as it is coded on the target system. The remote file does not need to exist when the Distributed Data Management (DDM) file is changed.
</p>
<p>
<b>Note: </b>This file name must be specified in code page 500.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The name of the remote file does not change.
</dd>
</dl>
<p><b>Element 1: File</b>
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*NONSTD</u></b></dt>
<dd>The remote file name is not at standard iSeries file name. Specify the complete file name in apostrophes for the second element of this parameter.
</dd>
</dl>
<dl>
<dt><b></b></dt>
<dd>
<p><b>Qualifier 1: File</b>
</p>
<dl>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the remote file as it is known on the remote system. If the remote system is an iSeries system, specify the file name. The file name can be up to 10 characters in length. If the remote system is a System/36, the file name is the same as its System/36 file label. The file name can be up to eight characters in length. If the remote system is a System/38, a simple (unqualified) file name can be specified. The file name can be up to 10 characters in length. Labels for all other remote systems (including qualified file names for System/38) must use *NONSTD followed by the remote file name in apostrophes.
</dd>
</dl>
</dd>
<dt><b></b></dt>
<dd>
<p><b>Qualifier 2: Library</b>
</p>
<dl>
<dt><b>*LIBL</b></dt>
<dd>All libraries in the library list for the current thread are searched until the first match is found.
</dd>
<dt><b>*CURLIB</b></dt>
<dd>The current library for the job is used to locate the file. If no library is specified as the current library for the job, QGPL is used.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specifies the library where the file is located.
</dd>
</dl>
<p>
<b>Note: </b>The library name is used only if the target system is an iSeries system.
</p>
</dd>
</dl>
<p><b>Element 2: Nonstandard file 'name'</b>
</p>
<dl>
<dt><b><i>character-value</i></b></dt>
<dd>For target systems that allow naming conventions other than those used by the iSeries system and System/36, and when specifying a qualified System/38 file name and when specifying a <i>member</i> name of a remote iSeries or System/38 file, specify up to 255 characters for the name of the remote file to be accessed. The name must be coded in the form required by the target system. The name must always be enclosed in apostrophes, and may contain lowercase letters, blanks, periods, or any other special characters.
<p>Names for the iSeries system, System/38, and System/36 must be in uppercase, and no blanks are allowed.
</p>
<p>If the target system is an iSeries system or a System/38, a file name, library name, and member name can all be specified. If a member name is specified, the full file name must be enclosed in apostrophes and must follow the value *NONSTD, and the member name must be enclosed in parentheses and immediately follow (with no space) either the library name (System/38) or the file name (iSeries).
</p>
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.RMTLOCNAME"></a>
<h3>Remote location (RMTLOCNAME)</h3>
<p>Specifies the remote (target) system location name or address used with the distributed data management (DDM) file. Multiple DDM files can use the same remote location for the target system.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b>*RDB</b></dt>
<dd>The remote location information from the relational database entry specified for the <b>Relational database (RDB)</b> parameter is used to determine the remote system.
</dd>
</dl>
<p><b>Element 1: Name or address</b>
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The remote location name specified in the file description does not change.
</dd>
<dt><b>*DEVD</b></dt>
<dd>The remote location name defined in the device description specified for the <b>Device (DEV)</b> parameter is used.
<p>
<b>Note: </b>If *LOC is specified for the DEV parameter, a remote location name must be specified for this parameter.
</p>
</dd>
<dt><b><i>character-value</i></b></dt>
<dd>Specify the name or address of the remote location that is associated with the target system. The remote location, which is used in accessing the target system, does not need to exist when the DDM file is created but must exist when the DDM file is opened. The remote location can take several forms:
<ul>
<li>SNA remote location name (LU name). Specify a maximum of 8 characters for the remote location name. If this form is used, the address type of this parameter must be *SNA (the default).
</li>
<li>SNA remote network identifier and remote location name separated by a period. Specify a maximum of 8 characters for the remote location name, and a maximum of 8 characters for the remote network identifier. If this form of the parameter is used, the address type of this parameter must be *SNA (the default), and any value specified for the RMTNETID parameter must agree. If the RMTNETID parameter is not specified, the RMTNETID value will be set to agree with the RMTLOCNAME parameter.
</li>
<li>IP address in dotted decimal form. Specify an internet protocol address in the form nnn.nnn.nnn.nnn where each nnn is a number in the range 0 through 255. If this form is used, the address type of this parameter must be specified as *IP.
</li>
<li>IP host domain name. Specify an internet host domain name of up to 254 characters in length. If this form is used, the address type of this parameter must be specified as *IP.
</li>
</ul>
<p>If *IP is specified for the address type, the DDM server at the remote location must support the use of TCP/IP, and the DEV, LCLLOCNAME, RMTNETID, and MODE parameters will be ignored.
</p>
<p>If *IP is not specified, the DDM server must support SNA connectivity, and the PORT parameter will be ignored.
</p>
</dd>
</dl>
<p><b>Element 2: Type</b>
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The address type does not change.
</dd>
<dt><b>*SNA</b></dt>
<dd>The remote location has a Systems Network Architecture (SNA) address type.
</dd>
<dt><b>*IP</b></dt>
<dd>The remote location has an Internet Protocol (IP) address type.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.LVLCHK"></a>
<h3>Record format level check (LVLCHK)</h3>
<p>Specifies whether the level identifiers in the program are checked with the level identifiers of the record formats in the remote file when the distributed data management (DDM) file is opened. If they do not match, an error message is sent to the program requesting the open, and neither the DDM file nor the associated remote file is opened. This parameter value can be overridden by an Override Database File (OVRDBF) command before the remote file is opened.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The level identifiers value does not change.
</dd>
<dt><b>*RMTFILE</b></dt>
<dd>The level identifiers of the record formats of the remote file are checked at the time the DDM file is opened.
<p>
<b>Note: </b>For systems other than iSeries systems, the program must be compiled (or recompiled) by using the DDM file. During the compile operation, the DDM file is used to establish communications with the target system, get the remote file's attributes from the target system, and create the level identifier values so they can be included in the compiled program for later level checking.
</p>
</dd>
</dl>
<dl>
<dt><b>*NO</b></dt>
<dd>The level identifiers are not checked when the file is opened.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.RDB"></a>
<h3>Relational database (RDB)</h3>
<p>Specifies the relational database entry that is used to determine the remote location information for the DDM file.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The relational database entry does not change.
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of the relational database entry that identifies the target system or target ASP (auxiliary storage pool) group. The relational database name can refer to a remote system or an ASP group that is configured and available on a remote system. The relational database entry does not need to exist when the DDM file is created but must exist when the DDM file is opened. This parameter is required when *RDB is used as the remote location name (RMTLOCNAME parameter).
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.TEXT"></a>
<h3>Text 'description' (TEXT)</h3>
<p>Specifies the text that briefly describes the object.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The text (if any) does not change.
</dd>
<dt><b>*BLANK</b></dt>
<dd>No text is specified.
</dd>
<dt><b><i>character-value</i></b></dt>
<dd>Specify no more than 50 characters of text, enclosed in apostrophes.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.DEV"></a>
<h3>Device (DEV)</h3>
<p>Specifies the name of the advanced program-to-program communications (APPC) device description on the source system that is used with this DDM file.
</p>
<p>This parameter will be ignored if *IP is specified for the <b>Remote location (RMTLOCNAME)</b> parameter.
</p>
<p>More information on device names is in the APPC Programming book, SC41-5443.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The device name specified in the file description does not change.
</dd>
<dt><b>*LOC</b></dt>
<dd>The device associated with the remote location is used. If several devices are associated with the remote location, the system determines which device is used.
<p>
<b>Note: </b>If *DEVD is specified for the RMTLOCNAME parameter for the remote location, a device name must be specified for this parameter.
</p>
</dd>
<dt><b><i>name</i></b></dt>
<dd>Specify the name of a communications device that is associated with the remote location. If the device name is not valid for the remote location, an escape message is sent when the DDM file is opened.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.LCLLOCNAME"></a>
<h3>Local location (LCLLOCNAME)</h3>
<p>Specifies the local location name.
</p>
<p>This parameter will be ignored if *IP is specified for the <b>Remote location (RMTLOCNAME)</b> parameter.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The local location name specified in the file description does not change.
</dd>
<dt><b>*LOC</b></dt>
<dd>The local location name associated with the remote location is used.
</dd>
</dl>
<dl>
<dt><b>*NETATR</b></dt>
<dd>The LCLLOCNAME value specified in the system network attributes is used.
</dd>
</dl>
<dl>
<dt><b><i>communications-name</i></b></dt>
<dd>Specify the name of the local location used with the remote location name. The local location name is only specified to indicate a specific local location for the remote location.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.MODE"></a>
<h3>Mode (MODE)</h3>
<p>Specifies the mode name that is used with the remote location name to communicate with the target system.
</p>
<p>This parameter will be ignored if *IP is specified for the <b>Remote location (RMTLOCNAME)</b> parameter.
</p>
<p>More information on mode names is in the APPC Programming book, SC41-5443.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The mode name does not change.
</dd>
</dl>
<dl>
<dt><b>*NETATR</b></dt>
<dd>The mode in the network attributes is used.
</dd>
</dl>
<dl>
<dt><b>BLANK</b></dt>
<dd>A mode name consisting of 8 blank characters is used.
</dd>
<dt><b><i>communications-name</i></b></dt>
<dd>Specify the name of the mode that is used. If the mode name is not valid for any combination of remote location name and local location name, an escape message is sent when the Distributed Data Management (DDM) file is opened.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.RMTNETID"></a>
<h3>Remote network identifier (RMTNETID)</h3>
<p>Specifies the remote network identifier (remote network ID) in which the remote location resides, and which is used to communicate with the target system.
</p>
<p>If this parameter is specified, the value specified for the <b>Remote location (RMTLOCNAME)</b> parameter must be consistent with the RMTNETID parameter. If the RMTLOCNAME parameter specified a network ID, this parameter must agree (otherwise, an error message will be issued). If the RMTLOCNAME parameter does not specify any network ID, there is no possibility of conflict with this parameter.
</p>
<p>This parameter will be ignored if *IP is specified for the RMTLOCNAME parameter.
</p>
<p>More information on remote network IDs is in the APPC Programming book, SC41-5443.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The remote network ID specified in the file description does not change.
</dd>
<dt><b>*LOC</b></dt>
<dd>The remote network ID associated with the remote location is used.
</dd>
</dl>
<dl>
<dt><b>*NETATR</b></dt>
<dd>The remote network identifier specified in the network attributes is used.
</dd>
</dl>
<dl>
<dt><b>*NONE</b></dt>
<dd>No remote network ID is used.
</dd>
<dt><b><i>communications-name</i></b></dt>
<dd>Specify the remote network ID to be associated with the remote location. The remote network ID is specified only if the user wants to indicate a specific remote network ID for the remote location. If the remote network ID is not valid for the remote location, an escape message is sent when the distributed data management (DDM) file is opened.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.PORT"></a>
<h3>Port number (PORT)</h3>
<p>Specifies the TCP/IP port that is used at the remote location to communicate with the system on which the remote file is located.
</p>
<p>This parameter will be ignored if *SNA is specified for the <b>Remote location (RMTLOCNAME)</b> parameter.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The value does not change.
</dd>
</dl>
<dl>
<dt><b>*DRDA</b></dt>
<dd>The DRDA well-known port of 446 will be used. This is the port on which the iSeries DDM TCP/IP server listens.
</dd>
<dt><b><i>1-65535</i></b></dt>
<dd>Specify a port number.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.ACCMTH"></a>
<h3>Access method (ACCMTH)</h3>
<p>Specifies the distributed data management (DDM) access method used to open the remote file and access its records when the target system is not an iSeries system. Specifying a value other than *RMTFILE for this parameter may improve performance when requests to remote files are processed on the target system. This parameter is ignored when the target system is an iSeries system or a System/38. The remote system file is accessed as if it is a local file.
</p>
<p><b>Single values</b>
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The access method does not change.
</dd>
<dt><b>*RMTFILE</b></dt>
<dd>The source system selects the access method that is compatible with the attributes of the remote file identified by the <b>Remote file (RMTFILE)</b> parameter and the access methods supported by the target system for that file. For target systems other than iSeries systems, if this value is used and the source system cannot select an access method when the file is opened, a message is sent to the program user.
</dd>
<dt><b>*COMBINED</b></dt>
<dd>The DDM combined access method is used for the remote file. This access method combines the file processing capabilities of the <i>combined by key</i> (*KEYED *BOTH) and the <i>combined by record number</i> (*ARRIVAL *BOTH) access methods, as shown in the following table. The record can be selected with a key value or a record number. From that position, the position can be set relatively or randomly by key value or by record number. If duplicate keys are present in the file, they are processed in the order defined by each target system's implementation of the DDM architecture.
</dd>
</dl>
<p><b>Element 1: Remote file attribute</b>
</p>
<dl>
<dt><b><u>*KEYED</u></b></dt>
<dd>Remote file is a keyed file.
</dd>
<dt><b>*ARRIVAL</b></dt>
<dd>Remote file is a non-keyed file.
</dd>
</dl>
<p><b>Element 2: Local access method</b>
</p>
<dl>
<dt><b><u>*BOTH</u></b></dt>
<dd>Remote file allows both sequential and random record access.
</dd>
<dt><b>*RANDOM</b></dt>
<dd>Remote file allows random record access.
</dd>
<dt><b>*SEQUENTIAL</b></dt>
<dd>Remote file allows sequential record access.
</dd>
</dl>
<p><b>Determining the Access Method</b>
</p>
<p>The two elements of this parameter indicate the access method to be used to access the remote file. The following table shows the combinations of values for the ACCMTH parameter. The remote file attributes (in the far left column) refer to the type of file on the target system. The local access method (in the last three columns) refers to the way in which the source iSeries program intends to access the records in the remote file.
</p>
<table border="1">
<caption align="bottom"><b>Figure: Access Method Combinations of Values</b>
</caption>
<tr>
<td>
<p>
<pre>
Remote Local Access Method
File
Attributes *SEQUENTIAL *RANDOM *BOTH
---------- ------------ ------------ ------------
*ARRIVAL Relative by Random by Combined by
record number record number record number
*KEYED Relative by Random by Combined by
key key key
</pre>
</p>
</td>
</tr>
</table>
<dl>
<dt><b>Relative by record number access method (*ARRIVAL *SEQUENTIAL):</b></dt>
<dd>This method allows access to records relative to the current position in record number sequence. The record number is not specified to identify the record.
</dd>
<dt><b>Random by record number access method (*ARRIVAL *RANDOM):</b></dt>
<dd>This method allows access to records by specifying a record number in a random sequence determined by the requester.
</dd>
<dt><b>Combined by record number access method (*ARRIVAL *BOTH):</b></dt>
<dd>This method combines the capabilities of the relative by record number and random by record number access methods.
</dd>
<dt><b>Relative by key access method (*KEYED *SEQUENTIAL):</b></dt>
<dd>This method allows records in a keyed file accessed in key value sequence. Records can be accessed by moving forward or backwards in key sequence from the current record. The key value is not specified to identify the record.
</dd>
<dt><b>Random by key access method (*KEYED *RANDOM):</b></dt>
<dd>This method allows records in a keyed file accessed in a random sequence. Records are selected by their key value and not their position in the file.
</dd>
<dt><b>Combined by key access method (*KEYED *BOTH):</b></dt>
<dd>This method combines the capabilities of the relative by key and random by key access methods.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.SHARE"></a>
<h3>Share open data path (SHARE)</h3>
<p>Specifies whether the open data path (ODP) is shared with other programs in the same routing step. When an ODP is shared, the programs accessing the file share facilities such as the file status and the buffer.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The value does not change.
</dd>
</dl>
<dl>
<dt><b>*NO</b></dt>
<dd>The ODP is not shared with other programs in the routing step. A new ODP for the file is created and used every time a program opens the file.
</dd>
</dl>
<dl>
<dt><b>*YES</b></dt>
<dd>The same ODP is shared with each program in the job that also specifies *YES when it opens the file.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<div> <a name="CHGDDMF.PTCCNV"></a>
<h3>Protected conversation (PTCCNV)</h3>
<p>Specifies whether the DDM conversation that is started for the DDM file is a protected conversation or not. A <b>protected conversation</b> is a conversation that uses two-phase commit protocols to ensure, even if a failure occurs, updates made on the remote system are synchronized with updates to other remote or local resources. A protected conversation is required to use two-phase commitment control with DDM. More information on using two-phase commitment control with DDM is in the Distributed Data Management information in the iSeries Information Center at http://www.ibm.com/eserver/iseries/infocenter. PTCCNV(*NO) must be specified if *IP is specified for the <b>Remote location (RMTLOCNAME)</b> parameter.
</p>
<dl>
<dt><b><u>*SAME</u></b></dt>
<dd>The value does not change.
</dd>
<dt><b>*NO</b></dt>
<dd>The DDM conversation started, using this DDM file, is not a protected conversation.
</dd>
<dt><b>*YES</b></dt>
<dd>The DDM conversation started, using this DDM file, is a protected conversation. Two-phase commitment control can be used with this DDM file.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="CHGDDMF.COMMAND.EXAMPLES">Examples</a> </h3>
<p>The following examples describe the changing of a DDM file.
</p>
<p><b>Example 1: Changing the Communications Mode System</b>
</p>
<p>
<pre>
CHGDDMF FILE(SOURCE/SALES) MODE(MODEX)
</pre>
</p>
<p>This command changes the communications mode for the DDM file named SALES stored in the SOURCE library on the source system. The mode is changed to MODEX.
</p>
<p><b>Example 2: Changing a DDM File to Access a File through TCP/IP</b>
</p>
<p>
<pre>
CHGDDMF FILE(OTHER/SALES) RMTLOCNAME(ROCHESTER.XYZ.COM *IP)
PORT(*DRDA)
</pre>
</p>
<p>This command changes the remote location name for the DDM file named SALES stored in the OTHER library on the source system. The remote location is changed to the TCP/IP host having the domain name of ROCHESTER.XYZ.COM. The host listens on the standard DRDA port of 446.
</p>
<p><b>Example 3: Changing a DDM File to Access a File through TCP/IP using Dotted Decimal IP Address and a Numeric Port Number</b>
</p>
<p>
<pre>
CHGDDMF FILE(OTHER/SALES) RMTLOCNAME('9.5.36.17' *IP)
PORT(5021)
</pre>
</p>
<p>This command changes the remote location name for the DDM file named SALES stored in the OTHER library on the source system. The remote location is changed to the TCP/IP host with the IP address of 9.5.36.17. The host listens on port 5021.
</p>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
<hr size="2" width="100%">
<div><h3><a name="CHGDDMF.ERROR.MESSAGES">Error messages</a> </h3>
<p><b><u>*ESCAPE Messages</u></b>
</p>
<dl>
<dt><b>CPF7304</b></dt>
<dd>File &amp;1 in &amp;2 not changed.
</dd>
</dl>
</div>
<table width="100%">
<tr><td align="right"><a href="#CHGDDMF.Top_Of_Page">Top</a></td></tr>
</table>
</body>
</html>