56 lines
4.7 KiB
HTML
56 lines
4.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="Output for journal entries directed to a database output file" />
|
|
<meta name="abstract" content="If you direct the output from the Display Journal (DSPJRN) command to a database output file, you can further restrict the journal entries you want to process by creating logical files over the database output file." />
|
|
<meta name="description" content="If you direct the output from the Display Journal (DSPJRN) command to a database output file, you can further restrict the journal entries you want to process by creating logical files over the database output file." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzakidsplyjrnentry.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="../cl/dspjrn.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="rzakidboutfile" />
|
|
<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>Output for journal entries directed to a database output file</title>
|
|
</head>
|
|
<body id="rzakidboutfile"><a name="rzakidboutfile"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Output for journal entries directed to a database output file</h1>
|
|
<div><p>If you direct the output from the Display Journal (DSPJRN) command to a database output file, you can further restrict the journal entries you want to process by creating logical files over the
|
|
database output file.</p>
|
|
<p>Each journal entry occupies one record in the output file. Each has a fixed-length portion for standard files. Before-images and after-images occupy separate records. The ENTDTALEN parameter
|
|
controls the length of the field that is used to contain the record image. The ENTDTALEN parameter also controls whether the field is a fixed or variable length field. If the journal entry is smaller than
|
|
the output file record, the journal entry is padded with blanks. If the journal entry is larger than the output file record, the remainder of the journal entry is truncated, and the system issues a warning
|
|
message. To avoid truncation, specify the maximum record length in your files for the ENTDTALEN parameter on the DSPJRN command or specify *CALC for the ENTDTALEN parameter to allow the system to calculate
|
|
the length of the specific data field so no entry is truncated.</p>
|
|
<p>If you write journal entries to a database output file, you can write application programs that will process the data to:</p>
|
|
<ul><li>Write your own apply program.</li>
|
|
<li>Correct data that has been incorrectly updated.</li>
|
|
<li>Remove or review all changes that were made by a particular program.</li>
|
|
</ul>
|
|
<p>If you remove all changes that were made by a particular program, you could remove some valid updates. For example, assume that two work station users are using the same program to update an object,
|
|
and one user enters some data that is not valid. If you remove all invalid data changes that are made by that program, you also remove the valid data that is entered by the other work station user.</p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzakidsplyjrnentry.htm" title="Use the Display Journal (DSPJRN) command to display journal entries. The entries are displayed at a work station, printed, or written to an output file. You cannot directly access the journal entries in the form in which they are contained in the journal receivers.">Display and print journal entries</a></div>
|
|
</div>
|
|
<div class="relref"><strong>Related reference</strong><br />
|
|
<div><a href="../cl/dspjrn.htm">Display Journal (DSPJRN) command</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |