76 lines
5.1 KiB
HTML
76 lines
5.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="Naming conventions for journals" />
|
||
|
|
<meta name="abstract" content="When you create a journal with iSeries Navigator or the Create Journal (CRTJRN) command, you assign a name to it. If you plan to have more than one journal on your system, use a naming convention that links each journal with its associated receiver." />
|
||
|
|
<meta name="description" content="When you create a journal with iSeries Navigator or the Create Journal (CRTJRN) command, you assign a name to it. If you plan to have more than one journal on your system, use a naming convention that links each journal with its associated receiver." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakiplnjrnsu.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/crtjrn.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="rzakinamejrn" />
|
||
|
|
<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>Naming conventions for journals</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakinamejrn"><a name="rzakinamejrn"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Naming conventions for journals</h1>
|
||
|
|
<div><p>When you create a journal with iSeries™ Navigator or the Create Journal
|
||
|
|
(CRTJRN) command, you assign a name to it. If you plan to have more than one
|
||
|
|
journal on your system, use a naming convention that links each journal with
|
||
|
|
its associated receiver.</p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />To simplify recovery and avoid confusion, make
|
||
|
|
each journal name unique for your entire system, not unique within a library.
|
||
|
|
If you have two journals with the same name in different libraries and they
|
||
|
|
both become damaged, the reclaim storage operation renames both journals when
|
||
|
|
they are placed in the QRCL library. When you use the Move Object (MOVOBJ)
|
||
|
|
command for a journal in the QRCL library, you can change the name of the
|
||
|
|
library back to the original library name. You cannot change the name of the
|
||
|
|
journal itself. In this case, you would not be able to recover your journal
|
||
|
|
from QRCL since its name has been changed.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Naming conventions to ensure restore sequence</h4><p>Name
|
||
|
|
the libraries for the journals, objects, and journal receivers to ensure that
|
||
|
|
the objects are restored in the correct order. A naming convention will ensure
|
||
|
|
that the system automatically starts journaling after a restore operation.
|
||
|
|
To ensure that journaling is automatically started again, the journals must
|
||
|
|
be restored before the objects being journaled. (If the journals and associated
|
||
|
|
objects are in the same library, then the system automatically restores the
|
||
|
|
objects in the correct order.)</p>
|
||
|
|
<p>If you start the name of the library
|
||
|
|
for the journal with a special character, such as #, $, or @, the system will
|
||
|
|
restore the library for the journal before the library for the objects. This
|
||
|
|
is because in normal sort sequence, special characters appear before alphabetic
|
||
|
|
characters.</p>
|
||
|
|
<p>When the journals and associated objects are in different
|
||
|
|
libraries, you must ensure that the objects are restored in the correct order.</p>
|
||
|
|
<p>Since
|
||
|
|
independent file system objects do not exist in a library, your restore processing
|
||
|
|
must ensure the objects are restored in the correct order. That is, you must
|
||
|
|
restore your libraries which contain the journals before restoring the independent
|
||
|
|
file system objects that were journaled to that journal.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakiplnjrnsu.htm" title="The following topics provide information to plan configuration for journals. They provide information about each option that you can select for journal.">Plan setup for journals</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="../cl/crtjrn.htm">Create Journal (CRTJRN) command</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|