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

2853 lines
85 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>Retrieve Program Temporary Fix Information (QPZRTVFX) 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. -->
<!-- QPZRTVFX SCRIPT A converted by B2H R4.1 (346) (CMS) by KENTALA -->
<!-- at RCHVMW2 on 7 Oct 1998 at 20:34:56 -->
<!-- Change History: -->
<!-- YYMMDD USERID Change description -->
<!-- Edited by Kersten Jan 02 -->
<!--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>Retrieve Program Temporary Fix Information (QPZRTVFX) 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="50%">Receiver variable</td>
<td align="left" valign="top" width="20%">Output</td>
<td align="left" valign="top" width="20%">Char(*)</td>
</tr>
<tr>
<td align="center" valign="top">2</td>
<td align="left" valign="top">Length of receiver variable</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Binary(4)</td>
</tr>
<tr>
<td align="center" valign="top">3</td>
<td align="left" valign="top">PTF information</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(50)</td>
</tr>
<tr>
<td align="center" valign="top">4</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">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;Default Public Authority: *USE<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Threadsafe: No<br>
<!-- iddvc RMBR -->
<br>
</div>
<p>The Retrieve Program Temporary Fix Information (QPZRTVFX) API returns
information about a specific program temporary fix (PTF). The information
returned is determined by the format specified.</p>
<p>You can use the QPZRTVFX API to:</p>
<ul>
<li>Retrieve basic information about a PTF.</li>
<li>Retrieve the cover letter information for a PTF.</li>
<li>Retrieve the requisites for a PTF.</li>
<li>Retrieve the list of objects for a PTF.</li>
<li>Retrieve the dependents for a PTF.</li>
<li>Retrieve the list of APARs for a PTF.</li>
<li>Retrieve the list of symptom strings for a PTF.</li>
<li>Retrieve the list of exit programs for a PTF.</li>
<li>Retrieve the preconditions for a PTF.</li>
<li>Retrieve the superseded PTF
IDs for a PTF.</li>
</ul>
<br>
<h3>Authorities and Locks</h3>
<dl>
<dt><strong>None.</strong></dt>
</dl>
<p>Lock conflicts may occur if this API is called while another PTF operation
is in progress.</p>
<br>
<h3>Required Parameter Group</h3>
<dl>
<dt><strong>Receiver variable</strong></dt>
<dd>OUTPUT; CHAR(*)
<p>The receiver variable that is to receive the information requested. The
length of this area must be passed in the length of receiver variable
parameter. The API returns only the data the area can hold.</p>
</dd>
<dt><strong>Length of receiver variable</strong></dt>
<dd>INPUT; Binary(4)
<p>The length of the receiver variable. You can specify a smaller area than the
format requested as long as you specify the length of receiver variable
parameter correctly. If the length specified is larger than the size of the
receiver variable, the results are not predictable. This value must be greater
than or equal to 8.</p>
</dd>
<dt><strong>PTF information</strong></dt>
<dd>INPUT; CHAR(50)
<p>The attributes of the PTF for which information is being requested. For more
information on this parameter see <a href="#HDRPTFINF4">Format of PTF
Information</a>.</p>
</dd>
<dt><strong>Format name</strong></dt>
<dd>INPUT; CHAR(8)
<p>The content and format of the information returned for the PTF. The possible
format names are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>PTFR0100</em></td>
<td align="left" valign="top">Basic information; for details, see <a href=
"#HDRPTFLIP1">PTFR0100 Format</a>.<br>
<br>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR0200</em></td>
<td align="left" valign="top">This format contains the basic information as
well as an array of cover letters in the format given. If the receiver variable
does not have enough space for all the cover letters to be returned, only the
cover letters that fit in the space provided are returned. For details, see <a
href="#HDRPTFLLH1">PTFR0200 Format</a>.<br>
<br>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR0300</em></td>
<td align="left" valign="top">This contains the basic information plus an array
that contains information about the requisite PTFs. If the receiver variable
does not have enough space to return all requisite information, only the
information that fits in the space provided is returned. For details, see <a
href="#HDRPTFLLH2">PTFR0300 Format</a>.<br>
<br>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR0400</em></td>
<td align="left" valign="top">This contains the basic information plus an array
that contains a list of the PTF objects and their alternative names. If the
receiver variable does not have enough space to return all of the PTF object
information, only the information that fits in the space provided is returned.
For details, see <a href="#HDRPTFLLH3">PTFR0400 Format</a>.<br>
<br>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR0500</em></td>
<td align="left" valign="top">This contains the basic information plus an array
that contains information about the dependent PTFs. If the receiver variable
does not have enough space to return all dependent information, only the
information that fits in the space provided is returned. For details, see <a
href="#HDRPTFLLH4">PTFR0500 Format</a>.<br>
<br>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR0600</em></td>
<td align="left" valign="top">This contains the basic information plus an array
that contains information about the APAR numbers. If the receiver variable does
not have enough space to return all APAR information, only the information that
fits in the space provided is returned. For details, see <a href=
"#HDRPTFLLH6">PTFR0600 Format</a>.<br>
<br>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR0700</em></td>
<td align="left" valign="top">This contains the basic information plus an array
that contains information about the symptom strings. If the receiver variable
does not have enough space to return all symptom string information, only the
information that fits in the space provided is returned. For details, see <a
href="#HDRPTFLLH7">PTFR0700 Format</a>.<br>
<br>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR0800</em></td>
<td align="left" valign="top">This contains the basic information plus an array
that contains the exit program information. If the receiver variable does not
have enough space to return all exit program information, only the information
that fits in the space provided is returned. For details, see <a href=
"#HDRPTFLLH8">PTFR0800 Format</a>.<br>
<br>
</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR0900</em></td>
<td align="left" valign="top">This contains the basic information plus an array
that contains the information about the preconditions. If the receiver variable
does not have enough space to return the precondition information, only the
information that fits in the space provided is returned. For details, see <a
href="#HDRPTFLLH9">PTFR0900 Format</a>.</td>
</tr>
<tr>
<td align="left" valign="top"><em>PTFR1000</em></td>
<td align="left" valign="top">This contains the basic information plus an array
that contains the information about the superseded PTFs. If the receiver
variable does not have enough space to return the superseded PTF information,
only the information that fits in the space provided is returned. For details,
see <a href="#HDRPTFLLHA">PTFR1000 Format</a>.</td>
</tr>
</table>
</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><a name="HDRPTFINF4">Format of PTF Information</a></h3>
<p>For detailed descriptions of each field, see <a href="#HDRRTVPTFD">Field
Descriptions</a>.</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(7)</td>
<td align="left" valign="top" width="60%">PTF ID</td>
</tr>
<tr>
<td align="center" valign="top">7</td>
<td align="center" valign="top">7</td>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Product ID</td>
</tr>
<tr>
<td align="center" valign="top">14</td>
<td align="center" valign="top">E</td>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Release level</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">CCSID for returned directory names</td>
</tr>
<tr>
<td align="center" valign="top">24</td>
<td align="center" valign="top">18</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Close PTF database files</td>
</tr>
<tr>
<td align="center" valign="top">25</td>
<td align="center" valign="top">19</td>
<td align="left" valign="top">CHAR(25)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRRTVPTFD">Field Descriptions</a></h3>
<p><strong>CCSID for returned directory names.</strong> The CCSID in which the
directory names should be returned. If this field is blank, the CCSID is the
job default CCSID. This value is used only for returned directory names.</p>
<p><strong>Close PTF database files.</strong> Whether the PTF database files
should remain open after returning from the API call. This field allows for
improved performance when this API is called numerous times during processing.
Do not leave the PTF database files open for long periods of time because other
PTF operations cannot be performed while these files are open. If a blank is
specified in this field, it will be treated as a 0.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The PTF database files will be closed before
returning from the API call.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF database files will remain open until the
API is called again with this field set to 0.</td>
</tr>
</table>
<p><strong>Product ID.</strong> The product ID for the PTF for which
information is requested. The possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*ONLY</em></td>
<td align="left" valign="top">The product ID is not known, but only one PTF
exists on the system by this PTF ID.</td>
</tr>
<tr>
<td align="left" valign="top"><em>product ID</em></td>
<td align="left" valign="top">The product ID for the PTF.</td>
</tr>
</table>
<p><strong>PTF ID.</strong> The identifier of the PTF for which information is
requested.</p>
<p><strong>Release level.</strong> The release of the PTF for which information
is requested. This field is ignored if *ONLY is specified in the product ID
field. The format is:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>VxRyMz</em></td>
<td align="left" valign="top">The release of the PTF is in the format VxRyMz.
Valid entries for x and y are any number between 0 and 9. A valid entry for z
is a number between 0 and 9 or a character between A and Z.</td>
</tr>
</table>
<p><strong>Reserved.</strong> This field must contain blanks.</p>
<br>
<h3><a name="HDRPTFLIP1">PTFR0100 Format</a></h3>
<p>This format returns basic information about the PTF. For detailed
descriptions of each field, see <a href="#HDRFISHY">Field Descriptions</a>.</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%">BINARY(4)</td>
<td align="left" valign="top" width="60%">Bytes returned</td>
</tr>
<tr>
<td align="center" valign="top">4</td>
<td align="center" valign="top">4</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Bytes available</td>
</tr>
<tr>
<td align="center" valign="top">8</td>
<td align="center" valign="top">8</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to additional information</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Product ID</td>
</tr>
<tr>
<td align="center" valign="top">19</td>
<td align="center" valign="top">13</td>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">PTF ID</td>
</tr>
<tr>
<td align="center" valign="top">26</td>
<td align="center" valign="top">1A</td>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Release level</td>
</tr>
<tr>
<td align="center" valign="top">32</td>
<td align="center" valign="top">20</td>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Product option</td>
</tr>
<tr>
<td align="center" valign="top">36</td>
<td align="center" valign="top">24</td>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Load ID</td>
</tr>
<tr>
<td align="center" valign="top">40</td>
<td align="center" valign="top">28</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Loaded status</td>
</tr>
<tr>
<td align="center" valign="top">41</td>
<td align="center" valign="top">29</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Cover letter status</td>
</tr>
<tr>
<td align="center" valign="top">42</td>
<td align="center" valign="top">2A</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">On-order status</td>
</tr>
<tr>
<td align="center" valign="top">43</td>
<td align="center" valign="top">2B</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Save file status</td>
</tr>
<tr>
<td align="center" valign="top">44</td>
<td align="center" valign="top">2C</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">File name</td>
</tr>
<tr>
<td align="center" valign="top">54</td>
<td align="center" valign="top">36</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">File library name</td>
</tr>
<tr>
<td align="center" valign="top">64</td>
<td align="center" valign="top">40</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">PTF type</td>
</tr>
<tr>
<td align="center" valign="top">65</td>
<td align="center" valign="top">41</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">IPL action</td>
</tr>
<tr>
<td align="center" valign="top">66</td>
<td align="center" valign="top">42</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Action pending</td>
</tr>
<tr>
<td align="center" valign="top">67</td>
<td align="center" valign="top">43</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Action required</td>
</tr>
<tr>
<td align="center" valign="top">68</td>
<td align="center" valign="top">44</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">PTF is released</td>
</tr>
<tr>
<td align="center" valign="top">69</td>
<td align="center" valign="top">45</td>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Target release</td>
</tr>
<tr>
<td align="center" valign="top">75</td>
<td align="center" valign="top">4B</td>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Superseding PTF</td>
</tr>
<tr>
<td align="center" valign="top">82</td>
<td align="center" valign="top">52</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Current IPL source</td>
</tr>
<tr>
<td align="center" valign="top">83</td>
<td align="center" valign="top">53</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Minimum level</td>
</tr>
<tr>
<td align="center" valign="top">85</td>
<td align="center" valign="top">55</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Maximum level</td>
</tr>
<tr>
<td align="center" valign="top">87</td>
<td align="center" valign="top">57</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Format information available</td>
</tr>
<tr>
<td align="center" valign="top">88</td>
<td align="center" valign="top">58</td>
<td align="left" valign="top">CHAR(13)</td>
<td align="left" valign="top">Status date and time</td>
</tr>
<tr>
<td align="center" valign="top">101</td>
<td align="center" valign="top">65</td>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Licensed Internal Code group</td>
</tr>
<tr>
<td align="center" valign="top">108</td>
<td align="center" valign="top">6C</td>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Superseded by PTF ID</td>
</tr>
<tr>
<td align="center" valign="top">115</td>
<td align="center" valign="top">73</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Current server IPL source
</td>
</tr>
<tr>
<td align="center" valign="top">116</td>
<td align="center" valign="top">74</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Server IPL required
</td>
</tr>
<tr>
<td align="center" valign="top">117</td>
<td align="center" valign="top">75</td>
<td align="left" valign="top">CHAR(13)</td>
<td align="left" valign="top">Creation date and time
</td>
</tr>
<tr>
<td align="center" valign="top">130</td>
<td align="center" valign="top">82</td>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">
Reserved
</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLH1">PTFR0200 Format</a></h3>
<p>The fields that follow the cover letter records field define an entry in
that array. That group of fields is repeated by the number of different NLVs
available for the cover letter field. For detailed descriptions of each field,
see <a href="#HDRFISHY">Field Descriptions</a>.</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%">&nbsp;</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to first cover letter record from the
beginning</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of different NLVs available for the cover
letter</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of cover letter record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to
first cover letter of format PTFR0200.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="8" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">Cover letter records</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Cover letter national language version (NLV)</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Cover letter file name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Cover letter library name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Cover letter member name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Pre-apply or pre-remove considerations</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Post-apply or post-remove considerations</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLH2">PTFR0300 Format</a></h3>
<p>The fields following the requisite record field define an entry in that
array. That group of fields is repeated by the number of requisites. For
detailed descriptions of each field, see<a href="#HDRFISHY">Field
Descriptions</a>.</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%">&nbsp;</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to first requisite record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of requisites</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of requisite record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to
first requisite record of format PTFR0300.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="12" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">Requisite record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Requisite product ID</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Requisite PTF ID</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Release of requisite</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Requisite minimum level</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Requisite maximum level</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Type of requisite</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Requisite is conditional</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Requisite is required</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Requisite option</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Requisite load ID</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLH3">PTFR0400 Format</a></h3>
<p>The fields following the PTF object record field define an entry in that
array. That group of fields is repeated by the number of PTF objects. If a PTF
contains subobjects, an offset to an array of subobjects is provided. The
subobject fields are repeated by the number of PTF subobjects. For detailed
descriptions of each field, see <a href="#HDRFISHY">Field Descriptions</a>.</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%"><br>
</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="6" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to the first PTF object record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of PTF objects</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of PTF object record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">CCSID of returned directories</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Error indicator for CCSID conversion</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
first PTF object record of format PTFR0400.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="9" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">PTF object record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to this PTF object's first subobject
record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of PTF subobjects</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of subobject record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Object name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Object library</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Alternative object name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Object type</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to this
PTF object's first subobject record of format PTFR0400.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="5" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">PTF subobject record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to subobject name</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of subobject name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Subobject attribute</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
subobject name in the subobject array record of format PTFR0400.</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Subobject name</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLH4">PTFR0500 Format</a></h3>
<p>The fields following the dependent record field define an entry in that
array. That group of fields is repeated by the number of dependents. For
detailed descriptions of each field, see <a href="#HDRFISHY">Field
Descriptions</a>.</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%">&nbsp;</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to first dependent PTF record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of dependent PTFs</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of dependent PTF record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to
first dependent PTF record of format PTFR0500.</td>
</tr>
<tr>
<td align="left" valign="top" rowspan="10" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">Dependent PTF record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Dependent product ID</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Dependent PTF ID</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(6)</td>
<td align="left" valign="top">Release of dependent PTF</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Dependent minimum level</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Dependent maximum level</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Type of dependent PTF</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Dependent option</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(4)</td>
<td align="left" valign="top">Dependent load ID</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLH6">PTFR0600 Format</a></h3>
<p>The fields following the APAR record field define an entry in that array.
That group of fields is repeated by the number of APAR records. For detailed
descriptions of each field, see <a href="#HDRFISHY">Field Descriptions</a>.</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%">&nbsp;</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to first APAR record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of APAR records</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of APAR record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
first APAR record of format PTFR0600.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="3" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">APAR record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">APAR number</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLH7">PTFR0700 Format</a></h3>
<p>The fields following the symptom string record field define an entry in that
array. That group of fields is repeated by the number of symptom string
records. For detailed descriptions of each field, see <a href="#HDRFISHY">Field
Descriptions</a>.</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%">&nbsp;</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to first symptom string record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of symptom string records</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of symptom string record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
first symptom string record of format PTFR0700.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">Symptom string record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to symptom string data</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of symptom string data</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
symptom string data of format PTFR0700.</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Symptom string data</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLH8">PTFR0800 Format</a></h3>
<p>The fields following the exit program record field define an entry in that
array. That group of fields is repeated by the number of exit programs. For
detailed descriptions of each field, see <a href="#HDRFISHY">Field
Descriptions</a>.</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%">&nbsp;</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to first exit program record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of exit program records</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of exit program record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
first exit program record of format PTFR0800.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="7" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">Exit program record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to exit program user data</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of exit program user data</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Exit program name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Exit program library</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Exit program run option</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
exit program user data of format PTFR0800.</td>
</tr>
<tr>
<td align="center" valign="top">&nbsp;</td>
<td align="center" valign="top">&nbsp;</td>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Exit program user data</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLH9">PTFR0900 Format</a></h3>
<p>The fields following the precondition record field define an entry in that
array. That group of fields is repeated by the number of precondition records.
For detailed descriptions of each field, see <a href="#HDRFISHY">Field
Descriptions</a>.</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%">&nbsp;</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to first precondition record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of precondition records</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of precondition record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
first precondition record of format PTFR0900.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="6" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">Precondition record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Precondition type</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Precondition name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Precondition library name</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRPTFLLHA">PTFR1000 Format</a></h3>
<p>The fields following the superseded PTF record field define an entry in that
array. That group of fields is repeated by the number of superseded PTF
records. For detailed descriptions of each field, see <a href="#HDRFISHY">Field
Descriptions</a>.</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%">&nbsp;</td>
<td align="left" valign="top" width="60%">All information from format
PTFR0100</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are reached by using the offset to additional
information field in format PTFR0100.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="4" colspan="2">&nbsp;</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to first superseded PTF record</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of superseded PTF records</td>
</tr>
<tr>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Length of superseded PTF record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The decimal
and hexadecimal offsets are determined by using the value in the offset to the
first superseded PTF record of format PTFR1000.</td>
</tr>
<tr>
<td align="center" valign="top" rowspan="6" colspan="2">&nbsp;</td>
<td align="left" valign="top">ARRAY of CHAR(*)</td>
<td align="left" valign="top">Superseded PTF record</td>
</tr>
<tr>
<td align="left" valign="top">CHAR(7)</td>
<td align="left" valign="top">Superseded PTF ID</td>
</tr>
<tr>
<td></td>
</tr>
<tr>
<td align="left" valign="top">CHAR(*)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRFISHY">Field Descriptions</a></h3>
<p><strong>APAR number.</strong> The number of the APAR that is fixed when you
install this PTF.</p>
<p><strong>APAR record.</strong> The information about the APAR. The record is
an array that contains the fields in format PTFR0600.</p>
<p><strong>Action pending.</strong> Whether a required action has yet to be
performed to make this PTF active. This field reflects the current status of
any required actions. The following values are valid:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">No required actions are pending for this
PTF.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">A required action needs to occur for this PTF to
be active.
<p>Check the activation instructions section of the cover letter to determine
what the action is.</p>
<p>If the action required field is a 2 and you have performed the activation
instructions, then the PTF is active. However, this field will not be updated
until the next IPL.</p>
</td>
</tr>
</table>
<p><strong>Action required.</strong> Whether an action is required to make this
PTF active when it is applied. See the cover letter to determine what action
needs to be taken. The following values are valid.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">No activations instructions are needed for this
PTF.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">This PTF was shipped with activation instructions
in the cover letter. This PTF has an exit program to update the status of the
PTF after the activation instructions have been performed.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">This PTF was shipped with activation instructions
in the cover letter. No exit program exists to verify the activation
instructions were performed.</td>
</tr>
</table>
<p><strong>Alternative object name.</strong> The alternative name of the object
when the PTF is temporarily applied or temporarily removed. PTFs that have been
temporarily applied have alternative object names in the format of
QPZA<em>nnnnnn</em>; PTFs that are temporarily removed have alternative object
names in the format of QPZR<em>nnnnnn</em>, where <em>nnnnnn</em> is some
number. This field is blank for the following reasons:</p>
<ul>
<li>the PTF is not temporarily applied or is temporarily removed.</li>
<li>the object is a temporary object on the system; that is, an object name
that starts with QPZ1 or QPZ2.</li>
<li>the object was bypassed when the PTF was loaded.</li>
</ul>
<p><strong>Bytes available.</strong> The number of bytes of data available to
be returned to the user.</p>
<p><strong>Bytes returned.</strong> The number of bytes that were returned to
the user. This is the lesser of the number of bytes available to be returned or
the length of the receiver variable.</p>
<p><strong>CCSID of returned directories.</strong> The value of the CCSID in
which the directories were returned. This will be the requested CCSID if the
value of the CCSID conversion indicator is 0. This field is used only for
subobject attributes of DIR (directory) and SOM (system object model).</p>
<p><strong>Cover letter file name.</strong> The file containing the cover
letter member.</p>
<p><strong>Cover letter library name.</strong> The library containing the cover
letter file.</p>
<p><strong>Cover letter member name.</strong> The member containing the cover
letter.</p>
<p><strong>Cover letter national language version (NLV).</strong> The NLV
corresponds to a code that indicates the language in which the cover letter was
written. For more information on NLVs, see the <a href=
"../nls/rbagsglobalmain.htm">Globalization</a> topic in the iSeries Information
Center.</p>
<p><strong>Cover letter records.</strong> The record containing the cover
letter information.</p>
<p><strong>Cover letter status.</strong> Whether a cover letter exists for the
PTF. The following values are valid.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The PTF has no cover letter.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF has a cover letter.</td>
</tr>
</table>
<p><strong>Creation date and time.</strong> The date and time that the PTF was created.
This value will be blanks when the creation date and time cannot be determined.
The date and time field is in the CYYMMDDHHMMSS format:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>C</em></td>
<td align="left" valign="top">Century, where 0 indicates years 19xx and 1
indicates years 20xx.</td>
</tr>
<tr>
<td align="left" valign="top"><em>YY</em></td>
<td align="left" valign="top">Year</td>
</tr>
<tr>
<td align="left" valign="top"><em>MM</em></td>
<td align="left" valign="top">Month</td>
</tr>
<tr>
<td align="left" valign="top"><em>DD</em></td>
<td align="left" valign="top">Day</td>
</tr>
<tr>
<td align="left" valign="top"><em>HH</em></td>
<td align="left" valign="top">Hour</td>
</tr>
<tr>
<td align="left" valign="top"><em>MM</em></td>
<td align="left" valign="top">Minute</td>
</tr>
<tr>
<td align="left" valign="top"><em>SS</em></td>
<td align="left" valign="top">Second</td>
</tr>
</table>
<p><strong>Current IPL source.</strong> The copy of Licensed Internal Code that
the system is currently operating from. The previous IPL of the system used
this copy of Licensed Internal Code.</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>A</em></td>
<td align="left" valign="top">The system is currently operating on the A IPL
source.</td>
</tr>
<tr>
<td align="left" valign="top"><em>B</em></td>
<td align="left" valign="top">The system is currently operating on the B IPL
source.</td>
</tr>
<tr>
<td align="left" valign="top"><em>Blank</em></td>
<td align="left" valign="top">The current IPL source could not be determined.</td>
</tr>
</table>
<p><img src="delta.gif" alt="Start of change"><strong>Current server IPL source.</strong> The copy of the server firmware that was used on the previous server IPL.<img src="deltaend.gif" alt="End of change"></p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">There is no server IPL source because the system is not operating as a service partition.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The server is currently operating on the T server IPL source.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The server is currently operating on the P server IPL source.</td>
</tr>
</table>
<p><strong>Dependent load ID.</strong> The load ID of the dependent PTF. This
value is blank when the load ID of the dependent PTF cannot be determined.</p>
<p><strong>Dependent maximum level.</strong> The indicator of the highest level
of the product for which this PTF can be installed. This field will be blank if
the product has no level.</p>
<p><strong>Dependent minimum level.</strong> The indicator of the lowest level
of the product for which this PTF can be installed. This field will be blank if
the product has no level.</p>
<p><strong>Dependent option.</strong> The product option of the dependent PTF.
This value is blank when the option of the dependent PTF cannot be
determined.</p>
<p><strong>Dependent product ID.</strong> The product ID of the dependent
PTF.</p>
<p><strong>Dependent PTF ID.</strong> The PTF ID of the dependent PTF.</p>
<p><strong>Dependent PTF record.</strong> The information about the dependent
PTF. The record is an array that contains the fields in format PTFR0500.</p>
<p><strong>Error indicator about CCSID conversion.</strong> Whether the CCSID
conversion to the requested CCSID was successful. If the requested CCSID
conversion fails, the CCSID in which the directories are returned is identified
in the CCSID of returned directories field. This field is used only for
subobject attributes of DIR (directory) and SOM (system object model). Possible
values follow:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">CCSID conversion was successful.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">CCSID conversion failed.</td>
</tr>
</table>
<p><strong>Exit program library.</strong> The name of the library containing
the exit program.</p>
<p><strong>Exit program name.</strong> The name of a program that will be run
at certain stages of the PTF process.</p>
<p><strong>Exit program record.</strong> The information about the exit
program. The record is an array that contains the fields in format
PTFR0800.</p>
<p><strong>Exit program run option.</strong></p>
<p>The stage of the PTF process in which the exit program will be run. Possible
values follow:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">*ACTION - The exit program is called to determine
if there is action necessary to make the PTF active or inactive.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">*BOTH - The exit program will be run at the end
of apply and remove processing.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">*APPLY - The exit program will be run at the end
of apply processing.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">*REMOVE - The exit program will be run at the end
of remove processing.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">*PREAPY - The exit program will be run before the
PTF is applied and at the end of apply processing.</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em></td>
<td align="left" valign="top">*PRERMV - The exit program will be run before the
PTF is removed and at the end of remove processing.</td>
</tr>
<tr>
<td align="left" valign="top"><em>6</em></td>
<td align="left" valign="top">*PREBTH - The exit program will be run before the
PTF is removed and at the end of remove processing. It is also run before the
PTF is applied and at the end of apply processing.</td>
</tr>
</table>
<p><strong>File library name.</strong> The name of the library where the save
file for the PTF is located. If no save file name has been reserved, this field
will be blank.</p>
<p><strong>File name.</strong> The name of the file where the save file for the
PTF is located. If no save file name has been reserved, this field will be
blank.</p>
<p><strong>Format information available.</strong> When you request information
using formats PTFR0300, PTFR0400, PTFR0600, PTFR0700, PTFR0800, PTFR0900, or PTFR1000 this field indicates whether the system
has the information available to return for the PTF. The system may not be able
to return the requested information if the PTF is permanently applied or
superseded and does not have a save file. 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">There was not enough information available about
this PTF to return the requested data.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The information is available and complete. Refer
to specific format fields for the details.</td>
</tr>
</table>
<p><strong>IPL action.</strong> The action to be taken on this PTF during the
next IPL. The following values are valid:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">No action will occur at the next IPL.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF will be temporarily applied at the next
IPL.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The PTF will be temporarily removed at the next
IPL.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">The PTF will be permanently applied at the next
IPL.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">The PTF will be permanently removed at the next
IPL.</td>
</tr>
</table>
<p><strong>Length of APAR record.</strong> The length of each APAR record.</p>
<p><strong>Length of cover letter record.</strong> The length of each cover
letter record.</p>
<p><strong>Length of dependent PTF record.</strong> The length of each
dependent PTF record.</p>
<p><strong>Length of exit program record.</strong> The length of each exit
program record.</p>
<p><strong>Length of precondition record.</strong> The length of each
precondition record.</p>
<p><strong>Length of PTF object record.</strong> The length of one array
element in the PTF object record.</p>
<p><strong>Length of requisite record.</strong> The length of each requisite
record.</p>
<p><strong>Length of subobject name.</strong> The length of the subobject
name.</p>
<p><strong>Length of subobject record.</strong> The length of one array element
in the subobject record.</p>
<p><strong>Length of superseded
PTF record.</strong> The length of each superseded PTF record.</p>
<p><strong>Length of symptom string data.</strong> The length of the returned
symptom string.</p>
<p><strong>Length of symptom string record.</strong> The length of each symptom
string record.</p>
<p><strong>Length of exit program user data.</strong> The length of the
returned exit program user data string.</p>
<p><strong>Licensed Internal Code Group.</strong> The name of the Licensed
Internal Code Group for this PTF. If the name of the group is not available or
if the PTF is not a Licensed Internal Code fix, this field will be blank.</p>
<p><strong>Loaded status.</strong> The current loaded status of the PTF. A PTF
can have any of the following statuses:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The PTF has never been loaded.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF has been loaded.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The PTF has been applied.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">The PTF has been applied permanently.</td>
</tr>
<tr>
<td align="left" valign="top"><em>4</em></td>
<td align="left" valign="top">The PTF has been permanently removed.</td>
</tr>
<tr>
<td align="left" valign="top"><em>5</em></td>
<td align="left" valign="top">The PTF is damaged. An error occurred while
applying the PTF. It needs to be reloaded and applied.</td>
</tr>
<tr>
<td align="left" valign="top"><em>6</em></td>
<td align="left" valign="top">
The PTF is superseded. A PTF will have a status of superseded when one of the
following situations occurs :
<ul>
<li>Another PTF with a more recent correction for the problem has been loaded
on the system. The identifier of the PTF that has been loaded can be found in
the superseded by PTF ID field.</li>
<li>The PTF save file for another PTF with a more recent correction for the
problem has been logged into *SERVICE on the system. The most recent PTF ID
with a PTF save file that has been logged into *SERVICE can be found in the
superseding PTF field.</li>
</ul>
</td>
</tr>
</table>
<p><strong>Note:</strong> These fields are returned as numbers instead of text
because statuses are translatable text instead of special values. The text
message that contains these values is CPX3501.</p>
<p>This field may be blank.</p>
<p><strong>Load ID.</strong> The load ID of the product load for the PTF.</p>
<p><strong>Maximum level.</strong> The indicator of the highest level of the
product on which this PTF can be installed. If the minimum and maximum levels
are the same, then this PTF can only be installed on one level of the product.
The level can be AA to 99. This field will be blank if the product has no
level.</p>
<p><strong>Minimum level.</strong> The indicator of the lowest level of the
product on which this PTF can be installed. If the minimum and maximum levels
are the same, then this PTF can only be installed on one level of the product.
The level can be AA to 99. This field will be blank if the product has no
level.</p>
<p><strong>Number of APAR records.</strong> The number of returned APAR
records.</p>
<p>Check the format information available field returned in PTFR0100 before
using this value. The number of APARs will be zero when the system cannot
determine if this PTF has APARs.</p>
<p><strong>Number of dependent PTFs.</strong> The number of dependent PTFs
available. The receiver variable may not have been large enough to hold all the
dependent PTF records. If so, the number of dependents returned may be less
than this value.</p>
<p><strong>Number of different NLVs available for the cover letter.</strong>
Cover letter member names are returned in an array. This number indicates how
many NLVs were available for the cover letter. However, the length of the
receiver may not have been large enough to hold all the cover letter NLVs
available. If so, the number of cover letter member names returned may be less
than this value.</p>
<p><strong>Number of exit program records.</strong> The number of exit program
records. The receiver variable may not have been large enough to hold all the
exit program records. If so, the number of exit programs returned may be less
than this value.</p>
<p>Check the format information available field returned in PTFR0100 before
using this value. The number of exit programs will be zero when the system
cannot determine if this PTF has any exit programs.</p>
<p><strong>Number of precondition records.</strong> The number of returned
precondition records.</p>
<p>Check the format information available field returned in PTFR0100 before
using this value. The number of precondition records will be zero when the
system cannot determine if this PTF has preconditions.</p>
<p><strong>Number of PTF objects.</strong> The number of PTF objects available.
The receiver variable may not have been large enough to hold all the PTF object
records. If so, the number of PTF objects returned may be less than this
value.</p>
<p>Check the format information available field returned in PTFR0100 before
using this value. The number of objects will be zero when the system cannot
determine the number of objects contained in this PTF.</p>
<p><strong>Number of PTF subobjects.</strong> The number of PTF subobjects
associated with this PTF object. The receiver variable may not have been large
enough to hold all the PTF subobject records. If so, the number of PTF
subobjects returned may be less than this value.</p>
<p><strong>Number of requisites.</strong> The number of requisite PTFs
available. The receiver variable may not have been large enough to hold all the
requisite PTF records. If so, the number of requisites returned may be less
than this value.</p>
<p>Check the format information available field returned in PTFR0100 before
using this value. The number of requisites will be zero when the system cannot
determine if this PTF has requisite PTFs.</p>
<p><strong>Number of superseded
PTF records.</strong> The number of superseded PTF records. The receiver
variable may not have been large enough to hold all the superseded PTF records.
If so, the number of superseded PTFs returned may be less than this value.</p>
<p>Check the format information available field returned in PTFR0100 before
using this value. The number of superseded PTF records will be zero when the
system cannot determine if this PTF has any superseded PTFs.</p>
<p><strong>Number of symptom string records.</strong> The number of returned
symptom string records.</p>
<p>Check the format information available field returned in PTFR0100 before
using this value. The number of symptom strings will be zero when the system
cannot determine if this PTF has symptom strings.</p>
<p><strong>Object library.</strong> The primary library where PTF objects will
be placed for this product. If the product was installed in the primary
library, this is the library where the PTF objects will reside.</p>
<p><strong>Note:</strong> If the product was installed in a library other than
the primary library, the API user might need to determine the installed library
that corresponds to this primary library by using format PRDR0200 of the
Retrieve Product Information (QSZRTVPR) API.</p>
<p><strong>Object name.</strong> The name of the object that is contained in
the PTF.</p>
<p><strong>Object type.</strong> The symbolic type of the object that is
contained in the PTF.</p>
<p><strong>Offset to additional information.</strong> The offset from the
beginning of the receiver variable to the start of either the cover letter
information or the requisite information. This is to allow expansion of the
basic information.</p>
<p><strong>Offset to exit program user data.</strong> The offset from the
beginning of the receiver variable to the start of the exit program user
data.</p>
<p><strong>Offset to first APAR record.</strong> The offset from the beginning
of the receiver variable to the start of the APAR record.</p>
<p><strong>Offset to first cover letter record from the beginning.</strong> The
offset from the beginning of the receiver variable to the first cover letter
record.</p>
<p><strong>Offset to first dependent PTF record.</strong> The offset from the
beginning of the receiver variable to the start of the first dependent PTF
record.</p>
<p><strong>Offset to first exit program record</strong> The offset from the
beginning of the receiver variable to the start of the first exit program
record.</p>
<p><strong>Offset to first precondition record.</strong> The offset from the
beginning of the receiver variable to the first precondition record.</p>
<p><strong>Offset to first PTF object record.</strong> The offset from the
beginning of the receiver variable to the start of the PTF object record.</p>
<p><strong>Offset to first requisite record.</strong> The offset from the
beginning of the receiver variable to the start of the first requisite
record.</p>
<p><strong>Offset to first
superseded PTF record</strong> The offset from the beginning of the receiver
variable to the start of the first superseded PTF record.</p>
<p><strong>Offset to first symptom string record.</strong> The offset from the
beginning of the receiver variable to the start of the first symptom string
record.</p>
<p><strong>Offset to subobject name.</strong> The offset from the beginning of
the receiver variable to the start of the subobject name.</p>
<p><strong>Offset to symptom string data.</strong> The offset from the
beginning of the receiver variable to the start of the symptom string data.</p>
<p><strong>Offset to this PTF object's first subobject record.</strong> The
offset from the beginning of the receiver variable to the start of the first
PTF subobject record.</p>
<p><strong>On-order status.</strong> Whether the PTF has been ordered. The
following values are valid:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The PTF has not been ordered or has already been
received.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF has been ordered.</td>
</tr>
</table>
<p><strong>Post-apply or post-remove considerations.</strong> Whether the cover
letter contains special instructions that should be followed after applying or
removing the PTF.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The PTF cover letter does not have any post-apply
or post-remove considerations.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF cover letter does have post-apply or
post-remove considerations.</td>
</tr>
<tr>
<td align="left" valign="top"><em>9</em></td>
<td align="left" valign="top">It is not known if the PTF cover letter has any
post-apply or post-remove considerations. The most likely reasons are that the
PTF cover letter was created prior to operating system release V5R1M0, or the
cover letter was created using the System Manager licensed product.</td>
</tr>
</table>
<p><strong>Pre-apply or pre-remove considerations.</strong> Whether the cover
letter contains special instructions that should be followed prior to applying
or removing the PTF.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The PTF cover letter does not have any pre-apply
or pre-remove considerations.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF cover letter does have pre-apply or
pre-remove considerations that should be followed regardless of how the PTF is
applied or removed (either immediately or during an IPL).</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The PTF cover letter does have pre-apply or
pre-remove considerations, but only when the PTF is applied or removed
immediately.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">The PTF cover letter does have pre-apply or
pre-remove considerations, but only when the PTF is applied or removed during
an IPL.</td>
</tr>
<tr>
<td align="left" valign="top"><em>9</em></td>
<td align="left" valign="top">It is not known if the PTF cover letter has any
pre-apply or pre-remove considerations. The most likely reasons are that the
PTF cover letter was created prior to operating system release V5R1M0, or the
cover letter was created using the System Manager licensed product.</td>
</tr>
</table>
<p><strong>Precondition library name.</strong> The name of the library for the
precondition object. This field contains blanks when the precondition type is
*JOB, *SBS, *RSTD, or *JVM.</p>
<p><strong>Precondition name.</strong> The name of the object, job, or
subsystem for which the precondition exists. The name can be either a specific
name or a generic name. A generic name is a character string that contains one
or more characters followed by an asterisk(*). The field contains blanks when
the precondition type is *RSTD or *JVM.</p>
<p><strong>Precondition record.</strong> The information about the
precondition. Precondition records identify objects, jobs, or subsystems that
cannot be active when this PTF is temporarily applied or removed immediately.
The record is an array that contains the fields in format PTFR0900.</p>
<p><strong>Precondition type.</strong> The type of the object indicated in the
precondition name. Possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>Object type</em></td>
<td align="left" valign="top">The precondition name specifies the name of an
object of this type that exists in the precondition library.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*JOB</em></td>
<td align="left" valign="top">The precondition name specifies the name of a
job.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*SBS</em></td>
<td align="left" valign="top">The precondition name specifies the name of a
subsystem.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*RSTD</em></td>
<td align="left" valign="top">The system must be in a restricted state to
temporarily apply or temporarily remove this PTF immediately.</td>
</tr>
<tr>
<td align="left" valign="top"><em>*JVM</em></td>
<td align="left" valign="top">No Java virtual machines can be active on the
system in order to temporarily apply or temporarily remove this PTF
immediately. Any new Java virtual machines will be prevented from
being started during the apply or remove processing.</td>
</table>
<p><strong>Product ID.</strong> The PTF is for this product. The product must
be installed or supported.</p>
<p><strong>Product option.</strong> The PTF is for this option of the
product.</p>
<p><strong>PTF ID.</strong> The identifier of the PTF.</p>
<p><strong>PTF is released.</strong> Whether the PTF save file is available for
distribution to another system. This is set to 1 only when the System Manager
licensed product is on the system and the product is supported. The user needs
to check the PTF save file status before using this field. 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 PTF save file cannot be distributed.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF save file is released and can be
distributed to another system.</td>
</tr>
</table>
<p><strong>PTF object record.</strong> The information about the PTF objects.
The record is an array that contains the fields described in format
PTFR0400.</p>
<p>This information is available only if the PTF is loaded, temporarily
applied, or has a save file.</p>
<p><strong>PTF subobject record.</strong> The information about the PTF
subobjects. The record is an array that contains the fields described in format
PTFR0400.</p>
<p><strong>PTF type.</strong> The type of PTF. The possible values are:</p>
<table cellpadding="5">
<!-- cols="10 90" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">PTF is delayed. The PTF must be applied at IPL
time.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF is immediate. The PTF can be applied
immediately. No IPL is needed.</td>
</tr>
<tr>
<td align="left" valign="top"><em>Blank</em></td>
<td align="left" valign="top">The PTF type is not known.</td>
</tr>
</table>
<p><strong>Release level.</strong> The release of the PTF. It must be in the
format of VxRyMz. Valid entries for x and y are any number between 0 and 9.
Valid entries for z is any number between 0 and 9 or a character between A and
Z.</p>
<p><strong>Release of dependent PTF.</strong> The release of the dependent
PTF.</p>
<p><strong>Release of requisite.</strong> The release of the requisite PTF.</p>
<p><strong>Requisite is conditional.</strong> Whether the requisite
relationship is conditional. Users should check this field to determine whether
it is necessary to check a remote system for the presence of the software that
is described in the product ID, release, option, and load ID.</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The requisite relationship is not conditional.
The requisite PTF is required by this PTF on all systems that can use this
PTF.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The requisite relationship is conditional. The
requisite PTF is required by this PTF only on systems that contain the software
described in the other fields.</td>
</tr>
</table>
<p><strong>Requisite is required.</strong> Whether a requisite PTF is required
on this system. 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 requisite PTF is not required with this PTF
on this system.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The requisite PTF is required with this PTF on
this system.</td>
</tr>
</table>
<p><strong>Requisite load ID.</strong> The load ID of the requisite PTF. This
value may be blank when the load ID of the requisite PTF cannot be
determined.</p>
<p><strong>Requisite option.</strong> The product option of the requisite PTF.
This value may be blank when the option of the requisite cannot be
determined.</p>
<p><strong>Requisite maximum level.</strong> The indicator of the highest level
of the product on which this PTF can be installed. This field will be blank if
the product has no level.</p>
<p><strong>Requisite minimum level.</strong> The indicator of the lowest level
of the product on which this PTF can be installed. This field will be blank if
the product has no level.</p>
<p><strong>Requisite product ID.</strong> The product ID of the requisite
PTF.</p>
<p><strong>Requisite PTF ID.</strong> The PTF ID of the requisite PTF.</p>
<p><strong>Requisite record.</strong> The information about the requisite. The
record is an array that contains the fields in format PTFR0300.</p>
<p><strong>Reserved.</strong> This field is ignored.</p>
<p><strong>Save file status.</strong> Whether a save file exists for the PTF.
This field should always be checked to determine if a save file exists. The
following values are valid:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The PTF has no save file.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF has a save file.</td>
</tr>
</table>
<p><strong>Server IPL required.</strong> Indicates whether or not a server IPL must be
performed in order to activate the changes for the PTF. 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 server IPL is required to activate the changes for the PTF.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">A server IPL must be performed using the T server IPL source in order to activate the changes for the PTF.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">A server IPL must be performed using the P server IPL source in order to activate the changes for the PTF.</td>
</tr>
</table>
<p><strong>Status date and time.</strong> The date and time the PTF status was
last changed. This field will be blank when the status date and time is not
available. The date and time field is in the CYYMMDDHHMMSS format:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>C</em></td>
<td align="left" valign="top">Century, where 0 indicates years 19<em>xx</em>
and 1 indicates years 20<em>xx</em>.</td>
</tr>
<tr>
<td align="left" valign="top"><em>YY</em></td>
<td align="left" valign="top">Year</td>
</tr>
<tr>
<td align="left" valign="top"><em>MM</em></td>
<td align="left" valign="top">Month</td>
</tr>
<tr>
<td align="left" valign="top"><em>DD</em></td>
<td align="left" valign="top">Day</td>
</tr>
<tr>
<td align="left" valign="top"><em>HH</em></td>
<td align="left" valign="top">Hour</td>
</tr>
<tr>
<td align="left" valign="top"><em>MM</em></td>
<td align="left" valign="top">Minute</td>
</tr>
<tr>
<td align="left" valign="top"><em>SS</em></td>
<td align="left" valign="top">Second</td>
</tr>
</table>
<p><strong>Subobject attribute.</strong> The type of subobject contained in the
PTF. The possible values follow:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>DIR</em></td>
<td align="left" valign="top">The PTF subobject is a directory.</td>
</tr>
<tr>
<td align="left" valign="top"><em>DOC</em></td>
<td align="left" valign="top">The PTF subobject is a document.</td>
</tr>
</table>
<p><strong>Subobject name.</strong> The name of the subobject. This is a name
of an object that is not limited to 10 characters.</p>
<p><strong>Superseded by PTF
ID.</strong> The identifier of the PTF that has replaced this PTF. This field
will be blank when the PTF is not superseded or when the superseding PTF has
not been loaded on the system.</p>
<p><strong>Superseded PTF
ID.</strong> The identifier of a PTF that is superseded by this PTF.</p>
<p><strong>Superseded PTF
record.</strong> The information about the superseded PTFs. The record is an
array that contains the fields in format PTFR1000.</p>
<p><strong>Superseding PTF.</strong> The identifier of the most recent supersede of this PTF that
exists on the system. This field will be blank when the PTF does not have a
superseding PTF.</p>
<p><strong>Symptom string data.</strong> The symptom string for the problems
fixed by this PTF.</p>
<p><strong>Symptom string record.</strong> The information about the symptom
string. The record is an array that contains the fields in format PTFR0700.</p>
<p><strong>Target release.</strong> The earliest release of the
operating system on which you can load and apply the PTF. The release level is
specified in the format V<em>x</em>R<em>y</em>M<em>z</em>, where V<em>x</em> is
the version, R<em>y</em> is the release, and M<em>z</em> is the modification
level.</p>
<p><strong>Type of dependent PTF.</strong> The type of dependent relationship.
The possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The PTF you are retrieving is a prerequisite for
this PTF.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The PTF you are retrieving is a corequisite for
this PTF.</td>
</tr>
</table>
<p><strong>Type of requisite.</strong> The type of requisite relationship. The
possible values are:</p>
<table cellpadding="5">
<!-- cols="5 95" -->
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The requisite PTF is a prerequisite of this PTF.
It does not require this PTF.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">The requisite PTF is a corequisite of this PTF.
It does require this PTF.</td>
</tr>
<tr>
<td align="left" valign="top"><em>9</em></td>
<td align="left" valign="top">The requisite PTF is a distribution requisite of
this PTF. It requires this PTF for distribution purposes only.</td>
</tr>
</table>
<br>
<h3>Error Messages</h3>
<table width="100%" cellpadding="5">
<!-- cols="15 85" -->
<tr>
<th align="left" valign="top">Message ID</th>
<th align="left" valign="top">Error Message Text</th>
</tr>
<tr>
<td width="15%" valign="top">CPF0CB3 E</td>
<td width="85%" valign="top">Value for reserved field not valid.</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">CPF3CF1 E</td>
<td align="left" valign="top">Error code parameter not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C19 E</td>
<td align="left" valign="top">Error occurred with receiver variable
specified.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C20 E</td>
<td align="left" valign="top">Error found by program &amp;1.</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">CPF3C24 E</td>
<td align="left" valign="top">Length of the receiver variable is not
valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3C90 E</td>
<td align="left" valign="top">Literal value cannot be changed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF35BE E</td>
<td align="left" valign="top">Product &amp;1 &amp;3 not supported or
installed.</td>
</tr>
<tr>
<td align="left" valign="top">CPF358A E</td>
<td align="left" valign="top">Release not valid.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3598 E</td>
<td align="left" valign="top">PTF function already in progress.</td>
</tr>
<tr>
<td align="left" valign="top">CPF3902 E</td>
<td align="left" valign="top">PTF &amp;1 located more than once.</td>
</tr>
<tr>
<td align="left" valign="top">CPF6602 E</td>
<td align="left" valign="top">PTF &amp;1-&amp;2 &amp;3 not found.</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>
</table>
<br>
<hr>
API introduced: V2R3
<hr>
<table cellpadding="2" cellspacing="2" align="center">
<tr align="center">
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
"sw1.htm">Software Product APIs</a> | <a href="aplist.htm">APIs by
category</a></td>
</tr>
</table>
</body>
</html>
Reference in New Issue Copy Permalink