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

1693 lines
53 KiB
HTML
Raw Permalink Blame History

<!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>List Cluster Resource Group Information (QcstListClusterResourceGroupIn)
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. -->
<!-- Change History: -->
<!-- YYMMDD USERID Change description -->
<!-- CLUST3A SCRIPT A converted by B2H R4.1 (346) (CMS) by NLJONES at -->
<!-- RCHVMX on 24 Feb 1999 at 17:23:22 -->
<!-- Edited by Kersten Oct 2001 -->
<!-- End Header Records -->
<!-- -->
<!-- -->
<!-- -->
<!-- Begin Developer Note ========================================== -->
<!-- NOTE: If you are adding, changing, or removing ANY requirements -->
<!-- for this API chance are good that the GUI code need to change -->
<!-- also. The Cluster GUI code is built on top of this API and it -->
<!-- does a certain amount of explicit and implicit validation -->
<!-- checking of user data prior to the API call being made. Please -->
<!-- have the Cluster GUI developer check the -->
<!--/as400/v5r4m0.guix/cur/cmvc/java.pgm/ugcl.guix/com/ibm/as400/opnav/ugcl/ClGuiActionsManager.java/ClGuiActionsManager.java -->
<!-- part to determine if any Cluster GUI code changes are needed. -->
<!-- End Developer Note -->
<link rel="stylesheet" type="text/css" href="../rzahg/ic.css">
</head>
<body>
<!--Java sync-link-->
<script type="text/javascript" language="Javascript" src="../rzahg/synch.js">
</script>
<a name="Top_Of_Page"></a>
<h2>List Cluster Resource Group Information (QcstListClusterResourceGroupIn)
API</h2>
<div class="box" style="width: 70%;">
<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%">Request handle</td>
<td align="left" valign="top" width="20%">Output</td>
<td align="left" valign="top" width="20%">Char(16)</td>
</tr>
<tr>
<td align="center" valign="top">2</td>
<td align="left" valign="top">Qualified user space name</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(20)</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">Cluster name</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(10)</td>
</tr>
<tr>
<td align="center" valign="top">5</td>
<td align="left" valign="top">Cluster resource group name</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(10)</td>
</tr>
<tr>
<td align="center" valign="top">6</td>
<td align="left" valign="top">Results information</td>
<td align="left" valign="top">Input</td>
<td align="left" valign="top">Char(30)</td>
</tr>
<tr>
<td align="center" valign="top">7</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;Service Program: QCSTCRG3<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Default Public Authority: *USE<br>
<!-- iddvc RMBR -->
<br>
&nbsp;&nbsp;Threadsafe: Yes<br>
<!-- iddvc RMBR -->
<br>
</div>
<p>The List Cluster Resource Group Information (QcstListClusterResourceGroupIn) API returns the contents of a
cluster resource group object. </p>
<p>This API can be called from a cluster resource group exit program. However
if the status of the cluster resource group specified on the list request is Initialize Pending (540); this API will fail. The cluster resource group
exit program will not be called when this API is run.</p>
<p>If Cluster Resource Services has not been started:</p>
<ul>
<li>The information returned may not be current.</li>
<li>Information will only be returned for a cluster resource group on the node
running the API.</li>
</ul>
<p>If Cluster Resource Services has been started, this API will return
information about the cluster resource group even if it does not exist on the
node from which the API is called. For information retrieved from another node,
the API will always indicate success. To determine if data was actually
returned, wait for the API completion message which is sent to the results
information queue and then check the length returned in the generic header
portion of the user space.</p>
<p>If format LRGI0200 information about a device cluster resource group is
requested and no configuration object entries have yet been added to the
cluster resource group, the list entry size will be 0.</p>
<h3>Authorities and Locks</h3>
<dl>
<dt><em>Cluster Resource Group Authority</em></dt>
<dd>*USE</dd>
<dt><em>Cluster Resource Group Library Authority</em></dt>
<dd>*EXECUTE</dd>
<dt><em>Cluster Resource Group Lock</em></dt>
<dd>*SHRRD</dd>
<dt><em>User Space Authority</em></dt>
<dd>*CHANGE</dd>
<dt><em>User Space Library Authority</em></dt>
<dd>*EXECUTE</dd>
<dt><em>User Space Lock</em></dt>
<dd>*EXCLRD</dd>
<dt><em>Request Information User Queue Authority</em></dt>
<dd>*OBJOPR, *ADD</dd>
<dt><em>Request Information User Queue Library Authority</em></dt>
<dd>*EXECUTE</dd>
<dt><em>Request Information User Queue Lock</em></dt>
<dd>*EXCLRD</dd>
</dl>
<br>
<h3>Required Parameter Group</h3>
<dl>
<dt><strong>Request handle</strong></dt>
<dd>OUTPUT; CHAR(16)
<p>A unique string or handle that identifies this API call. It is used to
associate this call to any responses placed on the user queue specified in the
Results information parameter. If the cluster resource group exists on this
node, then the Request handle field will be blank.</p>
</dd>
<dt><strong>Qualified user space object</strong></dt>
<dd>INPUT; CHAR(20)
<p>The user space that is to receive the created list. The first 10 characters
contain the user space name, and the second 10 characters contain the name of
the library where the user space is located. No special values can used for the
library name, for example, QTEMP, *CURLIB, or *LIBL.</p>
<p>The user space cannot be in
an independent auxiliary storage pool. </p>
</dd>
<dt><strong>Format name</strong></dt>
<dd>INPUT; CHAR(8)
<p>The format of the information to be returned. The format names supported
are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em><a href="#HDRLRGI01">LRGI0100</a></em></td>
<td align="left" valign="top">Recovery Domain Entries</td>
</tr>
<tr>
<td align="left" valign="top"><em><a href="#HDRLRGI02">LRGI0200</a></em></td>
<td align="left" valign="top">Configuration Object Entries</td>
</tr>
<tr>
<td align="left" valign="top"><em><a href="#HDRLRGI02">LRGI0300</a></em></td>
<td align="left" valign="top">Recovery Domain Entries with additional information on site name and data port IP addresses.</td>
</tr>
</table>
<br>
</dd>
<dt><strong>Cluster name</strong></dt>
<dd>INPUT; CHAR(10)
<p>The name of the cluster containing the cluster resource group.</p>
</dd>
<dt><strong>Cluster resource group name</strong></dt>
<dd>INPUT; CHAR(10)
<p>The name of the cluster resource group for which information is
retrieved.</p>
</dd>
<dt><strong>Results information</strong></dt>
<dd>INPUT; CHAR(30)
<p>This parameter identifies a qualified user queue field and is followed by a
reserved field. This parameter is ignored if the cluster resource group exists
on the node initiating the API request.</p>
<p>Qualified user queue: Completion information is returned to this user queue,
which exists on the node from which the API was called, after the function has
completed. See the <a href="#usage_notes">
Usage Notes</a> section of this API for a description of the data that is
placed on this queue. This is a 20-character field. The first 10 characters
contain the user queue name, and the second 10 characters contain the user
queue library name. No special values are supported. QTEMP, *LIBL, *CURLIB are
not valid library names. The attributes of this user queue must be keyed.
<!-- and
have a domain of user.-->
</p>
<p>Reserved: The last 10 characters of the 30-character results information are
reserved. Each character in this field must be set to hexadecimal zero.</p>
</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="HDRRTVLIST">Format of the Generated Lists</a></h3>
<p>The cluster resource group list consists of:</p>
<ul>
<li>A user space</li>
<li>A generic header</li>
<li>An input parameter section</li>
<li>A header section</li>
<li>A list data section:
<ul>
<li>LRGI0100 format,</li>
<li>LRGI0200 format</li>
<li>LRGI0300 format</li>
</ul>
</li>
</ul>
<p>For details about the user area and generic header, see <a href="../apiref/usf.htm">
User Space Format for List APIs</a>. For details about the remaining items, see
the following sections. For detailed descriptions of the fields in the list
returned, see <a href="#HDRAAADDE">Field Descriptions</a>.</p>
<p>When you retrieve list entry information from a user space, you must use the
entry size returned in the generic header for the LRGI0100 or LRGI0200
formats. The size of each
entry may be padded at the end. If you do not use the entry size, the result
may not be valid. For examples of how to process lists, see <a href=
"../apiref/apiexmp.htm">Examples</a>.<br>
</p>
<h3><a name="HDRLSTLIP1">Input Parameter Section</a></h3>
<p>A copy of most parameters coded in the call to the API.<br>
</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%">User space 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 space library name</td>
</tr>
<tr>
<td align="center" valign="top">20</td>
<td align="center" valign="top">14</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Format name</td>
</tr>
<tr>
<td align="center" valign="top">28</td>
<td align="center" valign="top">1C</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Cluster name</td>
</tr>
<tr>
<td align="center" valign="top">38</td>
<td align="center" valign="top">26</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Cluster resource group name</td>
</tr>
<tr>
<td align="center" valign="top">48</td>
<td align="center" valign="top">30</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Request handle</td>
</tr>
<tr>
<td align="center" valign="top">64</td>
<td align="center" valign="top">40</td>
<td align="left" valign="top">CHAR(30)</td>
<td align="left" valign="top">Results information</td>
</tr>
<tr>
<td align="left" valign="top" colspan="4"><strong>Note:</strong> The <strong>
Results information</strong> field is comprised of the following 3 fields.</td>
</tr>
<tr>
<td align="center" valign="top">64</td>
<td align="center" valign="top">40</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Results information user queue name</td>
</tr>
<tr>
<td align="center" valign="top">74</td>
<td align="center" valign="top">4A</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Results information user queue library name</td>
</tr>
<tr>
<td align="center" valign="top">84</td>
<td align="center" valign="top">54</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Reserved</td>
</tr>
</table>
<br>
<br>
<h3><a name="HDRLSTLIP2">Header Section</a></h3>
<p>Global information about the cluster resource group.<br>
</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(1)</td>
<td align="left" valign="top" width="60%">Information status</td>
</tr>
<tr>
<td align="center" valign="top">1</td>
<td align="center" valign="top">1</td>
<td align="left" valign="top">CHAR(3)</td>
<td align="left" valign="top">Reserved</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">Cluster resource group type</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">Current cluster resource group status</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Cluster resource group exit program name</td>
</tr>
<tr>
<td align="center" valign="top">22</td>
<td align="center" valign="top">16</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Cluster resource group exit program library
name</td>
</tr>
<tr>
<td align="center" valign="top">32</td>
<td align="center" valign="top">20</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Cluster resource group exit program format
name</td>
</tr>
<tr>
<td align="center" valign="top">40</td>
<td align="center" valign="top">28</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">User profile</td>
</tr>
<tr>
<td align="center" valign="top">50</td>
<td align="center" valign="top">32</td>
<td align="left" valign="top">CHAR(256)</td>
<td align="left" valign="top">Exit program data</td>
</tr>
<tr>
<td align="center" valign="top">306</td>
<td align="center" valign="top">132</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Takeover IP address</td>
</tr>
<tr>
<td align="center" valign="top">322</td>
<td align="center" valign="top">142</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Job name</td>
</tr>
<tr>
<td align="center" valign="top">332</td>
<td align="center" valign="top">14C</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Allow application restart</td>
</tr>
<tr>
<td align="center" valign="top">336</td>
<td align="center" valign="top">150</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of restarts</td>
</tr>
<tr>
<td align="center" valign="top">340</td>
<td align="center" valign="top">154</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Previous cluster resource group status</td>
</tr>
<tr>
<td align="center" valign="top">344</td>
<td align="center" valign="top">158</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Reporting node</td>
</tr>
<tr>
<td align="center" valign="top">352</td>
<td align="center" valign="top">160</td>
<td align="left" valign="top">CHAR(50)</td>
<td align="left" valign="top">Text description</td>
</tr>
<tr>
<td align="center" valign="top">402</td>
<td align="center" valign="top">192</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Distribute information user queue name</td>
</tr>
<tr>
<td align="center" valign="top">412</td>
<td align="center" valign="top">19C</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Distribute information user queue library
name</td>
</tr>
<tr>
<td align="center" valign="top">422</td>
<td align="center" valign="top">1A6</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Configure takeover IP address</td>
</tr>
<tr>
<td align="center" valign="top">
423</td>
<td align="center" valign="top">1A7</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Clustered hash table cluster resource group</td>
</tr>
<tr>
<td align="center" valign="top">424</td>
<td align="center" valign="top">1A8</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Failover wait time</td>
</tr>
<tr>
<td align="center" valign="top">428</td>
<td align="center" valign="top">1AC</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Failover default action</td>
</tr>
<tr>
<td align="center" valign="top">432</td>
<td align="center" valign="top">1B0</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Failover message queue name</td>
</tr>
<tr>
<td align="center" valign="top">442</td>
<td align="center" valign="top">1BA</td>
<td align="left" valign="top">CHAR(10)</td>
<td align="left" valign="top">Failover message queue library name</td>
</tr>
<tr>
<td align="center" valign="top">452</td>
<td align="center" valign="top">1C4</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top"><img src="delta.gif" alt="Start of change">Reserved<img src="deltaend.gif" alt="End of change"></td>
</tr>
<tr>
<td align="center" valign="top"><img src="delta.gif" alt="Start of change">453</td>
<td align="center" valign="top">1C5</td>
<td align="left" valign="top">CHAR(20)</td>
<td align="left" valign="top">Application id<img src="deltaend.gif" alt="End of change"></td>
</tr>
<tr>
<td align="center" valign="top"><img src="delta.gif" alt="Start of change">473</td>
<td align="center" valign="top">1D9</td>
<td align="left" valign="top">CHAR(1)</td>
<td align="left" valign="top">Allow active takeover IP address<img src="deltaend.gif" alt="End of change"></td>
</tr>
</table>
<br>
<h3><a name="HDRLRGI01">LRGI0100 Recovery Domain Entries Section</a></h3>
<p>The cluster resource group recovery domain information is returned when
LRGI0100 is specified as the format type. Each recovery domain entry returned
will contain both the current and the preferred node role. For detailed
descriptions of the fields in the table, see <a href="#HDRAAADDE">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(8)</td>
<td align="left" valign="top" width="60%">Node id</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">Current node role</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Membership status</td>
</tr>
<tr>
<td align="center" valign="top">16</td>
<td align="center" valign="top">10</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Preferred node role</td>
</tr>
</table>
<br>
<h3><a name="HDRLRGI02">LRGI0200 Configuration Object Entries Section</a></h3>
<p>The cluster resource group resilient device information is returned when
LRGI0200 is specified as the format type. For detailed descriptions of the
fields in the table, see <a href="#HDRAAADDE">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(10)</td>
<td align="left" valign="top" width="60%">Configuration object name</td>
</tr>
<tr>
<td align="center" valign="top">10</td>
<td align="center" valign="top">A</td>
<td align="left" valign="top">CHAR(2)</td>
<td align="left" valign="top">Reserved</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Configuration object type</td>
</tr>
<tr>
<td align="center" valign="top">16</td>
<td align="center" valign="top">10</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Device type</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">Configuration object online</td>
</tr>
<tr>
<td align="center" valign="top">
24</td>
<td align="center" valign="top">18</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Device subtype</td>
</tr>
<tr>
<td align="center" valign="top">28</td>
<td align="center" valign="top">1C</td>
<td align="left" valign="top">CHAR(16)</td>
<td align="left" valign="top">Server takeover IP address</td>
</tr>
<tr>
<td></td>
</tr>
</table>
<br>
<h3><a name="HDRLRGI03">LRGI0300 Recovery Domain Entries Section</a></h3>
<p>The cluster resource group recovery domain information is returned when
LRGI0300 is specified as the format type. Each recovery domain entry returned
will contain both the current and the preferred node role. For detailed
descriptions of the fields in the table, see <a href="#HDRAAADDE">Field
Descriptions</a>.</p>
<table border="1" 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%">BIN(4)</td>
<td align="left" valign="top" width="60%">Length of recovery domain entry</td>
</tr>
<tr>
<td align="center" valign="top" width="10%">4</td>
<td align="center" valign="top" width="10%">4</td>
<td align="left" valign="top" width="20%">CHAR(8)</td>
<td align="left" valign="top" width="60%">Node id</td>
</tr>
<tr>
<td align="center" valign="top">12</td>
<td align="center" valign="top">C</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Current node role</td>
</tr>
<tr>
<td align="center" valign="top">16</td>
<td align="center" valign="top">10</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Membership status</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">Preferred node role</td>
</tr>
<tr>
<td align="center" valign="top">24</td>
<td align="center" valign="top">18</td>
<td align="left" valign="top">CHAR(8)</td>
<td align="left" valign="top">Site name</td>
</tr>
<tr>
<td align="center" valign="top">32</td>
<td align="center" valign="top">20</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Offset to data port IP address array</td>
</tr>
<tr>
<td align="center" valign="top">36</td>
<td align="center" valign="top">24</td>
<td align="left" valign="top">BINARY(4)</td>
<td align="left" valign="top">Number of data port IP addresses</td>
</tr>
<tr>
<td align="center" valign="top">*</td>
<td align="center" valign="top">*</td>
<td align="left" valign="top">Array(*) of CHAR(16)</td>
<td align="left" valign="top">Data Port IP address</td>
</tr>
</table>
<br>
<h3><a name="HDRAAADDE">Field Descriptions</a></h3>
<p><strong>Allow application restart.</strong> Attempt to restart an
application if the cluster resource group exit program fails. Possible values
are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Do not attempt to restart the application. The
cluster resource group exit program is called with an action code of Failover
(9).</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Attempt to restart the application on the same
node. The cluster resource group exit program will be called with an action
code of Restart (3). If the application cannot be restarted in the specified
maximum number of attempts, the cluster resource group exit program will be
called with an action code of Failover (9).</td>
</tr>
</table>
<img src="delta.gif" alt="Start of change">
<p><strong>Allow active takeover IP address.</strong>
Allows a takeover IP address to already be active when it
is assigned to an application cluster resource group. This field is only
valid when configure takeover IP address field is 0x01. Possible values
are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The takeover IP address must not already
be active when starting the cluster resource group. This is the default
value if the field is not specified.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The takeover IP address is allowed to be
active prior to starting the cluster resource group but only on the
primary node.</td>
</tr>
</table>
<img src="deltaend.gif" alt="End of change">
<p><strong><img src="delta.gif" alt="Start of change">Application id.</strong>
This is a string to identify the application supplying the peer cluster
resource group. The recommended format is 'vendor-id.name' where vendor-id is an
identifier for the vendor creating the cluster resource group and name is the application
name. For example, QIBM.ExamplePeer, indicates it is supplied by IBM for the ExamplePeer
application. It is not recommended to use QIBM for vendor id name unless
the cluster resource group is supplied by IBM.
<img src="deltaend.gif" alt="End of change"></p>
<p><strong>Clustered hash table (CHT) cluster resource
group.</strong> Indicates if this cluster resource group is associated with the
clustered hash table server.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Cluster resource group not associated with CHT
server.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Cluster resource group associated with CHT
server.</td>
</tr>
</table>
<br>
<p><strong>Cluster name.</strong> The name of the cluster containing the
cluster resource group.</p>
<p><strong>Cluster resource group exit program format name.</strong> Indicates
which format should be used for the Information Given To User
parameter on the cluster resource group exit program when it is called. See <a href="clrgexit.htm">Cluster Resource Group
Exit Program</a> for details. This
field will contain hexadecimal zeroes if no exit program is specified for the
cluster resource group.
<p><strong>Cluster resource group exit program library name.</strong> The name
of the library that contains the exit program for the cluster resource group.
This field will contain hexadecimal zeroes if no exit program is specified for
the cluster resource group.</p>
<p><strong>Cluster resource group exit program name.</strong> The name of the
user provided exit program. This field will contain *NONE left justified and
padded with blanks if no exit program is specified for the cluster resource
group.</p>
<p><strong>Cluster resource group name.</strong> The name of the cluster
resource group.</p>
<p><strong>Cluster resource group type.</strong> The type of resilient resource
information contained within the cluster resource group object.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Data resiliency</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Application resiliency</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">Device resiliency</td>
</tr>
<tr>
<td align="left" valign="top"><em><img src="delta.gif" alt="Start of change">4</em></td>
<td align="left" valign="top">Peer resiliency<img src="deltaend.gif" alt="End of change"></td>
</tr>
</table>
<p><strong>Configuration object name.</strong> The configuration object name
for a device entry. For example, the auxiliary storage pool device description
name.</p>
<p><strong>Configuration object
online.</strong>Vary the configuration object on and start the server takeover
IP address or leave the configuration object varied off and the server takeover
IP address inactive when a device is switched from one node to another with the
<a href="clrginitso.htm">Initiate Switchover (QcstInitiateSwitchOver) API</a> or when it is failed over to a backup node. This
attribute does <strong>not</strong> vary the device on or off and does <strong>
not</strong> start or end the server takeover IP address when the cluster
resource group is started or ended and when adding a new device entry to the
cluster resource group. For secondary auxiliary storage pools, only a value of
2 is valid. If cluster resources cannot determine if this value is correct for
a device entry because the auxiliary storage pool is not yet created, any
errors will be detected when the cluster resource group is started. A value of
2 cannot be specified for any other device type. Possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Do not vary the configuration object on and do
not start the server takeover IP address.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Vary the configuration object on and start the
server takeover IP address.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Perform the same action for a secondary auxiliary
storage pool as is specified for the primary. </td>
</tr>
</table>
<p><strong>Configuration object type.</strong> This specifies the type of
configuration object specified with configuration object name. Possible values
are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Device description</td>
</tr>
</table>
<p><strong>Configure takeover IP address.</strong> This field identifies who is
responsible for configuring (adding and removing) the takeover IP address. This
does not affect the starting and ending of the takeover IP address, Cluster
Resource Services will perform this function. The following values are
valid:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0x00</em></td>
<td align="left" valign="top">Cluster Resource Services is responsible for
configuring the takeover IP address.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0x01</em></td>
<td align="left" valign="top">User is responsible for configuring the takeover
IP address.</td>
</tr>
</table>
<p><strong>Current cluster resource group status.</strong> The current status of the cluster
resource group when this information was gathered. See <a href=
"clust3a1TOC.htm#Header_3">Summary of Cluster Resource Group Status</a> for the possible values and
definitions of the status.</p>
<p><strong>Current node role.</strong> The curent role the node has in the current
recovery domain. <img src="delta.gif" alt="Start of change">For primary-backup model cluster resource groups
<img src="deltaend.gif" alt="End of change">a node can have one
of three roles: primary, backup, or replicate. Only one node can be designated
as the primary. Backup nodes are assigned a backup order. One indicates the
first backup, two the second backup, and so on. Replicates are not ordered and
cannot become a primary or backup node unless the <a href=
"clrgchgcrg.htm">Change Cluster Resource Group (QcstChangeClusterResourceGroup)
API</a> is used to change its role from replicate to either a backup or
primary.
<br><img src="delta.gif" alt="Start of change">For peer model cluster
resource groups a node can have one
of two roles: peer or replicate. Any number of nodes can be designated
as the peer or replicate. Peer nodes are not ordered and can be an active access point
for the cluster resources. Replicates are not ordered and
cannot become an active access point for the cluster resource unless the <a href=
"clrgchgcrg.htm">Change Cluster Resource Group (QcstChangeClusterResourceGroup)
API</a> is used to change its role from replicate to peer.
<img src="deltaend.gif" alt="End of change">
<br>The following summarizes the valid values for this field:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Primary node. Only one node can have this
value. </td>
</tr>
<tr>
<td align="left" valign="top"><em>&gt;=1</em></td>
<td align="left" valign="top">Backup node. The backup order is designated by
increasing value.</td>
</tr>
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">Replicate node. All replicates have this
value.</td>
</tr>
<tr>
<td align="left" valign="top"><em><img src="delta.gif" alt="Start of change"><br>-4</em></td>
<td align="left" valign="top">Peer node. All peers have this value.<img src="deltaend.gif" alt="End of change"></td>
</tr>
</table>
<p>
<strong>Data port IP address.</strong> The IP address associated with the recovery domain node.
</p>
<p><strong>Device
subtype.</strong> The subtype of the device. This information is only as current as
the last time the cluster resource group object could be updated. If
configuration changes have been made on the node which owns the hardware and
those changes have not yet been distributed to all nodes in the cluster, this
information may be inaccurate. The data cannot be distributed if the
configuration was changed on a node which does not have cluster resource
services running.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">The subtype cannot be determined because
hardware configuration is not complete.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">This device type does not have a subtype.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">UDFS independent auxiliary storage pool.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Secondary independent auxiliary storage
pool.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">Primary independent auxiliary storage pool.</td>
</tr>
</table>
<p><strong>Device type.</strong> The type of device description.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Auxiliary storage pool</td>
</tr>
</table>
<p><strong>Distribute information user queue library name.</strong> The name of
the library that contains the user queue to receive distributed information.
This field will contain hexadecimal zeroes if no user queue is specified for the
cluster resource group.</p>
<p><strong>Distribute information user queue name.</strong> The name of the
user queue to receive distributed information from the
<a href="cldistinfo.htm">Distribute Information (QcstDistributeInformation)</a> API. This field will contain *NONE left justified and
padded with blanks if no user queue is specified for the cluster resource
group.</p>
<p><strong>Exit program data.</strong> 256 bytes of data which is passed to the
cluster resource group exit program when it is called. This field will contain
hexadecimal zeroes if no exit program is specified for the cluster resource
group.</p>
<p><strong>Failover default
action.</strong> Should a response to the failover message queue not be
received in the failover wait time limit, then this field tells clustering what
it should do pertaining to the failover request.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Proceed with failover.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Do NOT attempt failover.</td>
</tr>
</table>
<p><strong>Failover message queue library name.</strong> The name of the
library that contains the user queue to receive failover messages. This field
will contain hexadecimal zeroes if if no message queue is specified for the
cluster resource group.</p>
<p><strong>Failover message queue name.</strong> The name of the message queue
to receive messages dealing with failover. This field will contain *NONE left
justified and padded with blanks if no message queue is specified for the
cluster resource group.</p>
<p><strong>Failover wait time.</strong> Number of minutes to wait for a reply
to the failover message that was enqueued on the failover message queue.
Possible values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">Wait forever until a response is given to the
failover inquiry message.</td>
</tr>
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Failover proceeds without user intervention. Acts
the same as V5R1M0 and prior.</td>
</tr>
<tr>
<td align="left" valign="top"><em>&gt;=1</em></td>
<td align="left" valign="top">Number of minutes to wait for a response to the
failover inquiry message. If no response is received in the specified number of
minutes, the failover default action field will be looked at to decide how to
proceed.</td>
</tr>
</table>
<p><strong>Format name.</strong> The content and format of the information
returned in the user space.</p>
<p><strong>Job name.</strong> The name given the batch job that is submitted to
call the cluster resource group exit program. This field will contain
hexadecimal zeroes if no exit program is specified for the cluster resource
group. Valid special values for this field are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*JOBD</em></td>
<td align="left" valign="top">The job name is determined from the job
description specified in the user profile for the cluster resource group exit
program.</td>
</tr>
</table>
<p><strong>Information status.</strong> Indicates the consistency of the
retrieved information.</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">The information is consistent for all active
nodes in the cluster.</td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">The information retrieved from the node running
the API may not be consistent with all active nodes in the cluster. In order to
obtain consistent information:
<ul>
<li>Call this API on an active node in the cluster, if the node running the API
is not active.</li>
<li>Start Cluster Resource Services on the node running the API if it is not
active.</li>
<li> <img src="delta.gif" alt="Start of change">Use the
Change Cluster Recovery (CHGCLURCY) CL command, if the cluster resource
group job if the cluster resource group is not running but Cluster Resource Services
is active on the node.
<img src="deltaend.gif" alt="End of change"></li>
</ul>
</td>
</tr>
</table>
<p>
<strong>Length of recovery domain entry.</strong> The length in bytes of the entry for LRGI0300 format in the list data section. Use this field to access the next entry in the list.
</p>
<p><strong>Membership status.</strong> The cluster resource group membership
status for the node.</p>
<table cellpadding="5">
<!-- cols="10 10 80" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Active</td>
<td align="left" valign="top">The node is an active member of the cluster resource group membership. </td>
</tr>
<tr>
<td align="left" valign="top"><em>1</em></td>
<td align="left" valign="top">Inactive</td>
<td align="left" valign="top">The node is not an active member of the cluster resource group membership. The Cluster Resource Services may not be active on the node or the cluster resource group job could be ended on the node.</td>
</tr>
<tr>
<td align="left" valign="top"><em>2</em></td>
<td align="left" valign="top">Partition</td>
<td align="left" valign="top">The node is partitioned from the other members of the cluster resource group membership.</td>
</tr>
<tr>
<td align="left" valign="top"><em>3</em></td>
<td align="left" valign="top">Ineligible</td>
<td align="left" valign="top">The node is an active member of the cluster resource group membership but not eligible to become the cluster resource group primary node. </td>
</tr>
</table>
<p><strong>Node id.</strong> A unique string of characters that identifies a
node that is in the recovery domain of the cluster resource group.</p>
<p>
<strong>Number of data port IP addresses.</strong> The number of data port IP addresses associated with the recovery domain node.
</p>
<p><strong>Number of restarts.</strong> Number of times the cluster resource
group exit program can be restarted on the same node before a failover occurs.
Maximum number of restarts is 3. This field is valid only for an application
cluster resource group. It will always contain hexadecimal zero for a data or
device cluster resource group.</p>
<p>
<strong>Offset to data port IP address array.</strong> The byte offset from the beginning
of the user space to the first data port IP address.
</p>
<p><strong> Preferred node role.</strong> The preferred role the node has in
the recovery domain. <img src="delta.gif" alt="Start of change">For primary-backup model cluster resource groups
<img src="deltaend.gif" alt="End of change">a node can have one
of three roles: primary, backup, or replicate. Only one node can be designated
as the primary. Backup nodes are assigned a backup order. One indicates the
first backup, two the second backup, and so on. Replicates are not ordered and
cannot become a primary or backup node unless the <a href=
"clrgchgcrg.htm">Change Cluster Resource Group (QcstChangeClusterResourceGroup)
API</a> is used to change its role from replicate to either a backup or
primary.
<br><img src="delta.gif" alt="Start of change">For peer model cluster
resource groups a node can have one
of two roles: peer or replicate. Any number of nodes can be designated
as the peer or replicate. Peer nodes are not ordered and can be an active access point
for the cluster resources. Replicates are not ordered and
cannot become an active access point for the cluster resource unless the <a href=
"clrgchgcrg.htm">Change Cluster Resource Group (QcstChangeClusterResourceGroup)
API</a> is used to change its role from replicate to peer.
<br><img src="deltaend.gif" alt="End of change"> Valid values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>0</em></td>
<td align="left" valign="top">Primary node. Only one node can have this
value.</td>
</tr>
<tr>
<td align="left" valign="top"><em>&gt;=1</em></td>
<td align="left" valign="top">Backup node. The backup order is designated by
increasing value.</td>
</tr>
<tr>
<td align="left" valign="top"><em>-1</em></td>
<td align="left" valign="top">Replicate node. All replicates have this
value.</td>
</tr>
<tr>
<td align="left" valign="top"><em><img src="delta.gif" alt="Start of change">-4</em></td>
<td align="left" valign="top">Peer node. All peers have this
value.<img src="deltaend.gif" alt="End of change"></td>
</tr>
</table>
<p><strong>Previous cluster resource group status.</strong> Indicates the
status of this cluster resource group before the current request was
executed.</p>
<p><strong>Reporting node.</strong> The cluster node which
returned the list information for the cluster resource group Valid special
values are:</p>
<table cellpadding="5">
<!-- cols="15 85" -->
<tr>
<td align="left" valign="top"><em>*LOCAL</em></td>
<td align="left" valign="top">The information was retrieved from a cluster
resource group on the local system and the local system did not have a cluster
node associated with it.</td>
</tr>
</table>
<p><strong>Request handle.</strong> Identifies this API call. It is used to
associate this call to a response on the user queue specified in the Results
Information parameter.</p>
<p><strong>Reserved.</strong> The field will contain hexadecimal zeroes.</p>
<p><strong>Results information.</strong> This field identifies a qualified user
queue name and is followed by a reserved field.</p>
<p><strong>Results information user queue library name.</strong> This field
identifies the library where the results information user queue resides.</p>
<p><strong>Results information user queue name.</strong> This field identifies
the name of the user queue to which messages are sent when this API operates
asynchronously.</p>
<p><strong>Server takeover IP
address.</strong> This is a takeover IP address for servers associated with the
relational database name in the device description for an auxiliary storage
pool. The address will be represented in dotted decimal format and returned as
a null-terminated string. If not specified, or for a secondary and UDFS
auxiliary storage pool, this field will contain *NONE left justified and
padded with blanks. If the current cluster version is 2, this field is set to
hexadecimal zeroes. </p>
<p>
<strong>Site name.</strong> The name of the site associated with the recovery domain node. If the current cluster version is 3, this field is set to
hexadecimal zeroes.
<p><strong>Takeover IP address.</strong> The floating IP address that is to be
associated with the application. This field is only meaningful for an
application cluster resource group. It is set to hexadecimal zeroes for a data
or device cluster resource group. This field will be represented in dotted
decimal format and returned as a null-terminated string.</p>
<p><strong>Text description.</strong> The text description associated with the
cluster resource group object.</p>
<p><strong>User profile.</strong> The name of the user profile under which the
cluster resource group exit program is run. This field will contain hexadecimal
zeroes if no exit program is specified for the cluster resource group.</p>
<p><strong>User space library name.</strong> The name of the library containing
the user space.</p>
<p><strong>User space name.</strong> The name of the user space which will
contain the information retrieved from the cluster resource group.<br>
</p>
<h3><a name="usage_notes">Usage Notes</a></h3>
<h3>Results Information User Queue</h3>
<p>Asynchronous results are returned to a user queue specified by the Results
Information parameter of the API. See <a href="clust1a4.htm">Cluster APIs Use
of User Queues</a> and <a href="clust1a5.htm">Using Results Information</a> for
details on how to create the results information user queue, the format of the
entries, and how to use the data placed on the queue. The data is sent to the
user queue in the form of a message identifier and the substitution data for
the message (if any exists). The following identifies the data sent to the user
queue (excluding the message text).</p>
<table width="100%" cellpadding="5">
<!-- cols="15 85" -->
<tr>
<th align="left" valign="top">Message ID</th>
<th align="left" valign="top">Message Text</th>
</tr>
<tr>
<td width="15%" valign="top">CPCBB01 C</td>
<td width="85%" valign="top">Cluster Resource Services API &amp;1
completed.</td>
</tr>
<tr>
<td valign="top">CPF2204 D</td>
<td valign="top">User profile &amp;1 not found.</td>
</tr>
<tr>
<td valign="top">CPF3CF2 D</td>
<td valign="top">Error(s) occurred during running of &amp;1 API.</td>
</tr>
<tr>
<td valign="top">CPF9801 D</td>
<td valign="top">Object &amp;2 in library &amp;3 not found.</td>
</tr>
<tr>
<td valign="top">CPF9802 D</td>
<td valign="top">Not authorized to object &amp;2 in &amp;3.</td>
</tr>
<tr>
<td valign="top">CPF9803 D</td>
<td valign="top">Cannot allocate object &amp;2 in library &amp;3.</td>
</tr>
<tr>
<td valign="top">CPF9804 D</td>
<td valign="top">Object &amp;2 in library &amp;3 damaged..</td>
</tr>
<tr>
<td valign="top">CPF9810 D</td>
<td valign="top">Library &amp;1 not found.</td>
</tr>
<tr>
<td valign="top">CPFBB24 D</td>
<td valign="top">Node &amp;1 not participating in &amp;2 API protocol.</td>
</tr>
<tr>
<td valign="top">CPFBB32 D</td>
<td valign="top">Attributes of user queue &amp;1 in library &amp;2 are not
valid.</td>
</tr>
<tr>
<td valign="top">CPFBB38 D</td>
<td valign="top">Library name &amp;1 not allowed for this request.</td>
</tr>
</table>
<br>
<h3><a name="Header_65">Error Messages</a></h3>
<p>Messages that are delivered through the error code parameter are listed
here. The data (messages) sent to the results information user queue are listed
in the <a href="#usage_notes">Usage Notes</a> above.</p>
<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">CPF2113 E</td>
<td width="85%" valign="top">Cannot allocate library &amp;1.</td>
</tr>
<tr>
<td valign="top">CPF3C1E E</td>
<td valign="top">Required parameter &amp;1 omitted.</td>
</tr>
<tr>
<td valign="top">CPF3C21 E</td>
<td valign="top">Format name &amp;1 is not valid.</td>
</tr>
<tr>
<td valign="top">CPF3C3C E</td>
<td valign="top">Value for parameter &amp;1 not valid.</td>
</tr>
<tr>
<td valign="top">CPF3C39 E</td>
<td valign="top">Value for reserved field not valid.</td>
</tr>
<tr>
<td valign="top">CPF3C3C E</td>
<td valign="top">Value for parameter &amp;1 not valid.</td>
</tr>
<tr>
<td valign="top">CPF3CF1 E</td>
<td valign="top">Error code parameter not valid.</td>
</tr>
<tr>
<td valign="top">CPF3CF2 E</td>
<td valign="top">Error(s) occurred during running of &amp;1 API.</td>
</tr>
<tr>
<td valign="top">CPF9801 E</td>
<td valign="top">Object &amp;2 in library &amp;3 not found.</td>
</tr>
<tr>
<td valign="top">CPF9802 E</td>
<td valign="top">Not authorized to object &amp;2 in &amp;3.</td>
</tr>
<tr>
<td valign="top">CPF9803 E</td>
<td valign="top">Cannot allocate object &amp;2 in library &amp;3.</td>
</tr>
<tr>
<td valign="top">CPF9804 E</td>
<td valign="top">Object &amp;2 in library &amp;3 damaged.</td>
</tr>
<tr>
<td valign="top">CPF980C E</td>
<td valign="top">Object &amp;1 in library &amp;2 cannot be in an independent
auxiliary storage pool. </td>
</tr>
<tr>
<td valign="top">CPF9810 E</td>
<td valign="top">Library &amp;1 not found.</td>
</tr>
<tr>
<td valign="top">CPF9820 E</td>
<td valign="top">Not authorized to use library &amp;1.</td>
</tr>
<tr>
<td valign="top">CPFBB02 E</td>
<td valign="top">Cluster &amp;1 does not exist.</td>
</tr>
<tr>
<td valign="top">CPFBB0F E</td>
<td valign="top">Cluster resource group &amp;1 does not exist in cluster
&amp;2.</td>
</tr>
<tr>
<td valign="top">CPFBB26 E</td>
<td valign="top">Cluster Resource Services not active or not responding.</td>
</tr>
<tr>
<td valign="top">CPFBB32 E</td>
<td valign="top">Attributes of user queue &amp;1 in library &amp;2 are not
valid.</td>
</tr>
<tr>
<td valign="top">CPFBB38 E</td>
<td valign="top">Library name &amp;1 not allowed for this request.</td>
</tr>
<tr>
<td valign="top">CPFBB39 E</td>
<td valign="top">Current user does not have IOSYSCFG special authority.</td>
</tr>
<tr>
<td valign="top">CPFBB40 E</td>
<td valign="top">The value &amp;1 specified for the allow application restarts
parameter is not valid</td>
</tr>
<tr>
<td valign="top">CPFBB43 E</td>
<td valign="top">Format name &amp;1 not valid for cluster resource group type
&amp;2.</td>
</tr>
<tr>
<td valign="top">CPFBB46 E</td>
<td valign="top">Cluster Resource Services internal error.</td>
</tr>
<tr>
<td valign="top">CPFBB70 E</td>
<td valign="top">API request &amp;1 not compatible with current cluster
version.</td>
</tr>
</table>
<br>
<hr>
API introduced: V4R4
<hr>
<center>
<table cellpadding="2" cellspacing="2">
<tr align="center">
<td valign="middle" align="center"><a href="#Top_Of_Page">Top</a> | <a href=
"clust1a1.htm">Cluster APIs</a> | <a href="aplist.htm">APIs by
category</a></td>
</tr>
</table>
</center>
</body>
</html>
Reference in New Issue View Git Blame Copy Permalink