180 lines
12 KiB
HTML
180 lines
12 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="QHST history log" />
|
||
|
|
<meta name="abstract" content="The history log (QHST) consists of a message queue and a physical file known as a log-version." />
|
||
|
|
<meta name="description" content="The history log (QHST) consists of a message queue and a physical file known as a log-version." />
|
||
|
|
<meta name="DC.subject" content="message, history log (QHST), version, QHST (history log), message queue, description, log, QHST (history), displaying, history, displaying system, QHST (history log) message queue, QHST log, system log, naming version, DSPOBJD (Display Object Description) command, log-version selection, Display Object Description (DSPOBJD) command, log-version selection, command, CL, DSPOBJD (Display Object Description), Display Object Description (DSPOBJD), object description, log-versions, DSPLOG (Display Log) command, Display Log (DSPLOG) command, DSPLOG (Display Log), Display Log (DSPLOG), batch job log, Display History Log Contents display" />
|
||
|
|
<meta name="keywords" content="message, history log (QHST), version, QHST (history log), message queue, description, log, QHST (history), displaying, history, displaying system, QHST (history log) message queue, QHST log, system log, naming version, DSPOBJD (Display Object Description) command, log-version selection, Display Object Description (DSPOBJD) command, log-version selection, command, CL, DSPOBJD (Display Object Description), Display Object Description (DSPOBJD), object description, log-versions, DSPLOG (Display Log) command, Display Log (DSPLOG) command, DSPLOG (Display Log), Display Log (DSPLOG), batch job log, Display History Log Contents display" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="mlogg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="hlformat.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="pqhst.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="qhstjob.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="dellf.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="systl" />
|
||
|
|
<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>QHST history log</title>
|
||
|
|
</head>
|
||
|
|
<body id="systl"><a name="systl"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">QHST history log</h1>
|
||
|
|
<div><p>The history log (QHST) consists of a message queue and a physical
|
||
|
|
file known as a log-version. </p>
|
||
|
|
<p>Messages sent to the history log message queue (QHST) are written by the
|
||
|
|
system to the current log version physical file. The history log contains
|
||
|
|
a high-level trace of system activities such as system, subsystem, and job
|
||
|
|
information, device status, and system operator messages.</p>
|
||
|
|
<p>When a log-version is full, a new version of the log is automatically created.
|
||
|
|
Each version is a physical file that is named in the following way: </p>
|
||
|
|
<pre>Qxxxyydddn</pre>
|
||
|
|
<p>where the following is true: </p>
|
||
|
|
<dl><dt class="dlterm"><samp class="codeph">xxx</samp></dt>
|
||
|
|
<dd>Is a 3-character description of the log type (HST)</dd>
|
||
|
|
<dt class="dlterm"><samp class="codeph">yyddd</samp></dt>
|
||
|
|
<dd>Is the Julian date of the first message in the log version</dd>
|
||
|
|
<dt class="dlterm"><samp class="codeph">n</samp></dt>
|
||
|
|
<dd>Is a sequence number within the Julian date (A through Z and 0 through
|
||
|
|
9)</dd>
|
||
|
|
</dl>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> The number of records in each version of the history log is specified
|
||
|
|
in the system value QHSTLOGSIZ. There is also a value of *DAILY to allow a
|
||
|
|
new log version to be created each day instead of creating a new file based
|
||
|
|
only on size.</div>
|
||
|
|
<p>The text of the log version file contains the date and time of the first
|
||
|
|
message and last message in the log version. The date and time of the first
|
||
|
|
message are in positions 1-13 of the text; the date and time of the last message
|
||
|
|
are in positions 14-26. The date and time are in the format cyymmddhhmmss,
|
||
|
|
where: </p>
|
||
|
|
<dl><dt class="dlterm"><samp class="codeph">c</samp></dt>
|
||
|
|
<dd>Is the century guard digit</dd>
|
||
|
|
<dt class="dlterm"><samp class="codeph">yymmdd</samp></dt>
|
||
|
|
<dd>Is the date the message was sent</dd>
|
||
|
|
<dt class="dlterm"><samp class="codeph">hhmmss</samp></dt>
|
||
|
|
<dd>Is the time the message was sent</dd>
|
||
|
|
</dl>
|
||
|
|
<p>You can create a maximum of 36 log versions with the same Julian date.
|
||
|
|
If more than 36 log versions are created on the same day, the next available
|
||
|
|
Julian day is used for subsequent log versions. If some of the older log
|
||
|
|
versions are then deleted, it is possible to use the names again. Log versions
|
||
|
|
are out of order when sequenced by name if log versions are deleted and names
|
||
|
|
used again.</p>
|
||
|
|
<p>You can also write a program to process history log records. Because several
|
||
|
|
versions of each log may be available, you must select the log-version to
|
||
|
|
be processed. To determine the available log-versions, use the <span class="cmdname">Display
|
||
|
|
Object Description (DSPOBJD)</span> command. For example, the following <span class="cmdname">Display
|
||
|
|
Log (DSPLOG)</span> command displays what versions of the history log are
|
||
|
|
available: </p>
|
||
|
|
<pre>DSPOBJD OBJ(QSYS/QHST*) OBJTYPE(*FILE)</pre>
|
||
|
|
<p>You can delete logs on your system by using the delete option from the
|
||
|
|
display that is presented on the <span class="cmdname">Work with Objects (WRKOBJ)</span> command.</p>
|
||
|
|
<p>You can display or print the information in a log using the <span class="cmdname">Display
|
||
|
|
Log (DSPLOG)</span> command. You can select the information you want displayed
|
||
|
|
or printed by specifying any combination of the following: </p>
|
||
|
|
<ul><li>Period of time</li>
|
||
|
|
<li>Name of job that sent the log entry</li>
|
||
|
|
<li>Message identifiers of entries</li>
|
||
|
|
</ul>
|
||
|
|
<p>The following <span class="cmdname">Display Log (DSPLOG)</span> command displays
|
||
|
|
all the available entries for the job OEDAILY in the current day: </p>
|
||
|
|
<pre>DSPLOG JOB(OEDAILY)</pre>
|
||
|
|
<p>The resulting display is: </p>
|
||
|
|
<pre class="screen"> Display History Log Contents
|
||
|
|
|
||
|
|
Job OEDAILY started
|
||
|
|
Database file OEMSTR in library OELIB expired
|
||
|
|
Job OEDAILY abnormally ended
|
||
|
|
Job OEDAILY started
|
||
|
|
Job OEDAILY ended
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
|
||
|
|
Bottom
|
||
|
|
Press Enter to continue.
|
||
|
|
|
||
|
|
F3=Exit F10=Display all F12=Cancel
|
||
|
|
</pre>
|
||
|
|
<p>If you reset the system date or time to an earlier setting, or if you advanced
|
||
|
|
the system date and time by more than 48 hours, a new log version is started.
|
||
|
|
This ensures that all messages in a single log version are in chronological
|
||
|
|
order.</p>
|
||
|
|
<p>Log versions created on a release prior to V3R6M0 may contain entries that
|
||
|
|
are not in chronological order if the system date and time was reset to an
|
||
|
|
earlier setting. Therefore, when you try to display the log-version, some
|
||
|
|
entries may be missed. For example, if the log-version contains entries dated
|
||
|
|
1988 followed by entries dated 1987, and you want to display those 1987 entries,
|
||
|
|
you specify the 1987 dates on the PERIOD parameter on the <span class="cmdname">Display
|
||
|
|
Log (DSPLOG)</span> command but the expected entries are not displayed.
|
||
|
|
You should always use the system date (QDATE) and the system time (QTIME),
|
||
|
|
or you should specify the PERIOD parameter as follows: </p>
|
||
|
|
<pre>PERIOD((start-time start-date) (*AVAIL *END))</pre>
|
||
|
|
<p>The system writes the messages sent to a log message queue to the current
|
||
|
|
log version physical file when the message queue reaches a certain size or
|
||
|
|
when the <span class="cmdname">Display Log (DSPLOG)</span> command was used. If you
|
||
|
|
want to ensure the current log version is up-to-date, specify a fictitious
|
||
|
|
message identifier, such as <samp class="codeph">###0000</samp>, on the DSPLOG command.
|
||
|
|
No messages are displayed, but the messages in the message queue are copied
|
||
|
|
to the log version physical file to make it current.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> If a message is sent to QHST and the <span class="cmdname">Display Log (DSPLOG)</span> command
|
||
|
|
is done immediately, the DSPLOG command will show messages from the log version
|
||
|
|
physical file. Depending on the number of messages being copied to the log
|
||
|
|
version, your message may not be shown until a second <span class="cmdname">Display Log
|
||
|
|
(DSPLOG)</span> command is run later.</div>
|
||
|
|
<p>If you print the information in a log using the <span class="cmdname">Display Log (DSPLOG)</span> command
|
||
|
|
and output parameter *PRINT, (DSPLOG OUTPUT(*PRINT)), only one line from each
|
||
|
|
message is printed, using the first 105 characters of each message.</p>
|
||
|
|
<p>If you print the information in a log using the <span class="cmdname">Display Log (DSPLOG)</span> command
|
||
|
|
and output parameter *PRTWRAP, (DSPLOG OUTPUT(*PRTWRAP)), messages
|
||
|
|
longer than 105 characters are wrapped to include additional lines to a limit
|
||
|
|
of 2000 characters.</p>
|
||
|
|
<p>If you print the information in a log using the <span class="cmdname">Display Log (DSPLOG)</span> command
|
||
|
|
and output parameter *PRTSECLVL, messages longer than 105 characters are wrapped
|
||
|
|
to include additional lines to a limit of 2000 characters. The second-level
|
||
|
|
message text is also printed if available, up to a maximum of 6000 characters.</p>
|
||
|
|
<p>If you display the information in a log using the <span class="cmdname">Display Log
|
||
|
|
(DSPLOG)</span> command, only 105 characters of message text are shown.
|
||
|
|
Any characters after 105 characters are truncated at the right.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="hlformat.htm">Format of the history log</a></strong><br />
|
||
|
|
A database file is used to store the messages sent to a log message queue on the system. 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.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="pqhst.htm">Process the QHST file</a></strong><br />
|
||
|
|
If you use an HLL program to process the QHST file, keep in mind that the length of the message can vary with each occurrence of a message.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="qhstjob.htm">QHST job start and completion messages</a></strong><br />
|
||
|
|
The system performs special formatting of the job start and job completion messages.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="dellf.htm">Delete QHST files</a></strong><br />
|
||
|
|
Log-version physical files accumulate on a system and you should periodically delete old logs that are not needed.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="mlogg.htm" title="There are two types of logs for messages: job logs and history logs.">Log messages</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|