91 lines
7.4 KiB
HTML
91 lines
7.4 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="Manage journals" />
|
|
<meta name="abstract" content="Provides tasks to manage your journaling environment." />
|
|
<meta name="description" content="Provides tasks to manage your journaling environment." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnkickoff.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiswapdel.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakievaljrn.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakirecordjrn.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnaudit.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiwrkjrna.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiwrkinopjrnrcv.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakicomparjrnimg.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiibmjrn.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakisndjrne.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakichgjrnstate.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakimanorsysmng.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="rzakimanagejrn" />
|
|
<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>Manage journals</title>
|
|
</head>
|
|
<body id="rzakimanagejrn"><a name="rzakimanagejrn"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Manage journals</h1>
|
|
<div><p>Provides tasks to manage your journaling environment.</p>
|
|
<p>Managing your journaling environment requires these basic tasks:</p>
|
|
<ul><li>Keep records of which objects you are journaling.</li>
|
|
<li>Evaluate the impact on journaling when new applications or logical files
|
|
are added.</li>
|
|
<li>Regularly detach, save, and delete journal receivers.</li>
|
|
</ul>
|
|
<p>Your journal receivers enable you to recover changes to your important
|
|
objects. They also provide an audit trail of activity that occurs on your
|
|
system.</p>
|
|
<p>Protect your journal receivers by regularly detaching them and saving them;
|
|
or you can have the system take over the job of changing journal receivers
|
|
by specifying system journal-receiver management.</p>
|
|
<p>Do the following tasks to manage your journaling environment:</p>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="rzakiswapdel.htm">Swap, delete, and save journals and receivers</a></strong><br />
|
|
The management tasks that you need to perform most often for journaling are swapping journal receivers and saving and deleting journal receivers.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakievaljrn.htm">Evaluate how system changes affect journal management</a></strong><br />
|
|
After you have established your journaling environment, you need to keep up with changes that occur on your system.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakirecordjrn.htm">Keep records of journaled objects</a></strong><br />
|
|
You must always have a current list of objects that you are journaling and their assigned journals. Print a new list whenever you add or remove objects from the journal.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakijrnaudit.htm">Manage security for journals</a></strong><br />
|
|
Use journal management to provide an audit trail of changes that were made to your objects. You can determine which program or user made changes to objects by using the journal entries.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakiwrkjrna.htm">Display information for journaled objects, journals, and receivers</a></strong><br />
|
|
iSeries™ Navigator,
|
|
Control Language commands, and APIs provide several ways you can display information
|
|
about journaled objects, journals, and journal receivers.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakiwrkinopjrnrcv.htm">Work with inoperable journal receivers</a></strong><br />
|
|
If you have specified journaling for any objects, the system ensures that you have corrected problems that affect journaling before continuing with operations on those objects. If the attached journal receiver becomes inoperable, the operation that writes a journal entry is interrupted and the system sends an inquiry message that notifies the system operator.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakicomparjrnimg.htm">Compare journal images</a></strong><br />
|
|
Use the Compare Journal Images (CMPJRNIMG) command to compare and list the differences between the before-image of a record and the after-image of that record, or the after-image of a record with the previous after-image of that record.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakiibmjrn.htm">Work with IBM-supplied journals</a></strong><br />
|
|
The operating system and some licensed programs use journals to provide audit trails and assist with recovery.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakisndjrne.htm">Send your own journal entries</a></strong><br />
|
|
Use the Send Journal Entry (SNDJRNE) command or the Send Journal Entry (QJOSJRNE) API to add your own entries to a journal. The system places these entries in the journal's attached journal receiver along with the system-created journal entries.</li>
|
|
<li class="ulchildlink"><strong><a href="rzakichgjrnstate.htm">Change the state of local journals</a></strong><br />
|
|
Local journals can be in one of two states, active or standby. When the journal state of a local journal is active, journal entries are allowed to be deposited to the journal receiver.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakijrnkickoff.htm" title="Use local journal management to recover the changes to an object that have occurred since the object was last saved, as an audit trail, or to help replicate an object. Setting up journaling locally is a prerequisite for other iSeries functions such as Remote journal management and Commitment control. Use this information to set up, manage, and troubleshoot journaling on a local server.">Local journal management</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzakimanorsysmng.htm" title="When you create a journal with iSeries Navigator or the Create Journal (CRTJRN) command, you can select to have either system managed or user managed journal receivers.">Manual versus system journal-receiver management</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |