83 lines
7.2 KiB
HTML
83 lines
7.2 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 (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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshowjoblogscreated.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutjoblogpending.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogserverabout.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksjoblogdispchar.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksinteractjoblogs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksaboutspoolfile.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzakshistlogformat.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaksperformanceinfoqhist.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="rzaksqhistlog" />
|
||
|
|
<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="rzaksqhistlog"><a name="rzaksqhistlog"><!-- --></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 (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.</p>
|
||
|
|
<p>The history log (QHST) contains a high-level trace of system activities
|
||
|
|
such as system, subsystem, job information, device status, and system operator
|
||
|
|
messages. Its message queue is QHST.</p>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Log-Version</h4><div class="p">Each log-version is a physical file
|
||
|
|
that is named in the following way: <pre>Qxxxyydddn</pre>
|
||
|
|
Where:<blockquote><strong>xxx</strong> is
|
||
|
|
a 3 character description of the log type (HST)</blockquote>
|
||
|
|
<blockquote><strong>yyddd</strong> is the
|
||
|
|
Julian date on which the log-version was created</blockquote>
|
||
|
|
<blockquote><strong>n</strong> is a sequence
|
||
|
|
number within the Julian date (0 through 9 or A through Z)</blockquote>
|
||
|
|
</div>
|
||
|
|
<div class="p">When
|
||
|
|
a log-version is full, a new version of the log is automatically created.<div class="note"><span class="notetitle">Note:</span> The
|
||
|
|
number of records in the log-version of the history log is specified in the
|
||
|
|
Maximum records in history log (QHSTLOGSIZ) system value. This system value
|
||
|
|
also supports a *DAILY option which creates a new version each day. </div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzakshistlogformat.htm">Format of the History Log</a></strong><br />
|
||
|
|
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:</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzaksperformanceinfoqhist.htm">Performance information and QHST</a></strong><br />
|
||
|
|
Performance information is not displayed as text on message CPF1164. Because the message is in the QHST log, users can write application programs to retrieve this data.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaksjoblogs.htm" title="A job log contains information related to requests entered for a job. A job log has two forms, a pending form and a spooled form.">Job logs</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><img src="./delta.gif" alt="Start of change" /><a href="rzakshowjoblogscreated.htm" title="Release V5R4 brings job logs into the "on demand" world. The job logs are available when needed, but no work is done to produce job logs for which there is no need.">How job logs are created</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div><img src="./delta.gif" alt="Start of change" /><a href="rzaksaboutjoblogpending.htm" title="The job log pending state has been available for many years. When a job's job log attribute is *PND, no job log is produced. With the release of V5R4 enhancements have been made to both iSeries Navigator and the character-based interface so that you can now control how and under what circumstances the job log for a specific job will be produced.">Job log pending</a><img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div><a href="rzaksjoblogserverabout.htm" title="Typically the job log server writes a job's job log to a spooled file. You can route the job log to a printer or to an outfile, (if specified to do so by using the QMHCTLJL, Control job log API), however this is not the recommended method for producing job logs.">Job log server</a></div>
|
||
|
|
<div><a href="rzaksjoblogdispchar.htm" title="The iSeries Navigator provides you with a user friendly, easy to read interface from which you can view job logs and the job log's messages. You can also view job logs by using the character based interface.">Job log characteristics</a></div>
|
||
|
|
<div><a href="rzaksinteractjoblogs.htm" title="The IBM-supplied job descriptions QCTL, QINTER, and QPGMR all have a log level of LOG(4 0 *NOLIST); therefore all messages help text are written to the job log. However, the job logs are not printed if the job ends normally unless you specify *LIST on the SIGNOFF command.">Interactive job logs</a></div>
|
||
|
|
<div><a href="rzaksaboutspoolfile.htm" title="A spooled file holds output data until it can be printed. The spooled file collects data from a device until a program or device is able to process the data. A program uses a spooled file as if it were reading from or writing to an actual device. This is input and output spooling.">Spooled files</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|