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

4297 lines
134 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>Change Job (QWTCHGJB) API</title>
<!-- Begin Header Records ======================================= -->
<!-- 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. -->
<!-- WM SCRIPT A converted by B2H R4.1 (346) (CMS) by V2KEA304 -->
<!-- at RCHVMW2 on 17 Feb 1999 at 11:05:09 -->
<!-- Change History: -->
<!-- YYMMDD USERID Change description -->
<!-- File cleanup completed Dec 2001 by v2cdijab -->
<!-- 040315 WDTARARA Add LOGOUTPUT -->
<!-- End Header Records -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<a name="Top_Of_Page"></a>
<!-- Java sync-link -->
<script type="text/javascript" language="Javascript" src="../rzahg/synch.js">
</script>
<h2>Change Job (QWTCHGJB) API</h2>
<div class="box" style="width: 80%;">
<br>
&nbsp;&nbsp;Required Parameter Group:<br>
<!-- iddvc RMBR -->
<br>
<table width="100%">
<tr>
<td align="center" valign="top" width="10%">1</td>
<td align="left" valign="top" width="60%">Qualified job name</td>
<td align="left" valign="top" width="15%">Input</td>
<td align="left" valign="top" width="15%">Char(26)</td>
</tr>
<tr>
<td align="center" valign="top">2</td>
<td align="left" valign="top">Internal job identifier</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(16)</td>
</tr>
<tr>
<td align="center" valign="top">3</td>
<td align="left" valign="top">Format name</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(8)</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="left" valign="top">Job change information</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(*)</td>
</tr>
<tr>
<td align="center" valign="top">5</td>
<td align="left" valign="top">Error code</td>
<td align="left" valign="top">I/O</td>
<td align="left" valign="top">Char(*)</td>
</tr>
</table>
<br>
&nbsp;&nbsp;Optional Parameter Group:<br>
<!-- iddvc RMBR -->
<br>
<table width="100%">
<tr>
<td align="center" valign="top" width="10%">6</td>
<td align="left" valign="top" width="60%">Job or Thread identification
information</td>
<td align="left" valign="top" width="15%">Input</td>
<td align="left" valign="top" width="15%">Char(*)</td>
</tr>
<tr>
<td align="center" valign="top">7</td>
<td align="left" valign="top">Format of job identification information</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(8)</td>
</tr>
</table>
<br>
&nbsp;&nbsp;Default Public Authority: *USE<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Threadsafe: Conditional; see <a href="#Header_19">Usage Notes</a>.<br>
<!-- iddvc RMBR -->
<br>
</div>
<p>The Change Job (QWTCHGJB) API changes some of the attributes of a job or
thread. The attributes changed are determined by the job change information
parameter.</p>
<p>The current value of most of the job attributes can be retrieved with the
List Job (QUSLJOB) API, the Open List of Jobs (QGYOLJOB) API, the Retrieve
Current Attributes (QWCRTVCA) API, the Retrieve Job Information (QUSRJOBI) API
or the Retrieve Thread Attributes (QWTRTVTA) API.</p>
<p>If an error occurs, the error code will have a general failure error and the
specific error will need to be retrieved out of the job message queue of the
job that issued this API call.</p>
<p>The QWTCHGJB API changes a list of attributes similar to the attributes
changed with the Change Job (CHGJOB) command.</p>
<br>
<h3>Authorities and Locks</h3>
<dl>
<dt><em>Job Authority</em></dt>
<dd>The API must be called from within the job that is being changed, or the
caller of the API must be running under a user profile that is the same as the
job user identity of the job that is being changed. Otherwise, the caller of
the API must be running under a user profile that has job control (*JOBCTL)
special authority.
<p>The <strong>job user identity</strong> is the name of the user profile by
which a job is known to other jobs. It is described in more detail in the
<a href="../rzaks/rzaks1.htm">Work Management</a> topic.</p>
<p>Job control (*JOBCTL) special authority is needed for the following
attributes to be changed:</p>
<ul>
<li>Default wait time</li>
<li>Purge</li>
<li>Run priority</li>
<li><img src="delta.gif" alt="Start of change">Run priority (thread)
<img src="deltaend.gif" alt="End of change"></li>
<li>Time slice</li>
<li>Time slice end pool</li>
</ul>
<br>
</dd>
<dt><em>Command Authority</em></dt>
<dd>*USE authority to the Change Accounting Code (CHGACGCDE) command is needed
to change the job accounting code attribute.<br>
<br>
</dd>
<dt><em>Object Authority</em></dt>
<dd>If changing the job queue, *USE authority is required for the object, and
*EXECUTE authority is required for the library. If changing the output queue,
*READ authority is required for the object, and *EXECUTE authority is required
for the library. In addition, the caller must be authorized to the output queue
currently associated with the job that is being changed. If changing the sort
sequence table, *USE authority is required for the object, and *EXECUTE
authority is required for the library.
<p>If using the JOBC0300 format to change attributes that are retrieved from
the job description, *USE authority is required for the job description and
*EXECUTE authority is required for the library. If changing the ASP group
information, *USE authority is required for all ASP devices in the ASP group.
If changing the current library or the initial library list, *USE authority is
required for the libraries.</p>
</dd>
</dl>
<br>
<h3>Required Parameter Group</h3>
<dl>
<dt><strong>Qualified job name</strong></dt>
<dd>INPUT; CHAR(26)
<p>The name of the job for which the attributes are to be changed. If this
value is *INT, the internal job identifier will be used. The qualified job name
has three parts:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top" nowrap><em>Job name</em></td>
<td align="left" valign="top">CHAR(10). A specific job name or one of the
following special values:
<table cellpadding="5">
<tr>
<td align="left" valign="top"><em>*</em></td>
<td align="left" valign="top">The job or thread in which this program is
running. The rest of the qualified job name parameter must be blank. This
special value must be used when using the JOBC0200 or JOBC0300 format.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*INT</em></td>
<td align="left" valign="top">The internal job identifier locates the job. The
user name and job number must be blank. This is only valid for the JOBC0100
format.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*THREAD</em></td>
<td align="left" valign="top">The job information is specified in the
<a href="#HDRTHDINF6">Job or thread identification information</a>
parameter. This special value must be used
when using the JOBC0400 format. The user name, job number, and internal job
identifier must be blank when using *THREAD. This is valid for the JOBC0400
format only.</td>
</tr>
</table>
</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>User name</em></td>
<td align="left" valign="top">CHAR(10). A specific user profile name, or blanks
when the job name is a special value.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>Job number</em></td>
<td align="left" valign="top">CHAR(6). A specific job number, or blanks when
the job name is a special value.</td>
</tr>
</table>
<br>
</dd>
<dt><strong>Internal job identifier</strong></dt>
<dd>INPUT; CHAR(16)
<p> The internal identifier for the job. The QUSLJOB API creates this
identifier. If you do not specify *INT for the job name parameter, this
parameter must be blanks. With this parameter, the system can locate the job
more quickly than with a fully qualified job name.</p>
</dd>
<dt><strong>Format name</strong></dt>
<dd>INPUT; CHAR(8)
<p> The format of the list of job or thread attributes to be changed. You must
use one of the following format names:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>JOBC0100</em></td>
<td align="left" valign="top">Basic change job list. To be used when changing
the attributes of your job or the attributes of another job. This format will
not change any specific attributes of a thread. This format will function the
same way that the CHGJOB command works.</td>
</tr>
<tr>
<td align="left" valign="top"><em>JOBC0200</em></td>
<td align="left" valign="top">Basic change job list for changing the attributes
of your own thread. The special value of '*' must be used for the job name. See
<a href="#HDRJOBRDE3">Field Descriptions for Valid Keys</a> for the scope of
each of the valid key fields. If no scope is mentioned, the attribute is scoped
to the job.
<p><strong>Note:</strong> The scope of selected attributes may change over
time. Currently there are only a few attributes that are scoped to the thread.
The attributes that are not scoped to the thread will be updated at the job
level. This will affect all threads running under this job. As attributes
become scoped to the thread, attributes changed with this format will then be
changed for the current thread and will not affect other threads.</p>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>JOBC0300</em></td>
<td align="left" valign="top">Change select attributes to user profile values.
This format is intended to be used after a swap user profile. The special value
of '*' must be used for the job name. This format will be functionally similar
to the Change Prestart Job (CHGPJ) command. See <a href="#HDRJOBRDE3">Field
Descriptions for Valid Keys</a> for the scope of each of the valid key fields.
If no scope is mentioned, the attribute is scoped to the job.
<p><strong>Note:</strong> The attributes for a thread will be updated at the
job level if the specific attributes are not currently defined at the thread
level. Selected attributes may be moved to the thread level in a later
release.</p>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>JOBC0400</em></td>
<td align="left" valign="top">Change select attributes of a specific thread.
The special value of '*THREAD' must be used for the job name.</td>
</tr>
</table>
<br>
</dd>
<dt><strong>Job change information</strong></dt>
<dd>INPUT; CHAR(*)
<p> The information for the job that you want to change. The information must
be in the following format:</p>
<dl>
<dt><em>Number of variable length records</em></dt>
<dd>BINARY(4). The total number of all the variable length records. If this
value is less than 1, an error message is returned.<br>
<br>
</dd>
<dt><em>Variable length records.</em></dt>
<dd>The attributes of the job to change and the data used for the change. For
the specific format of the variable length record, see <a href="#HDRVARLRC2">
Formats for Variable Length Record</a>.</dd>
</dl>
<br>
</dd>
<dt><strong>Error code</strong></dt>
<dd>I/O; CHAR(*)
<p>The structure in which to return error information. For the format of the
structure, see <a href="../apiref/error.htm#hdrerrcod">Error Code Parameter</a>.</p>
</dd>
</dl>
<br>
<h3>Optional Parameter Group</h3>
<dl>
<dt><strong><a name="HDRTHDINF6"></a>Job or thread identification information</strong></dt>
<dd>INPUT; CHAR(*)
<p>The information that is used to identify the thread within a job for which
specified attributes are to be changed. See <a href="#HDRXXJJJF1">Format of job
or thread identification information</a> for details.</p>
</dd>
<dt><strong>Format of job or thread identification information</strong></dt>
<dd>INPUT; CHAR(8)
<p>The format of the job or thread identification information. The possible
format names are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>JIDF0100</em></td>
<td align="left" valign="top">See <a href="#HDRXXJJJF1">Format of job or thread
identification information</a> for details on the job identification
information.</td>
</tr>
<tr>
<td align="left" valign="top"><em>JIDF0200</em></td>
<td align="left" valign="top">See <a href="#HDRXXJJJF1">Format of job or thread
identification information</a> for details on the job identification
information.</td>
</tr>
</table>
<p><strong>Note:</strong> If the thread handle is available, Format JIDF0200
provides a faster method of accessing a thread that is not the current thread
than Format JIDF0100.</p>
</dd>
</dl>
<br>
<h3><a name="HDRVARLRC2">Formats for Variable Length Record</a></h3>
<p>The following tables define the format for the variable length records.</p>
<p><strong>JOBC0100, JOBC0200 and JOBC0400 Format</strong>: The layout of the
JOBC0100, JOBC0200 and JOBC0400 format is the same layout as the information
returned with the List Job (QUSLJOB) API.</p>
<table border width="80%">
<!-- cols="10 10 20 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="left" valign="top" rowspan="7" colspan="2" width="20%">These fields
repeat, in the order listed, for each key requested.</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Length of attribute information</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Key</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Type of data</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(3)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of data</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Data</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<p><strong>JOBC0300 Format</strong>: The JOBC0300 format is for changing
attributes to values specified in either the current user profile or the
initial user profile.</p>
<table border width="80%">
<!-- cols="10 10 20 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="left" valign="top" rowspan="3" colspan="2" width="20%">These fields
repeat for each key requested.</td>
<td align="left" valign="top" width="20%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Key</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Data</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<p>If the length of the data is longer than the key field's data length, the
data will be truncated at the right. No message will be issued.</p>
<p>If the length of the data is smaller than the key field's data length, the
data will be padded with blanks at the right. No message will be issued.</p>
<p>It is not an error to specify a key more than once. If duplicate keys are
specified, the last specified value for that key is used.</p>
<p>Each variable length record must be 4-byte aligned. If not, unpredictable
results may occur.</p>
<br>
<h3><a name="Header_16">Field Descriptions for JOBC0100, JOBC0200, JOBC0300 and
JOBC0400 Formats</a></h3>
<p><strong>Data.</strong> The data for the attribute that is to be changed. The
data for the JOBC0100, JOBC0200, JOBC0300 and JOBC0400 formats is defined in
the key list section.</p>
<p><strong>Key.</strong> The key for the attribute to be changed. See <a href=
"#HDRLKEYS2">Valid Keys</a> for the list of valid keys.</p>
<p><strong>Length of data.</strong> The length of the data for the key
field.</p>
<p><strong>Length of attribute information.</strong> The total length of input
information for this attribute. This value is used to increment to the next
attribute in the list.</p>
<p><strong>Reserved.</strong> An ignored field. This field must be blanks.</p>
<p><strong>Type of data.</strong> The type of input data. This field is
provided to maintain the same format layout that is used in the List Job
(QUSLJOB) API. This field will not cause any conversion to occur.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>B</em></td>
<td align="left" valign="top">The input data is in binary format.</td>
</tr>
<tr>
<td align="left" valign="top"><em>C</em></td>
<td align="left" valign="top">The input data is in character format.</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRLKEYS2">Valid Keys</a></h3>
<p>The following table contains a list of the valid keys for the JOBC0100
formats. See <a href="#HDRJOBRDE3">Field Descriptions for Valid
Keys</a> for the descriptions of the valid key fields.</p>
<table border width="80%">
<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%">0201</td>
<td align="left" valign="top" width="20%">CHAR(10)</td>
<td align="left" valign="top" width="65%">Break message handling</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(8)</td>
<td align="left" valign="top">Country or region ID</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">0318</td>
<td align="left" valign="top">CHAR(15)</td>
<td align="left" valign="top">Client IP address - IPv4 (job)</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">0408</td>
<td align="left" valign="top">CHAR(5)</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">0413</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Decimal format</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">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">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">
<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(8)</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(7)</td>
<td align="left" valign="top">Logging text</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">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(4)</td>
<td align="left" valign="top">Purge</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">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">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">1920</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Schedule date</td>
</tr>
<tr>
<td align="left" valign="top">1921</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Schedule time</td>
</tr>
<tr>
<td align="left" valign="top">1922</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Server mode for Structured Query Language</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>
</table>
<br>
<br>
<p>The following table contains a list of the valid keys for the
JOBC0200 formats. See <a href="#HDRJOBRDE3">Field Descriptions for Valid
Keys</a> for the descriptions of the valid key fields.</p>
<table border width="80%">
<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%">0201</td>
<td align="left" valign="top" width="20%">CHAR(10)</td>
<td align="left" valign="top" width="65%">Break message handling</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(8)</td>
<td align="left" valign="top">Country or region ID</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">0318</td>
<td align="left" valign="top">CHAR(15)</td>
<td align="left" valign="top">Client IP address - IPv4 (job)</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">0408</td>
<td align="left" valign="top">CHAR(5)</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">0413</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Decimal format</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">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">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">
<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(8)</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(7)</td>
<td align="left" valign="top">Logging text</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">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(4)</td>
<td align="left" valign="top">Purge</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">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">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">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">1920</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Schedule date</td>
</tr>
<tr>
<td align="left" valign="top">1921</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Schedule time</td>
</tr>
<tr>
<td align="left" valign="top">1922</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Server mode for Structured Query Language</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>
</table>
<br>
<br>
<p>The following table contains a list of the valid keys for the JOBC0300
format. See <a href="#HDRJOBRDE3">Field Descriptions for Valid Keys</a> for the
descriptions of the valid key fields.</p>
<table border width="80%">
<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%">0104</td>
<td align="left" valign="top" width="20%">CHAR(10)</td>
<td align="left" valign="top" width="65%">ASP group information</td>
</tr>
<tr>
<td align="left" valign="top">0302</td>
<td align="left" valign="top">CHAR(10)</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(10)</td>
<td align="left" valign="top">Country or region ID</td>
</tr>
<tr>
<td align="left" valign="top">0310</td>
<td align="left" valign="top">CHAR(10)</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">0801</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Home directory</td>
</tr>
<tr>
<td align="left" valign="top">0910</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Initial library list</td>
</tr>
<tr>
<td align="left" valign="top">1001</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Job accounting code</td>
</tr>
<tr>
<td align="left" valign="top">1201</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Language ID</td>
</tr>
<tr>
<td align="left" valign="top">1210</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Locale</td>
</tr>
<tr>
<td align="left" valign="top">1501</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Output queue name</td>
</tr>
<tr>
<td align="left" valign="top">1502</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Output queue priority</td>
</tr>
<tr>
<td align="left" valign="top">1602</td>
<td align="left" valign="top">CHAR(10)</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">1901</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Sort sequence table</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">2701</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">All keys for JOBC0300 format</td>
</tr>
</table>
<br>
<br>
<p>The following table contains a list of the valid keys for the JOBC0400
format. See <a href="#HDRJOBRDE3">Field Descriptions for Valid Keys</a> for the
descriptions of the valid key fields.</p>
<table border width="80%">
<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%">1804</td>
<td align="left" valign="top" width="20%">BIN(4)</td>
<td align="left" valign="top" width="65%">Run priority (thread)</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRJOBRDE3">Field Descriptions for Valid Keys</a></h3>
<p><strong>All keys for JOBC0300 format.</strong> All the keys that are valid
for the JOBC0300 format will be changed. The list of keys is subject to change
at a later time. If other attributes are added to this key in the future, no
change will be needed for them to take effect. If this key (2701) is specified,
no other keys can be specified. Even though specifying this key is similar to
specifying a list of all the keys that are valid for the JOBC0300 format, the
error handling is different. Errors encountered when changing some of the
attributes will not cause the change request to fail, although a diagnostic
message may be sent. Errors with ASP group information (key 0104), Current
library (key 0310), and Initial library list (key 0910) are considered critical
and will stop the change request. In general, errors that would prevent a job
from starting will cause the change request to fail. If multiple threads are
active, attributes that cannot be changed in a safe manner will be ignored and
a diagnostic message will be sent. See the <a href="#Header_19">Usage Notes</a>
for a list of attributes that can be changed in a safe manner. The following
keys will be changed by this key:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<th align="left" valign="top">Key ID</th>
<th align="left" valign="top">Key Name</th>
</tr>
<tr>
<td align="left" valign="top"><em>0104</em></td>
<td align="left" valign="top">ASP group information</td>
</tr>
<tr>
<td align="left" valign="top"><em>0302</em></td>
<td align="left" valign="top">Coded character set ID</td>
</tr>
<tr>
<td align="left" valign="top"><em>0303</em></td>
<td align="left" valign="top">Country or region ID</td>
</tr>
<tr>
<td align="left" valign="top"><em>0310</em></td>
<td align="left" valign="top">Current library</td>
</tr>
<tr>
<td align="left" valign="top"><em>0311</em></td>
<td align="left" valign="top">Character identifier control</td>
</tr>
<tr>
<td align="left" valign="top"><em>0801</em></td>
<td align="left" valign="top">Home directory</td>
</tr>
<tr>
<td align="left" valign="top"><em>0910</em></td>
<td align="left" valign="top">Initial library list</td>
</tr>
<tr>
<td align="left" valign="top"><em>1001</em></td>
<td align="left" valign="top">Job accounting code</td>
</tr>
<tr>
<td align="left" valign="top"><em>1201</em></td>
<td align="left" valign="top">Language ID</td>
</tr>
<tr>
<td align="left" valign="top"><em>1210</em></td>
<td align="left" valign="top">Locale</td>
</tr>
<tr>
<td align="left" valign="top"><em>1501</em></td>
<td align="left" valign="top">Output queue name</td>
</tr>
<tr>
<td align="left" valign="top"><em>1502</em></td>
<td align="left" valign="top">Output queue priority</td>
</tr>
<tr>
<td align="left" valign="top"><em>1602</em></td>
<td align="left" valign="top">Print text</td>
</tr>
<tr>
<td align="left" valign="top"><em>1603</em></td>
<td align="left" valign="top">Printer device name</td>
</tr>
<tr>
<td align="left" valign="top"><em>1901</em></td>
<td align="left" valign="top">Sort sequence table</td>
</tr>
<tr>
<td align="left" valign="top"><em>1902</em></td>
<td align="left" valign="top">Status message handling</td>
</tr>
</table>
<p>The attributes that can be set from the locale (coded character set ID and
sort sequence table) based on the locale job attributes field (that is
retrieved out of the same user profile specified on the locale field) take
precedence over the values that are retrieved from the user profile.</p>
<p>This key is valid for the JOBC0300 format only. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The value for the attributes is retrieved for the
user profile under which this thread was initially running.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The value for the attributes is retrieved for the
user profile under which this thread is currently running</td>
</tr>
</table>
<p><strong>ASP group information.</strong> The name of the auxiliary storage
pool (ASP) group that is associated with this thread. The ASP group name is the
name of the primary ASP device within the ASP group. The libraries in the
independent ASPs in the new ASP group plus the libraries in the system ASP (ASP
number 1) and basic user ASPs (ASP numbers 2-32) form the library name space
and all libraries in the library list of this thread are required to be in the
new library name space. Therefore, when the ASP group is updated, the libraries
in the system part of the library list, the product libraries, the current
library and the libraries in the user part of the library list will also be
updated.</p>
<p>The libraries currently in the system part of the library list that are
found in the system ASP or any configured basic user ASP are used as the new
system part of the library list. The product libraries that are found in the
system ASP or any configured basic user ASP are used as the new product
libraries. If the current library is being changed (either with key 0310 or key
2701), the value specified will be used. Otherwise, the library name in the
current library entry of the library list is used as the new current library if
the library is found in the system ASP or any configured basic user ASP. If the
library name in the current entry is not found in the system ASP or any basic
user ASP, the current library entry will be removed from the library list. If
the user part of the library list is being changed (either with key 0910 or key
2701), the value specified will be used. Otherwise, the libraries currently in
the user part of the library list that are found in the system ASP or any
configured basic user ASP are used as the new user part of the library
list.</p>
<p>This key is valid for the JOBC0300 format only. The following values are
possible:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The ASP group information specified in the job
description of the user profile under which this thread was initially running
is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The ASP group information specified in the job
description of the current user profile for this thread is used.</td>
</tr>
</table>
<p><strong>Break message handling.</strong> How this job handles break
messages. This key isvalid for the JOBC0100 and JOBC0200 formats only . 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>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>
<p>The possible values for the JOBC0100 and JOBC0200 formats are:</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>
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The value in the QCHRIDCTL system value will be
used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*USRPRF</em></td>
<td align="left" valign="top">The CHRIDCTL specified in the user profile under
which this thread was initially running will be used.</td>
</tr>
</table>
<p>The possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The CHRIDCTL specified in the user profile under
which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The CHRIDCTL specified in the current user
profile for this thread is used.</td>
</tr>
</table>
<p><strong>Client IP address - IPv4 (job).</strong> The IPv4 address of the
client for which the thread of this server is servicing currently. This key is
valid for the JOBC0200 format only. A value of blanks indicates that the thread
is not currently servicing a client. A value of hexadecimal zeros is not
allowed. An address is expressed in standard dotted-decimal form
www.xxx.yyy.zzz; for example, 130.99.128.1. This field is not required to be an
IP address. A change to this attribute in a secondary thread is possible,
however, it is essentially meaningless as only the attribute for the inital
thread can be retrieved using the Retrieve Job Information (QUSRJOBI) API. For
further information on retrieving the <em>Client IP address - IPv4 or IPv6</em>
that has been implicity set by the operating system, see the <a href=
"qwtrtvta.htm">Retrieve Thread Attribute</a> (QWTRTVTA) API.</p>
<p><strong>Coded character set ID.</strong> The coded character set identifier
used for this job.</p>
<p>The possible values for the JOBC0100 and JOBC0200 formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">The CCSID specified in the system value QCCSID is
used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>-2</em></td>
<td align="left" valign="top">The CCSID specified in the user profile under
which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>
coded-character-set-identifier</em></td>
<td align="left" valign="top">Specify the CCSID.</td>
</tr>
</table>
<p>The possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The CCSID specified in the user profile under
which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The CCSID specified in the current user profile
for this thread is used.</td>
</tr>
</table>
<p><strong>Country or region ID.</strong> The country or region identifier
associated with this job.</p>
<p>The possible values for the JOBC0100 and JOBC0200 formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The system value QCNTRYID is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*USRPRF</em></td>
<td align="left" valign="top">The country or region ID specified in the user
profile under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>country-or-region-ID</em></td>
<td align="left" valign="top">Specify the country or region identifier to be
used by the job.</td>
</tr>
</table>
<p>The possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The country or region ID specified in the user
profile under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The country or region ID specified in the current
user profile for this thread is used.</td>
</tr>
</table>
<p><strong>Current library.</strong> The name of the current library that is
associated with this thread. This key is valid for the JOBC0300 format only.
The following values are possible:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The current library specified in the user profile
under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The current library specified in the current user
profile for this thread is used.</td>
</tr>
</table>
<p><strong>Date format.</strong> The format that the date is presented in. This
key is only valid for the JOBC0100 and JOBC0200 formats. The following values
are possible:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>*SYS</em></td>
<td align="left" valign="top">The system value, QDATFMT, is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*YMD</em></td>
<td align="left" valign="top">The date format used is year, month, and
day.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*MDY</em></td>
<td align="left" valign="top">The date format used is month, day, and
year.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*DMY</em></td>
<td align="left" valign="top">The date format used is day, month, and
year.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*JUL</em></td>
<td align="left" valign="top">The date format used is Julian (year and
day).</td>
</tr>
</table>
<p><strong>Date separator.</strong> The value used to separate days, months,
and years when presenting a date. This key is valid for the JOBC0100 and
JOBC0200 formats only. The following values are possible:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>S</em></td>
<td align="left" valign="top">The system value, QDATSEP is used.</td>
</tr>
<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>DDM conversation handling.</strong> Specifies whether the
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 (DRDA) applications, DDM
applications, or DB2 Multisystem applications. This key is only valid for the
JOBC0100 and JOBC0200 formats. The following values are possible:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<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:
<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.</li>
<li>A DRDA connection to an application server not running on an iSeries server
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 an SQL DISCONNECT statement.</td>
</tr>
</table>
<p><strong>Decimal format.</strong> The type of zero suppression and the
decimal point character. This key is only valid for the JOBC0100 and JOBC0200
formats. The following values are possible:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The value in the system value, QDECFMT, is used
as the decimal format for this job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*BLANK</em></td>
<td align="left" valign="top">Period for decimal, zero suppression.</td>
</tr>
<tr>
<td align="left" valign="top"><em>J</em></td>
<td align="left" valign="top">Comma for decimal, one leading zero.</td>
</tr>
<tr>
<td align="left" valign="top"><em>I</em></td>
<td align="left" valign="top">Comma for decimal, zero suppression.</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. This default wait time is
used when a wait time is not otherwise specified for a given situation.
Normally, this is the amount of time the user is willing to wait for the system
before the request is ended. If the job consists of multiple routing steps, a
change to this attribute during a routing step does not apply to subsequent
routing steps. The valid range is 1 through 9999999. A value of -1 specifies to
change to no maximum wait time. This key is valid for the JOBC0100 and JOBC0200
formats only.</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. This key
is valid for the JOBC0100 and JOBC0200 formats only. The possible values
are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The value in the system value, QDEVRCYACN, is
used as the device recovery action for this job.</td>
</tr>
<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 to the application program an error
message, that indicates that 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. The system
sends to the job's log and to the history log (QHST) a message that indicates
that 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 to the QHST log a message
that indicates that the job ended because of a device error.</td>
</tr>
</table>
<p><strong>Home directory.</strong> The name of the home directory for the
integrated file system that is associated with this thread. If the home
directory associated with this thread was retrieved from the same user profile
that is being specified by either *INLUSR or *CURUSR, then the home directory
will not be changed for this thread, even if that user profile's home directory
has been changed. If you change the home directory, the job's current working
directory will not change. This key is valid for the JOBC0300 format only. The
following values are possible:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The home directory specified in the user profile
under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The home directory specified in the current user
profile for this thread is used.</td>
</tr>
</table>
<p><strong>Initial library list.</strong> The initial user part of the library
list that is associated with this thread. This key is only valid for the
JOBC0300 format. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The initial library list specified in the job
description of the user profile under which this thread was initially running
is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The initial library list specified in the job
description of the user profile under which this thread is currently running is
used.</td>
</tr>
</table>
<p><strong>Inquiry message reply.</strong> How the job answers inquiry
messages. This key is only valid for the JOBC0100 and JOBC0200 formats. The
possible values are:</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 that are 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 that was 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>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. The user who is changing this field must have authority to the
CHGACGCDE CL command. If the user does not have the proper authority, this
field is ignored and processing continues.</p>
<p>The possible values for the JOBC0100 and JOBC0200 formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*BLANK</em></td>
<td align="left" valign="top">The accounting code is changed to all
blanks.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>accounting-code</em></td>
<td align="left" valign="top">Specify the 15-character accounting code used for
the next accounting segment. The accounting code may contain alphabetic or
numeric characters.</td>
</tr>
</table>
<p>The possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The accounting code specified in the job
description of the user profile under which this thread was initially running
is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The accounting code specified in the job
description of the user profile under which this thread is currently running is
used.</td>
</tr>
</table>
<p><strong>Job date.</strong> The date that is assigned to 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 will only be changed for jobs whose
status is *JOBQ or *ACTIVE. This key is only valid for the JOBC0100 and
JOBC0200 formats.</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.
The job log output value can be changed at any time
until the job log has been produced or removed.
</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>*SYSVAL</em></td>
<td align="left" valign="top">The value is specified
by the QLOGOUTPUT system value.</td>
</tr>
<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 message queue full action.</strong> The action to take when the
message queue is full. This key is only valid for the JOBC0100 and JOBC0200
formats. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The value specified for the QJOBMSGQFL system
value is used.</td>
</tr>
<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 queue name - qualified.</strong> The qualified name of the job
queue that the job is to be on. The format of the qualified name is a
10-character simple object name followed by a 10-character library name. This
value is valid for jobs whose status is *JOBQ. For jobs with a status of *OUTQ
or *ACTIVE, an error will be signaled. This key is valid for the JOBC0100 and
JOBC0200 formats only.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top" nowrap><em>Job queue name</em></td>
<td align="left" valign="top">CHAR(10). The specific name of the job queue the
job is to be on.</td>
</tr>
<tr>
<td align="left" valign="top"><em>Library name</em></td>
<td align="left" valign="top">CHAR(10). The name of the library where the job
queue is located. This value must be left-justified and padded with blanks. The
possible values are:
<table cellpadding="5">
<tr>
<td align="left" valign="top"><em>*LIBL</em></td>
<td align="left" valign="top">All libraries in the job's library list are
searched until the first match is found.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURLIB</em></td>
<td align="left" valign="top">The current library for the job is used to locate
the job queue. If no library is specified as the current library for the job,
QGPL is used.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>library-name</em></td>
<td align="left" valign="top">Specify the name of the library where the job
queue is placed.</td>
</tr>
</table>
</td>
</tr>
</table>
<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 valid for jobs whose status is *JOBQ or *ACTIVE. For
jobs with a status of *OUTQ, an error will be signaled. This key is only valid
for the JOBC0100 and JOBC0200 formats.</p>
<p><strong>Job switches.</strong> The current setting of the job switches that
are used by this job. Specify any combination of eight 0's, 1's, or X's to
change the job switch settings. If a switch value is not being changed, enter
an X in the position that represents that switch. This key is only valid for
the JOBC0100 and JOBC0200 formats.</p>
<p><strong>Language ID.</strong> The language identifier that is associated
with this job. The language identifier is used when *LANGIDUNQ or *LANGIDSHR is
specified on the sort sequence parameter. If the job CCSID is 65535, this
parameter is also used to determine the value of the job default CCSID.</p>
<p>The possible values for the JOBC0100 and JOBC0200 formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The system value QLANGID is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*USRPRF</em></td>
<td align="left" valign="top">The language ID specified in the user profile
under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>language-ID</em></td>
<td align="left" valign="top">Specify the language identifier to be used by the
job.</td>
</tr>
</table>
<p>The possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The language ID specified in the user profile
under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The language ID specified in the user profile
under which this thread is currently running is used.</td>
</tr>
<tr>
<td align="left" valign="top"></td>
<td align="left" valign="top"></td>
</tr>
</table>
<p><strong>Locale.</strong> The path name of the locale that is assigned to the
LANG environment variables. Several job attributes can be set from the locale
based on the values from the locale job attributes (locale job attributes are
retrieved from the same user profile as the locale). The attributes that can be
changed are CCSID, date format, date separator, sort sequence, time separator,
and decimal format. This key is only valid for the JOBC0300 format. The
possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The locale specified in the user profile under
which this thread was initially running will be used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The locale specified in the user profile under
which this thread is currently running will be used.</td>
</tr>
</table>
<p><strong>Logging level.</strong> What type of information is logged. This key
is valid for the JOBC0100 and JOBC0200 formats only. The possible values
are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<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 indications 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>Logging 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 that caused 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>Logging 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. This key is
valid for the JOBC0100 and JOBC0200 formats only.</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. This key is valid for the
JOBC0100 and JOBC0200 formats only.</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. This key is valid for the JOBC0100 and JOBC0200 formats only. 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 (if 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>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. The
possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The output queue specified in the job description
of the user profile under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The output queue specified in the job description
of the user profile under which this thread is currently running is used.</td>
</tr>
</table>
<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. 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.</p>
<dl>
<dt><em>Output queue name.</em></dt>
<dd>CHAR(10). The specific name of the output queue that is used. If a special
value is specified, it must be the only value in the field.
<p>The possible values for the JOBC0100 and JOBC0200 formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*DEV</em></td>
<td align="left" valign="top">The DEV parameter is determined by one of these
printer file commands: Create Printer File (CRTPRTF), Change Printer File
(CHGPRTF), or Override with Printer File (OVRPRTF).</td>
</tr>
<tr>
<td align="left" valign="top"><em>*WRKSTN</em></td>
<td align="left" valign="top">The default output queue that is used with this
job is the output queue that is assigned to the work station associated with
the job at the time the job is started.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*USRPRF</em></td>
<td align="left" valign="top">The output queue name specified in the user
profile under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>output-queue-name</em></td>
<td align="left" valign="top">The name and library of the default output queue
that is used by the job. Specify the library name last (left-adjusted and
padded with blanks) preceded by the output queue name.</td>
</tr>
</table>
<br>
</dd>
<dt><em>Output queue library name.</em></dt>
<dd>CHAR(10). The name of the library that contains the output queue. The
library name must follow the output queue name. The possible values are:
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*LIBL</em></td>
<td align="left" valign="top">All libraries in the job's library list are
searched until the first match is found.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURLIB</em></td>
<td align="left" valign="top">The current library for the job is used to locate
the name of the spooled output queue. If no library is specified as the current
library for the job, QGPL is used.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>library-name</em></td>
<td align="left" valign="top">Specify the name of the library where the spooled
output queue is located.</td>
</tr>
</table>
</dd>
</dl>
<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>The possible CHAR(2) values for the JOBC0100 and JOBC0200 formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top" nowrap><em>output-priority</em></td>
<td align="left" valign="top">A value, ranging from 1 through 9, for the
priority of the job's output files. The output priority specified cannot be
higher than the priority specified in the user profile under which the job is
running.</td>
</tr>
</table>
<p>The possible CHAR(10) values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The output priority specified in the job
description of the user profile under which this thread was initially running
is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The output priority specified in the job
description of the user profile under which this thread is currently running is
used.</td>
</tr>
</table>
<p><strong>Printer device name.</strong> The printer device used for printing
output from this job.</p>
<p>The possible values for the JOBC0100 and JOBC0200 formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The value in the system value QPRTDEV is used as
the printer device.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*WRKSTN</em></td>
<td align="left" valign="top">The default printer device used with this job is
the printer device assigned to the work station that is associated with the
job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*USRPRF</em></td>
<td align="left" valign="top">The printer device name specified in the user
profile under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>printer-device-name</em></td>
<td align="left" valign="top">The name of the printer device that is used with
this job.</td>
</tr>
</table>
<p>The possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The printer device that is specified in the job
description of the user profile under which this thread was initially running
is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The printer device specified in the job
description of the user profile under which this thread is currently running is
used.</td>
</tr>
</table>
<p><strong>Print key format.</strong> Whether border and header information is
provided when the Print key is pressed. This key is only valid for the JOBC0100
and JOBC0200 formats. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The value specified on the system value
QPRTKEYFMT determines whether header or border information is printed.</td>
</tr>
<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. The possible values for
the JOBC0100 and JOBC0200 formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The system value, QPRTTXT, is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*BLANK</em></td>
<td align="left" valign="top">No text is printed on printed output.</td>
</tr>
<tr>
<td align="left" valign="top"><em>print-text</em></td>
<td align="left" valign="top">The character string that is printed at the
bottom of each page. A maximum of 30 characters can be entered.</td>
</tr>
</table>
<p>The possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The print text specified in the job description
of the user profile under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The print text specified in the job description
of the user profile under which this thread is currently running is used.</td>
</tr>
</table>
<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 entering 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.
If the job consists of multiple routing steps, a change to this attribute
during a routing step does not apply to subsequent routing steps. This key is
valid for the JOBC0100 and JOBC0200 formats only. The possible values are:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<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 this job may be moved to auxiliary storage.
Then, when a thread in this job runs again, its pages are returned to main
storage as they are needed.</td>
</tr>
</table>
<p><strong>Run priority (job).</strong> The priority at which the job or thread
competes for the processing unit relative to other jobs and threads that are
active at the same time. The run priority ranges from 1 (highest priority) to
99 (lowest priority). This value represents the relative (not absolute)
importance of the job or thread. For example, a run priority of 25 is not twice
as important as a run priority of 50. If the job consists of multiple routing
steps, a change to this attribute during a routing step does not apply to
subsequent routing steps. This key is valid for the JOBC0100 and JOBC0200
formats only. This key can be used to change the current thread using the
JOBC0200 format, but when changing a specific thread, the JOBC0400 format
should be used with the <em>Run priority (thread)</em> key.</p>
<p>The possible values for the JOBC0100 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>priority</em></td>
<td align="left" valign="top">The run priority of the job is changed. The range
of values is 1 (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. If
a priority higher than the job's is entered, an error is returned. Changing the
run priority of the job affects the run priorities of all threads within the
job. For example, the job is running at priority 10, thread A within the job is
running at priority 10, and thread B within the job is running at priority 15.
The priority of the job is changed to 20. The priority of thread A would then
be adjusted to 20 and the priority of thread B would be adjusted to 25.</td>
</tr>
</table>
<p>The possible values for the JOBC0200 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">The run priority of the current thread will be
set equal to the priority of the job. The thread cannot have a lower priority
than its corresponding job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>priority</em></td>
<td align="left" valign="top">The run priority of the thread is changed. The
range of values are the current job's run priority (highest priority) to 99
(lowest priority). If a priority that is higher than the job's is entered, an
error is returned.</td>
</tr>
</table>
<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.
The range of values are from 1 (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. If a priority higher than the job's is entered, an error is
returned. This key is valid for the JOBC0200 and JOBC0400 format only.</p>
<p><strong>Schedule date.</strong> The date on which the submitted job becomes
eligible to run.</p>
<p>If your system or your job is configured to use the Julian date format,
*MONTHSTR and *MONTHEND are calculated as if the system or job did not use the
Julian date format. This key is only valid for the JOBC0100 format. The
possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*CURRENT</em></td>
<td align="left" valign="top">The submitted job becomes eligible to run on the
current date.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*MONTHSTR</em></td>
<td align="left" valign="top">The submitted job becomes eligible to run on the
first day of the month. If you specify *MONTHSTR and if today is the first day
of the month and the time you specify on the schedule time parameter has not
passed, the job becomes eligible to run today. Otherwise, the job becomes
eligible on the first day of the next month.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*MONTHEND</em></td>
<td align="left" valign="top">The submitted job becomes eligible to run on the
last day of the month. If you specify *MONTHEND and if today is the last day of
the month and the time you specify on the schedule time parameter has not
passed, the job becomes eligible to run today. Otherwise, the job becomes
eligible on the last day of the next month.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*MON</em></td>
<td align="left" valign="top">The job becomes eligible to run on Monday.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*TUE</em></td>
<td align="left" valign="top">The job becomes eligible to run on Tuesday.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*WED</em></td>
<td align="left" valign="top">The job becomes eligible to run on
Wednesday.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*THU</em></td>
<td align="left" valign="top">The job becomes eligible to run on Thursday.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*FRI</em></td>
<td align="left" valign="top">The job becomes eligible to run on Friday.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*SAT</em></td>
<td align="left" valign="top">The job becomes eligible to run on Saturday.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*SUN</em></td>
<td align="left" valign="top">The job becomes eligible to run on Sunday.</td>
</tr>
<tr>
<td align="left" valign="top"><em>date</em></td>
<td align="left" valign="top">Specify a date 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>.</td>
</tr>
</table>
<p><strong>Schedule time.</strong> The time on the scheduled date at which the
job becomes eligible to run. This key is valid for the JOBC0100 format
only.</p>
<p><strong>Note:</strong> Although the time can be specified to the second, the
load on the system may affect the exact time at which the job becomes eligible
to run.</p>
<p>The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*CURRENT</em></td>
<td align="left" valign="top">The job is submitted on the current time.</td>
</tr>
<tr>
<td align="left" valign="top"><em>time</em></td>
<td align="left" valign="top">The time you want the job to start. The time is
specified in 24-hour format as follows:
<p>Specify a string of 6 digits (HHMMSS) where HH equals hours, MM equals
minutes, and SS equals seconds. Valid values for HH range from 00 to 23. Valid
values for MM and SS range from 00 to 59.</p>
</td>
</tr>
</table>
<p><strong>Server mode for Structured Query Language.</strong> Whether or not
Structured Query Language (SQL) statements should run in a separate server job.
This key is only valid for the JOBC0200 format. The possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<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.
This key is valid for the JOBC0200 format only. A value of blanks indicates
that the job is not part of a server. A value of hexadecimal zeros is not
allowed. IBM servers start with QIBM.</p>
<p><strong>Sort sequence table.</strong> The sort sequence table to be used for
string comparisons for this job. The possible values for the JOBC0300 format
are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">The sort table specified in the user profile
under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">The sort table specified in the user profile
under which this thread is currently running is used.</td>
</tr>
</table>
<p><strong>Sort sequence table - qualified.</strong> The qualified name of the
sort sequence table to be used for string comparisons for this job. The format
of the qualified name is a 10-character simple object name followed by a
10-character library name. The sort sequence table consists of 2 parts:</p>
<dl>
<dt><em>Sort sequence table name</em></dt>
<dd>CHAR(10). The specific name of the sort sequence table. The possible values
for the JOBC0100 and JOBC0200 formats are:<br>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The system value QSRTSEQ is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*USRPRF</em></td>
<td align="left" valign="top">The sort sequence table specified in the user
profile under which this thread was initially running is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*HEX</em></td>
<td align="left" valign="top">A sort sequence table is not used. The
hexadecimal values of the characters are used to determine the sort
sequence.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*LANGIDUNQ</em></td>
<td align="left" valign="top">A unique-weight sort table is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*LANGIDSHR</em></td>
<td align="left" valign="top">A shared-weight sort table is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>table-name</em></td>
<td align="left" valign="top">The name of the sort sequence table to be used
with this job. The table name must be preceded by the library name,
left-adjusted, and padded with blanks.</td>
</tr>
</table>
<br>
</dd>
<dt><em>Sort sequence library</em></dt>
<dd>CHAR(10). The sort sequence table library that is associated with this job.
The possible values are:<br>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*LIBL</em></td>
<td align="left" valign="top">All libraries in the job's library list are
searched until the first match is found.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURLIB</em></td>
<td align="left" valign="top">The current library for the job is searched. If
no library is specified as the current library for the job, the QGPL library is
used.</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><em>library-name</em></td>
<td align="left" valign="top">The name of the library to be searched. This must
be specified after the sort sequence table name and must be left-adjusted and
padded with blanks.</td>
</tr>
</table>
</dd>
</dl>
<p><strong>Spooled file action.</strong> Whether spooled files can be accessed
through job interfaces once a job has completed its normal activity.</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">Spooled files are detached from the job when the
job completes its activity.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The job will take the spooled file action
specified by the QSPLFACN system value.</td>
</tr>
</table>
<p><strong>Status message handling.</strong> Whether you want status messages
displayed for this job. The possible values for the JOBC0100 and JOBC0200
formats are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The system value QSTSMSG is used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*USRPRF</em></td>
<td align="left" valign="top">The status message handling that is specified in
the user profile under which this thread was initially running is used.</td>
</tr>
<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>The possible values for the JOBC0300 format are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*INLUSR</em></td>
<td align="left" valign="top">Status messages are shown or not shown as
specified in the user profile under which this thread was initial running.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*CURUSR</em></td>
<td align="left" valign="top">Status messages are shown or not shown as
specified in the current user profile under which this thread is running.</td>
</tr>
</table>
<p><strong>Time separator.</strong> The value used to separate hours, minutes,
and seconds when presenting a time. This key is only valid for the JOBC0100 and
JOBC0200 formats. The possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>S</em></td>
<td align="left" valign="top">The time separator specified in the system value
QTIMSEP is used.</td>
</tr>
<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 or in other jobs) are given the opportunity to run. The time slice
establishes the amount of time that is needed by a thread in the 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. If the job consists of multiple routing steps, a
change to this attribute during a routing step does not apply to subsequent
routing steps. Valid values range from 1 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. If you display a job's run attributes, the time slice value is never
less than 8. This key is valid for the JOBC0100 and JOBC0200 formats only.</p>
<p><strong>Time-slice end pool.</strong> Whether you want interactive jobs
moved to another main storage pool at the end of the time slice. This key is
only valid for the JOBC0100 and JOBC0200 formats. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*SYSVAL</em></td>
<td align="left" valign="top">The value in the system value, QTSEPOOL, is
used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*NONE</em></td>
<td align="left" valign="top">The job does not move to another main storage
pool when it reaches the end of the time slice.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*BASE</em></td>
<td align="left" valign="top">The job moves to the base pool when it reaches
the end of the time slice.</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRXXJJJF1">Format of job or thread identification
information</a></h3>
<p>Format JIDF0100 is the format of the information needed to identify the job
and the thread for which the thread's attributes will be changed. This format
supports several special values that can help in identifying the thread.</p>
<p>Format JIDF0200 is the format of the information needed to identify the
thread for which the thread's attributes will be changed. This format is to be
used when referencing a specific thread for which you already have the thread
handle.</p>
<p><strong>Note:</strong> If the thread handle is available, Format JIDF0200
provides a faster method of accessing a thread that is not the current thread
than Format JIDF0100.</p>
<br>
<p><strong>JIDF0100 format.</strong></p>
<table border width="80%">
<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="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">CHAR(10)</td>
<td align="left" valign="top" width="60%">Job name</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">User name</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Job number</td>
</tr>
<tr>
<td align="center" valign="top">26</td>
<td align="center" valign="top">1A</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Internal job identifier</td>
</tr>
<tr>
<td align="center" valign="top">42</td>
<td align="center" valign="top">2A</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">44</td>
<td align="center" valign="top">2C</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Thread indicator</td>
</tr>
<tr>
<td align="center" valign="top">48</td>
<td align="center" valign="top">30</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Thread identifier</td>
</tr>
</table>
<br>
<br>
<h3>Field Descriptions</h3>
<p><strong>Internal job identifier.</strong> The internal identifier for the
job. The List Job (QUSLJOB) API returns this identifier. If you do not specify
*INT for the job name parameter, this parameter must contain blanks. With this
parameter, the system can locate the job more quickly than with a job name.</p>
<p><strong>Job name.</strong> A specific job name or one of the following
special values:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>*</em></td>
<td align="left" valign="top">The job that this program is running in. The job
number and user name must contain blanks.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*INT</em></td>
<td align="left" valign="top">The internal job identifier locates the job. The
job number and user name must contain blanks.</td>
</tr>
</table>
<p><strong>Job number.</strong> A specific job number, or blanks when the job
name specified is a special value.</p>
<p><strong>Reserved.</strong> An unused field. This field must contain
hexadecimal zeros.</p>
<p><strong>Thread identifier.</strong> A value that uniquely identifies a
thread within a job. If a thread identifier is specified, a thread indicator
must also be specified. If the thread indicator is not 0, this field must
contain hexadecimal zeros.</p>
<p><strong>Thread indicator.</strong> A value that is used to specify the
thread within the job. If a thread indicator is specified, a thread identifier
must be specified also. The following values are supported:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Information from the thread identifier field
should be used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The thread that this program is running in
currently should be used.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The initial thread of the identified job should
be used.</td>
</tr>
</table>
<p><strong>Note:</strong> For all of the supported values, the combination of
the internal job identifier, job name, job number, and user name fields must
also identify the job containing the thread.</p>
<p><strong>User name.</strong> A specific user profile name, or blanks when the
job name specified is a special value.</p>
<br>
<p><strong>JIDF0200 format.</strong></p>
<table border width="80%">
<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="10%">0</td>
<td align="center" valign="top" width="10%">0</td>
<td align="left" valign="top" width="20%">CHAR(10)</td>
<td align="left" valign="top" width="60%">Job name</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">User name</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Job number</td>
</tr>
<tr>
<td align="center" valign="top">26</td>
<td align="center" valign="top">1A</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Internal job identifier</td>
</tr>
<tr>
<td align="center" valign="top">42</td>
<td align="center" valign="top">2A</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">44</td>
<td align="center" valign="top">2C</td>
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
<td align="left" valign="top">Thread handle</td>
</tr>
<tr>
<td align="center" valign="top">48</td>
<td align="center" valign="top">30</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Thread identifier</td>
</tr>
</table>
<br>
<br>
<h3>Field Descriptions</h3>
<p><strong>Internal job identifier.</strong> The internal identifier for the
job. The List Job (QUSLJOB) API returns this identifier. If you do not specify
*INT for the job name parameter, this parameter must contain blanks. With this
parameter, the system can locate the job more quickly than with a job name.</p>
<p><strong>Job name.</strong> A specific job name or one of the following
special values:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>*</em></td>
<td align="left" valign="top">The job that this program is running in. The job
number and user name must contain blanks.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*INT</em></td>
<td align="left" valign="top">The internal job identifier locates the job. The
job number and user name must contain blanks.</td>
</tr>
</table>
<p><strong>Job number.</strong> A specific job number, or blanks when the job
name specified is a special value.</p>
<p><strong>Reserved.</strong> An unused field. This field must contain
hexadecimal zeros.</p>
<p><strong>Thread handle.</strong> A value that addresses a particular thread
within a job. While the thread identifier uniquely identifies the thread within
the job, the thread handle can improve performance when referencing the thread.
A valid thread handle must be specified. The thread handle is returned on
several other interfaces.</p>
<p><strong>Thread identifier.</strong> A value which uniquely identifies a
thread within a job. A valid thread identifier must be specified.</p>
<p><strong>User name.</strong> A specific user profile name, or blanks when the
job name specified is a special value.</p>
<br>
<h3><a name="Header_19">Usage Notes</a></h3>
<p><strong>How to determine the format to use</strong></p>
<p>The JOBC0100 format is to be used to change an attribute that is scoped to
the job. This format will change the attribute for either the job that the
request is issued from or for any other job that is on the system.</p>
<p>The JOBC0200 format is to be used to change an attribute for the thread that
the request is being issued from. This will change the attribute at the thread
level for attributes that are scoped to the thread and will change the
attribute at the job level for attributes that are scoped to the job. For
attributes that are scoped to the thread, there may be multiple threads active
when the change is requested. The change will only affect the current thread.
The other active threads will not be affected by the change. The attributes
that are scoped to the job may only be changed if there are no secondary
threads active, so as to not affect other threads. If a job attribute needs to
be changed by a secondary thread or while secondary threads are active, the
JOBC0100 format should be used.</p>
<p>The JOBC0300 format may be used after a set user profile has been done with
the Set Profile (QWTSETP) API. This format will perform job-initialization type
activities. When a job is started, information for various attributes is
retrieved from the user profile that the job is starting under. This format
will perform a similar function for either the user profile that the thread is
currently running under or for the user profile that the thread was initiated
under. For attributes that are scoped to the thread, if this format is called
with multiple threads active, the change will only affect the current thread.
Attributes that are scoped to the job may only be changed if there are no
secondary threads active.</p>
<p>The JOBC0400 format is to be used to change an attribute that is scoped to
the thread. It allows changing a thread other than the current thread as well
as the current thread.</p>
<br>
<p><strong>Considerations for attribute scope and thread safety</strong></p>
<p>In the <a href="#TBLCHGASTS">Attribute Scope and Thread Safety</a> table,
the <em>Attribute</em> column shows the key identifier and the text description
for the attribute.</p>
<p>The <em>Scope</em> column shows whether the attribute is scoped to the job
or to the thread. Attributes changed with this API may be scoped to the job or
to the current thread. Some attributes that are scoped to the job could be
moved to the thread level in a future release. If that were to occur, this API
would be updated to change the thread attribute.</p>
<p>The <em>Format</em> columns indicate whether the attributes are considered
to be threadsafe when being changed for that format.</p>
<p>The following describes the terminology used in the <em>Format</em>
columns:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><strong>Threadsafe</strong></td>
<td align="left" valign="top">In general threads terminology, indicates that an
interface may be called safely from either an initial thread or a secondary
thread. For this particular API, <em>threadsafe</em> indicates that an
attribute can always be changed and can be considered correct.
<p>The API may be called from the initial or secondary thread to change the
attributes of the current job or a different job. The job whose attributes are
being changed may be either single threaded or multithreaded.</p>
<p><strong>Note:</strong> When attributes that are marked <em>threadsafe</em>
and are scoped to the job are changed, the change will affect all threads that
are running under that job.</p>
</td>
</tr>
<tr>
<td align="left" valign="top" nowrap><strong>Single threaded only</strong></td>
<td align="left" valign="top">In general threads terminology, indicates that an
interface may be called safely only while the job is running single threaded
(that is, no secondary threads are active). For this particular API, an
attribute marked as <em>single threaded only</em> indicates that the attribute
can only be changed by that format when changing one's own attribute and there
are no other threads active. The change will not be allowed if the target job
is multithreaded.</td>
</tr>
<tr>
<td align="left" valign="top"><strong>No</strong></td>
<td align="left" valign="top">The attribute may not be changed safely. The
change will not be allowed if multiple threads are active in the job calling
this API or in the target job.</td>
</tr>
<tr>
<td align="left" valign="top"><strong>Blank</strong></td>
<td align="left" valign="top">The attribute is not supported for this
request.</td>
</tr>
</table>
<br>
<br>
<table border width="80%">
<tr>
<th align="left" valign="bottom" colspan="6"><a name="TBLCHGASTS"><em>Attribute
Scope and Thread Safety</em></a></th>
</tr>
<tr>
<th align="left" valign="bottom">Attribute</th>
<th align="left" valign="bottom">Scope</th>
<th align="left" valign="bottom">JOBC0100</th>
<th align="left" valign="bottom">JOBC0200</th>
<th align="left" valign="bottom">JOBC0300</th>
<th align="left" valign="bottom">JOBC0400</th>
</tr>
<tr>
<td align="left" valign="top" width="25%">0104: ASP group information</td>
<td align="left" valign="top" width="15%">Current thread</td>
<td align="left" valign="top" width="15%">&nbsp;</td>
<td align="left" valign="top" width="15%">&nbsp;</td>
<td align="left" valign="top" width="15%">Threadsafe</td>
<td align="left" valign="top" width="15%">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0201: Break message handling</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0302: Coded character set ID</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0303: Country or region ID</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0310: Current library</td>
<td align="left" valign="top">Current thread</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0311: Character identifier control</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0318: Client IP address - IPv4 (job)</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Initial thread only<sup>1</sup></td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0405: Date format</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0406: Date separator</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0408: DDM conversation</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0409: Default wait</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0410: Device recovery action</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0413: Decimal format</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0801: Home directory</td>
<td align="left" valign="top">Current thread</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0901: Inquiry message reply</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">0910: Initial library list</td>
<td align="left" valign="top">Current thread</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1001: Job accounting code</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1002: Job date</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1004: Job queue name - qualified</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1005: Job queue priority</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1006: Job switches</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1007: Job message queue full action</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">
<img src="delta.gif" alt="Start of change">1018: Job log output</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;
<img src="deltaend.gif" alt="End of change"></td>
</tr>
<tr>
<td align="left" valign="top">1201: Language ID</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1202: Logging level</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1203: Logging of CL programs</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1204: Logging severity</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1205: Logging text</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1210: Locale</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1501: Output queue name</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1501: Output queue name - qualified</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1502: Output queue priority</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1601: Print key format</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1602: Print text</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1603: Printer device name</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1604: Purge</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1802: Run priority (job)</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1802: Run priority (job)</td>
<td align="left" valign="top">Current thread</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1804: Run priority (thread)</td>
<td align="left" valign="top">Current thread</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1804: Run priority (thread)</td>
<td align="left" valign="top">Thread</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Threadsafe</td>
</tr>
<tr>
<td align="left" valign="top">1901: Sort sequence table</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1901: Sort sequence table - qualified</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1902: Status message handling</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1911: Server type</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1920: Schedule date</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1921: Schedule time</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">No</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1922: Server mode for Structured Query
Language</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">1982: Spooled file action</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">2001: Time separator</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">2002: Time slice</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">2003: Time-slice end pool</td>
<td align="left" valign="top">Job</td>
<td align="left" valign="top">Threadsafe</td>
<td align="left" valign="top">Single threaded only</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top">2701: All keys for JOBC0300 format</td>
<td align="left" valign="top">See the specific keys in this table</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">&nbsp;</td>
<td align="left" valign="top">See the specific keys in this table</td>
<td align="left" valign="top">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" colspan="6">
<table cellpadding="3">
<tr>
<td align="left" valign="top"><sup>1</sup></td>
<td align="left" valign="top">A change to this attribute in a secondary thread
is possible; however, it is essentially meaningless as only the attribute for
the inital thread can be retrieved using the Retrieve Job Information
(QUSRJOBI) API. This key has no correlation to the attribute set by the system.
For further information on retrieving the <em>Client IP address - IPv4 or
IPv6</em> that has been implicity set by the operating system, see the <a href=
"qwtrtvta.htm"> Retrieve Thread Attribute</a> (QWTRTVTA) API.</td>
</tr>
</table>
</td>
</tr>
</table>
<br>
<br>
<h3>Error Messages</h3>
<table width="100%" cellpadding="5">
<!-- cols="15 85" -->
<tr>
<th align="left" valign="top" nowrap>Message ID</th>
<th align="left" valign="top">Error Message Text</th>
</tr>
<tr>
<td align="left" valign="top">CPD0912 D</td>
<td align="left" valign="top">Printer device &amp;1 not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPD1102 D</td>
<td align="left" valign="top">Change to &amp;1 only allowed for interactive
jobs.</td>
</tr>
<tr>
<td align="left" valign="top">CPD1104 D</td>
<td align="left" valign="top">Changing &amp;1 to *WRKSTN only allowed for
interactive jobs.</td>
</tr>
<tr>
<td align="left" valign="top">CPD1612 D</td>
<td align="left" valign="top">Not able to allocate job description &amp;1 in
&amp;2.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1075 D</td>
<td align="left" valign="top">Job description &amp;1 in &amp;2 is not
found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1077 D</td>
<td align="left" valign="top">Not authorized to job description &amp;1 in
library &amp;2.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1134 D</td>
<td align="left" valign="top">Job &amp;3/&amp;2/&amp;1 priority &amp;4 exceeds
priority limit &amp;5.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1135 D</td>
<td align="left" valign="top">Job &amp;3/&amp;2/&amp;1 output priority &amp;4
exceeds priority limit &amp;5.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1144 D</td>
<td align="left" valign="top">Job queue &amp;1 in library &amp;2 not
found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1145 D</td>
<td align="left" valign="top">Job queue &amp;1 in library &amp;2 not
accessible.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1146 D</td>
<td align="left" valign="top">User &amp;1 not authorized to job queue &amp;2 in
library &amp;3.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1156 D</td>
<td align="left" valign="top">Job &amp;3/&amp;2/&amp;1 job switch &amp;4 not
valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1160 D</td>
<td align="left" valign="top">Job priority not changed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1252 D</td>
<td align="left" valign="top">Output queue &amp;1 in library &amp;2 not
found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1253 D</td>
<td align="left" valign="top">Output queue &amp;1 in library &amp;2 not
accessible.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1254 D</td>
<td align="left" valign="top">User &amp;1 not authorized to output queue &amp;2
in library &amp;3.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1255 D</td>
<td align="left" valign="top">Output queue library &amp;2 not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1264 E</td>
<td align="left" valign="top">User profile for user name &amp;1 not
accessible.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1317 E</td>
<td align="left" valign="top">No response from subsystem for job
&amp;3/&amp;2/&amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1321 E</td>
<td align="left" valign="top">Job &amp;1 user &amp;2 job number &amp;3 not
found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1334 D</td>
<td align="left" valign="top">BRKMSG(*NOTIFY) only valid for interactive
jobs.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1335 D</td>
<td align="left" valign="top">Job queue not changed. Job &amp;3/&amp;2/&amp;1
not batch job.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1337 E</td>
<td align="left" valign="top">&amp;3/&amp;2/&amp;1 not authorized to change
parameters.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1339 D</td>
<td align="left" valign="top">Job queue not changed. Job &amp;3/&amp;2/&amp;1
not on job queue.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1340 E</td>
<td align="left" valign="top">Job control function not performed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1343 E</td>
<td align="left" valign="top">Job &amp;3/&amp;2/&amp;1 not valid job type for
function.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1344 E</td>
<td align="left" valign="top">Not authorized to control job
&amp;3/&amp;2/&amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1351 E</td>
<td align="left" valign="top">Function check occurred in subsystem for job
&amp;3/&amp;2/&amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1352 E</td>
<td align="left" valign="top">Function not done. &amp;3/&amp;2/&amp;1 in
transition condition.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1618 E</td>
<td align="left" valign="top">Job description &amp;1 in library &amp;2
damaged.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1635 D</td>
<td align="left" valign="top">Requested change no longer allowed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1644 D</td>
<td align="left" valign="top">Scheduled date and time not changed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1650 D</td>
<td align="left" valign="top">Both scheduled date and time must be
changed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1651 E</td>
<td align="left" valign="top">Sort sequence table not accessed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF180C E</td>
<td align="left" valign="top">Function &amp;1 not allowed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1846 D</td>
<td align="left" valign="top">CHGJOB did not complete. System value not
available.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1854 E</td>
<td align="left" valign="top">Value &amp;1 for CCSID not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF188F E</td>
<td align="left" valign="top">Not authorized to change job accounting
code.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1893 E</td>
<td align="left" valign="top">Errors occurred while changing job
&amp;3/&amp;2/&amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1895 D</td>
<td align="left" valign="top">Incorrect format specified with the internal job
identifier.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1896 D</td>
<td align="left" valign="top">Incorrect job name specified.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1897 D</td>
<td align="left" valign="top">Data for key field &amp;1 not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1898 D</td>
<td align="left" valign="top">Key field &amp;1 not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF1899 D</td>
<td align="left" valign="top">No other key allowed when specifying key
&amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF189A D</td>
<td align="left" valign="top">Reserved field must be blanks.</td>
</tr>
<tr>
<td align="left" valign="top">CPF189B D</td>
<td align="left" valign="top">Length field not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF189C D</td>
<td align="left" valign="top">&amp;1 not valid for the data type field.</td>
</tr>
<tr>
<td align="left" valign="top">CPF189E D</td>
<td align="left" valign="top">Key field &amp;1 not valid with format
&amp;2.</td>
</tr>
<tr>
<td align="left" valign="top">CPF189F D</td>
<td align="left" valign="top">Request not completed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF18BF E</td>
<td align="left" valign="top">Thread &amp; not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF24B4 E</td>
<td align="left" valign="top">Severe error while addressing parameter
list.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C21 E</td>
<td align="left" valign="top">Format name &amp;1 is not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C36 E</td>
<td align="left" valign="top">Number of parameters, &amp;1, entered for this
API was not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C3B E</td>
<td align="left" valign="top">Value for parameter &amp;2 for API &amp;1 not
valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C51 E</td>
<td align="left" valign="top">Internal job identifier not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C52 E</td>
<td align="left" valign="top">Internal job identifier no longer valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C58 E</td>
<td align="left" valign="top">Job name specified is not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C59 E</td>
<td align="left" valign="top">Internal identifier is not blanks and job name is
not *INT.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C88 E</td>
<td align="left" valign="top">Number of variable length records &amp;1 is not
valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3CF1 E</td>
<td align="left" valign="top">Error code parameter not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF8100 E</td>
<td align="left" valign="top">All CPF81xx messages could be returned. xx is
from 01 to FF.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9800 E</td>
<td align="left" valign="top">All CPF98xx messages could be signaled. xx is
from 01 to FF.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9801 E</td>
<td align="left" valign="top">Object &amp;2 in library &amp;3 not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9802 E</td>
<td align="left" valign="top">Not authorized to object &amp;2 in &amp;3.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9803 E</td>
<td align="left" valign="top">Cannot allocate object &amp;2 in library
&amp;3.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9807 E</td>
<td align="left" valign="top">One or more libraries in library list
deleted.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9808 E</td>
<td align="left" valign="top">Cannot allocate one or more libraries on library
list.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9810 E</td>
<td align="left" valign="top">Library &amp;1 not found.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9820 E</td>
<td align="left" valign="top">Not authorized to use library &amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9830 E</td>
<td align="left" valign="top">Cannot assign library &amp;1.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9838 E</td>
<td align="left" valign="top">User profile storage limit exceeded.</td>
</tr>
<tr>
<td align="left" valign="top">CPF9872 E</td>
<td align="left" valign="top">Program or service program &amp;1 in library
&amp;2 ended. Reason code &amp;3.</td>
</tr>
<tr>
<td align="left" valign="top">CPFB8E9 E</td>
<td align="left" valign="top">ASP group &amp;1 not set for thread &amp;2.</td>
</tr>
</table>
<br>
<hr>
API introduced: V4R2
<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