87 lines
5.9 KiB
HTML
87 lines
5.9 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="Performance information and QHST" />
|
||
|
|
<meta name="abstract" content="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." />
|
||
|
|
<meta name="description" content="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." />
|
||
|
|
<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="rzaksperformanceinfoqhist" />
|
||
|
|
<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>Performance information and QHST</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaksperformanceinfoqhist"><a name="rzaksperformanceinfoqhist"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Performance information and QHST</h1>
|
||
|
|
<div><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. </p>
|
||
|
|
<p>The performance information is passed as a variable length replacement
|
||
|
|
text value. This means that the data is in a structure within the first entry
|
||
|
|
being the length of the data. The size of the length field is not included
|
||
|
|
in the length.</p>
|
||
|
|
<p><strong>Time and Date:</strong> 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 time
|
||
|
|
separators in this example are colons. This separator is determined by the
|
||
|
|
value specified in the Date and time (QTIMSEP) system value. The dates are
|
||
|
|
in the format defined in the Date and time (QDATFMT) system value and the
|
||
|
|
separators are in the Date and time (QDATSEP) system value. The time and date
|
||
|
|
the job entered the system precede the job start time and date in the structure.
|
||
|
|
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 Batch Job (<span class="cmdname">BCHJOB</span>)
|
||
|
|
or Submit Job (<span class="cmdname">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><strong>Total Response Time and Number of Transactions:</strong> 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 Work with Active Job (<span class="cmdname">WRKACTJOB</span>) 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>
|
||
|
|
<div class="p"><strong>Number of Synchronous Auxiliary I/O Operations: </strong>The number of synchronous
|
||
|
|
auxiliary I/O operations follows the number of transactions. For a job with
|
||
|
|
multiple threads, this value includes only synchronous auxiliary I/O operations
|
||
|
|
from the initial thread. This is the same as the AUXIO field that appears
|
||
|
|
on the <span class="cmdname">WRKACTJOB</span> display except for the following difference:<ul><li>The <span class="cmdname">WRKACTJOB</span> display shows the value for the initial
|
||
|
|
thread of the current routing step.</li>
|
||
|
|
<li>The QHST message contains the cumulative total for the initial thread
|
||
|
|
of each routing step in the job.</li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>If the job ends with an 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 Transfer Batch Job (<span class="cmdname">TFRBCHJOB</span>)
|
||
|
|
command) it is ended before becoming active following an IPL, the value is
|
||
|
|
0.</p>
|
||
|
|
</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>
|