friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0332907f0f
ibm-information-center/dist/eclipse/plugins/i5OS.ic.apis_5.4.0.1/WMAttrDesc.htm

4362 lines
144 KiB
HTML
Raw Normal View History

Add readme and dist folders
2024-04-02 14:02:31 +00:00
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Copyright" content="Copyright (c) 2006 by IBM Corporation">
<title>Work Management API Attribute Descriptions (WMAttrDesc)</title>
<!-- 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. -->
<!-- Begin Header Records ========================================= -->
<!-- WM SCRIPT A converted by B2H R4.1 (346) (CMS) by V2KEA304 -->
<!-- at RCHVMW2 on 17 Feb 1999 at 11:05:09 -->
<!-- File cleanup completed Jan 2002 by v2cdijab -->
<!-- End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<!-- Java sync-link -->
<script type="text/javascript" language="Javascript" src="../rzahg/synch.js">
</script>
<a name="Top_Of_Page"></a>
<h2>Work Management API Attribute Descriptions</h2>
<p>The purpose of this document is to provide one place that describes all the
Job and Thread attributes that are used in all the Work Management APIs. The
list of attributes encompasses the following APIs:</p>
<dl>
<dt>Retrieve Job Information (QUSRJOBI)</dt>
<dt>List Job (QUSLJOB)</dt>
<dt>Retrieve Current Attribute (QWCRTVCA)</dt>
<dt>Open List of Jobs (QGYOLJOB)</dt>
<dt>Retrieve Thread Attribute (QWTRTVTA)</dt>
<dt>Open List of Threads (QWCOLTHD)</dt>
</dl>
<br>
<h3><a name="HDRJOBRDE">Attributes</a></h3>
<p>The following are the list of attributes that have keys associated with
them.</p>
<table border>
<tr>
<th align="left" valign="top">Key</th>
<th align="left" valign="top">Type</th>
<th align="left" valign="top">Description</th>
</tr>
<tr>
<td align="left" valign="top" width="15%">0101</td>
<td align="left" valign="top" width="25%">CHAR(4)</td>
<td align="left" valign="top" width="60%">Active job status</td>
</tr>
<tr>
<td align="left" valign="top">0102</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Allow multiple threads</td>
</tr>
<tr>
<td align="left" valign="top">0103</td>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Active job status for jobs ending</td>
</tr>
<tr>
<td align="left" valign="top">0104</td>
<td align="left" valign="top">See APIs for details</td>
<td align="left" valign="top">ASP group information</td>
</tr>
<tr>
<td align="left" valign="top">0201</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Break message handling</td>
</tr>
<tr>
<td align="left" valign="top">0301</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Cancel key</td>
</tr>
<tr>
<td align="left" valign="top">0302</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Coded character set ID</td>
</tr>
<tr>
<td align="left" valign="top">0303</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Country or region ID</td>
</tr>
<tr>
<td align="left" valign="top">0304</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Processing unit time used, if less than
2,147,483,647 milliseconds</td>
</tr>
<tr>
<td align="left" valign="top">0305</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Current user profile</td>
</tr>
<tr>
<td align="left" valign="top">0306</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Completion status</td>
</tr>
<tr>
<td align="left" valign="top">0307</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Current system pool identifier</td>
</tr>
<tr>
<td align="left" valign="top">0310</td>
<td align="left" valign="top">See APIs for details</td>
<td align="left" valign="top">Current library</td>
</tr>
<tr>
<td align="left" valign="top">0311</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Character identifier control</td>
</tr>
<tr>
<td align="left" valign="top">0312</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Processing unit time used - total for the
job</td>
</tr>
<tr>
<td align="left" valign="top">0313</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Processing unit time used for database - total
for the job</td>
</tr>
<tr>
<td align="left" valign="top">0314</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Processing unit used - percent used during the
elapsed time (job)</td>
</tr>
<tr>
<td align="left" valign="top">0315</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Processing unit used - time during the elapsed
time (job)</td>
</tr>
<tr>
<td align="left" valign="top">0316</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Processing unit used for database - percent used
during the elapsed time (job)</td>
</tr>
<tr>
<td align="left" valign="top">0317</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Processing unit used for database - time during
the elapsed time (job)</td>
</tr>
<tr>
<td align="left" valign="top">0318</td>
<td align="left" valign="top">CHAR(15)</td>
<td align="left" valign="top">Client IP address - IPv4</td>
</tr>
<tr>
<td align="left" valign="top">0319</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Processing unit time used - total for the
thread</td>
</tr>
<tr>
<td align="left" valign="top">0320</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Processing unit time used for database - total
for the thread</td>
</tr>
<tr>
<td align="left" valign="top">0321</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Processing unit used - percent during the elapsed
time (thread)</td>
</tr>
<tr>
<td align="left" valign="top">0322</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Processing unit used - time during the elapsed
time (thread)</td>
</tr>
<tr>
<td align="left" valign="top">0323</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Processing unit used for database - percent used
during the elapsed time (thread)</td>
</tr>
<tr>
<td align="left" valign="top">0324</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Processing unit used for database - time during
the elapsed time (thread)</td>
</tr>
<tr>
<td align="left" valign="top">0326</td>
<td align="left" valign="top">CHAR(45)</td>
<td align="left" valign="top">Client IP address - IPv4 or IPv6</td>
</tr>
<tr>
<td align="left" valign="top">0401</td>
<td align="left" valign="top">CHAR(13)</td>
<td align="left" valign="top">Date and time job became active</td>
</tr>
<tr>
<td align="left" valign="top">0402</td>
<td align="left" valign="top">CHAR(13)</td>
<td align="left" valign="top">Date and time job entered system</td>
</tr>
<tr>
<td align="left" valign="top">0403</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Date and time job is scheduled to run</td>
</tr>
<tr>
<td align="left" valign="top">0404</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Date and time job was put on this job queue</td>
</tr>
<tr>
<td align="left" valign="top">0405</td>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Date format</td>
</tr>
<tr>
<td align="left" valign="top">0406</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Date separator</td>
</tr>
<tr>
<td align="left" valign="top">0407</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">DBCS-capable</td>
</tr>
<tr>
<td align="left" valign="top">0408</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">DDM conversation handling</td>
</tr>
<tr>
<td align="left" valign="top">0409</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Default wait</td>
</tr>
<tr>
<td align="left" valign="top">0410</td>
<td align="left" valign="top">CHAR(13)</td>
<td align="left" valign="top">Device recovery action</td>
</tr>
<tr>
<td align="left" valign="top">0411</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Device name</td>
</tr>
<tr>
<td align="left" valign="top">0412</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Default coded character set identifier</td>
</tr>
<tr>
<td align="left" valign="top">0413</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Decimal format</td>
</tr>
<tr>
<td align="left" valign="top">0414</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Disk I/O count during the elapsed time (job)</td>
</tr>
<tr>
<td align="left" valign="top">0415</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Disk I/O count - total for the job</td>
</tr>
<tr>
<td align="left" valign="top">0416</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Disk I/O count during the elapsed time -
asynchronous I/O (job)</td>
</tr>
<tr>
<td align="left" valign="top">0417</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Disk I/O count during the elapsed time -
synchronous I/O (job)</td>
</tr>
<tr>
<td align="left" valign="top">0418</td>
<td align="left" valign="top">CHAR(13)</td>
<td align="left" valign="top">Date and time job ended</td>
</tr>
<tr>
<td align="left" valign="top">0419</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Disk I/O count during the elapsed time
(thread)</td>
</tr>
<tr>
<td align="left" valign="top">0420</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Disk I/O count - total for the thread</td>
</tr>
<tr>
<td align="left" valign="top">0421</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Disk I/O count during the elapsed time -
asynchronous I/O (thread)</td>
</tr>
<tr>
<td align="left" valign="top">0422</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Disk I/O count during the elapsed time -
synchronous I/O (thread)</td>
</tr>
<tr>
<td align="left" valign="top">0501</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">End severity</td>
</tr>
<tr>
<td align="left" valign="top">0502</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">End status</td>
</tr>
<tr>
<td align="left" valign="top">0503</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Exit key</td>
</tr>
<tr>
<td align="left" valign="top">
0504</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Extended object attribute of entity thread is
waiting on</td>
</tr>
<tr>
<td align="left" valign="top">0601</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Function name</td>
</tr>
<tr>
<td align="left" valign="top">0602</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Function type</td>
</tr>
<tr>
<td align="left" valign="top">0701</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Signed-on job</td>
</tr>
<tr>
<td align="left" valign="top">0702</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Group profile name</td>
</tr>
<tr>
<td align="left" valign="top">0703</td>
<td align="left" valign="top">CHAR(150)</td>
<td align="left" valign="top">Group profile name - supplemental</td>
</tr>
<tr>
<td align="left" valign="top">0901</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Inquiry message reply</td>
</tr>
<tr>
<td align="left" valign="top">0902</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Internal job identifier</td>
</tr>
<tr>
<td align="left" valign="top">0903</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Initial thread</td>
</tr>
<tr>
<td align="left" valign="top">0904</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Interactive response time - total during the
elapsed time</td>
</tr>
<tr>
<td align="left" valign="top">0905</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Interactive transactions - count during the
elapsed time</td>
</tr>
<tr>
<td align="left" valign="top">1001</td>
<td align="left" valign="top">CHAR(15)</td>
<td align="left" valign="top">Job accounting code</td>
</tr>
<tr>
<td align="left" valign="top">1002</td>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Job date</td>
</tr>
<tr>
<td align="left" valign="top">1003</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Job description name - qualified</td>
</tr>
<tr>
<td align="left" valign="top">1004</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Job queue name - qualified</td>
</tr>
<tr>
<td align="left" valign="top">1005</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Job queue priority</td>
</tr>
<tr>
<td align="left" valign="top">1006</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Job switches</td>
</tr>
<tr>
<td align="left" valign="top">1007</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Job message queue full action</td>
</tr>
<tr>
<td align="left" valign="top">1008</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Job message queue maximum size</td>
</tr>
<tr>
<td align="left" valign="top">1009</td>
<td align="left" valign="top">CHAR(26)</td>
<td align="left" valign="top">Job name</td>
</tr>
<tr>
<td align="left" valign="top">1010</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Job type</td>
</tr>
<tr>
<td align="left" valign="top">1011</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Job subtype</td>
</tr>
<tr>
<td align="left" valign="top">1012</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Job user identity</td>
</tr>
<tr>
<td align="left" valign="top">1013</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Job user identity setting</td>
</tr>
<tr>
<td align="left" valign="top">1014</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Job end reason</td>
</tr>
<tr>
<td align="left" valign="top">1015</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Job log pending</td>
</tr>
<tr>
<td align="left" valign="top">1016</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Job type - enhanced</td>
</tr>
<tr>
<td align="left" valign="top">1017</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Job local time</td>
</tr>
<tr>
<td align="left" valign="top">
<img src="delta.gif" alt="Start of change">1018</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Job log output
<img src="deltaend.gif" alt="End of change"></td>
</tr>
<tr>
<td align="left" valign="top">1201</td>
<td align="left" valign="top">CHAR(3)</td>
<td align="left" valign="top">Language ID</td>
</tr>
<tr>
<td align="left" valign="top">1202</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Logging level</td>
</tr>
<tr>
<td align="left" valign="top">1203</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Logging of CL programs</td>
</tr>
<tr>
<td align="left" valign="top">1204</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Logging severity</td>
</tr>
<tr>
<td align="left" valign="top">1205</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Logging text</td>
</tr>
<tr>
<td align="left" valign="top">1206</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Library of entity thread is waiting on</td>
</tr>
<tr>
<td align="left" valign="top">1301</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Mode name</td>
</tr>
<tr>
<td align="left" valign="top">1302</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Maximum processing unit time</td>
</tr>
<tr>
<td align="left" valign="top">1303</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Maximum temporary storage in kilobytes</td>
</tr>
<tr>
<td align="left" valign="top">1304</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Maximum threads</td>
</tr>
<tr>
<td align="left" valign="top">1305</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Maximum temporary storage in megabytes</td>
</tr>
<tr>
<td align="left" valign="top">1306</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Memory pool name</td>
</tr>
<tr>
<td align="left" valign="top">1307</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Message reply</td>
</tr>
<tr>
<td align="left" valign="top">1401</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of auxiliary I/O requests, if less than
2,147,483,647</td>
</tr>
<tr>
<td align="left" valign="top">1402</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of interactive transactions</td>
</tr>
<tr>
<td align="left" valign="top">1403</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of database lock waits</td>
</tr>
<tr>
<td align="left" valign="top">1404</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of internal machine lock waits</td>
</tr>
<tr>
<td align="left" valign="top">1405</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of nondatabase lock waits</td>
</tr>
<tr>
<td align="left" valign="top">1406</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Number of auxiliary I/O requests</td>
</tr>
<tr>
<td align="left" valign="top">1407</td>
<td align="left" valign="top">CHAR(30)</td>
<td align="left" valign="top">Name of entity thread is waiting on</td>
</tr>
<tr>
<td align="left" valign="top">1501</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Output queue name - qualified</td>
</tr>
<tr>
<td align="left" valign="top">1502</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Output queue priority</td>
</tr>
<tr>
<td align="left" valign="top">1503</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Object type of entity thread is waiting on</td>
</tr>
<tr>
<td align="left" valign="top">1601</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Print key format</td>
</tr>
<tr>
<td align="left" valign="top">1602</td>
<td align="left" valign="top">CHAR(30)</td>
<td align="left" valign="top">Print text</td>
</tr>
<tr>
<td align="left" valign="top">1603</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Printer device name</td>
</tr>
<tr>
<td align="left" valign="top">1604</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Purge</td>
</tr>
<tr>
<td align="left" valign="top">1605</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Product return code</td>
</tr>
<tr>
<td align="left" valign="top">1606</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Program return code</td>
</tr>
<tr>
<td align="left" valign="top">1607</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Pending signal set</td>
</tr>
<tr>
<td align="left" valign="top">1608</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Process ID number</td>
</tr>
<tr>
<td align="left" valign="top">1609</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Page fault count during the elapsed time
(job)</td>
</tr>
<tr>
<td align="left" valign="top">1610</td>
<td align="left" valign="top">BINARY(8), UNSIGNED</td>
<td align="left" valign="top">Page fault count during the elapsed time
(thread)</td>
</tr>
<tr>
<td align="left" valign="top">1660</td>
<td align="left" valign="top">See APIs for details</td>
<td align="left" valign="top">Product libraries</td>
</tr>
<tr>
<td align="left" valign="top">1801</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Response time total</td>
</tr>
<tr>
<td align="left" valign="top">1802</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Run priority (job)</td>
</tr>
<tr>
<td align="left" valign="top">1803</td>
<td align="left" valign="top">CHAR(80)</td>
<td align="left" valign="top">Routing data</td>
</tr>
<tr>
<td align="left" valign="top">1804</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Run priority (thread)</td>
</tr>
<tr>
<td align="left" valign="top">1805</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Resources affinity group</td>
</tr>
<tr>
<td align="left" valign="top">1901</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Sort sequence table - qualified</td>
</tr>
<tr>
<td align="left" valign="top">1902</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Status message handling</td>
</tr>
<tr>
<td align="left" valign="top">1903</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Status of job on the job queue</td>
</tr>
<tr>
<td align="left" valign="top">1904</td>
<td align="left" valign="top">CHAR(26)</td>
<td align="left" valign="top">Submitter's job name - qualified</td>
</tr>
<tr>
<td align="left" valign="top">1905</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Submitter's message queue name - qualified</td>
</tr>
<tr>
<td align="left" valign="top">1906</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Subsystem description name - qualified</td>
</tr>
<tr>
<td align="left" valign="top">1907</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">System pool identifier</td>
</tr>
<tr>
<td align="left" valign="top">1908</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Special environment</td>
</tr>
<tr>
<td align="left" valign="top">1909</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Signal blocking mask</td>
</tr>
<tr>
<td align="left" valign="top">1910</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Signal status</td>
</tr>
<tr>
<td align="left" valign="top">1911</td>
<td align="left" valign="top">CHAR(30)</td>
<td align="left" valign="top">Server type</td>
</tr>
<tr>
<td align="left" valign="top">1980</td>
<td align="left" valign="top">See APIs for details</td>
<td align="left" valign="top">System library list</td>
</tr>
<tr>
<td align="left" valign="top">1982</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Spooled file action</td>
</tr>
<tr>
<td align="left" valign="top">2001</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Time separator</td>
</tr>
<tr>
<td align="left" valign="top">2002</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Time slice</td>
</tr>
<tr>
<td align="left" valign="top">2003</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Time-slice end pool</td>
</tr>
<tr>
<td align="left" valign="top">2004</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Temporary storage used in kilobytes</td>
</tr>
<tr>
<td align="left" valign="top">2005</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Time spent on database lock waits</td>
</tr>
<tr>
<td align="left" valign="top">2006</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Time spent on internal machine lock waits</td>
</tr>
<tr>
<td align="left" valign="top">2007</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Time spent on nondatabase lock waits</td>
</tr>
<tr>
<td align="left" valign="top">2008</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Thread count</td>
</tr>
<tr>
<td align="left" valign="top">2009</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Temporary storage used in megabytes</td>
</tr>
<tr>
<td align="left" valign="top">2010</td>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Thread status</td>
</tr>
<tr>
<td align="left" valign="top">2011</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Thread type</td>
</tr>
<tr>
<td align="left" valign="top">2012</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Thread hold count</td>
</tr>
<tr>
<td align="left" valign="top">2013</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Thread resources affinity</td>
</tr>
<tr>
<td align="left" valign="top">2015</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Type of entity thread is waiting on</td>
</tr>
<tr>
<td align="left" valign="top">2020</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Time zone current abbreviated name</td>
</tr>
<tr>
<td align="left" valign="top">2021</td>
<td align="left" valign="top">CHAR(50)</td>
<td align="left" valign="top">Time zone current full name</td>
</tr>
<tr>
<td align="left" valign="top">2022</td>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Time zone current message identifier</td>
</tr>
<tr>
<td align="left" valign="top">2023</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Time zone current offset</td>
</tr>
<tr>
<td align="left" valign="top">2024</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Time zone description name</td>
</tr>
<tr>
<td align="left" valign="top">2025</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Time zone message file name - qualified</td>
</tr>
<tr>
<td align="left" valign="top">2026</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Time zone Daylight Saving Time indicator</td>
</tr>
<tr>
<td align="left" valign="top">2101</td>
<td align="left" valign="top">CHAR(24)</td>
<td align="left" valign="top">Unit of work ID</td>
</tr>
<tr>
<td align="left" valign="top">2102</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">User return code</td>
</tr>
<tr>
<td align="left" valign="top">2110</td>
<td align="left" valign="top">See APIs for details</td>
<td align="left" valign="top">User library list</td>
</tr>
<tr>
<td align="left" valign="top">2702</td>
<td align="left" valign="top">See APIs for details</td>
<td align="left" valign="top">All portions of the library list for format
RTVC0200</td>
</tr>
<tr>
<td align="left" valign="top">2703</td>
<td align="left" valign="top">See APIs for details</td>
<td align="left" valign="top">All portions of the library list for format
RTVT0200</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRJOBRDE">Field Descriptions</a></h3>
<p>The following section describes the fields returned in further detail. For
details on the thread safety of a particular attribute see the thread safety
section in the API being used. The fields are listed in alphabetical order.</p>
<p><strong>Active job status.</strong> The active status of the initial thread
of the job. Only one status is returned. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top" nowrap><em>no status</em></td>
<td align="left" valign="top">A blank status field represents a job that is in
transition or is not active.</td>
</tr>
<tr>
<td align="left" valign="top"><em>BSCA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for the
completion of an I/O operation to a binary synchronous device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>BSCW</em></td>
<td align="left" valign="top">Waiting for the completion of an I/O operation to
a binary synchronous device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>CMNA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for the
completion of an I/O operation to a communications device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>CMNW</em></td>
<td align="left" valign="top">Waiting for the completion of an I/O operation to
a communications device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>CMTW</em></td>
<td align="left" valign="top">Waiting for the completion of save-while-active
checkpoint processing in another job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>CNDW</em></td>
<td align="left" valign="top">Waiting on handle-based condition.</td>
</tr>
<tr>
<td align="left" valign="top"><em>CPCW</em></td>
<td align="left" valign="top">Jobs waiting for the completion of a CPI
Communications call.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DEQA</em></td>
<td align="left" valign="top">Waiting in the pool activity level for completion
of a dequeue operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DEQW</em></td>
<td align="left" valign="top">Waiting for completion of a dequeue operation.
For example, QSYSARB and subsystem monitors generally wait for work by waiting
for a dequeue operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DKTA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for the
completion of an I/O operation to a diskette unit.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DKTW</em></td>
<td align="left" valign="top">Waiting for the completion of an I/O operation to
a diskette unit.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DLYW</em></td>
<td align="left" valign="top">The Delay Job (DLYJOB) command delays the job for
a time interval to end, or for a specific delay end time. The function field
shows either the number of seconds the job is to delay (999999), or the
specific time when the job is to resume running.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DSC</em></td>
<td align="left" valign="top">Disconnected from a work station display.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DSPA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for input from a
work station display.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DSPW</em></td>
<td align="left" valign="top">Waiting for input from a work station
display.</td>
</tr>
<tr>
<td align="left" valign="top"><em>END</em></td>
<td align="left" valign="top">The job has been ended with the *IMMED option, or
its delay time has ended with the *CNTRLD option.</td>
</tr>
<tr>
<td align="left" valign="top"><em>EOFA</em></td>
<td align="left" valign="top">Waiting in the activity level to try a read
operation again on a database file after the end-of-file has been reached.</td>
</tr>
<tr>
<td align="left" valign="top"><em>EOFW</em></td>
<td align="left" valign="top">Waiting to try a read operation again on a
database file after the end-of-file has been reached.</td>
</tr>
<tr>
<td align="left" valign="top"><em>EOJ</em></td>
<td align="left" valign="top">Ending for a reason other than running the End
Job (ENDJOB) or End Subsystem (ENDSBS) command, such as SIGNOFF, End Group Job
(ENDGRPJOB), or an exception that is not handled.</td>
</tr>
<tr>
<td align="left" valign="top"><em>EVTW</em></td>
<td align="left" valign="top">Waiting for an event. For example, QLUS and SCPF
generally wait for work by waiting for an event.</td>
</tr>
<tr>
<td align="left" valign="top"><em>GRP</em></td>
<td align="left" valign="top">Suspended by a Transfer Group Job (TFRGRPJOB)
command.</td>
</tr>
<tr>
<td align="left" valign="top"><em>HLD</em></td>
<td align="left" valign="top">Held.</td>
</tr>
<tr>
<td align="left" valign="top"><em>HLDT</em></td>
<td align="left" valign="top">Held due to suspended thread.</td>
</tr>
<tr>
<td align="left" valign="top"><em>ICFA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for the
completion of an I/O operation to an intersystem communications function
file.</td>
</tr>
<tr>
<td align="left" valign="top"><em>ICFW</em></td>
<td align="left" valign="top">Waiting for the completion of an I/O operation to
an intersystem communications function file.</td>
</tr>
<tr>
<td align="left" valign="top"><em>INEL</em></td>
<td align="left" valign="top">Ineligible and not currently in the pool activity
level.</td>
</tr>
<tr>
<td align="left" valign="top"><em>JVAA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for a Java
program operation to complete.</td>
</tr>
<tr>
<td align="left" valign="top"><em>JVAW</em></td>
<td align="left" valign="top">Waiting for a Java program operation to
complete.</td>
</tr>
<tr>
<td align="left" valign="top"><em>LCKW</em></td>
<td align="left" valign="top">Waiting for a lock.</td>
</tr>
<tr>
<td align="left" valign="top"><em>LSPA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for a lock space
to be attached.</td>
</tr>
<tr>
<td align="left" valign="top"><em>LSPW</em></td>
<td align="left" valign="top">Waiting for a lock space to be attached.</td>
</tr>
<tr>
<td align="left" valign="top"><em>MLTA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for the
completion of an I/O operation to multiple files.</td>
</tr>
<tr>
<td align="left" valign="top"><em>MLTW</em></td>
<td align="left" valign="top">Waiting for the completion of an I/O operation to
multiple files.</td>
</tr>
<tr>
<td align="left" valign="top"><em>MSGW</em></td>
<td align="left" valign="top">Waiting for a message from a message queue.</td>
</tr>
<tr>
<td align="left" valign="top"><em>MTXW</em></td>
<td align="left" valign="top">Waiting for a mutex. A <strong>mutex</strong> is
a synchronization function that is used to allow multiple jobs or threads to
serialize their access to shared data.</td>
</tr>
<tr>
<td align="left" valign="top"><em>MXDW</em></td>
<td align="left" valign="top">Waiting for the completion of an I/O operation to
a mixed device file.</td>
</tr>
<tr>
<td align="left" valign="top"><em>OPTA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for the
completion of an I/O operation to an optical device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>OPTW</em></td>
<td align="left" valign="top">Waiting for the completion of an I/O operation to
an optical device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>OSIW</em></td>
<td align="left" valign="top">Jobs waiting for the completion of an OSI
Communications Subsystem for i5/OS operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>PRTA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for output to a
printer to complete.</td>
</tr>
<tr>
<td align="left" valign="top"><em>PRTW</em></td>
<td align="left" valign="top">Waiting for output to a printer to be
completed.</td>
</tr>
<tr>
<td align="left" valign="top"><em>PSRW</em></td>
<td align="left" valign="top">A prestart job waiting for a program start
request.</td>
</tr>
<tr>
<td align="left" valign="top"><em>RUN</em></td>
<td align="left" valign="top">Currently running in the pool activity
level.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SELW</em></td>
<td align="left" valign="top">Waiting for a selection to complete.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SEMW</em></td>
<td align="left" valign="top">Waiting for a semaphore. A <strong>
semaphore</strong> is a synchronization function that is used to allow multiple
jobs or threads to serialize their access to shared data.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SIGS</em></td>
<td align="left" valign="top">Stopped as the result of a signal</td>
</tr>
<tr>
<td align="left" valign="top"><em>SIGW</em></td>
<td align="left" valign="top">Waiting for a signal</td>
</tr>
<tr>
<td align="left" valign="top"><em>SRQ</em></td>
<td align="left" valign="top">The suspended half of a system request job
pair.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SVFA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for completion
of a save file operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SVFW</em></td>
<td align="left" valign="top">Waiting for completion of a save file
operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>TAPA</em></td>
<td align="left" valign="top">The job is waiting in a pool activity level for
completion of an I/O operation to a tape device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>TAPW</em></td>
<td align="left" valign="top">Waiting for completion of an I/O operation to a
tape device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>THDW</em></td>
<td align="left" valign="top">Waiting for another thread to complete an
operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>TIMA</em></td>
<td align="left" valign="top">Waiting in a pool activity level for a time
interval to end.</td>
</tr>
<tr>
<td align="left" valign="top"><em>TIMW</em></td>
<td align="left" valign="top">Waiting for a time interval to end.</td>
</tr>
</table>
<p><strong>Active job status for jobs ending.</strong> When the active job
status field is END or EOJ, this field contains the status of what the initial
thread is doing currently. This field is blank if the job is not ending
currently. See the active job status field for the list of possible values. For
example, the active job status would be EOJ, but the job could be waiting on a
lock that could keep the job from ending. The active job status for jobs ending
field would then be LCKW.</p>
<p><strong>Allow multiple threads.</strong> Whether this job allows multiple
user threads. This attribute does not prevent the operating system from
creating system threads in the job. Possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">This job does not allow multiple user
threads.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">This job allows multiple user threads.</td>
</tr>
</table>
<p><strong>All portions of the library list for format RTVT0200.</strong> All
portions of the library list will be returned.</p>
<p><strong>ASP group
information.</strong> The list of ASP group information for the current thread.
This information does not include the system ASP or the basic user ASPs.</p>
<p><strong>Break message handling.</strong> How this job handles break
messages. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NORMAL</em></td>
<td align="left" valign="top">The message queue status determines break message
handling.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*HOLD</em></td>
<td align="left" valign="top">The message queue holds break messages until a
user or program requests them. The work station user uses the Display Message
(DSPMSG) command to display the messages; a program must issue a Receive
Message (RCVMSG) command to receive a message and handle it.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*NOTIFY</em></td>
<td align="left" valign="top">The system notifies the job's message queue when
a message arrives. For interactive jobs, the audible alarm sounds if there is
one, and the message-waiting light comes on.</td>
</tr>
</table>
<p><strong>Cancel key.</strong> Whether the user pressed the cancel key.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The user did not press the cancel key.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The user did press the cancel key.
<p><strong>Note:</strong> The application or command that was called before
this API determines how the key is set.</p>
</td>
</tr>
</table>
<p><strong>CCSID of current SQL statement.</strong> The CCSID of the current
SQL statement string that is returned.</p>
<p><strong>Character identifier control.</strong> The character identifier
control for the job. This attribute controls the type of CCSID conversion that
occurs for display files, printer files, and panel groups. The *CHRIDCTL
special value must be specified on the CHRID command parameter on the create,
change, or override command for display files, printer files, and panel groups
before this attribute will be used.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*DEVD</em></td>
<td align="left" valign="top">The *DEVD special value performs the same
function as on the CHRID command parameter for display files, printer files,
and panel groups.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*JOBCCSID</em></td>
<td align="left" valign="top">The *JOBCCSID special value performs the same
function as on the CHRID command parameter for display files, printer files,
and panel groups.</td>
</tr>
</table>
<p><strong>Client IP address -
IPv4.</strong> The IPv4 address of the client for which this server is doing
work. An address is expressed in standard IPv4 dotted-decimal form
www.xxx.yyy.zzz (for example, 130.99.128.1). This field is not guaranteed to be
an IP address. This field will be blank if the address is not explicitly set to
a value by the Change Job (QWTCHGJB) API. For additional usage information of
the Client IP address, see the <a href="qwtrtvta.htm"> Retrieve Thread
Attribute</a> (QWTRTVTA) API.</p>
<p><strong>Client IP address -
IPv4 or IPv6.</strong> The IPv4 or IPv6 address of the client for which the
specified thread of this server most recently communicated with over sockets.
If this field is requested for a job, the value from the initial thread of the
job will be returned. If a sockets connection has not been established in the
initial thread, this field will be blank. An IPv4 address is expressed in
standard dotted-decimal form www.xxx.yyy.zzz (for example, 130.99.128.1). An
IPv6 address always has at least one occurrence of a colon (':') in the format.
Some possible IPv6 address formats would be: ::x (for example, ::1) or
::w.xxx.y.zzz (for example, ::9.130.4.169). For further IPv6 examples and
explanation, refer to the Usage Notes section in the <a href="inet_pton.htm">
Convert IPv4 and IPv6 Addresses Between Text and Binary Form (inet_pton)
API</a>. This field is implicitly set by the operating system.</p>
<p><strong>Coded character set ID.</strong> The coded character set identifier
used for this job.</p>
<p><strong>Completion status.</strong> The completion status of the job.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">The job has not completed.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The job completed normally.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The job completed abnormally.</td>
</tr>
</table>
<p><strong>Country or region ID.</strong> The country or region identifier
associated with this job.</p>
<p><strong>Current library.</strong> The name of the current library for the
thread. If no current library exists, the current library existence field is
zero and this field has no entry in the list. If this field is requested for a
job, the value for the initial thread of the job will be returned.</p>
<p><strong>Current library existence.</strong> The current library existence
field:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">No current library exists.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">A current library exists.</td>
</tr>
</table>
<p><strong>Current number of pending signals.</strong> The number of signals
that have been received for a signal monitor but whose signal action has not
been taken.</p>
<p><strong>Current SQL statement.</strong> The SQL statement that is running
currently or was last run in the job.</p>
<p><strong>Current system pool identifier.</strong> The identifier of the
system-related pool from which main storage is currently being allocated for
the job's initial thread. These identifiers are not the same as those specified
in the subsystem description, but are the same as the system pool identifiers
shown on the system status display. If a thread reaches its time-slice end, the
pool the thread is running in can be switched based on the job's time-slice end
pool value. The current system pool identifier returned will be the actual pool
in which the initial thread of the job is running.</p>
<p><strong>Current user profile.</strong> The user profile that the thread for
which information is being retrieved is currently running under. This name may
differ from the user portion of the job name. If this field is requested for a
job, the value for the initial thread of the job will be returned.</p>
<p><strong>Date and time job became active.</strong> When the job began to run
on the system. This is blank if the job did not become active. It is in the
format CYYMMDDHHMMSS, where:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>C</em></td>
<td align="left" valign="top">Century, where 0 indicates years 19<em>xx</em>
and 1 indicates years 20<em>xx</em>.</td>
</tr>
<tr>
<td align="left" valign="top"><em>YY</em></td>
<td align="left" valign="top">Year</td>
</tr>
<tr>
<td align="left" valign="top"><em>MM</em></td>
<td align="left" valign="top">Month</td>
</tr>
<tr>
<td align="left" valign="top"><em>DD</em></td>
<td align="left" valign="top">Day</td>
</tr>
<tr>
<td align="left" valign="top"><em>HH</em></td>
<td align="left" valign="top">Hour</td>
</tr>
<tr>
<td align="left" valign="top"><em>MM</em></td>
<td align="left" valign="top">Minute</td>
</tr>
<tr>
<td align="left" valign="top"><em>SS</em></td>
<td align="left" valign="top">Second</td>
</tr>
</table>
<p><strong>Date and time job ended.</strong> When the job completed running on
the system, in the CYYMMDDHHMMSS format described for the date and time job
became active field.</p>
<p><strong>Date and time job entered system.</strong> When the job was placed
on the system, in the CYYMMDDHHMMSS format described for the date and time job
became active field.</p>
<p><strong>Date and time job is scheduled to run.</strong> Date and time the
job is scheduled to become active. This field is returned as hexadecimal zeros
if the job is not a scheduled job. The format for this field is the system
time-stamp format.</p>
<p><strong>Date and time job was put on this job queue.</strong> This is the
date and time this job was put on this job queue. It is in system timestamp
format. This field will contain blanks if the job was not on a job queue.</p>
<p><strong>Date format.</strong> The format that the date is presented in. The
following values are possible:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*YMD</em></td>
<td align="left" valign="top">Year, month, and day format</td>
</tr>
<tr>
<td align="left" valign="top"><em>*MDY</em></td>
<td align="left" valign="top">Month, day, and year format</td>
</tr>
<tr>
<td align="left" valign="top"><em>*DMY</em></td>
<td align="left" valign="top">Day, month, and year format</td>
</tr>
<tr>
<td align="left" valign="top"><em>*JUL</em></td>
<td align="left" valign="top">Julian format (year and day)</td>
</tr>
</table>
<p><strong>Date separator.</strong> The value used to separate days, months,
and years when presenting a date. The following values are possible:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>'/'</em></td>
<td align="left" valign="top">A slash (/) is used for the date separator.</td>
</tr>
<tr>
<td align="left" valign="top"><em>'-'</em></td>
<td align="left" valign="top">A dash (-) is used for the date separator.</td>
</tr>
<tr>
<td align="left" valign="top"><em>'.'</em></td>
<td align="left" valign="top">A period (.) is used for the date separator.</td>
</tr>
<tr>
<td align="left" valign="top"><em>' '</em></td>
<td align="left" valign="top">A blank is used for the date separator.</td>
</tr>
<tr>
<td align="left" valign="top"><em>','</em></td>
<td align="left" valign="top">A comma (,) is used for the date separator.</td>
</tr>
</table>
<p><strong>DBCS-capable.</strong> Whether the job is DBCS-capable.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The job is not DBCS-capable.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The job is DBCS-capable.</td>
</tr>
</table>
<p><strong>DDM conversation handling.</strong> Specifies whether connections
using distributed data management (DDM) protocols remain active when they are
not being used. The connections include APPC conversations, active TCP/IP
connections or Opti-Connect connections. The DDM protocols are used in
Distributed Relational Database Architecture<sup>(TM)</sup> (DRDA<sup>(R)</sup>)
applications, DDM applications, or DB2 Multisystem applications.
The following values are possible:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*KEEP</em></td>
<td align="left" valign="top">The system keeps DDM connections active when
there are no users, except for the following:<br>
<ul>
<li>The routing step ends on the source system. The routing step ends when the
job ends or when the job is rerouted to another routing step.</li>
<li>The Reclaim Distributed Data Management Conversation (RCLDDMCNV) command or
the Reclaim Resources (RCLRSC) command runs.</li>
<li>A communications failure or an internal failure occurs.</li>
<li>A DRDA connection to an application server not running on the system
ends.</li>
</ul>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>*DROP</em></td>
<td align="left" valign="top">The system ends a DDM connection when there are
no users. Examples include when an application closes a DDM file, or when a
DRDA application runs a SQL DISCONNECT statement.</td>
</tr>
</table>
<p><strong>Decimal format.</strong> The decimal format used for this job. The
following values are possible:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Uses a period for a decimal point, a comma for a
3-digit grouping character, and zero-suppress to the left of the decimal
point.</td>
</tr>
<tr>
<td align="left" valign="top"><em>J</em></td>
<td align="left" valign="top">Uses a comma for a decimal point and a period for
a 3-digit grouping character. The zero-suppression character is in the second
position (rather than the first) to the left of the decimal notation. Balances
with zero values to the left of the comma are written with one leading zero
(0,04). The J entry also overrides any edit codes that might suppress the
leading zero.</td>
</tr>
<tr>
<td align="left" valign="top"><em>I</em></td>
<td align="left" valign="top">Uses a comma for a decimal point, a period for a
3-digit grouping character, and zero-suppress to the left of the decimal
point.</td>
</tr>
</table>
<p><strong>Default coded character set identifier.</strong> The default coded
character set identifier used for this job. This field contains zeros if the
job is not an active job.</p>
<p><strong>Default signal action.</strong> The action to be taken by a signal
when the signal action specifies that the signal should be handled using the
default signal action. Possible values are as follows:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">End the job</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Cancel the request</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Ignore the signal (discard)</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">Stop the job</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">Continue the job if stopped</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em></td>
<td align="left" valign="top">Signal exception</td>
</tr>
</table>
<p><strong>Default wait.</strong> The default maximum time (in seconds) that a
thread in the job waits for a system instruction, such as a LOCK machine
interface (MI) instruction, to acquire a resource. A value of -1 is returned if
the value is *NOMAX.</p>
<p><strong>Device name.</strong> The name of the device as identified to the
system. For an interactive job, the device where the job started; for all other
jobs types it will be blanks.</p>
<p><strong>Device recovery action.</strong> The action taken for interactive
jobs when an I/O error occurs for the job's requesting program device. The
possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*MSG</em></td>
<td align="left" valign="top">Signals the I/O error message to the application
and lets the application program perform error recovery.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*DSCMSG</em></td>
<td align="left" valign="top">Disconnects the job when an I/O error occurs.
When the job reconnects, the system sends an error message to the application
program, indicating the job has reconnected and that the work station device
has recovered.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*DSCENDRQS</em></td>
<td align="left" valign="top">Disconnects the job when an I/O error occurs.
When the job reconnects, the system sends the End Request (ENDRQS) command to
return control to the previous request level.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*ENDJOB</em></td>
<td align="left" valign="top">Ends the job when an I/O error occurs. A message
is sent to the job's log and to the history log (QHST) indicating the job ended
because of a device error.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*ENDJOBNOLIST</em></td>
<td align="left" valign="top">Ends the job when an I/O error occurs. There is
no job log produced for the job. The system sends a message to the QHST log
indicating the job ended because of a device error.</td>
</tr>
</table>
<p><strong>Disk I/O count during the elapsed time (job).</strong> The number of
disk I/O operations performed by the job during the elapsed time. This is the
sum of the asynchronous and synchronous disk I/O.</p>
<p><strong>Disk I/O count during the elapsed time (thread).</strong> The number
of disk I/O operations performed by the specified thread during the elapsed
time. This is the sum of the asynchronous and synchronous disk I/O.</p>
<p><strong>Disk I/O count during the elapsed time - asynchronous I/O
(job).</strong> The number of asynchronous (physical) disk I/O operations
performed by the job during the elapsed time. This value is the sum of the
asynchronous database and nondatabase reads and writes.</p>
<p><strong>Disk I/O count during the elapsed time - asynchronous I/O
(thread).</strong> The number of asynchronous (physical) disk I/O operations
performed by the specified thread during the elapsed time. This value is the
sum of the asynchronous database and nondatabase reads and writes.</p>
<p><strong>Disk I/O count during the elapsed time - synchronous I/O
(job).</strong> The number of synchronous (physical) disk I/O operations
performed by the job during the elapsed time. This value is the sum of the
synchronous database and nondatabase reads and writes.</p>
<p><strong>Disk I/O count during the elapsed time - synchronous I/O
(thread).</strong> The number of synchronous (physical) disk I/O operations
performed by the specified thread during the elapsed time. This value is the
sum of the synchronous database and nondatabase reads and writes.</p>
<p><strong>Disk I/O count - total for the job.</strong> The total number of
disk I/O operations performed by the job across all routing steps. This is the
sum of the asynchronous and synchronous disk I/O.</p>
<p><strong>Disk I/O count - total for the thread.</strong> The total number of
disk I/O operations performed by the specified thread. This is the sum of the
asynchronous and synchronous disk I/O.</p>
<p><strong>Elapsed time.</strong> The time, in milliseconds, that has elapsed
between the measurement start time and the current system time. This value is 0
the first time this API is called by this job. The measurement start is set the
first time this API is called and when the reset status statistics is set to
reset the elapsed time.</p>
<p><strong>End severity.</strong> The message severity level of escape messages
that can cause a batch job to end. The batch job ends when a request in the
batch input stream sends an escape message, whose severity is equal to or
greater than this value, to the request processing program.</p>
<p><strong>End status.</strong> Whether the system issued a controlled
cancelation. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The system, the subsystem in which the job is
running, or the job itself is canceled.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The system, subsystem, or job is not
cancelled.</td>
</tr>
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">The job is not running.</td>
</tr>
</table>
<p><strong>Exit key.</strong> Whether the user pressed the exit key.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The user did not press the exit key.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The user did press the exit key.
<p><strong>Note:</strong> The application or command that was called before
this API determines how the key is set.</p>
</td>
</tr>
</table>
<p><strong>Extended object
attribute of entity thread is waiting on.</strong> The extended attribute of
the object, such as a program or file type, that the thread is waiting on.
Extended attributes further describe the object. For example, an object type of
*PGM may have a value of RPG(RPG program) or CLP(CL program), and an object
type of *FILE may have a value of PF(physical file), LF(logical file),
DSPF(display file), SAVF(save file), and so on. This field may blank if there
is no extended attribute associated with the object type, or the type of entity
the thread is waiting on is not an i5/OS external object or an i5/OS external
object space location. If this field is requested for a job, the value for the
initial thread of the job will be returned.</p>
<p><strong>Function name.</strong>
Additional information (as described in the function type field) about the last high-level
function initiated by the initial thread.</p>
<p><strong>Function type.</strong>
This is the last high-level function initiated by the initial thread. This field may not
be cleared when a function is completed. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">The system is not doing a logged function.</td>
</tr>
<tr>
<td align="left" valign="top"><em>C</em></td>
<td align="left" valign="top">A command is running interactively, or it is in a batch input stream, or it was
requested from a system menu. Commands in CL programs or REXX procedures are not logged.
The function name field contains the name of the command and is only updated when
a command is processed.</td>
</tr>
<tr>
<td align="left" valign="top"><em>D</em></td>
<td align="left" valign="top">The initial thread of the job is processing a
Delay Job (DLYJOB) command. The function name contains the number of seconds
the job is delayed (up to 999999 seconds), or the time when the job is to
resume processing (HH:MM:SS), depending on how you specified the command.</td>
</tr>
<tr>
<td align="left" valign="top"><em>G</em></td>
<td align="left" valign="top">The Transfer Group Job (TFRGRPJOB) command
suspended the job. The function name field contains the group job name for that
job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>I</em></td>
<td align="left" valign="top">The initial thread of the job is rebuilding an
index (access path). The function name field contains the name of the logical
file whose index is rebuilt.</td>
</tr>
<tr>
<td align="left" valign="top"><em>J</em></td>
<td align="left" valign="top">The initial thread of the job is running a Java Virtual Machine (JVM). The
function name field contains the name of the java class.</td>
</tr>
<tr>
<td align="left" valign="top"><em>L</em></td>
<td align="left" valign="top">The system logs history information in a database
file. The function name field contains the name of the log (QHST is the only
log currently supported).</td>
</tr>
<tr>
<td align="left" valign="top"><em>M</em></td>
<td align="left" valign="top">The job is a multiple requester terminal (MRT)
job if the job type is BATCH and the subtype is MRT, or it is an interactive
job attached to an MRT job if the job type is interactive. See job type,
subtype, or field for how to determine what type of job this is.
<p>For MRT jobs, the function name field contains information in the following
format:</p>
<ul>
<li>CHAR(2): The number of requesters currently attached to the MRT job.</li>
<li>CHAR(1): The field is reserved for a / (slash).</li>
<li>CHAR(2): The maximum number (MRTMAX) of requesters.</li>
<li>CHAR(1): Reserved.</li>
<li>CHAR(3): The never-ending program (NEP) indicator. If an MRT is also an
NEP, the MRT stays active even if there are no requesters of the MRT. A value
of NEP indicates a never-ending program. A value of blanks indicates that it is
not a never-ending program.</li>
<li>CHAR(1): Reserved.</li>
</ul>
<p>For interactive jobs attached to an MRT, the function name field contains
the name of the MRT procedure.</p>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>N</em></td>
<td align="left" valign="top">The initial thread of the job is currently at a
system menu. The function name field contains the name of the menu.</td>
</tr>
<tr>
<td align="left" valign="top"><em>O</em></td>
<td align="left" valign="top">The job is a subsystem monitor that is performing
input/output (I/O) operations to a work station. The function name field
contains the name of the work station device to which the subsystem is
performing an input/output operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>P</em></td>
<td align="left" valign="top">The initial thread of the job is running a
program. The function name field contains the name of the program.</td>
</tr>
<tr>
<td align="left" valign="top"><em>R</em></td>
<td align="left" valign="top">The initial thread of the job is running a
procedure. The function name field contains the name of the procedure.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*</em></td>
<td align="left" valign="top">This does a special function. For this value, the
function name field contains one of the following values:<br>
<br>
<ul>
<li>ADLACTJOB: Auxiliary storage is being allocated for the number of active
jobs specified in the QADLACTJ system value. This may indicate that the system
value for the initial number of active jobs is too low.</li>
<li>ADLTOTJOB: Auxiliary storage is being allocated for the number of jobs
specified in the QADLTOTJ system value.</li>
<li>CMDENT: The Command Entry display is being used.</li>
<li>COMMIT: A commit operation is being performed.</li>
<li>DIRSHD: Directory shadowing.</li>
<li>DLTSPLF: The system is deleting a spooled file.</li>
<li>DUMP: A dump is in process.</li>
<li>JOBIDXRCY: A damaged job index is being recovered.</li>
<li>JOBLOG: The system is producing a job log.</li>
<li>PASSTHRU: The job is a pass-through job.</li>
<li>RCLSPLSTG: Empty spooled database members are being deleted.</li>
<li>ROLLBACK: A rollback operation is being performed.</li>
<li>SPLCLNUP: Spool cleanup is in process.</li>
</ul>
</td>
</tr>
</table>
<p><strong>Group profile name.</strong> The name of the group profile that is
associated with the initial thread. The user's group authority is used if no
specific authority is granted for the user. The value *NONE is returned if no
group profile name is found.</p>
<p><strong>Group profile name - supplemental.</strong> The name of the group
profile associated with the initial thread. The user's group authority is used
if no specific authority is granted for the user. Up to 15 supplemental group
profile names may be specified. Blanks are returned if no supplemental group
profile names are found.</p>
<p><strong>Initial thread.</strong> Whether this thread is the initial thread
of this job.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">This thread is not the initial thread.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">This thread is the initial thread.</td>
</tr>
</table>
<p><strong>Inquiry message reply.</strong> How the job answers inquiry
messages:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*RQD</em></td>
<td align="left" valign="top">The job requires an answer for any inquiry
messages that occur while this job is running.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*DFT</em></td>
<td align="left" valign="top">The system uses the default message reply to
answer any inquiry messages issued while this job is running. The default reply
is either defined in the message description or is the default system
reply.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*SYSRPYL</em></td>
<td align="left" valign="top">The system reply list is checked to see if there
is an entry for an inquiry message issued while this job is running. If a match
occurs, the system uses the reply value for that entry. If no entry exists for
that message, the system uses an inquiry message.</td>
</tr>
</table>
<p><strong>Interactive response time - total during the elapsed time.</strong>
The total interactive response time for the initial thread, in hundredth of
seconds, for the job during the elapsed time. This value does not include the
time used by the machine, by the attached input/output (I/O) hardware, and by
the transmission lines for sending and receiving data. This field is 0 for
noninteractive jobs.</p>
<p><strong>Interactive transactions - count during the elapsed time.</strong>
The number of user interactions, such as pressing the Enter key or a function
key, for the job during the elapsed time for the initial thread. This value is
returned for interactive jobs only.</p>
<p><strong>Internal job identifier.</strong> A value input to other APIs to
increase the speed of locating the job on the system. Only APIs described in
this manual use this identifier. The identifier is not valid following an
initial program load (IPL). If you attempt to use it after an IPL, an exception
occurs.</p>
<p><strong>Job accounting code.</strong> An identifier assigned to the job by
the system to collect resource use information for the job when job accounting
is active.</p>
<p><strong>Job date.</strong> This is the date to be used for the job. It is in
the format CYYMMDD where C is the century, YY is the year, MM is the month, and
DD is the day. A 0 for the century flag indicates years 19<em>xx</em> and a 1
indicates years 20<em>xx</em>. This value is for jobs whose status is *JOBQ or
*ACTIVE. For jobs with a status of *OUTQ, the value for this field is
blank.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">This job will use the system date.</td>
</tr>
</table>
<p><strong>Job description library name.</strong> The library containing the
job description.</p>
<p><strong>Job description name.</strong> A CHAR(10) representation of the set
of job-related attributes used for one or more jobs on the system. These
attributes determine how the job is run on the system. Multiple jobs can also
use the same job description.</p>
<p><strong>Job description name - qualified.</strong> A CHAR(20) representation
of the set of job-related attributes used for one or more jobs on the system.
These attributes determine how the job is run on the system. Multiple jobs can
also use the same job description. The format of the qualified name is a
10-character simple object name followed by a 10-character library name. The
data is left-justified and padded with blanks on the right.</p>
<p><strong>Job end reason.</strong> The most recent action that caused the job
to end. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Job not ending.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Job ending in normal manner.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Job ended while it was still on a job queue.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">System ended abnormally.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">Job ending normally after a controlled end was
requested.</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em></td>
<td align="left" valign="top">Job ending immediately.</td>
</tr>
<tr>
<td align="left" valign="top"><em>6</em></td>
<td align="left" valign="top">Job ending abnormally.</td>
</tr>
<tr>
<td align="left" valign="top"><em>7</em></td>
<td align="left" valign="top">Job ended due to the CPU limit being
exceeded.</td>
</tr>
<tr>
<td align="left" valign="top"><em>8</em></td>
<td align="left" valign="top">Job ended due to the storage limit being
exceeded.</td>
</tr>
<tr>
<td align="left" valign="top"><em>9</em></td>
<td align="left" valign="top">Job ended due to the message severity level being
exceeded.</td>
</tr>
<tr>
<td align="left" valign="top"><em>10</em></td>
<td align="left" valign="top">Job ended due to the disconnect time interval
being exceeded.</td>
</tr>
<tr>
<td align="left" valign="top"><em>11</em></td>
<td align="left" valign="top">Job ended due to the inactivity time interval
being exceeded.</td>
</tr>
<tr>
<td align="left" valign="top"><em>12</em></td>
<td align="left" valign="top">Job ended due to a device error.</td>
</tr>
<tr>
<td align="left" valign="top"><em>13</em></td>
<td align="left" valign="top">Job ended due to a signal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>14</em></td>
<td align="left" valign="top">Job ended due to an unhandled error.</td>
</tr>
</table>
<p><strong>Job local time.</strong> The current local time of the job expressed as an 8 byte time-of-day
timestamp. The time zone current offset for this job has been applied to this time value.
</p>
<p><img src="delta.gif" alt="Start of change">
<strong>Job log output.</strong> How the job log will be produced
when the job completes.
This does not affect job logs produced when
the message queue is full and
the job message queue full action specifies *PRTWRAP.
Messages in the job message queue are written to a spooled file,
from which the job log can be printed,
unless the Control Job Log Output (QMHCTLJL) API was used in the job
to specify that the messages in the job log
are to be written to a database file.
</p>
<p>The job log output value can be changed at any time
until the job log has been produced or removed.
To change the job log output value for a job,
use the Change Job (QWTCHGJB) API or
the Change Job (CHGJOB) command.
</p>
<p>The job log can be displayed at any time
until the job log has been produced or removed.
To display the job log, use the Display Job Log (DSPJOBLOG) command.
</p>
<p>The job log can be removed when the job has completed
and the job log has not yet been produced or removed.
To remove the job log,
use the Remove Pending Job Log (QWTRMVJL) API
or the End Job (ENDJOB) command.</p>
<p>The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*JOBLOGSVR</em></td>
<td align="left" valign="top">
The job log will be produced by a job log server.
For more information about job log servers,
refer to the Start Job Log Server (STRLOGSVR) command.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*JOBEND</em></td>
<td align="left" valign="top">
The job log will be produced by the job itself.
If the job cannot produce its own job log,
the job log will be produced by a job log server.
For example, a job does not produce its own job log
when the system is processing a Power Down System (PWRDWNSYS) command.
</td>
</tr>
<tr>
<td align="left" valign="top"><em>*PND</em></td>
<td align="left" valign="top">
The job log will not be produced.
The job log remains pending until removed.
<img src="deltaend.gif" alt="End of change"></td>
</tr>
</table>
<p><strong>Job log pending.</strong> Whether there is a job log
that has not yet been written.
<img src="delta.gif" alt="Start of change">
The writing of the job log may become pending
based on the value of the <em>job log output</em> job attribute
when the job completes its activity.
The job log may also become pending
if the job is ended due to a Power Down System (PWRDWNSYS) command,
if the system fails while the job is active,
or if errors prevent the job from writing its own job log.
<img src="deltaend.gif" alt="End of change">
The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Job log is not pending.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Job log is pending.</td>
</tr>
</table>
<p><strong>Job message queue full action.</strong> The action to take when the
message queue is full. The values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NOWRAP</em></td>
<td align="left" valign="top">When the job message queue is full, do not wrap.
This action causes the job to end.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*WRAP</em></td>
<td align="left" valign="top">When the job message queue is full, wrap to the
beginning and start filling again.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*PRTWRAP</em></td>
<td align="left" valign="top">When the job message queue is full, wrap the
message queue and print the messages that are being overlaid because of the
wrapping.</td>
</tr>
</table>
<p><strong>Job message queue maximum size.</strong> The maximum size (in
megabytes) that the job message queue can become. The range is 2 to 64.</p>
<p><strong>Job name.</strong> The name of the job as identified to the system.
For an interactive job, the system assigns the job the name of the work station
where the job started; for a batch job, you specify the name in the command
when you submit the job.</p>
<p><strong>Job number.</strong> The system-generated job number.</p>
<p><strong>Job queue library name.</strong> The name of the library where the
job queue is located.</p>
<p><strong>Job queue name.</strong> The CHAR(10) representation of the name of
the job queue that the job is currently on, or that the job was on if it is
currently active. This value is for jobs whose status is *JOBQ or *ACTIVE. For
jobs with a status of *OUTQ, the value for this field is blank.</p>
<p><strong>Job queue name - qualified.</strong> The CHAR(20) representation of
the name of the job queue that the job is currently on, or that the job was on
if it is currently active. This value is for jobs whose status is *JOBQ or
*ACTIVE. For jobs with a status of *OUTQ, the value for this field is blank.
The format of the qualified name is a 10-character simple object name followed
by a 10-character library name. The data is left-justified and padded with
blanks on the right.</p>
<p><strong>Job queue priority.</strong> The scheduling priority of the job
compared to other jobs on the same job queue. The highest priority is 0 and the
lowest is 9. This value is for jobs whose status is *JOBQ or *ACTIVE. For jobs
with a status of *OUTQ, the value for this field is blank.</p>
<p><strong>Job status.</strong> The status of the jobs. The special values
are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*ACTIVE</em></td>
<td align="left" valign="top">Active jobs. This includes group jobs, system
request jobs, and disconnected jobs.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*JOBQ</em></td>
<td align="left" valign="top">Jobs that are currently on job queues.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*OUTQ</em></td>
<td align="left" valign="top">Jobs that have completed running but still have
output on an output queue or the job's job log has not yet been written.</td>
</tr>
</table>
<p><strong>Job subtype.</strong> Additional information about the job type (if
any exists). The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">The job has no special subtype or is not a valid
job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>D</em></td>
<td align="left" valign="top">The job is an immediate job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>E</em></td>
<td align="left" valign="top">The job started with a procedure start
request.</td>
</tr>
<tr>
<td align="left" valign="top"><em>F</em></td>
<td align="left" valign="top">The job is an AS/400<sup>(R)</sup> Advanced 36<sup>(R)</sup>
machine server job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>J</em></td>
<td align="left" valign="top">The job is a prestart job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>P</em></td>
<td align="left" valign="top">The job is a print driver job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>T</em></td>
<td align="left" valign="top">The job is a System/36 multiple requester
terminal (MRT) job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>U</em></td>
<td align="left" valign="top">Alternate spool user.</td>
</tr>
</table>
<p><strong>Job switches.</strong> The current setting of the job switches used
by this job. This value is returned for all job types.</p>
<p><strong>Job type.</strong> The type of job. The possible values for this
field are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">The job is not a valid job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>A</em></td>
<td align="left" valign="top">The job is an autostart job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>B</em></td>
<td align="left" valign="top">The job is a batch job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>I</em></td>
<td align="left" valign="top">The job is an interactive job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>M</em></td>
<td align="left" valign="top">The job is a subsystem monitor job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>R</em></td>
<td align="left" valign="top">The job is a spooled reader job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>S</em></td>
<td align="left" valign="top">The job is a system job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>W</em></td>
<td align="left" valign="top">The job is a spooled writer job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>X</em></td>
<td align="left" valign="top">The job is the SCPF system job.</td>
</tr>
</table>
<p>Refer to <a href="#HDRWRKJOB">Comparing Job Type and Subtype with the Work
with Active Job Command</a> for information about how the job type field and
the job subtype field equate to the type field in the Work with Active Job
(WRKACTJOB) command.</p>
<p><strong>Job type - enhanced.</strong> The type of job. This field combines
the job type and job subtype fields. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"></td>
<td align="left" valign="top"></td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="left" valign="top"></td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="left" valign="top"></td>
</tr>
</table>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0110</em></td>
<td align="left" valign="top">Autostart job</td>
</tr>
<tr>
<td align="left" valign="top"><em>0210</em></td>
<td align="left" valign="top">Batch job</td>
</tr>
<tr>
<td align="left" valign="top"><em>0220</em></td>
<td align="left" valign="top">Batch immediate job</td>
</tr>
<tr>
<td align="left" valign="top"><em>0230</em></td>
<td align="left" valign="top">Batch - System/36 multiple requester terminal
(MRT) job</td>
</tr>
<tr>
<td align="left" valign="top"><em>0240</em></td>
<td align="left" valign="top">Batch - alternate spool user</td>
</tr>
<tr>
<td align="left" valign="top"><em>0310</em></td>
<td align="left" valign="top">Communications job - procedure start request
job</td>
</tr>
<tr>
<td align="left" valign="top"><em>0910</em></td>
<td align="left" valign="top">Interactive job</td>
</tr>
<tr>
<td align="left" valign="top"><em>0920</em></td>
<td align="left" valign="top">Interactive job - Part of group</td>
</tr>
<tr>
<td align="left" valign="top"><em>0930</em></td>
<td align="left" valign="top">Interactive job - Part of system request
pair</td>
</tr>
<tr>
<td align="left" valign="top"><em>0940</em></td>
<td align="left" valign="top">Interactive job - Part of system request pair and
part of a group</td>
</tr>
<tr>
<td align="left" valign="top"><em>1610</em></td>
<td align="left" valign="top">Prestart job</td>
</tr>
<tr>
<td align="left" valign="top"><em>1620</em></td>
<td align="left" valign="top">Prestart batch job</td>
</tr>
<tr>
<td align="left" valign="top"><em>1630</em></td>
<td align="left" valign="top">Prestart communications job</td>
</tr>
<tr>
<td align="left" valign="top"><em>1810</em></td>
<td align="left" valign="top">Reader job</td>
</tr>
<tr>
<td align="left" valign="top"><em>1910</em></td>
<td align="left" valign="top">Subsystem job</td>
</tr>
<tr>
<td align="left" valign="top"><em>1920</em></td>
<td align="left" valign="top">System job (all system jobs including SCPF)</td>
</tr>
<tr>
<td align="left" valign="top"><em>2310</em></td>
<td align="left" valign="top">Writer job (including both spool writers and
print drivers)</td>
</tr>
</table>
<p><strong>Job user identity.</strong> The user profile name by which the job
is known to other jobs on the system. The job user identity is used for
authorization checks when other jobs on the system attempt to operate against
the job. For more detail on how the job user identity is set and used, refer to
the Set Job User Identity (QWTSJUID) API in the Security part. For jobs that
are on a job queue or have completed running, the job user identity is same as
the user name from the qualified job name. This field will return blanks for
these jobs. A value of *N is returned if the job user identity is set, but the
user profile to which it is set no longer exists.</p>
<p><strong>Job user identity setting.</strong> An indicator of the method by
which the job user identity was set. Possible values are as follows:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>o</em></td>
<td align="left" valign="top">The job is currently running single threaded and
the job user identity is the name of the user profile under which the job is
currently running. This value is also returned for jobs that are on a job queue
or have completed running. This has the same meaning as a value of *DEFAULT on
the Display Job Status Attributes display.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The job user identity was explicitly set by an
application using one of the Set Job User Identity APIs, QWTSJUID or
QwtSetJuid(). The job may be running either single threaded or multithreaded.
This has the same meaning as a value of *APPLICATION on the Display Job Status
Attributes display.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The job is currently running multithreaded and
the job user identity was implicitly set by the system when the job became
multithreaded. It was set to the name of the user profile that the job was
running under when it became multithreaded. This has the same meaning as a
value of *SYSTEM on the Display Job Status Attributes display.</td>
</tr>
</table>
<p><strong>Language ID.</strong> The language identifier associated with this
job.</p>
<p><strong>Length of current SQL statement.</strong> The length of the current
SQL statement. Zero indicates that a current SQL statement could not be
returned. This can occur if an SQL statement has never been issued in the job,
if the job is ending, if the program or package that contained the SQL
statement no longer exists, or if the API is unable to access the SQL
statement.</p>
<p><strong>Library name.</strong> The name of the library object.</p>
<p><strong>Library of entity
thread is waiting on.</strong> The library name of the entity that the thread
is waiting on. This field may be blank if the type of entity the thread is
waiting on is not an i5/OS external object, a member object, an i5/OS
external object space location, a lock space, or if there is no library
associated with the particular type of entity. If the type of entity the thread
is waiting on is a member object, this field will return the library name of
the file that contains the member. If this field is requested for a job, the
value for the initial thread of the job will be returned.</p>
<p><strong>Library text description.</strong> The text description of the
library object. This field is blank if no text description is specified.</p>
<p><strong>Lock wait time -
time during the elapsed time.</strong> The amount of time (in milliseconds)
that the initial thread has to wait to obtain database, nondatabase, and
internal machine locks during the elapsed time.</p>
<p><strong>Logging level.</strong> What type of information is logged. The
possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">No messages are logged.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">All messages sent to the job's external message
queue with a severity greater than or equal to the message logging severity are
logged. This includes the indication of job start, job end and job completion
status.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The following information is logged:
<ul>
<li>Level 1 information</li>
<li>Request messages that result in a high-level message with a severity code
greater than or equal to the logging severity cause the request message and all
associated messages to be logged.
<p> <strong>Note:</strong> A high-level message is one that is sent to the
program message queue of the program that receives the request message. For
example, QCMD is an IBM-supplied request processing program that receives
request messages.</p>
</li>
</ul>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">The following information is logged:
<ul>
<li>Level 1 and 2 information</li>
<li>All request messages</li>
<li>Commands run by a CL program are logged if it is allowed by the logging of
CL programs job attribute and the log attribute of the CL program.</li>
</ul>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">The following information is logged:
<ul>
<li>All request messages and all messages with a severity greater than or equal
to the message logging severity, including trace messages.</li>
<li>Commands run by a CL program are logged if it is allowed by the logging of
CL programs job attribute and the log attribute of the CL program.</li>
</ul>
</td>
</tr>
</table>
<p><strong>Logging of CL programs.</strong> Whether or not commands are logged
for CL programs that are run. The possible values are *YES and *NO.</p>
<p><strong>Logging severity.</strong> The severity level that is used in
conjunction with the logging level to determine which error messages are logged
in the job log. The values range from 00 through 99.</p>
<p><strong>Logging text.</strong> The level of message text that is written in
the job log when a message is logged according to the logging level and logging
severity. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*MSG</em></td>
<td align="left" valign="top">Only the message text is written to the job
log.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*SECLVL</em></td>
<td align="left" valign="top">Both the message text and the message help (cause
and recovery) of the error message are written to the job log.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*NOLIST</em></td>
<td align="left" valign="top">If the job ends normally, no job log is produced.
If the job ends abnormally (the job end code is 20 or higher), a job log is
produced. The messages that appear in the job log contain both the message text
and the message help.</td>
</tr>
</table>
<p><strong>Maximum number of signals retained.</strong> The number of signals
that are kept for a signal monitor when the signal action is blocked.</p>
<p><strong>Maximum processing unit time.</strong> The maximum processing unit
time (in milliseconds) that the job can use. If the job consists of multiple
routing steps, this is the maximum processing unit time that the current
routing step can use. If the maximum time is exceeded, the job is ended. A
value of -1 is returned for *NOMAX. A zero is returned if the job is not
active.</p>
<p><strong>Maximum temporary storage in kilobytes.</strong> The maximum amount
of auxiliary storage (in kilobytes) that the job can use. If the job consists
of multiple routing steps, this is the maximum temporary storage that the
routing step can use. This temporary storage is used for storage required by
the program itself and by implicitly created internal system objects used to
support the routing step. (It does not include storage in the QTEMP library.)
If the maximum temporary storage is exceeded, the job is ended. This does not
apply to the use of permanent storage, which is controlled through the user
profile. A value of -1 is returned for *NOMAX.</p>
<p><strong>Maximum temporary storage in megabytes.</strong> The maximum amount
of auxiliary storage (in megabytes) that the job can use. If the job consists
of multiple routing steps, this is the maximum temporary storage that the
routing step can use. This temporary storage is used for storage required by
the program itself and by implicitly created internal system objects used to
support the routing step. (It does not include storage in the QTEMP library.)
If the maximum temporary storage is exceeded, the job is ended. This does not
apply to the use of permanent storage, which is controlled through the user
profile. A value of -1 is returned for *NOMAX.</p>
<p><strong>Maximum threads.</strong> The maximum number of threads that a job
can run with at any time. If multiple threads are initiated simultaneously,
this value may be exceeded. If this maximum value is exceeded, the excess
threads will be allowed to run to their normal completion. Initiation of
additional threads will be inhibited until the maximum number of threads in the
job drops below this maximum value. A value of -1 is returned for *NOMAX.</p>
<p><strong>Note:</strong>&nbsp;&nbsp;Depending on the resources used by the
threads and the resources available on the system, the initiation of additional
threads may be inhibited before this maximum value is reached.</p>
<p><strong>Memory pool name.</strong> The name of the memory pool in which the
job started running. The name may be a number, in which case it is a private
pool associated with a subsystem. The following special values may be
returned.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*MACHINE</em></td>
<td align="left" valign="top">This job is running in the machine pool.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*BASE</em></td>
<td align="left" valign="top">This job is running in the base system pool,
which can be shared with other subsystems.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*INTERACT</em></td>
<td align="left" valign="top">This job is running in the shared pool used for
interactive work.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*SPOOL</em></td>
<td align="left" valign="top">This job is running in the shared pool for
spooled writers.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>*SHRPOOL1 - *SHRPOOL60</em></td>
<td align="left" valign="top">This job is running in the identified shared
pool.</td>
</tr>
<tr>
<td align="left" valign="top"><em>01 - 99</em></td>
<td align="left" valign="top">This job is running in the identified private
pool. This value is right-adjusted and padded with blanks.</td>
</tr>
</table>
<p><strong>Message reply.</strong> Whether the job is waiting for a reply to a
specific message. The field applies only when the active job status or active
job status for job ending is MSGW. Possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The job currently is not in message wait
status.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The job is waiting for a reply to a message.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The job is not waiting for a reply to a
message.</td>
</tr>
</table>
<p><strong>Mode name.</strong> The mode name of the advanced program-to-program
communications device that started the job. Possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*BLANK</em></td>
<td align="left" valign="top">The mode name is *BLANK.</td>
</tr>
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">The mode name is blanks.</td>
</tr>
<tr>
<td align="left" valign="top"><em>Mode name</em></td>
<td align="left" valign="top">The name of the mode.</td>
</tr>
</table>
<p><strong>Name of entity thread
is waiting on.</strong> The name of the entity that the thread is waiting on.
The format of the name will vary based on the type of entity the thread is
waiting on.</p>
<p>For an i5/OS external object, an internal system object, an i5/OS external
object space location, or an internal system object space location, the format
of the name will be as follows(however, an i5/OS external object and an i5/OS
external object space location will only return up to a ten character
name):</p>
<blockquote>
<table border="1" width="60%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="15%">0</td>
<td align="center" valign="top" width="15%">0</td>
<td align="left" valign="top" width="30%">CHAR(30)</td>
<td align="left" valign="top" width="40%">Extended name</td>
</tr>
</table>
</blockquote>
<p>For a member object, the format of the name will be as follows:</p>
<blockquote>
<table border="1" width="60%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="15%">0</td>
<td align="center" valign="top" width="15%">0</td>
<td align="left" valign="top" width="30%">CHAR(10)</td>
<td align="left" valign="top" width="40%">File</td>
</tr>
<tr>
<td align="center" valign="top">10</td>
<td align="center" valign="top">A</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Member</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
</blockquote>
<p>For a lock space object, the format of the name will be as follows:</p>
<blockquote>
<table border="1" width="60%">
<tr>
<th align="center" valign="bottom" colspan="2">Offset</th>
<th align="left" valign="bottom" rowspan="2">Type</th>
<th align="left" valign="bottom" rowspan="2">Field</th>
</tr>
<tr>
<th align="center" valign="bottom">Dec</th>
<th align="center" valign="bottom">Hex</th>
</tr>
<tr>
<td align="center" valign="top" width="15%">0</td>
<td align="center" valign="top" width="15%">0</td>
<td align="left" valign="top" width="30%">CHAR(20)</td>
<td align="left" valign="top" width="40%">Lock space ID</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
</blockquote>
<p>This field will be blank if the type of entity the thread is waiting on is
unknown or the thread is not waiting. This field will also be blank if the name
is for an internal system object or an internal system object space location
and the user does not have *JOBCTL special authority. If this field is
requested for a job, the value for the initial thread of the job will be
returned.</p>
<p><strong>Number of auxiliary I/O requests.</strong> The number of auxiliary
I/O requests performed by the job across all routing steps. This includes both
database and nondatabase paging. This is an unsigned BINARY(8) value.</p>
<p><strong>Number of auxiliary I/O requests, if less than
2,147,483,647.</strong> The number of auxiliary I/O requests performed by the
job across all routing steps. This includes both database and nondatabase
paging. If the number of auxiliary I/O requests is greater than or equal to
2,147,483,647, a value of -1 is returned. Use the <strong>Number of auxiliary
I/O requests</strong> field to retrieve values that are greater than or equal
to 2,147,483,647.</p>
<p><strong>Number of bytes available.</strong> All of the available bytes for
use in your application. <strong>Note:</strong> When you request format
JOBI0700 for the Retrieve Job Information (QUSRJOBI) API, the actual length
depends on how many libraries are in the library list.</p>
<p><strong>Number of bytes returned.</strong> The number of bytes returned to
the user. This may be some but not all of the bytes available.</p>
<p><strong>Number of database lock waits.</strong> The number of times that the
initial thread had to wait to obtain a database lock. (These performance
attributes may be a cumulative job total in a future release.)</p>
<p><strong>Number of interactive transactions.</strong> The count of operator
interactions, such as pressing the Enter key or a function key. This field is
zero for jobs that have no interactions.</p>
<p><strong>Number of internal machine lock waits.</strong> The number of times
that the initial thread had to wait to obtain an internal machine lock. (These
performance attributes may be a cumulative job total in a future release.)</p>
<p><strong>Number of libraries in SYSLIBL.</strong> The number of libraries in
the system part of the library list of the initial thread.</p>
<p><strong>Number of libraries in USRLIBL.</strong> The number of libraries in
the user library list of the initial thread.</p>
<p><strong>Number of nondatabase lock waits.</strong> The number of times that
the initial thread had to wait to obtain a nondatabase lock. (These performance
attributes may be a cumulative job total in a future release.)</p>
<p><strong>Number of product libraries.</strong> The number of product
libraries found in the library list of the initial thread.</p>
<p><strong>Number of signal monitors.</strong> The number of signal monitors
that are present for the job.</p>
<p><strong>Number of SQL open cursors.</strong> The number of SQL cursors that
are currently open for the job.</p>
<p><strong>Object library for SQL cursor.</strong> The name of the library the
object is in that contains the associated SQL open cursor.</p>
<p><strong>Object name for SQL cursor.</strong> The name of the object that
contains the associated SQL open cursor.</p>
<p><strong>Object type for SQL cursor.</strong> The type of object with which
the SQL cursor is associated.</p>
<p><strong>Object type of entity
thread is waiting on.</strong> The object type of the entity the thread is
waiting on. This field may be blank if the type of entity that the thread is
waiting on is not a defined i5/OS external object, a member object, an
internal system object, an i5/OS external object space location, or an
internal system object space location.
For a list of all the available external i5/OS object types,
see <a href="../rbam6/rbam6objecttypes.htm">External object types</a> in the
Control Language (CL) topic.
For a list of all internal system object types, see
<a href="../apiref/conObject.htm">Internal object types</a>. If this field is
requested for a job, the value for the initial thread of the job will be
returned.</p>
<p><strong>Offset to current SQL statement.</strong> The offset from the start
of the format to the start of the current SQL statement.</p>
<p><strong>Offset to SQL open cursor data.</strong> The offset from the start
of the format to the start of the SQL open cursor data.</p>
<p><strong>Offset to signal monitor data.</strong> The offset from the start of
the format to the start of the signal monitor data.</p>
<p><strong>Output queue library name.</strong> The name of the library
containing the output queue.</p>
<p><strong>Output queue name.</strong> The name of the default output queue
that is used for spooled output produced by this job. The default output queue
is only for spooled printer files that specify *JOB for the output queue.</p>
<p><strong>Output queue name -
qualified.</strong> The qualified name of the default output queue that is used
for spooled output produced by this job and the name of the library that
contains the output queue. The default output queue is only for spooled printer
files that specify *JOB for the output queue. The format of the qualified name
is a 10-character simple object name followed by a 10-character library name.
The data is left-justified and padded with blanks on the right.</p>
<p><strong>Output queue priority.</strong> The output priority for spooled
output files that this job produces. The highest priority is 0, and the lowest
is 9.</p>
<p><strong>Page fault count during the elapsed time (job).</strong> The number
of times an active program referenced an address that is not in main storage
for the current routing step of the specified job during the elapsed time.</p>
<p><strong>Page fault count during the elapsed time (thread).</strong> The
number of times an active program referenced an address that is not in main
storage for the specified thread during the elapsed time.</p>
<p><strong>Page faults.</strong>
The number of times an active program referenced an address that is not in main
storage during the current routing step of the specified job.</p>
<p><strong>Pending signal set.</strong> A bit field that is used to determine
the set of signals that have been received but not acted upon by a signal
monitor. The nth bit in the pending signal set represents the nth signal
monitor defined for the job. If a bit within the pending signal set has a value
of 1, then a signal is present but has not been acted upon yet.</p>
<p><strong>Print key format.</strong> Whether border and header information is
provided when the Print key is pressed.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NONE</em></td>
<td align="left" valign="top">The border and header information is not included
with output from the Print key.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*PRTBDR</em></td>
<td align="left" valign="top">The border information is included with output
from the Print key.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*PRTHDR</em></td>
<td align="left" valign="top">The header information is included with output
from the Print key.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*PRTALL</em></td>
<td align="left" valign="top">The border and header information is included
with output from the Print key.</td>
</tr>
</table>
<p><strong>Print text.</strong> The line of text (if any) that is printed at
the bottom of each page of printed output for the job.</p>
<p><strong>Printer device name.</strong> The printer device used for printing
output from this job.</p>
<p><strong>Process ID number.</strong> A unique UNIX-style process ID number
(PID) that is associated with the current routing step of the job. A value of 1
indicates that the PID has not been set.</p>
<p><strong>Processing unit time used for database - total for the job.</strong>
The amount of processing unit time (in milliseconds) that the job used for
processing data base requests across all routing steps. This is an unsigned
BINARY(8) value.</p>
<p><strong>Processing unit time used for database - total for the
thread.</strong>The amount of processing unit time (in milliseconds)that the
specified thread used for processing database requests across all routing
steps. This is an unsigned BINARY(8) value.</p>
<p><strong>Processing unit time used, if less than 2,147,483,647
milliseconds.</strong> The amount of processing unit time (in milliseconds)
that the job used. If the processing unit time used is greater than or equal to
2,147,483,647 milliseconds, a value of -1 is returned. Use the <strong>
Processing unit time used - total for the job</strong> field to retrieve values
that are greater than or equal to 2,147,483,647.</p>
<p><strong>Processing unit time used - total for the job.</strong> The amount
of processing unit time (in milliseconds) that the job used across all routing
steps. This is an unsigned BINARY(8) value.</p>
<p><strong>Processing unit time used - total for the thread.</strong>The amount
of processing unit time (in milliseconds) used by the specified thread. This is
an unsigned BINARY(8) value.</p>
<p><strong>Processing unit used for database - percent used during the elapsed
time (job).</strong> The percentage of processing unit used for database
processing during the elapsed time by the specified job. For multiple-processor
systems, this is the average across processors.</p>
<p><strong>Processing unit used for database - percent used during the elapsed
time (thread).</strong> The percentage of processing unit used for database
processing during the elapsed time by the specified thread. For
multiple-processor systems, this is the average across processors.</p>
<p><strong>Processing unit used for database - time during the elapsed time
(job).</strong> The amount of processing unit time (in milliseconds) used for
database processing during the elapsed time by the specified job.</p>
<p><strong>Processing unit used for database - time during the elapsed time
(thread).</strong> The amount of processing unit time (in milliseconds) used
for database processing during the elapsed time by the specified thread.</p>
<p><strong>Processing unit used - percent during the elapsed time
(job).</strong> The percentage of processing time used during the elapsed time.
For multiple-processor systems, this is the average across processors.</p>
<p><strong>Processing unit used - percent during the elapsed time
(thread).</strong> The percentage of processing time used during the elapsed
time by the specified thread. For multiple-processor systems, this is the
average across processors.</p>
<p><strong>Processing unit used - time during the elapsed time (job).</strong>
The amount of processing unit time (in milliseconds) used during the elapsed
time by the specified job.</p>
<p><strong>Processing unit used - time during the elapsed time
(thread).</strong> The amount of processing unit time (in milliseconds) used
during the elapsed time by the specified thread.</p>
<p><strong>Product libraries.</strong> The libraries that contain product
information for the thread. If requesting this field for a job, the information
for the initial thread of the job will be returned. If this field is defined as
a CHAR(11), a blank will be in the last position of the name.</p>
<p><strong>Product return code.</strong> The return code set by the compiler
for Integrated Language Environment (ILE) languages. Refer to the appropriate
ILE-conforming language manual for possible values. This field is scoped to the
job and represents the most recent return code set by any thread within the
job.</p>
<p><strong>Program return code.</strong> If the job contains any RPG, COBOL,
data file utility (DFU), or sort utility programs, the completion status of the
last program that has finished running is shown; otherwise, a value of zero is
shown.</p>
<p><strong>Purge.</strong> Whether or not the job is eligible to be moved out
of main storage and put into auxiliary storage at the end of a time slice or
when it is beginning a long wait (such as waiting for a work station user's
response). This attribute is ignored when more than one thread is active within
the job. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*YES</em></td>
<td align="left" valign="top">The job is eligible to be moved out of main
storage and put into auxiliary storage. A job with multiple threads, however,
is never purged from main storage.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*NO</em></td>
<td align="left" valign="top">The job is not eligible to be moved out of main
storage and put into auxiliary storage. When main storage is needed, however,
pages belonging to a thread in the job may be moved to auxiliary storage. Then,
when a thread in the job runs again, its pages are returned to main storage as
they are needed.</td>
</tr>
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">Not used for job types *JOBQ or *OUTQ, or for
invalid jobs.</td>
</tr>
</table>
<p><strong>Relational Database
name.</strong> The name used to uniquely identify a data source or relational
database.</p>
<p><strong>Reserved.</strong> An ignored field.</p>
<p><strong>Resources affinity group.</strong> Specifies whether or not the job is grouped together with other jobs on the same set of processors and memory. The Resources affinity group (RSCAFNGRP) parameter on the Add Routing Entry (ADDRTGE) or Add Prestart Job Entry (ADDPJE) commands determines how jobs are grouped. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NO</em></td>
<td align="left" valign="top">The job is not grouped with other jobs. They are spread across all the available system resources.
</td>
</tr>
<tr>
<td align="left" valign="top"><em>*YES</em></td>
<td align="left" valign="top">The job is in the same affinity group as other jobs.</td>
</tr>
</table>
<p><strong>Response time total.</strong> The total amount of response time for
the initial thread, in milliseconds. This value does not include the time used
by the machine, by the attached input/output (I/O) hardware, and by the
transmission lines for sending and receiving data. This field is zero for jobs
that have no interactions. A value of -1 is returned if the field is not large
enough to hold the actual result.</p>
<p><strong>Routing data.</strong> The routing data that is used to determine
the routing entry that identifies the program to start for the routing
step.</p>
<p><strong>Run priority (job).</strong> The priority at which the job is
currently running, relative to other jobs on the system. The run priority
ranges from 0 (highest priority) to 99 (lowest priority).</p>
<p><strong>Run priority (thread).</strong> The run priority for the thread
relative to the priority of the other threads that are running in the system.
This is displayed as a number ranging from 0 (highest priority) to 99 (lowest
priority). The value may never be higher than the run priority for the job in
which the thread is running.</p>
<p><strong>Server mode for Structured Query Language.</strong> Whether or not
Structured Query Language (SQL) statements should run in a separate server job.
The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The SQL statements will not run in a separate
server job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The SQL statements will run in a separate server
job. Each SQL connection will be allowed to run with a different user profile
and separate transaction scoping.</td>
</tr>
</table>
<p><strong>Server type.</strong> The type of server represented by the job. A
value of blanks indicates that the job is not part of a server.</p>
<p><strong>Signal action.</strong> The action to be taken when a signal is
received for a signal monitor. Possible values are as follows:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">The signal associated with this signal monitor is
not supported.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Handle the signal using the signal default
action.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Ignore the signal (discard).</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Handle the signal by running the signal catching
function.</td>
</tr>
</table>
<p><strong>Signal blocking mask.</strong> A bit field that is used to represent
the set of signals whose signal actions are to be held for the initial thread
of the job. The nth bit in the signal blocking mask represents the nth signal
monitor defined for the initial thread. If a bit within the signal blocking
mask has a value of 1, then the signal action is blocked and the signal is
held.</p>
<p><strong>Signal monitor data.</strong> The signal information for a given
signal monitor for the job. This information consists of the signal number,
signal action, default signal action, maximum number of signals to be retained,
and the current number of signals pending.</p>
<p><strong>Signal number.</strong> A numeric value assigned to the signal
monitor. This value is used to locate the signal monitor for the job when a
signal is sent to the job.</p>
<p><strong>Signal status.</strong> A numerical value used to determine if the
job is enables to receive signals from another job or the system.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The job is not enabled for signals. This job
cannot receive signals from another job or system.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The job is enabled for signals. This job can
receive signals from another job or system.</td>
</tr>
</table>
<p><strong>Signed-on job.</strong> Whether the job is a to be treated like a
signed-on user on the system.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The job should be treated like a signed-on
user.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The job should not be treated like a signed-on
user.</td>
</tr>
</table>
<p><strong>Size of SQL open cursor data.</strong> The size of a single entry
for a given SQL cursor for the job. This information consists of the object
name, object library, object type, SQL cursor name, and SQL statement name.</p>
<p><strong>Sort sequence library.</strong> The sort sequence library associated
with this job.</p>
<p><strong>Sort sequence table name.</strong> The sort sequence table
associated with this job. Possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*HEX</em></td>
<td align="left" valign="top">No sort sequence table is used. The hexadecimal
values of the characters are used to determine the sort sequence.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*LANGIDSHR</em></td>
<td align="left" valign="top">The sort sequence table used can contain the same
weight for multiple characters, and it is the shared weight sort table
associated with the language specified in the LANGID parameter.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*LANGIDUNQ</em></td>
<td align="left" valign="top">The sort sequence table used must contain a
unique weight for each character in the code page, and it is the unique weight
sort table associated with the language specified in the LANGID parameter.</td>
</tr>
</table>
<p><strong>Sort sequence table -
qualified.</strong> The qualified name of the sort sequence table associated
with this job. The format of the qualified name is a 10-character sort sequence
table name followed by a 10-character library name. The data is left-justified
and padded with blanks on the right. If the sort sequence table name is a
special value, the library name is blank.</p>
<p><strong>Special environment.</strong> Whether the job is running in a
particular environment. Possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NONE</em></td>
<td align="left" valign="top">The job is not running in any special
environment.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*S36</em></td>
<td align="left" valign="top">The job is running in the System/36
environment.</td>
</tr>
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">This job is not currently active.</td>
</tr>
</table>
<p><strong>Spooled file action.</strong>
Whether spooled files are accessed through job interfaces
after the job has completed is normal activity. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*KEEP</em></td>
<td align="left" valign="top">
When the job completes its activity,
as long as at least one spooled file for the job
exists in the system auxiliary storage pool (ASP 1)
or in a basic user ASP (ASPs 2-32),
the spooled files are kept with the job
and the status of the job is
updated to indicate that the job has completed.
If all remaining spooled files for the job
are in independent ASPs (ASPs 33-255),
the spooled files will be detached from the job
and the job will be removed from the system.
</td>
</tr>
<tr>
<td align="left" valign="top"><em>*DETACH</em></td>
<td align="left" valign="top">The spooled files are detached from the job when
the job completes its activity.</td>
</tr>
</table>
<p><strong>SQL cursor name.</strong> The name of the SQL cursor.</p>
<p><strong>SQL open cursor data.</strong> The SQL cursor information for a
given SQL cursor for the job. This information consists of the object name,
object library, object type, SQL cursor name, and SQL statement name.</p>
<p><strong>SQL statement name.</strong> The name of the SQL statement that is
associated with the SQL cursor.</p>
<p><strong>Status message handling.</strong> Whether you want status messages
displayed for this job. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NONE</em></td>
<td align="left" valign="top">This job does not display status messages.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*NORMAL</em></td>
<td align="left" valign="top">This job displays status messages.</td>
</tr>
</table>
<p><strong>Status of current SQL statement.</strong> The status of the current
SQL statement. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The SQL statement returned is running
currently.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The SQL statement returned has completed.</td>
</tr>
</table>
<p><strong>Status of job on the job queue.</strong> The status of this job on
the job queue.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>blank</em></td>
<td align="left" valign="top">This job was not on a job queue.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SCD</em></td>
<td align="left" valign="top">This job will run as scheduled.</td>
</tr>
<tr>
<td align="left" valign="top"><em>HLD</em></td>
<td align="left" valign="top">This job is being held on the job queue.</td>
</tr>
<tr>
<td align="left" valign="top"><em>RLS</em></td>
<td align="left" valign="top">This job is ready to be selected.</td>
</tr>
</table>
<p><strong>Submitter's job name.</strong> The job name of the submitter's job.
If the job has no submitter, this field is blank.</p>
<p><strong>Submitter's job name
- qualified.</strong> The qualified job name of the submitter's job. The format
of the qualified job name is a 10-character simple job name, a 10-character
user name, and a 6-character job number. If the job has no submitter, this
field is blank.</p>
<p><strong>Submitter's job number.</strong> The job number of the submitter's
job. If the job has no submitter, this field is blank.</p>
<p><strong>Submitter's message queue library name.</strong> The name of the
library that contains the message queue. If the job has no submitter, this
field is blank.</p>
<p><strong>Submitter's message queue name.</strong> The name of the message
queue where the system sends a completion message when a batch job ends. If the
job has no submitter, this field is blank.</p>
<p><strong>Submitter's message
queue name - qualified.</strong> The qualified name of the message queue where
the system sends a completion message when a batch job ends and the name of the
library that contains the message queue. If the job has no submitter, this
field is blank. The format of the qualified name is a 10-character simple
object name followed by a 10-character library name. The data is left-justified
and padded with blanks on the right.</p>
<p><strong>Submitter's user name.</strong> The user name of the submitter. If
the job has no submitter, this field is blank.</p>
<p><strong>Subsystem description library name.</strong> The library that
contains the subsystem description. This value is only for jobs whose status is
*ACTIVE. For jobs with a status of *OUTQ or *JOBQ, the value for this field is
blank.</p>
<p><strong>Subsystem description name.</strong> The name of the subsystem in
which an active job is running. This value is only for jobs whose status is
*ACTIVE. For jobs with status of *OUTQ or *JOBQ, the value for this field is
blank.</p>
<p><strong>Subsystem description
name - qualified.</strong> The qualified name of the subsystem in which an
active job is running. The format of the qualified name is a 10-character
simple object name followed by a 10-character library name. This value is only
for jobs whose status is *ACTIVE. For jobs with status of *OUTQ or *JOBQ, the
value for this field is blank.</p>
<p><strong>System library list.</strong> The system portion of the library list
of the thread. If requesting this field for a job, the information for the
initial thread of the job will be returned. If this field is defined as a
CHAR(11), a blank will be in the last position of the name.</p>
<p><strong>System pool identifier.</strong> The identifier of the
system-related pool from which the job's main storage is allocated. These
identifiers are not the same as those specified in the subsystem description,
but are the same as the system pool identifiers shown on the system status
display. This is the pool that the threads in the job start in. Also see the
Current system pool identifier field for more information.</p>
<p><strong>Temporary storage used in kilobytes.</strong> The amount of
auxiliary storage (in kilobytes) that is currently allocated to this job.</p>
<p><strong>Note:</strong>&nbsp;&nbsp;This value will reach a maximum of
2&nbsp;147&nbsp;483&nbsp;647 kilobytes. If the actual temporary storage used is
larger than that value, this field will return 2&nbsp;147&nbsp;483&nbsp;647
kilobytes. It is recommended that the temporary storage used in megabytes field
be used to get over this limit.</p>
<p><strong>Temporary storage used in megabytes.</strong> The amount of
auxiliary storage (in megabytes) that is currently allocated to this job. This
is an unsigned BINARY(4) value.</p>
<p><strong>Thread count.</strong> The count of the current number of active
threads in the process at the time of the materialization. An <strong>active
thread</strong> may be either actively running, suspended, or waiting for a
resource.</p>
<p><strong>Thread hold count.</strong> The count of the number of times that
the specified thread has been held using the hold thread interface. If this
field is requested for a job, the value for the initial thread of the job will
be returned.</p>
<p><strong>Thread resources affinity.</strong> Specifies whether or not secondary threads are grouped together with the initial thread when they are started. If they are grouped together, they will have affinity to, or a preference for, the same set of processors and memory, which may affect performance. The first 10 characters contain a special value indicating how the threads will be grouped. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NOGROUP</em></td>
<td align="left" valign="top">Secondary threads are not grouped with the initial thread. They are spread across all the available system resources.
</td>
</tr>
<tr>
<td align="left" valign="top"><em>*GROUP</em></td>
<td align="left" valign="top">Secondary threads are grouped with the initial thread.</td>
</tr>
</table>
<p>The last 10 characters contain a special value that indicates to what degree the system tries to maintain the affinity of threads to the system resources that they are internally assigned to. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NORMAL</em></td>
<td align="left" valign="top">A thread will use any processor or memory in the system if the resources it has affinity to are not readily available.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*HIGH</em></td>
<td align="left" valign="top">A thread will only use the resources it has affinity to, and will wait until they become available if necessary.</td>
</tr>
</table>
<p><strong>Thread status.</strong> The current status of the thread. If this
field is requested for a job, the value for the initial thread of the job will
be returned. The status of a thread may be one of the following values:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>Blank</em></td>
<td align="left" valign="top">The status of the thread is unknown.</td>
</tr>
<tr>
<td align="left" valign="top"><em>CMTW</em></td>
<td align="left" valign="top">The thread is waiting for the completion of
save-while-active checkpoint processing in another job. This wait is necessary
to prevent a partial commitment control transaction from being saved to the
media.</td>
</tr>
<tr>
<td align="left" valign="top"><em>CNDW</em></td>
<td align="left" valign="top">The thread is waiting for a condition.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DEQA</em></td>
<td align="left" valign="top">The thread is waiting for completion of a dequeue
operation in the pool activity level.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DEQW</em></td>
<td align="left" valign="top">The thread is waiting for completion of a dequeue
operation. For example, a server may wait for work by waiting for a dequeue
operation</td>
</tr>
<tr>
<td align="left" valign="top"><em>EVTW</em></td>
<td align="left" valign="top">The thread is waiting for an event.</td>
</tr>
<tr>
<td align="left" valign="top"><em>HLD</em></td>
<td align="left" valign="top">The thread is in a job that is being held.</td>
</tr>
<tr>
<td align="left" valign="top"><em>HLDT</em></td>
<td align="left" valign="top">The thread is being held.</td>
</tr>
<tr>
<td align="left" valign="top"><em>INEL</em></td>
<td align="left" valign="top">The thread is ineligible and not currently in the
pool activity level.</td>
</tr>
<tr>
<td align="left" valign="top"><em>JVAA</em></td>
<td align="left" valign="top">The thread is waiting for completion of a Java
program operation in the pool activity level.</td>
</tr>
<tr>
<td align="left" valign="top"><em>JVAW</em></td>
<td align="left" valign="top">The thread is waiting for completion of a Java
program operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>LCKW</em></td>
<td align="left" valign="top">The thread is waiting for a lock.</td>
</tr>
<tr>
<td align="left" valign="top">
<em>LSPA</em></td>
<td align="left" valign="top">The thread is waiting for a lock space to be
attached while in a pool activity level.</td>
</tr>
<tr>
<td align="left" valign="top"><em>LSPW</em></td>
<td align="left" valign="top">The thread is waiting for a lock space to be
attached.</td>
</tr>
<tr>
<td align="left" valign="top"><em>MTXW</em></td>
<td align="left" valign="top">The thread is in a mutex wait. A mutex is a
synchronization function that is used to allow multiple threads to serialize
their access to shared data.</td>
</tr>
<tr>
<td align="left" valign="top"><em>RUN</em></td>
<td align="left" valign="top">The thread is currently running in the activity
level.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SELW</em></td>
<td align="left" valign="top">The thread is in a select wait. More information
on the select() function is in the Sockets APIs chapter in the System API
Reference, SC41-5801.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SEMW</em></td>
<td align="left" valign="top">The thread is waiting for a semaphore. A
semaphore is a synchronization function that is used to allow multiple jobs or
threads to serialize their access to shared data.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SIGS</em></td>
<td align="left" valign="top">The thread has been held by a signal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>SIGW</em></td>
<td align="left" valign="top">The thread is waiting for a signal.</td>
</tr>
<tr>
<td align="left" valign="top"><em>THDW</em></td>
<td align="left" valign="top">The thread is waiting for another thread to
complete an operation.</td>
</tr>
<tr>
<td align="left" valign="top"><em>TIMA</em></td>
<td align="left" valign="top">The thread is waiting, in the activity level, for
a time interval to end.</td>
</tr>
<tr>
<td align="left" valign="top"><em>TIMW</em></td>
<td align="left" valign="top">The thread is waiting for a time interval to
end.</td>
</tr>
</table>
<p><strong>Thread type.</strong> The thread type indicates how the thread was
created. If this field is requested for a job, the value for the initial thread
of the job will be returned. The type of a thread may be one of the following
values:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The thread was created either as the initial
thread of the job or explicitly by the application.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The thread was created by an operating system
function.</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="left" valign="top"></td>
</tr>
</table>
<p><strong>Time separator.</strong> The value used to separate hours, minutes,
and seconds when presenting a time. The following values are possible:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>':'</em></td>
<td align="left" valign="top">A colon (:) is used for the time separator.</td>
</tr>
<tr>
<td align="left" valign="top"><em>'.'</em></td>
<td align="left" valign="top">A period (.) is used for the time separator.</td>
</tr>
<tr>
<td align="left" valign="top"><em>' '</em></td>
<td align="left" valign="top">A blank is used for the time separator.</td>
</tr>
<tr>
<td align="left" valign="top"><em>','</em></td>
<td align="left" valign="top">A comma (,) is used for the time separator.</td>
</tr>
</table>
<p><strong>Time slice.</strong> The maximum amount of processor time (in
milliseconds) given to each thread in this job before other threads in this job
and in other jobs are given the opportunity to run. The time slice establishes
the amount of time needed by a thread in this job to accomplish a meaningful
amount of processing. At the end of the time slice, the thread might be put in
an inactive state so that other threads can become active in the storage pool.
Values retrieved range from 8 through 9999999 (that is, 9&nbsp;999&nbsp;999
milliseconds or 9999.999 seconds). Although you can specify a value of less
than 8, the system takes a minimum of 8 milliseconds to run a process.</p>
<p><strong>Time-slice end pool.</strong> Whether you want a thread in an
interactive job moved to another main storage pool at the end of its time
slice. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*NONE</em></td>
<td align="left" valign="top">A thread in the job does not move to another main
storage pool when it reaches the end of its time slice.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*BASE</em></td>
<td align="left" valign="top">A thread in the job moves to the base pool when
it reaches the end of its time slice.</td>
</tr>
</table>
<p><strong>Time spent on database lock waits.</strong> The cumulative amount of
time, in milliseconds, that the initial thread has had to wait to obtain
database locks. (These performance attributes may be a cumulative job total in
a future release.)</p>
<p><strong>Time spent on internal machine lock waits.</strong> The cumulative
amount of time, in milliseconds, that the initial thread has had to wait to
obtain internal machine locks. (These performance attributes may be a
cumulative job total in a future release.)</p>
<p><strong>Time spent on nondatabase lock waits.</strong> The cumulative amount
of time, in milliseconds, that the initial thread has had to wait to obtain
nondatabase locks. (These performance attributes may be a cumulative job total
in a future release.)</p>
<p>
<strong>Time zone current abbreviated name.</strong> The abbreviated, or short, name for the time zone. This field will contain either the standard or Daylight Saving Time abbreviated name depending on whether or not Daylight Saving Time is in effect. If the time zone description uses a message to specify the current abbreviated name and the message cannot be retrieved, this field returns *N. This can occur when the caller of the API is not authorized to the message file or its library, the message file cannot be found or the message does not exist in the message file.
</p>
<p>
<strong>Time zone current full name.</strong> The full, or long, name for the time zone. This field will contain either the standard or Daylight Saving Time full name depending on whether or not Daylight Saving Time is in effect. If the time zone description uses a message to specify the current full name and the message cannot be retrieved, this field returns *N. This can occur when the caller of the API is not authorized to the message file or its library, the message file cannot be found or the message does not exist in the message file.
</p>
<p>
<strong>Time zone current message identifier.</strong> The identifier of the message that contains the current full and abbreviated names. The message identifier could be *NONE if a message was not specified when the time zone description was created.
</p>
<p>
<strong>Time zone current offset.</strong> The offset, in minutes, used to calculate local job time. This value has been adjusted for Daylight Saving Time, if necessary.
</p>
<p>
<strong>Time zone Daylight Saving Time indicator.</strong> The indicator that is used to specify
whether or not Daylight Saving Time is being observed. Valid values that are returned are:
</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Daylight Saving Time is not being observed (Standard Time).</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Daylight Saving Time is being observed.</td>
</tr>
</table>
<p>
<strong>Time zone description name.</strong> The name of the time zone description that is used to calculate local job time.
</p>
<p>
<strong>Time zone message file name - qualified.</strong> The qualified name of the message file used to retrieve the Standard Time message and the Daylight Saving Time message. The format of the qualified name is a 10-character simple object name followed by a 10-character library name. The library name may contain *LIBL which means that the library list is searched to locate the message file. The message file name and the library name are left-justified and padded with blanks on the right. If a message was not specified when the time zone description was created or last changed, this field returns *NONE.
</p>
<!-- NOTE: If you add a type below, you may need to update -->
<!-- the following fields descriptions: -->
<!-- Extended object attribute of entity thread is waiting on -->
<!-- Library of entity thread is waiting on -->
<!-- Name of entity thread is waiting on -->
<!-- Object type of entity thread is waiting on -->
<p><strong>Type of entity thread
is waiting on.</strong> The type of entity, such as an i5/OS external object,
that the thread is waiting on. If this field is requested for a job, the value
for the initial thread of the job will be returned. The type of entity may be
one of the following values:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">Thread is not waiting</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">i5/OS external object</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Member object</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">Internal system object</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">i5/OS external object space location</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em></td>
<td align="left" valign="top">Internal system object space location</td>
</tr>
<tr>
<td align="left" valign="top"><em>6</em></td>
<td align="left" valign="top">Lock space object</td>
</tr>
<tr>
<td align="left" valign="top"><em>999</em></td>
<td align="left" valign="top">Unknown type</td>
</tr>
</table>
<p><strong>Unit of work ID.</strong> The unit of work ID is used to track jobs
across multiple systems. If a job is not associated with a source or target
system using advanced program-to-program communications (APPC), this
information is not used. Every job on the system is assigned a unit of work ID.
The unit-of-work identifier is made up of:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>Location name</em></td>
<td align="left" valign="top">CHAR(8). The name of the source system that
originated the APPC job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>Network ID</em></td>
<td align="left" valign="top">CHAR(8). The network name associated with the
unit of work.</td>
</tr>
<tr>
<td align="left" valign="top"><em>Instance</em></td>
<td align="left" valign="top">CHAR(6). The value that further identifies the
source of the job. This is shown as hexadecimal data.</td>
</tr>
<tr>
<td align="left" valign="top"><em>Sequence number</em></td>
<td align="left" valign="top">CHAR(2). A value that identifies a checkpoint
within the application program.</td>
</tr>
</table>
<p><strong>User library list.</strong> The user portion of the library list for
the thread. If requesting this field for a job, the information for the initial
thread of the job will be returned. If this field is defined as a CHAR(11), a
blank will be in the last position of the name.</p>
<p><strong>User name.</strong> The user name of the job, which is the same as
the name of the user profile under which the job was started. It can come from
several different sources depending on the type of job. This may be different
than the user profile under which the job is currently running. See the Current
user profile field for more information.</p>
<p><strong>User return code.</strong> The user-defined return code set by ILE
high-level language constructs. An example is the program return code in the C
language. This field is scoped to the job and represents the most recent return
code set by any thread within the job.</p>
<br>
<h3><a name="HDRWRKJOB">Comparing Job Type, Subtype, and Enhanced Job Type with
the Work with Active Job Command</a></h3>
<p>The following table compares the job type, job subtype, and enhanced job
type fields returned by the QUSRJOBI API to the type field on the Work with
Active Job (WRKACTJOB) command.</p>
<table border>
<tr>
<th align="left" valign="bottom" colspan="4"><em>WRKACTJOB and QUSRJOBI API
Comparison</em></th>
</tr>
<tr>
<th align="left" valign="bottom">Job Type Field</th>
<th align="center" valign="bottom">Job Type</th>
<th align="center" valign="bottom">Job Subtype</th>
<th align="left" valign="bottom">Enhanced<br>
Job Type</th>
</tr>
<tr>
<td align="left" valign="top" width="50%">ASJ (Autostart)</td>
<td align="center" valign="top" width="15%">A</td>
<td align="center" valign="top" width="15%">blank</td>
<td align="left" valign="top" width="20%">0110</td>
</tr>
<tr>
<td align="left" valign="top">BCH (Batch)</td>
<td align="center" valign="top">B</td>
<td align="center" valign="top">blank</td>
<td align="left" valign="top">0210</td>
</tr>
<tr>
<td align="left" valign="top">BCI (Batch immediate)</td>
<td align="center" valign="top">B</td>
<td align="center" valign="top">D</td>
<td align="left" valign="top">0220</td>
</tr>
<tr>
<td align="left" valign="top">EVK (Started by a program start request)</td>
<td align="center" valign="top">B</td>
<td align="center" valign="top">E</td>
<td align="left" valign="top">0310</td>
</tr>
<tr>
<td align="left" valign="top">INT (Interactive)</td>
<td align="center" valign="top">I</td>
<td align="center" valign="top">blank</td>
<td align="left" valign="top">0910, 0920, 0930, or 0940</td>
</tr>
<tr>
<td align="left" valign="top">M36 (AS/400 Advanced 36 machine server)</td>
<td align="center" valign="top">B</td>
<td align="center" valign="top">F</td>
<td align="left" valign="top">blank</td>
</tr>
<tr>
<td align="left" valign="top">MRT (Multiple requester terminal)</td>
<td align="center" valign="top">B</td>
<td align="center" valign="top">T</td>
<td align="left" valign="top">0230</td>
</tr>
<tr>
<td align="left" valign="top">PJ (Prestart job)</td>
<td align="center" valign="top">B</td>
<td align="center" valign="top">J</td>
<td align="left" valign="top">1610, 1620, or 1630</td>
</tr>
<tr>
<td align="left" valign="top">PDJ (Print driver job)</td>
<td align="center" valign="top">W</td>
<td align="center" valign="top">P</td>
<td align="left" valign="top">2310</td>
</tr>
<tr>
<td align="left" valign="top">RDR (Reader)</td>
<td align="center" valign="top">R</td>
<td align="center" valign="top">blank</td>
<td align="left" valign="top">1810</td>
</tr>
<tr>
<td align="left" valign="top">SYS (System)</td>
<td align="center" valign="top">S or X</td>
<td align="center" valign="top">blank</td>
<td align="left" valign="top">1920</td>
</tr>
<tr>
<td align="left" valign="top">SBS (Subsystem monitor)</td>
<td align="center" valign="top">M</td>
<td align="center" valign="top">blank</td>
<td align="left" valign="top">1910</td>
</tr>
<tr>
<td align="left" valign="top">WTR (Writer)</td>
<td align="center" valign="top">W</td>
<td align="center" valign="top">blank</td>
<td align="left" valign="top">2310</td>
</tr>
<tr>
<td align="left" valign="top">blank (Alternative user subtype--not an active
job)</td>
<td align="center" valign="top">B</td>
<td align="center" valign="top">U</td>
<td align="left" valign="top">240</td>
</tr>
</table>
<br>
<br>
<hr>
<table align="center" cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
"wm1.htm">Work Management APIs</a> | <a href="aplist.htm">APIs by
category</a></td>
</tr>
</table>
</body>
</html>
Reference in New Issue Copy Permalink