79 lines
4.9 KiB
HTML
79 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Journaled changes with referential constraints" />
|
||
|
|
<meta name="abstract" content="When you apply or remove journaled changes, journal management does not support referential constraints." />
|
||
|
|
<meta name="description" content="When you apply or remove journaled changes, journal management does not support referential constraints." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiapyjrnchg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahf/rzahftrigcontable.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/QJORJRNE.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzakiapywthref" />
|
||
|
|
<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>Journaled changes with referential constraints</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiapywthref"><a name="rzakiapywthref"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journaled changes with referential constraints</h1>
|
||
|
|
<div><p>When you apply or remove journaled changes, journal management
|
||
|
|
does not support referential constraints.</p>
|
||
|
|
<p>In the following cases, files may be in CHECK PENDING status after you
|
||
|
|
have applied or removed journaled changes:</p>
|
||
|
|
<ul><li>When you restore a file that already exists, the referential constraints
|
||
|
|
for the system copy of the file are used. Some of the journaled changes that
|
||
|
|
you apply may have been valid with the referential constraints that were associated
|
||
|
|
with the saved copy. However, they are not necessarily valid with the current
|
||
|
|
referential constraints. If you have changed the referential constraints on
|
||
|
|
the file, considering doing one of the following before applying or removing
|
||
|
|
journaled changes: <ul><li>Deleting the system copy and then restoring the file</li>
|
||
|
|
<li>Recreating the changes to the referential constraints</li>
|
||
|
|
</ul>
|
||
|
|
<p>When you apply or remove journaled changes, the system attempts to
|
||
|
|
verify the referential constraints at the end of the command, before returning
|
||
|
|
control to you. This may result in a CHECK PENDING status.</p>
|
||
|
|
</li>
|
||
|
|
<li>Some referential constraints cause an action to another file. You may
|
||
|
|
define a constraint so that deleting a record in one file causes a related
|
||
|
|
record to be deleted in another file. Because referential constraints are
|
||
|
|
not enforced when you apply journaled changes, the second delete operation
|
||
|
|
does not happen automatically. However, if you are journaling both files and
|
||
|
|
applying journaled changes to both files, the system applies the journal entry
|
||
|
|
for the second file when it encounters it. <p>If one of the files in a referential
|
||
|
|
constraint was not journaled or is not included when you apply or remove journaled
|
||
|
|
changes, the referential constraint will probably be put in CHECK PENDING
|
||
|
|
status.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
<p>The output format for journal entries (except the *TYPE1, *TYPE2, and *TYPE3
|
||
|
|
formats) and the QjoRetrieveJournalEntries API interface include information
|
||
|
|
about whether a journal entry was created because of changes that occurred
|
||
|
|
to a record that was part of a referential constraint.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiapyjrnchg.htm" title="One of the primary advantages of journaling is its ability to return a journaled object to its current state since the last save.">Recover journaled objects</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzahf/rzahftrigcontable.htm">Work with triggers and constraints</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../apis/QJORJRNE.htm">Retrieve Journal Entries (QjoRetrieveJournalEntries) API</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|