117 lines
7.6 KiB
HTML
117 lines
7.6 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="Why you must save objects after you start journaling" />
|
||
|
|
<meta name="abstract" content="After you start journaling, it is essential that you save objects that you are journaling." />
|
||
|
|
<meta name="description" content="After you start journaling, it is essential that you save objects that you are journaling." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakistartandend.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnentryconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaiu/rzaiurzaiu001.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiapyjrnchg.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="rzakiwhysavjrn" />
|
||
|
|
<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>Why you must save objects after you start journaling</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakiwhysavjrn"><a name="rzakiwhysavjrn"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Why you must save objects after you start journaling</h1>
|
||
|
|
<div><p>After you start journaling, it is essential that you save objects
|
||
|
|
that you are journaling.</p>
|
||
|
|
<p>It is critical to save the journaled object after journaling is started
|
||
|
|
to be able to apply journaled changes. When you start journaling an object,
|
||
|
|
the system assigns a unique <span class="uicontrol">journal identifier</span> (JID)
|
||
|
|
to that object. If the object is a physical database file, each member is
|
||
|
|
also assigned a unique JID. If you start journaling on a distributed file,
|
||
|
|
the piece on each server has its own unique JID. The JID is part of every
|
||
|
|
journal entry added to the journal receiver for a given object. The system
|
||
|
|
uses the JID to associate the journal entry with the corresponding journaled
|
||
|
|
object. The copy of the object on the save media that was saved before it
|
||
|
|
was journaled does not have the journal identifier saved with it. Therefore,
|
||
|
|
if this copy of the object is restored to the server, the journal entries
|
||
|
|
cannot be associated with the object and cannot be applied.</p>
|
||
|
|
<p>After you start journaling an object, do the following:</p>
|
||
|
|
<ul><li>Save the object immediately after you have started journaling it, before
|
||
|
|
any changes have occurred.</li>
|
||
|
|
<li>Save a physical file or a logical file after you start journaling access
|
||
|
|
paths for the file. This ensures that when you restore the file, journaling
|
||
|
|
access paths is started automatically.</li>
|
||
|
|
<li>If you are using distributed files, save the file separately on the systems
|
||
|
|
in the node group after starting journaling for the distributed file.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Saving these objects ensures that you can completely recover all the objects
|
||
|
|
by using your saved copy and your journal receivers.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Update the history</h4><p>If you are not using the save-while-active
|
||
|
|
function, update the history for the object when you save it so that processing
|
||
|
|
for applying and removing journaled changes will have the best information
|
||
|
|
for verification. If you save the object using the SAV command, change the
|
||
|
|
UPDHST value to something other than *NO. The default value for the SAV command
|
||
|
|
is to not preserve the update history. For the other Save related commands,
|
||
|
|
the default value is to preserve the update history. When you use the save-while-active
|
||
|
|
function, you do not need to update the history for the object for verification
|
||
|
|
when you apply and remove journaled changes. When you use the save-while-active
|
||
|
|
function, information is saved on the media with the object and restored when
|
||
|
|
the object is restored. This extra information provides the last save information
|
||
|
|
for applying and removing journaled changes.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><img src="./delta.gif" alt="Start of change" /><h4 class="sectiontitle">Saving queue contents</h4><div class="p"><ul><li>To save the contents of the queue as well, one must specify QDTA((*DTAQ)
|
||
|
|
on the <span class="cmdname">save</span> commands.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">The JID and other journaling operations</h4><p>Not only
|
||
|
|
do you need the JID to apply journaled changes, other journaling operations
|
||
|
|
use the JID. All formats, except the *TYPE1, *TYPE2, and *TYPE3 formats, for
|
||
|
|
the Display Journal (DSPJRN), Receive Journal Entry (RCVJRNE), or Retrieve
|
||
|
|
Journal Entry (RTVJRNE) command include the JID for the object. The JID is
|
||
|
|
also included with the *TYPEPTR and *JRNENTFMT format for the RCVJRNE command,
|
||
|
|
as well as the Retrieve Journal Entries (QjoRetrieveJournalEntries) API. You
|
||
|
|
can use the Retrieve JID Information (QJORJIDI) API to retrieve an object's
|
||
|
|
name (for an object not in the integrated file system) or the file identifier
|
||
|
|
(for an object in the integrated file system), if you know its JID.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Commands for saving objects</h4><p>You can use one of the
|
||
|
|
following commands to save journaled objects:</p>
|
||
|
|
<p><strong>Physical database files,
|
||
|
|
data areas, and data queues</strong></p>
|
||
|
|
<ul><li>Save Changed Objects (SAVCHGOBJ) and specify OBJTYPE(*object-type) OBJJRN(*YES)</li>
|
||
|
|
<li>Save Object (SAVOBJ)</li>
|
||
|
|
<li>Save Library (SAVLIB)</li>
|
||
|
|
<li>Save (SAV)</li>
|
||
|
|
</ul>
|
||
|
|
<p><strong>Integrated file system objects</strong></p>
|
||
|
|
<ul><li>SAV</li>
|
||
|
|
</ul>
|
||
|
|
<p>See the Manually saving parts of your server topic for more information
|
||
|
|
about saving journaled objects.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakistartandend.htm" title="The following links provide instructions on how to start and end journaling for all of the object types that journaling supports.">Start and end journaling and change journaling attributes</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakijrnentryconcepts.htm" title="When you use journal management, the system keeps a record of changes that you make to objects that are journaled and of other events that occur on the system. These records are called journal entries. You can use journal entries to help recover objects or analyze changes that were made to the objects.">Journal entries</a></div>
|
||
|
|
<div><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="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="../rzaiu/rzaiurzaiu001.htm">Manually saving parts of your server</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|