79 lines
5.9 KiB
HTML
79 lines
5.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="concept" />
|
||
|
|
<meta name="DC.Title" content="JKLDEV" />
|
||
|
|
<meta name="abstract" content="JKLDEV is JKL's development server. Though it does not require 24x7 availability, the data on it represent many person hours of work by the developers. Therefore it is important that in the event of a crash, the system be brought to a current state. Also, since it is a development server, changes to the data occur often." />
|
||
|
|
<meta name="description" content="JKLDEV is JKL's development server. Though it does not require 24x7 availability, the data on it represent many person hours of work by the developers. Therefore it is important that in the event of a crash, the system be brought to a current state. Also, since it is a development server, changes to the data occur often." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijournalscenario.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnobjrn.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakijrnap.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiobjassnjrn.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="rzakijkldev" />
|
||
|
|
<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>JKLDEV</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakijkldev"><a name="rzakijkldev"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">JKLDEV</h1>
|
||
|
|
<div><p>JKLDEV is JKL's development server. Though it does not require
|
||
|
|
24x7 availability, the data on it represent many person hours of work by the
|
||
|
|
developers. Therefore it is important that in the event of a crash, the system
|
||
|
|
be brought to a current state. Also, since it is a development server, changes
|
||
|
|
to the data occur often.</p>
|
||
|
|
<p>JKLDEV is used by both web and database developers. So several different
|
||
|
|
types of data are stored on this server, including stream files and database
|
||
|
|
files.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">JKLDEV journaling strategy</h4><p>Since many of the objects
|
||
|
|
on JKLDEV are important and changes often, Sharon has decided that they are
|
||
|
|
good candidates for journaling.</p>
|
||
|
|
<p>JKLDEV is used by both web and database
|
||
|
|
developers, so there are several physical files, and many stream files that
|
||
|
|
she wants to journal. Sharon has decided to do the following:</p>
|
||
|
|
<ul><li>Since none of the access paths are critical to her operation, Sharon does
|
||
|
|
not journal access paths.</li>
|
||
|
|
<li>To simplify setup and recovery, Sharon assigns all of the objects to one
|
||
|
|
journal.</li>
|
||
|
|
<li>Since there are many stream files to journal, Sharon journals the integrated
|
||
|
|
file system directories, in addition to individual files. She elects to use
|
||
|
|
the <span class="uicontrol">Current folder and all subfolders</span> option and <span class="uicontrol">Journal
|
||
|
|
new files and folders</span> option. This choice ensures that the objects
|
||
|
|
currently in the directory and in any subfolders are journaled and objects
|
||
|
|
that are created in the future are also journaled.</li>
|
||
|
|
<li>Since journaling with the <span class="uicontrol">Journal new files and folders</span> option
|
||
|
|
can quickly make the journal receiver size grow quickly, she uses system journal-receiver
|
||
|
|
management.</li>
|
||
|
|
<li>Because it supports all of the options she has chosen, Sharon sets up
|
||
|
|
journaling on iSeries™ Navigator.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakijournalscenario.htm" title="Provides the steps that a fictitious company, JKL Toy company, takes as it implements journal management on its iSeries server.">Scenario: Journal management</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzakiplnobjrn.htm" title="When you plan which objects to journal, consider the following:">Plan which objects to journal</a></div>
|
||
|
|
<div><a href="rzakijrnap.htm" title="If you journal access paths, the system can use the journal entries to recover access paths instead of rebuilding them completely.">Reasons to journal access paths</a></div>
|
||
|
|
<div><a href="rzakiobjassnjrn.htm" title="You can use one journal to manage all the objects you are journaling. Or, you can set up several journals if groups of objects have different backup and recovery requirements. Every journal has a single attached receiver. All journal entries for all objects being managed by the journal are written to the same journal receiver.">Object assignment to journals</a></div>
|
||
|
|
<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>
|