156 lines
9.9 KiB
HTML
156 lines
9.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="task" />
|
||
|
|
<meta name="DC.Title" content="Journal integrated file system objects" />
|
||
|
|
<meta name="abstract" content="You can journal the following integrated file system objects if they are in the "root"(/), QOpenSys, and user-defined file systems:" />
|
||
|
|
<meta name="description" content="You can journal the following integrated file system objects if they are in the "root"(/), QOpenSys, and user-defined file systems:" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakistrjrnl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiestimatercv.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/mmap.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahq/rzahqntspo.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/strjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../apis/qjosjobj.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../ifs/rzaaxkickoff.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiautostrjrnl.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="rzakistrjrn" />
|
||
|
|
<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>Journal integrated file system objects</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakistrjrn"><a name="rzakistrjrn"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Journal integrated file system objects</h1>
|
||
|
|
<div><p>You can journal the following integrated file system objects if
|
||
|
|
they are in the "root"(/), QOpenSys, and user-defined file systems:</p>
|
||
|
|
<div class="section"><ul><li>Stream files (*STMF)</li>
|
||
|
|
<li>Directories (*DIR)</li>
|
||
|
|
<li>Symbolic links (*SYMLNK)</li>
|
||
|
|
</ul>
|
||
|
|
<p>When you use the SAV command to save an integrated file system object,
|
||
|
|
the default is to not update the history information for the object. If you
|
||
|
|
plan to apply journaled changes to the objects you are journaling, and you
|
||
|
|
are not using the save-while-active function, specify to preserve the update
|
||
|
|
history information about the SAV command. </p>
|
||
|
|
<p>If you are journaling *DIR
|
||
|
|
or *STMF objects, you can reduce the number of journal entries in the journal
|
||
|
|
receiver. In iSeries™ Navigator,
|
||
|
|
if you ensure that <span class="uicontrol">Include open, close, and synchronization entries</span> is
|
||
|
|
unselected (<samp class="codeph">OMTJRNE(*OPNCLOSYN)</samp> on the Start Journal (STRJRN)
|
||
|
|
command), you can omit entries for open operations, close operations, and
|
||
|
|
force entries for the object. If you choose not to journal these entries be
|
||
|
|
aware of the following:</p>
|
||
|
|
<ul><li>You cannot use the journal to audit who has accessed the object for opens,
|
||
|
|
closes, and forces.</li>
|
||
|
|
<li>If an object is journaled, it cannot be memory mapped.</li>
|
||
|
|
<li>You cannot apply journal changes to open boundaries and close boundaries
|
||
|
|
using the TOJOBO and TOJOBC parameters.</li>
|
||
|
|
<li>This option is only valid for *DIR and *STMF objects.</li>
|
||
|
|
</ul>
|
||
|
|
<p>If you are journaling symbolic links, the system does not follow the
|
||
|
|
symbolic link to determine what to journal. That is, the system only journals
|
||
|
|
the actual symbolic link. If you want to journal the end object, you must
|
||
|
|
journal the end object directly.</p>
|
||
|
|
<p>If you are journaling a directory and
|
||
|
|
select <span class="uicontrol">Journal new files and folders</span> in iSeries Navigator
|
||
|
|
(INHERIT(*YES) on the STRJRN command), then objects created into that directory
|
||
|
|
will be automatically journaled to the same journal. Therefore use caution
|
||
|
|
because you can journal more objects than you realize. Also, even if this
|
||
|
|
option is on, if an object is restored to the directory, it keeps the journaling
|
||
|
|
attributes it had before the restore operation (when it was saved). For example,
|
||
|
|
if you restore a stream file that is journaled to Journal X, but the directory
|
||
|
|
you restore the stream file to is being journaled to Journal Y, the stream
|
||
|
|
file will still be journaled to Journal X, even if the directory has the inherit
|
||
|
|
option on.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> If you end journaling for an object and then rename that
|
||
|
|
object in the same directory in which it currently resides, journaling is
|
||
|
|
not started for the object, even if the directory has the inherit option on.</div>
|
||
|
|
<p>If
|
||
|
|
you select <span class="uicontrol">Current folder and all subfolders</span> in iSeries Navigator
|
||
|
|
(SUBTREE(*ALL) on the STRJRN command), journaling only starts on objects that
|
||
|
|
exist in the subtree when the STRJRN command is executed. To start journaling
|
||
|
|
on objects that are added to the subtree after this point you have three options:</p>
|
||
|
|
<ul><li>You can start journaling for each object after it is created.</li>
|
||
|
|
<li>You can select <span class="uicontrol">Journal new files and folders</span> (INHERIT
|
||
|
|
option) on the original start journal request.</li>
|
||
|
|
<li> After journaling is started you can use the Change Journaled Objects
|
||
|
|
(CHGJRNOBJ) command and specify INHERIT(*YES).</li>
|
||
|
|
</ul>
|
||
|
|
<p>If you select to journal the current folder and all subfolders, and
|
||
|
|
there are object types in the subtree that are not supported for journaling,
|
||
|
|
the unsupported object types are skipped over so that only object types that
|
||
|
|
are supported for journaling get journaled.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakistrjrnl.htm" title="This topic provides information about how to start journaling for all object types.">Start journaling</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzahq/rzahqntspo.htm">Windows environment on iSeries</a></div>
|
||
|
|
<div><a href="../ifs/rzaaxkickoff.htm">Integrated file system</a></div>
|
||
|
|
<div><a href="rzakiautostrjrnl.htm" title="Using a data area named QDFTJRN, you can automatically start journaling when a non-integrated file system object (data area, data queue, or file) is created, moved, or restored into the library, thus, ensuring the very first change to the object will be recorded in the journal and that no lock on the user's part prevents journaling from starting in the library. The QDFTJRN data area must exist in the library where the object is being added.">Automatically Start Journaling</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzakiestimatercv.htm" title="You can use the methods below to estimate the effect a journal receiver will have on auxiliary storage.">Methods to estimate the size of a journal receiver</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../apis/mmap.htm">Memory Map a File (mmap()) API</a></div>
|
||
|
|
<div><a href="../cl/strjrn.htm">Start Journal (STRJRN) command</a></div>
|
||
|
|
<div><a href="../apis/qjosjobj.htm">Start Journal (QjoStartJournal) API</a></div>
|
||
|
|
</div>
|
||
|
|
</div><div class="nested1" xml:lang="en-us" id="restobjects"><a name="restobjects"><!-- --></a><h2 class="topictitle2">Restrictions for journaling integrated file system objects</h2>
|
||
|
|
<div><div class="section"><p>Restrictions for journaling integrated file system objects are
|
||
|
|
as follows:</p>
|
||
|
|
<ul><li>You cannot journal files which are memory mapped. The Memory Map a File
|
||
|
|
(mmap()) API documentation has information about memory mapping.</li>
|
||
|
|
<li>iSeries servers
|
||
|
|
allocate disk space for Integrated xSeries™ servers as virtual disk drives
|
||
|
|
for the xSeries<sup>®</sup> servers.
|
||
|
|
From the perspective of the iSeries server, virtual drives appear as byte stream
|
||
|
|
files within the integrated file system. You cannot journal these byte stream
|
||
|
|
files. See the Windows<sup>®</sup> environment on iSeries topic for more information about
|
||
|
|
Integrated xSeries servers.</li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />Virtual volume files cannot be journaled.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div class="nested1" xml:lang="en-us" id="startjournalisysobjects"><a name="startjournalisysobjects"><!-- --></a><h2 class="topictitle2">Start journaling for integrated file system objects</h2>
|
||
|
|
<div><div class="section">To start journaling for integrated file system objects do the following
|
||
|
|
steps: </div>
|
||
|
|
<ol><li><span>In iSeries Navigator
|
||
|
|
select the system on which the object that you want to journal is located.</span></li>
|
||
|
|
<li><span>Expand File Systems.</span></li>
|
||
|
|
<li><span>Expand Integrated File Systems.</span></li>
|
||
|
|
<li><span>Expand the file system with the object you want to journal.</span></li>
|
||
|
|
<li><span>If you are journaling a directory, right-click the directory and
|
||
|
|
select <span class="uicontrol">Journaling</span>.</span></li>
|
||
|
|
<li><span>If you are journaling an object in a directory, expand the directory
|
||
|
|
and right click that object. Select <span class="uicontrol">Journaling</span>.</span></li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p>Or, use the STRJRN command or Start Journal (QjoStartJournal) API
|
||
|
|
for integrated file system objects that you want to journal.</p>
|
||
|
|
<p>For more
|
||
|
|
information about integrated file system objects, see the Integrated file
|
||
|
|
system topic.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|