84 lines
5.7 KiB
HTML
84 lines
5.7 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="JKLPROD" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<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="rzakiguivsgs.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="rzakijklprod" />
|
||
|
|
<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>JKLPROD</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzakijklprod"><a name="rzakijklprod"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">JKLPROD</h1>
|
||
|
|
<div><p>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.</p>
|
||
|
|
<p>Also, there are several users who have remote access to the system from
|
||
|
|
home connection. In addition, even though the company's web site is static,
|
||
|
|
the company has plans to establish a transactional site. Because of the importance
|
||
|
|
of the information about JKLPROD, Sharon wants to be able to audit the activity
|
||
|
|
that occurs on the system.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">JKLPROD journaling strategy</h4><p>Since the objects on
|
||
|
|
JKLPROD are crucial to JKL, and since they change often, Sharon has decided
|
||
|
|
that they are good candidates for journaling.</p>
|
||
|
|
<ul><li>Since there are access paths that are critical to her operation, Sharon
|
||
|
|
journals access paths.</li>
|
||
|
|
<li>Sharon already separates the information about JKLPROD on separate disk
|
||
|
|
pools: <ul><li>Disk pool 2 - inventory control</li>
|
||
|
|
<li>Disk pool 3 - customer orders</li>
|
||
|
|
<li>Disk pool 4 - contracts and pricing</li>
|
||
|
|
<li>Disk pool 5 - accounts receivable</li>
|
||
|
|
</ul>
|
||
|
|
<p>Since the journal and the journaled objects must be in the same disk
|
||
|
|
pool, Sharon creates four journals.</p>
|
||
|
|
</li>
|
||
|
|
<li>Since she wants to audit the activity that occurs on the system, and since
|
||
|
|
people have remote access to the system, Sharon journals fixed-length data
|
||
|
|
using the following values: <ul><li>Job name (*JOB)</li>
|
||
|
|
<li>User profile (*USR)</li>
|
||
|
|
<li>Program name (*PGM)</li>
|
||
|
|
<li>Remote address (*RMTADR)</li>
|
||
|
|
</ul>
|
||
|
|
</li>
|
||
|
|
<li>Since Sharon is using the FIXLENDTA parameter, she cannot minimize the
|
||
|
|
fixed-length portion of the journal entries.</li>
|
||
|
|
<li>Because she is using the FIXLENDTA parameter for all of the journals,
|
||
|
|
and since she is journaling access paths Sharon uses the character-based interface
|
||
|
|
to set up journaling.</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="rzakiguivsgs.htm" title="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.">iSeries Navigator versus the character-based interface for journaling objects</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|