ibm-information-center/dist/eclipse/plugins/i5OS.ic.ddm_5.4.0.1/rbae5dcom.htm

127 lines
7.0 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 DDM files with commitment control" />
<meta name="abstract" content="DDM files can be opened under commitment control." />
<meta name="description" content="DDM files can be opened under commitment control." />
<meta name="DC.subject" content="ROLLBACK operation" />
<meta name="keywords" content="ROLLBACK operation" />
<meta name="DC.Relation" scheme="URI" content="rbae5commit.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="rbae5dcom" />
<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 DDM files with commitment control</title>
</head>
<body id="rbae5dcom"><a name="rbae5dcom"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Use DDM files with commitment control</h1>
<div><p>DDM files can be opened under commitment control. </p>
<div class="section"><p>However, the following restrictions should be considered when
working with these DDM files: </p>
<ul><li>If more than one DDM file (with PTCCNV(*NO)) is opened under commitment
control, the following items must be the same for each file: <ul><li>Remote location name</li>
<li>Local location name</li>
<li>Device</li>
<li>Mode</li>
<li>Remote network ID</li>
<li>Transaction program name (TPN)</li>
<li>User ID</li>
<li>Activation group number</li>
<li>Open scope</li>
</ul>
The exception to this rule is when all of the DDM files opened under
commitment control are scoped to the job level. In this case, the activation
group numbers are ignored and do not need to match.</li>
<li>If a DDM file and a remote SQL object (Distributed
Relational Database Architecture™, DRDA<sup>®</sup>) are running under commitment control
(with PTCCNV(*NO)), the following items must be the same for the file and
object: <ul><li>Remote location name</li>
<li>Local location name</li>
<li>Device</li>
<li>Mode</li>
<li>Remote network ID</li>
<li>TPN</li>
<li>User ID</li>
<li>Activation group number</li>
<li>Open scope</li>
</ul>
</li>
<li>If the DDM file (with PTCCNV(*YES)) is being opened for output, update,
or delete (not opened for input only), then there cannot be any one-phase
DDM or DRDA conversations
active.</li>
<li>If a DDM with PTCCNV of *YES is being used, it must point to a target <span class="keyword">iSeries™ server</span> that supports two-phase commitment
control protocols.</li>
<li>DDM files (with PTCCNV(*NO)) and local database files cannot be opened
under commitment control at the same time within the same activation group.</li>
<li>DDM files (with PTCCNV(*NO)) and local database files cannot be opened
under commitment control at the same time within the same job if commitment
control is scoped to the job level.</li>
<li>To open a DDM file under commitment control and scope it to the job level,
you must have specified CMTSCOPE(*JOB) on the <span class="cmdname">Start Commitment Control
(STRCMTCTL)</span> command.</li>
<li>You cannot use the <span class="cmdname">Submit Remote Command (SBMRMTCMD)</span> command
to call programs that expect commitment control to be scoped to the job level.
Because commitment control is always scoped to the activation group level
in DDM target jobs, the program fails.</li>
<li>The <span class="cmdname">SBMRMTCMD</span> command should not be used to start or
end commitment control.</li>
<li>The target server specified from the <span class="keyword">iSeries server</span> working
under commitment control must be another <span class="keyword">iSeries server</span>.</li>
</ul>
</div>
<div class="section"> <div class="note"><span class="notetitle">Note:</span> If the communications line fails during a COMMIT operation,
the source and target servers will do a ROLLBACK operation. However, the target
server might successfully complete the COMMIT operation before the line fails,
but the source server will always do a ROLLBACK operation. </div>
</div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" width="100%" frame="border" border="1" rules="all"><caption>Table 1. High-level
language commit and rollback commands</caption><thead align="left"><tr><th valign="top" width="16.666666666666664%" id="d0e127">Operation</th>
<th valign="top" width="16.666666666666664%" id="d0e129">ILE RPG programming language</th>
<th valign="top" width="16.666666666666664%" id="d0e131">ILE COBOL programming language</th>
<th valign="top" width="16.666666666666664%" id="d0e133">PL/I</th>
<th valign="top" width="16.666666666666664%" id="d0e135">CL</th>
<th valign="top" width="16.666666666666664%" id="d0e137">ILE C programming language</th>
</tr>
</thead>
<tbody><tr><td valign="top" width="16.666666666666664%" headers="d0e127 ">Commit changes in transaction</td>
<td valign="top" width="16.666666666666664%" headers="d0e129 ">COMMIT</td>
<td valign="top" width="16.666666666666664%" headers="d0e131 ">COMMIT</td>
<td valign="top" width="16.666666666666664%" headers="d0e133 ">PLICOMMIT</td>
<td valign="top" width="16.666666666666664%" headers="d0e135 ">COMMIT</td>
<td valign="top" width="16.666666666666664%" headers="d0e137 ">_Rcommit</td>
</tr>
<tr><td valign="top" width="16.666666666666664%" headers="d0e127 ">Cancel entire transaction</td>
<td valign="top" width="16.666666666666664%" headers="d0e129 ">ROLBK</td>
<td valign="top" width="16.666666666666664%" headers="d0e131 ">ROLLBACK</td>
<td valign="top" width="16.666666666666664%" headers="d0e133 ">PLIROLLBACK</td>
<td valign="top" width="16.666666666666664%" headers="d0e135 ">ROLLBACK</td>
<td valign="top" width="16.666666666666664%" headers="d0e137 ">_Rrollback</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rbae5commit.htm" title="iSeries applications can commit or roll back transactions on remote iSeries servers.">Commitment control support for DDM</a></div>
</div>
</div>
</body>
</html>