122 lines
7.0 KiB
HTML
122 lines
7.0 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 job start and completion messages" />
|
||
|
|
<meta name="abstract" content="The system performs special formatting of the job start and job completion messages." />
|
||
|
|
<meta name="description" content="The system performs special formatting of the job start and job completion messages." />
|
||
|
|
<meta name="DC.subject" content="QHST (history log) file, job start message, job completion message, message" />
|
||
|
|
<meta name="keywords" content="QHST (history log) file, job start message, job completion message, message" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="systl.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="qhstjob" />
|
||
|
|
<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 job start and completion messages</title>
|
||
|
|
</head>
|
||
|
|
<body id="qhstjob"><a name="qhstjob"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">QHST job start and completion messages</h1>
|
||
|
|
<div><p>The system performs special formatting of the job start and job
|
||
|
|
completion messages.</p>
|
||
|
|
<p>For message CPF1124 (job start) and message CPF1164 (job completion), the
|
||
|
|
message data always begins in position 11 of the third record.</p>
|
||
|
|
<p>Job accounting provides more information than CPF1124 and CPF1164. For
|
||
|
|
simple job accounting functions, use the CPF1164 message.</p>
|
||
|
|
<p>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. The format of this performance information is as follows.</p>
|
||
|
|
<p>The performance information is passed as a variable length replacement
|
||
|
|
text value. This means that the data is in a structure with the first entry
|
||
|
|
being the length of the data. The size of the length field is not included
|
||
|
|
in the length. The first data fields in the structure are the times and dates
|
||
|
|
that the job entered the system and when the first routing step for the job
|
||
|
|
was started. The times are in the format 'hh:mm:ss'. The separators are always
|
||
|
|
colons. The dates are in the format defined in the system value QDATFMT and
|
||
|
|
the separators are in the system value QDATSEP. The time and date the job
|
||
|
|
entered the system precede the job start time and date in the structure.</p>
|
||
|
|
<p>The time and date the job entered the system are when the system becomes
|
||
|
|
aware of a job to be initiated (a job structure is set aside for the job).
|
||
|
|
For an interactive job, the job entry time is the time the password is recognized
|
||
|
|
by the system. For a batch job, it is the time the <span class="cmdname">Batch Job (BCHJOB)</span> or <span class="cmdname">Submit
|
||
|
|
Job (SBMJOB)</span> command is processed. For a monitor job, reader or
|
||
|
|
writer, it is the time the corresponding start command is processed, and for
|
||
|
|
autostart jobs it is during the start of the subsystem.</p>
|
||
|
|
<p>Following the times and dates are the total response time and the number
|
||
|
|
of transactions. The total response time is in seconds and contains the accumulated
|
||
|
|
value of all the intervals the job was processing between pressing the Enter
|
||
|
|
key at the workstation and when the next display is shown. This information
|
||
|
|
is similar to that shown on the WRKACTJOB display. This field is only meaningful
|
||
|
|
for interactive jobs.</p>
|
||
|
|
<p>It is also possible in the case of a system failure or abnormal job end
|
||
|
|
that the last transaction will not be included in the total. The job end
|
||
|
|
code in this case would be a 40 or greater. The transaction count is also
|
||
|
|
only meaningful for interactive jobs other than the console job and is the
|
||
|
|
number of response time intervals counted by the system during the job.</p>
|
||
|
|
<p>The number of synchronous auxiliary I/O operations follows the number of
|
||
|
|
transactions. This is the same as the AUXIO field that appears on the WRKACTJOB
|
||
|
|
display except that this value is the total for the job. If the job ends
|
||
|
|
with a end code of 70, this value may not contain the count for the final
|
||
|
|
routing step. Additionally, if a job exists across an IPL (using a <span class="cmdname">Transfer
|
||
|
|
Batch Job (TFRBCHJOB)</span> command) it is ended before becoming active
|
||
|
|
following an IPL, the value is 0.</p>
|
||
|
|
<p>The final field in the performance statistics is the job type. Values for
|
||
|
|
this field are: </p>
|
||
|
|
<dl><dt class="dlterm">A</dt>
|
||
|
|
<dd>Automatically started job</dd>
|
||
|
|
<dt class="dlterm">B</dt>
|
||
|
|
<dd>Batch job</dd>
|
||
|
|
<dt class="dlterm">I</dt>
|
||
|
|
<dd>Interactive job</dd>
|
||
|
|
<dt class="dlterm">M</dt>
|
||
|
|
<dd>Subsystem monitor</dd>
|
||
|
|
<dt class="dlterm">R</dt>
|
||
|
|
<dd>Spooling reader</dd>
|
||
|
|
<dt class="dlterm">S</dt>
|
||
|
|
<dd>System job</dd>
|
||
|
|
<dt class="dlterm">W</dt>
|
||
|
|
<dd>Spooling writer</dd>
|
||
|
|
<dt class="dlterm">X</dt>
|
||
|
|
<dd>Start job</dd>
|
||
|
|
</dl>
|
||
|
|
<p>For messages in which the message data begins in a variable position, you
|
||
|
|
can access the message data by doing the following:</p>
|
||
|
|
<ul><li>Determine the length of the variables in the message. For example, assume
|
||
|
|
that a message uses the following five variables: <pre>Job name *CHAR 10
|
||
|
|
User name *CHAR 10
|
||
|
|
Job number *CHAR 6
|
||
|
|
Time *CHAR 8
|
||
|
|
Date *CHAR 8</pre>
|
||
|
|
<p>These variables are fixed in the first 42 positions of the
|
||
|
|
message data.</p>
|
||
|
|
</li>
|
||
|
|
<li>To find the location of the message data, consider that: <ul><li>The message always begins in position 11 of the second record.</li>
|
||
|
|
<li>The length of the message is stored in a 2-position field beginning at
|
||
|
|
position 111 of the first record. This length is stored in a binary value
|
||
|
|
so if the message length is 60, the field contains hex <samp class="codeph">003C</samp>.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Then, by using the length of the message and the start position of
|
||
|
|
the message, you can determine the location of the message data.</p>
|
||
|
|
</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="systl.htm" title="The history log (QHST) consists of a message queue and a physical file known as a log-version.">QHST history log</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|