127 lines
9.2 KiB
HTML
127 lines
9.2 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 integrated file system objects" />
|
||
<meta name="abstract" content="Some integrated file system object types can be journaled using i5/OS journaling support." />
|
||
<meta name="description" content="Some integrated file system object types can be journaled using i5/OS journaling support." />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaaxjournaloverview.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaaxstmfile.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaaxdir.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaaxsymlnk.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaaxstartjour.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaaxendjour.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="rzaaxchgjour.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakikickoff.htm" />
|
||
<meta name="DC.Relation" scheme="URI" content="../rzaki/rzakifinder.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="rzaaxjourobj" />
|
||
<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 integrated file system objects</title>
|
||
</head>
|
||
<body id="rzaaxjourobj"><a name="rzaaxjourobj"><!-- --></a>
|
||
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
<h1 class="topictitle1">Journaled integrated file system objects</h1>
|
||
<div><p>Some integrated file system object types can be journaled using <span class="keyword">i5/OS™</span> journaling support.</p>
|
||
<p>The object types supported are stream files, directories, and symbolic
|
||
links. The "root" (/), QOpenSys, and UDFS are the only file systems that support
|
||
journaling of these object types. Integrated file system objects can be journaled
|
||
using either the traditional system interface (CL commands or APIs) or by
|
||
using <span class="keyword">iSeries™</span> Navigator. You
|
||
can Start journaling and End journaling through <span class="keyword">iSeries</span> Navigator,
|
||
as well as display journaling status information.</p>
|
||
<div class="note"><span class="notetitle">Note:</span> Memory-mapped stream files, <span><img src="./delta.gif" alt="Start of change" />virtual volume
|
||
files<img src="./deltaend.gif" alt="End of change" /></span>, and stream files that are used as <span class="keyword">Integrated xSeries<sup>®</sup> Server for iSeries</span> (IXS)
|
||
network storage spaces cannot be journaled. Directories that can contain block
|
||
special file objects cannot be journaled. Examples of these are: /dev/QASP01,
|
||
/dev/QASP22, and /dev/IASPNAME.</div>
|
||
<p>The following list summarizes journaling support in
|
||
the integrated file system: </p>
|
||
<ul><li>You can use both generic commands and APIs to perform journal operations
|
||
on the supported object types. These interfaces generally accept object identification
|
||
in the form of a path name, file ID, or both.</li>
|
||
<li>Some journal operation commands, including Start Journaling, End Journaling,
|
||
Change Journaling and Apply Journaled Changes, may be performed on entire
|
||
subtrees of integrated file system objects. You can optionally use the include
|
||
and exclude lists that may use wild card patterns for object names. For example,
|
||
you can use the Start Journaling command to specify to start on all objects
|
||
in the tree <samp class="codeph">"/MyCompany"</samp> that match the pattern <samp class="codeph">"*.data"</samp> but
|
||
that excludes any objects matching the patterns <samp class="codeph">"A*.data" </samp>and <samp class="codeph">"B*.data"</samp>.</li>
|
||
<li>Journaling support on directories includes directory operations such as
|
||
adding links, removing links, creating objects, renaming objects, and moving
|
||
objects within the directory. <p>Journaled directories support an attribute
|
||
that can be set to cause new objects in the subtree to inherit the current
|
||
journaling state of the directory. When this attribute is turned on for a
|
||
journaled directory, all stream files, directories, and symbolic links that
|
||
are created or linked into the directory (by adding a hard link or by renaming
|
||
or moving the object) will automatically have journaling started by the system.</p>
|
||
<div class="note"><span class="notetitle">Note:</span> Inherit
|
||
journaling attribute considerations: <ul><li>If you rename an object in the same directory it currently resides in,
|
||
journaling is not started for the object, even if the directory has the inherit
|
||
current journaling state attribute on.</li>
|
||
<li>When a directory is moved to a directory which has the inherit journaling
|
||
attribute on, only that moved directory has journaling started for it if appropriate.
|
||
The objects within that moved directory are not affected.</li>
|
||
<li>If an object is restored to a directory which has the inherit journaling
|
||
attribute on, journaling is not started for that object if the object has
|
||
ever been journaled.</li>
|
||
<li>When using the <span class="cmdname">Apply Journaled Changes (APYJRNCHG)</span> command,
|
||
the current value of the inherit journaling attribute for any directories
|
||
is not used. Instead, any objects which are created as part of the apply have
|
||
journaling started or not based on what happened during the runtime activity
|
||
which is being applied.</li>
|
||
</ul>
|
||
</div>
|
||
</li>
|
||
<li>Object names and complete path names are contained within several journal
|
||
entries of integrated file system objects. Object names and path names are
|
||
National Language Support (NLS)-enabled.</li>
|
||
<li>If the system ends abnormally, system initial program load (IPL) recovery
|
||
is provided for journaled integrated file system objects.</li>
|
||
<li>The maximum write limit supported by the various write interfaces is 2
|
||
GB - 1. The maximum journal entry size if RCVSIZOPT (*MAXOPT2 or *MAXOPT3)
|
||
is specified is 4 000 000 000 bytes. Otherwise, the maximum
|
||
journal entry size is 15 761 440 bytes. If you journal your stream
|
||
file and have any writes that exceed 15 761 440 bytes, you need
|
||
to use the *MAXOPT2 or *MAXOPT3 support to prevent any errors from occurring.</li>
|
||
</ul>
|
||
<p>For more information about the layout of various journal entries, there
|
||
is a C language include file, qp0ljrnl.h, shipped in member QSYSINC/H (QP0LJRNL),
|
||
that contains details of the integrated file system journal entry specific
|
||
data content and formats.</p>
|
||
</div>
|
||
<div>
|
||
<div class="familylinks">
|
||
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaaxjournaloverview.htm" title="These topics introduce journaling support for integrated file system objects.">Journaling overview</a></div>
|
||
</div>
|
||
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
<div><a href="rzaaxstmfile.htm" title="A stream file is a randomly accessible sequence of bytes, with no further structure imposed by the system.">Stream file</a></div>
|
||
<div><a href="rzaaxdir.htm" title="A directory is a special object that is used to locate objects by names that you specify. Each directory contains a list of objects that are attached to it. That list can include other directories.">Directory</a></div>
|
||
<div><a href="rzaaxsymlnk.htm" title="A symbolic link, which is also called a soft link, is a path name contained in a file.">Symbolic link</a></div>
|
||
</div>
|
||
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
<div><a href="rzaaxstartjour.htm" title="Do these steps to start journaling on an object through the iSeries Navigator.">Start journaling</a></div>
|
||
<div><a href="rzaaxendjour.htm" title="After journaling has started on an object and, for whatever reasons, you want to end journaling on this object, you can use the steps described in this topic.">End journaling</a></div>
|
||
<div><a href="rzaaxchgjour.htm" title="After journaling has started on an object and, for whatever reasons, you want to change the journal attributes on the object without having to end and restart journaling, you can use the Change Journaled Object (CHGJRNOBJ) command, which allows you to change journaled objects.">Change journaling</a></div>
|
||
</div>
|
||
<div class="relinfo"><strong>Related information</strong><br />
|
||
<div><a href="../rzaki/rzakikickoff.htm">Journal management</a></div>
|
||
<div><a href="../rzaki/rzakifinder.htm">Journal entry information finder</a></div>
|
||
</div>
|
||
</div>
|
||
</body>
|
||
</html> |