friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddm_5.4.0.1/rbae5pcsource.htm

145 lines
9.6 KiB
HTML
Raw Permalink Blame History

<?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="Personal computer source to iSeries target considerations for DDM" />
<meta name="abstract" content="iSeries Access Family uses DDM to allow a personal computer to communicate as a source server to access objects on an iSeries target. iSeries Access Family uses Level 3.0 of the DDM architecture stream file access support to access folder management services (FMS) folders and documents." />
<meta name="description" content="iSeries Access Family uses DDM to allow a personal computer to communicate as a source server to access objects on an iSeries target. iSeries Access Family uses Level 3.0 of the DDM architecture stream file access support to access folder management services (FMS) folders and documents." />
<meta name="DC.subject" content="source DDM (SDDM), personal computer, SDDM (source DDM), DDM source considerations, target DDM (TDDM), server, iSeries, TDDM (target DDM), DDM target considerations, as source system" />
<meta name="keywords" content="source DDM (SDDM), personal computer, SDDM (source DDM), DDM source considerations, target DDM (TDDM), server, iSeries, TDDM (target DDM), DDM target considerations, as source system" />
<meta name="DC.Relation" scheme="URI" content="rbae5ddmop.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="rbae5pcsource" />
<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>Personal computer source to iSeries target
considerations for DDM</title>
</head>
<body id="rbae5pcsource"><a name="rbae5pcsource"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Personal computer source to <span class="keyword">iSeries</span> target
considerations for DDM</h1>
<div><p><span class="keyword">iSeries™ Access Family</span> uses DDM
to allow a personal computer to communicate as a source server to access objects
on an <span class="keyword">iSeries</span> target. <span class="keyword">iSeries Access Family</span> uses Level 3.0 of the DDM
architecture stream file access support to access folder management services
(FMS) folders and documents.</p>
<div class="section"><p>The following considerations apply to <span class="keyword">iSeries Access Family</span> use
of the <span class="keyword">i5/OS™</span> DDM target
support for the DDM architecture, Level 3.0. Other source servers that send
Level 2.0 or Level 3.0 DDM architecture requests for stream files and directories
may be able to use this information to help in connecting to an <span class="keyword">iSeries server</span> by
using DDM. </p>
<ul><li>A FMS must follow the file or directory name to access folder management
services (FMS) folders and documents. There can be one or more blanks between
the end of the name and the FMS.</li>
<li>A leading slash (/) signifies the name is fully qualified. If there is
no leading slash, any current directory in use is added to the front of the
name given.</li>
<li>The total length of a fully qualified document name is 76 characters.
This includes any current directory that may be in use. This does not include
the trailing FMS, which is used for typing purposes.</li>
<li>A / FMS signifies the root folder for a directory name.</li>
<li>To reduce the number of messages logged to the job log, some errors occurring
on the <span class="keyword">iSeries</span> target during
open, get, put, and close document operations are not logged to the job log.
See <a href="#rbae5pcsource__rbae5return">Table 1</a> for an illustration of
these return codes.
<div class="tablenoborder"><a name="rbae5pcsource__rbae5return"><!-- --></a><table cellpadding="4" cellspacing="0" summary="" id="rbae5pcsource__rbae5return" width="90%" frame="border" border="1" rules="all"><caption>Table 1. <span class="keyword">iSeries</span> return codes</caption><thead align="left"><tr><th valign="top" width="33.33333333333333%" id="d0e114">Description</th>
<th valign="top" width="33.33333333333333%" id="d0e116">DDM reply</th>
<th valign="top" width="33.33333333333333%" id="d0e118">Function</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Folder not found</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">DRCNFNRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">OPEN</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Folder in use</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">DRCIUSRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">OPEN</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Document in use</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">FILIUSRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">OPEN</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Document not found</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">FILNFNRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">OPEN</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Document not found</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">EXSCNDRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">DELFIL</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Document is read only</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">ACCINTRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">OPEN</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">End of data</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">SUBSTRRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">GET</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Data stream (DS) in use</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">STRIUSRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">GET</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Data stream (DS) in use</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">STRIUSRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">PUT</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Substring not valid</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">SUBSTRRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">UNLOCK</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Unlocking a region that is not locked</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">EXSCNDRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">UNLOCK</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">File already open for the declare name</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">OPNCNFRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">OPEN</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">File not open</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">FILNOPRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">GET, PUT, LOCK, UNLOCK</td>
</tr>
<tr><td valign="top" width="33.33333333333333%" headers="d0e114 ">Delete document SHDONL(TRUE) specified, but shadow does not exist</td>
<td valign="top" width="33.33333333333333%" headers="d0e116 ">EXSCNDRM</td>
<td valign="top" width="33.33333333333333%" headers="d0e118 ">DELFIL</td>
</tr>
</tbody>
</table>
</div>
</li>
<li>To provide better performance, the <span class="keyword">iSeries</span> target
handles the closing document in a manner such that when the document is closing,
a command completion reply message (CMDCMPRM) is returned to the source server
before the document is actually closed. If the document is damaged during
the closing time, the user never receives this reply message unless he views
the job log. When the user opens the file again, the updated data may not
be there.</li>
<li>An <span class="keyword">iSeries server</span> does not support
wait on the locking data stream function. The user on the source system must
handle the wait function.</li>
</ul>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5ddmop.htm" title="This topic provides task-oriented information and examples that describe various aspects of DDM operation considerations.">Operating considerations for DDM</a></div>
</div>
</div>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink