155 lines
8.3 KiB
HTML
155 lines
8.3 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="Format of the History Log" />
|
|
<meta name="abstract" content="A database file is used to store the message sent to a system log. Because all records in a physical file have the same length and messages sent to a log have different lengths, the messages can span more than one record. Each record for a message has three fields:" />
|
|
<meta name="description" content="A database file is used to store the message sent to a system log. Because all records in a physical file have the same length and messages sent to a log have different lengths, the messages can span more than one record. Each record for a message has three fields:" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksqhistlog.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="rzakshistlogformat" />
|
|
<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>Format of the History Log</title>
|
|
</head>
|
|
<body id="rzakshistlogformat"><a name="rzakshistlogformat"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Format of the History Log</h1>
|
|
<div><p>A database file is used to store the message sent to a system log.
|
|
Because all records in a physical file have the same length and messages sent
|
|
to a log have different lengths, the messages can span more than one record.
|
|
Each record for a message has three fields:</p>
|
|
<ul><li>System date and time (a character field of length 8). This is an internal
|
|
field. The converted date and time also are in the message.</li>
|
|
<li>Record number (a 2-byte field). For example, the field contains hex 0001
|
|
for the first record, hex 002 for the second record, and so on.</li>
|
|
<li>Data (a character field of length 132).</li>
|
|
</ul>
|
|
<div class="section"><h4 class="sectiontitle">Format for the third field (data):</h4>
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="hsides" border="1" rules="rows"><caption>Table 1. Format for Third Field of the First Record</caption><thead align="left"><tr valign="bottom"><th valign="bottom" id="d0e32">Contents</th>
|
|
<th valign="bottom" id="d0e34">Type</th>
|
|
<th align="right" valign="bottom" id="d0e36">Length</th>
|
|
<th align="right" valign="bottom" id="d0e38">Positions in Record</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" headers="d0e32 ">Job name</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">26</td>
|
|
<td align="right" valign="top" headers="d0e38 ">11-36</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Converted date and time</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">13</td>
|
|
<td align="right" valign="top" headers="d0e38 ">37-49</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Message ID</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">7</td>
|
|
<td align="right" valign="top" headers="d0e38 ">50-56</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Message file name</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">10</td>
|
|
<td align="right" valign="top" headers="d0e38 ">57-66</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Library name</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">10</td>
|
|
<td align="right" valign="top" headers="d0e38 ">67-76</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Message type</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">2</td>
|
|
<td align="right" valign="top" headers="d0e38 ">77-78</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Severity code</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">2</td>
|
|
<td align="right" valign="top" headers="d0e38 ">79-80</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Sending program name</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">12</td>
|
|
<td align="right" valign="top" headers="d0e38 ">81-92</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Receiving program name</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">10</td>
|
|
<td align="right" valign="top" headers="d0e38 ">97-106</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Receiving program instruction number</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">4</td>
|
|
<td align="right" valign="top" headers="d0e38 ">107-110</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Message text length</td>
|
|
<td valign="top" headers="d0e34 ">Binary</td>
|
|
<td align="right" valign="top" headers="d0e36 ">2</td>
|
|
<td align="right" valign="top" headers="d0e38 ">111-112</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Message data length</td>
|
|
<td valign="top" headers="d0e34 ">Binary</td>
|
|
<td align="right" valign="top" headers="d0e36 ">2</td>
|
|
<td align="right" valign="top" headers="d0e38 ">113-114</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e32 ">Reserved</td>
|
|
<td valign="top" headers="d0e34 ">Character</td>
|
|
<td align="right" valign="top" headers="d0e36 ">28</td>
|
|
<td align="right" valign="top" headers="d0e38 ">115-142</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="hsides" border="1" rules="rows"><caption>Table 2. Format of the third field
|
|
(data) of the remaining records</caption><thead align="left"><tr valign="bottom"><th valign="bottom" id="d0e167">Contents</th>
|
|
<th valign="bottom" id="d0e169">Type</th>
|
|
<th valign="bottom" id="d0e171">Length</th>
|
|
</tr>
|
|
</thead>
|
|
<tbody><tr><td valign="top" headers="d0e167 ">Message</td>
|
|
<td valign="top" headers="d0e169 ">Character</td>
|
|
<td valign="top" headers="d0e171 ">Variable (This length is specified in the first record
|
|
(positions 111 and 112) and cannot exceed 132.)</td>
|
|
</tr>
|
|
<tr><td valign="top" headers="d0e167 ">Message data </td>
|
|
<td valign="top" headers="d0e169 ">Character</td>
|
|
<td valign="top" headers="d0e171 ">Variable (This length is specified in the first record
|
|
(positions 113 and 114).)</td>
|
|
</tr>
|
|
</tbody>
|
|
</table>
|
|
</div>
|
|
<p>A message is never split when a new version of a log is started.
|
|
The first and last records of a message are always in the same QHST version.</p>
|
|
</div>
|
|
<div class="section"><h4 class="sectiontitle">QHST File Processing</h4><p>If you use a high-level language
|
|
program to process the QHST file, keep in mind that the message data begins
|
|
at a variable location for each use of the same message. The reason for this
|
|
is that the message includes replaceable variables so the actual length of
|
|
the message varies.</p>
|
|
<p>However, for message CPF1124 (job start) and message
|
|
CPF1165 (job completion) the message data always begins in position 11 of
|
|
the third record.</p>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksqhistlog.htm" title="The history (QHST) log consists of a message queue and a physical file known as a log-version. Messages sent to the log message queue are written by the system to the current log-version physical file.">QHST History Log</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |