69 lines
7.1 KiB
HTML
69 lines
7.1 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="Integrated file system considerations for applying journaled changes" />
|
||
|
|
<meta name="abstract" content="If there is a create entry or delete entry in the range of journal entries to which you are applying journaled changes, changes to a directory can cause the creation or deletion of an object." />
|
||
|
|
<meta name="description" content="If there is a create entry or delete entry in the range of journal entries to which you are applying journaled changes, changes to a directory can cause the creation or deletion of an object." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiappyjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrncodes.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="rzakiifsconsid" />
|
||
|
|
<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>Integrated file system considerations for applying journaled changes</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiifsconsid"><a name="rzakiifsconsid"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Integrated file system considerations for applying journaled changes</h1>
|
||
|
|
<div><p>If there is a create entry or delete entry in the range of journal entries to which you are applying journaled changes, changes to a directory can cause the creation or deletion of an object.</p>
|
||
|
|
<p>If you are journaling a directory using the <span class="uicontrol">Journal new files and folders</span> (INHERIT(*YES)) option and an object is created into that directory, the system automatically starts journaling
|
||
|
|
that new object and deposits associated create and start journal object journal entries. The apply of these create and start journal entries during the apply operation on the directory then creates the
|
||
|
|
objects and starts journaling for them during the apply operation. For any subsequent journaled entries for that object, the apply operation applies any entries that it encounters for that object as well.
|
||
|
|
Similarly, if an entry is encountered which deletes (unlinks) an integrated file system object, that object is actually deleted as part of the apply operation.</p>
|
||
|
|
<p>Additionally, the apply operation will start journaling for any integrated file system journal entry that adds a link to the journaled directory, such as moving a nonjournaled object into the journaled
|
||
|
|
directory, or adding a new hard link to a nonjournaled object into this journaled directory. However, no entries will be applied to these objects since the state of those objects is not fully know during
|
||
|
|
the apply.</p>
|
||
|
|
<p>As objects are created, they are included in the maximum number of objects which can be applied as part of one Apply Journaled Changes (APYJRNCHG) request.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Error handling considerations</h4><p>When you apply journaled changes, you can use the Object Error Option (OBJERROPT) of the APYJRNCHG command to specify how the system responds to errors.
|
||
|
|
If you specify *CONTINUE, the system stops applying changes to the object that encounters an error, but continues the apply operation for the remaining objects.</p>
|
||
|
|
<p>For integrated file system objects,
|
||
|
|
the system processes errors for directory-level operations separately from object-level operations. For example, you perform an apply journaled changes operation for a directory and a stream file in that
|
||
|
|
directory. During the apply operation, an error occurs for the stream file and the apply process ends for that stream file. You might expect some operations that are associated with that stream file, such
|
||
|
|
as remove link, to end also. But since remove link is a directory level operation, the remove link operation still occurs, even though the apply operation ended for that stream file.</p>
|
||
|
|
<p>Therefore even
|
||
|
|
though object-level operations for an object might end, directory-level operations that are associated with that object still occur.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Commitment control considerations</h4><p>Many journaled integrated file system operations use system initiated commitment control for the duration of the operation. These operations are
|
||
|
|
not considered completed successfully unless the commitment control cycle is committed. Commitment control, here, refers to commitment control that the system initiates. Integrated file system operations
|
||
|
|
cannot be included in a user initiated commitment control cycle.</p>
|
||
|
|
<p> For integrated file system journal entries that are part of a commitment control cycle, do not apply individual entries from within
|
||
|
|
the cycle without applying the entire commit cycle. Using the Commit Boundary (CMTBDY(*YES)) parameter on the APYJRNCHG command can help enforce this. If you do not use this option and choose a specific
|
||
|
|
starting point, start from the Start of commit cycle (C SC) entry for that cycle. Likewise, if you choose to end applying a journaled change at a specific point, end on the Commit (C CM) or Rollback (C
|
||
|
|
RB) entry for that cycle.</p>
|
||
|
|
<p>See Actions of applying or removing journaled changes by journal code for what operations are applied for integrated file system related journal entries.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiappyjrn.htm" title="If an object becomes damaged or is not usable you can recover the object using the Apply Journaled Changes (APYJRNCHG) or Apply Journaled Changes Extend (APYJRNCHGX) command. If you restore an object that was saved with partial transactions, then you must apply journaled changes to that object before it is usable.">Apply journaled changes</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakijrncodes.htm" title="The following table shows the actions that are taken by the Apply Journaled Changes (APYJRNCHG), Apply Journaled Changes Extend (APYJRNCHGX), or Remove Journaled Changes (RMVJRNCHG) command by journal code and entry type.">Actions of applying or removing journaled changes by journal code</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|