66 lines
4.7 KiB
HTML
66 lines
4.7 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="Example: Access System/36 DDM remote files (iSeries-to-System/36)" />
|
||
|
|
<meta name="abstract" content="Of the command examples given in the previous topic (showing iSeries-to-iSeries examples), all except the first example can be coded the same way for accessing a file on a System/36." />
|
||
|
|
<meta name="description" content="Of the command examples given in the previous topic (showing iSeries-to-iSeries examples), all except the first example can be coded the same way for accessing a file on a System/36." />
|
||
|
|
<meta name="DC.subject" content="accessing, files, System/36, file, differences, remote file processing, remote system, file processing differences" />
|
||
|
|
<meta name="keywords" content="accessing, files, System/36, file, differences, remote file processing, remote system, file processing differences" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rbae5fac.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="rbae5ex36" />
|
||
|
|
<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>Example: Access System/36 DDM
|
||
|
|
remote files (iSeries-to-System/36)</title>
|
||
|
|
</head>
|
||
|
|
<body id="rbae5ex36"><a name="rbae5ex36"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Example: Access <span class="keyword">System/36</span> DDM
|
||
|
|
remote files (<span class="keyword">iSeries</span>-to-<span class="keyword">System/36</span>)</h1>
|
||
|
|
<div><p>Of the command examples given in the previous topic (showing <span class="keyword">iSeries™</span>-to-<span class="keyword">iSeries</span> examples),
|
||
|
|
all except the first example can be coded the same way for accessing a file
|
||
|
|
on a <span class="keyword">System/36™</span>.</p>
|
||
|
|
<div class="section"><p>That is, if the remote file name SALES/CAR is changed to CAR to
|
||
|
|
meet the <span class="keyword">System/36</span> naming conventions,
|
||
|
|
all the commands (except the first) can be used without change to access a
|
||
|
|
remote <span class="keyword">System/36</span> file instead
|
||
|
|
of an <span class="keyword">iSeries</span> file.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><div class="p">The first example from the topic Examples: Access <span class="keyword">iSeries</span> DDM remote files (<span class="keyword">iSeries</span> to <span class="keyword">iSeries</span>) is recorded here to access
|
||
|
|
a remote <span class="keyword">System/36</span> file. Besides
|
||
|
|
changing the remote file name, another parameter that should be coded is LVLCHK(*NO).
|
||
|
|
<pre>CRTDDMF FILE(DDMLIB/RMTCAR) RMTFILE(*NONSTD 'CAR')
|
||
|
|
RMTLOCNAME(CHICAGO) TEXT('Chicago file CAR on S/36')
|
||
|
|
LVLCHK(*NO)</pre>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>This command creates a DDM reference file named RMTCAR and stores
|
||
|
|
it in the DDMLIB library on the local <span class="keyword">iSeries server</span>.
|
||
|
|
The remote file to be accessed is the CAR file on the <span class="keyword">System/36</span> named
|
||
|
|
CHICAGO. LVLCHK(*NO) is specified to prevent level checking because the level
|
||
|
|
identifiers created for the <span class="keyword">System/36</span> file
|
||
|
|
do not match those in the program when it accesses the file.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<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>
|
||
|
|
</body>
|
||
|
|
</html>
|