104 lines
8.1 KiB
HTML
104 lines
8.1 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="iSeries Navigator versus the character-based interface for journaling objects" />
|
||
|
<meta name="abstract" content="There are two environments that you can use for journal management: iSeries Navigator and the character-based interface. iSeries Navigator provides a graphical interface for journaling that is easy to use and does not require the use of control language (CL) commands. The character-based interface requires the use of CL commands or APIs, but has more functionality than iSeries Navigator." />
|
||
|
<meta name="description" content="There are two environments that you can use for journal management: iSeries Navigator and the character-based interface. iSeries Navigator provides a graphical interface for journaling that is easy to use and does not require the use of control language (CL) commands. The character-based interface requires the use of CL commands or APIs, but has more functionality than iSeries Navigator." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrn.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakisizeoptions.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakiminendta.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakiintrusion.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakijrncache.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakichgjrnstate.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakisetupjrngs.htm" />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzakijklprod.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="rzakiguivsgs" />
|
||
|
<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>iSeries Navigator
|
||
|
versus the character-based interface for journaling objects</title>
|
||
|
</head>
|
||
|
<body id="rzakiguivsgs"><a name="rzakiguivsgs"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">iSeries Navigator
|
||
|
versus the character-based interface for journaling objects</h1>
|
||
|
<div><p>There are two environments that you can use for journal management: iSeries™ Navigator
|
||
|
and the character-based interface. iSeries Navigator provides a graphical
|
||
|
interface for journaling that is easy to use and does not require the use
|
||
|
of control language (CL) commands. The character-based interface requires
|
||
|
the use of CL commands or APIs, but has more functionality than iSeries Navigator.</p>
|
||
|
<p>The following is a list of journaling functions that are only available
|
||
|
with the character-based interface:</p>
|
||
|
<ul><li>Journal access paths.</li>
|
||
|
<li>Specify a maximum receiver-size option.</li>
|
||
|
<li>Specify that objects allow journal entries to have minimized entry-specific
|
||
|
data.</li>
|
||
|
<li>Specify the data that is included in the fixed-length portion of the journal
|
||
|
entries.</li>
|
||
|
<li>Specify the time to delay the next attempt to automatically attach or
|
||
|
delete a new journal receiver with system journal-receiver management.</li>
|
||
|
<li>Specify journal caching.</li>
|
||
|
<li>Specify journal standby state.</li>
|
||
|
<li>Specify the journal object limit.</li>
|
||
|
<li>Specify the journal recovery count.</li>
|
||
|
<li>Change the threshold for a journal receiver.</li>
|
||
|
<li>Compare journal entries.</li>
|
||
|
<li>Apply journaled changes.</li>
|
||
|
<li>Remove journaled changes.</li>
|
||
|
<li>Display journal entries.</li>
|
||
|
<li>Look at the journal to display all object types which are journaled to
|
||
|
that journal.</li>
|
||
|
<li>Change the journaling attributes for a journaled object without ending
|
||
|
journaling.</li>
|
||
|
</ul>
|
||
|
<p>Other journaling differences between iSeries Navigator and the character-based
|
||
|
interface are as follows:</p>
|
||
|
<ul><li>With iSeries Navigator,
|
||
|
you create the journal and journal receiver together. With the character-based
|
||
|
interface, you create the journal receiver first.</li>
|
||
|
<li>With iSeries Navigator
|
||
|
you set the permissions for the journal and receiver after they are created.
|
||
|
With the character-based interface you can set permissions (authority) at
|
||
|
creation time.</li>
|
||
|
</ul>
|
||
|
<p>Decide which of the two interfaces to use before you set up journal management,
|
||
|
since the character-based interface creates journal receivers and journals
|
||
|
separately, and iSeries Navigator
|
||
|
creates journals and receivers together. However, if you decide to use a function
|
||
|
that iSeries Navigator
|
||
|
does not support after you start journaling, you can do so with the character-based
|
||
|
interface, even if you used iSeries Navigator to set up journaling.</p>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplnjrn.htm" title="This topic provides you with the information you need to ensure you have enough disk space, to plan what objects to journal, and to plan which journaling options to use.">Plan for journal management</a></div>
|
||
|
</div>
|
||
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
<div><a href="rzakisizeoptions.htm" title="A journal receiver holds journal entries that you might use for recovery and entries that the system might use for recovery. For example, you might use record level entries, such as database record changes, and file level entries, such as the entry for opening or closing a file. Also, the system writes entries that you never see or use, such as entries for explicitly journaled access paths, for SMAPP, or for commitment control.">Receiver size options for journals</a></div>
|
||
|
<div><a href="rzakiminendta.htm" title="On the Create Journal (CRTJRN) and Change Journal (CHGJRN) commands, you can specify to allow for the deposit of minimized journal entries. This will decrease the size of your journal entries.">Minimized entry-specific data for journal entries</a></div>
|
||
|
<div><a href="rzakiintrusion.htm" title="You can use the Fixed Length Data (FIXLENDTA) parameter of Create Journal (CRTJRN) and Change Journal (CHGJRN) commands to audit security related activity for journaled objects on your system.">Fixed-length options for journal entries</a></div>
|
||
|
<div><a href="rzakijrncache.htm" title="Journal caching is separately chargeable feature with which you can specify that the system cache journal entries in main storage, before writing them to disk. Journal caching is option 42 of the i5/OS operating system.">Journal cache</a></div>
|
||
|
<div><a href="rzakijklprod.htm" title="JKLPROD is the system that JKL uses for all of their customer orders and where their business applications are installed (inventory control, customer orders, contracts and pricing, accounts receivable). The information about this server is extremely critical to their business and changes often.">JKLPROD</a></div>
|
||
|
</div>
|
||
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
<div><a href="rzakichgjrnstate.htm" title="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.">Change the state of local journals</a></div>
|
||
|
<div><a href="rzakisetupjrngs.htm" title="Provides instructions on how to set up journals and journal receivers.">Set up journaling</a></div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</body>
|
||
|
</html>
|