65 lines
4.7 KiB
HTML
65 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="concept" />
|
||
|
|
<meta name="DC.Title" content="Journaling overview" />
|
||
|
|
<meta name="abstract" content="These topics introduce journaling support for integrated file system objects." />
|
||
|
|
<meta name="description" content="These topics introduce journaling support for integrated file system objects." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxjournal.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxjournalmgmt.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxwhatobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxjourobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxjourdirectory.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxspecial.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaaxconlinkjour.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakikickoff.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="rzaaxjournaloverview" />
|
||
|
|
<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>Journaling overview</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaaxjournaloverview"><a name="rzaaxjournaloverview"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journaling overview</h1>
|
||
|
|
<div><p>These topics introduce journaling support for integrated
|
||
|
|
file system objects.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxjournalmgmt.htm">Journal management</a></strong><br />
|
||
|
|
The main purpose for journal management is to enable you to recover the changes to an object that have occurred since the object was last saved.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxwhatobj.htm">Objects you should journal</a></strong><br />
|
||
|
|
There are certain questions to consider when deciding whether to journal an integrated file system object.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxjourobj.htm">Journaled integrated file system objects</a></strong><br />
|
||
|
|
Some integrated file system object types can be journaled using <span class="keyword">i5/OS™</span> journaling support.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxjourdirectory.htm">Journaled operations</a></strong><br />
|
||
|
|
These operations are only journaled when the type of the object or link that the operation is using is a type that can also be journaled.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxspecial.htm">Special considerations for journal entries</a></strong><br />
|
||
|
|
Many journaled integrated file system operations internally use commitment control to form a single transaction from the multiple functions performed during the operations.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaaxconlinkjour.htm">Considerations for multiple hard links and journaling</a></strong><br />
|
||
|
|
If you have multiple hard links to a journaled integrated file system object, all the links should be saved and restored together so that the linkage is preserved as well as the associated journal information.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxjournal.htm" title="The primary purpose of journaling is to enable you to recover the changes to an object that have occurred since the object was last saved. Additionally, a key use of journaling is to assist in the replication of object changes to another system either for high availability or workload balancing.">Journaling objects</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzaki/rzakikickoff.htm">Journal management</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|