3994 lines
136 KiB
HTML
3994 lines
136 KiB
HTML
|
<!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 Member Description (QUSRMBRD) 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. -->
|
||
|
|
<!-- File SCRIPT A converted by B2H R4.1 (346) (CMS) by V2KEA304 -->
|
||
|
|
<!-- at RCHVMW2 on 17 Feb 1999 at 11:05:09 -->
|
||
|
|
<!-- This file has undergone html cleanup on 10/04/01 by JET -->
|
||
|
|
<!-- This file has undergone html cleanup on 07/30/02 by JET -->
|
||
|
|
<!-- Change history: -->
|
||
|
|
<!-- 021030 45HJAV: Update 32 to 256 for based on files -->
|
||
|
|
<!-- 030124 45HRLN: Ragged Save While Active, SWA, support -->
|
||
|
|
<!-- 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 Member Description (QUSRMBRD) API</h2>
|
||
|
|
|
||
|
|
<div class="box" style="width: 80%;">
|
||
|
|
<br>
|
||
|
|
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">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">Qualified database file name</td>
|
||
|
|
<td align="left" valign="top">Input</td>
|
||
|
|
<td align="left" valign="top">Char(20)</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">5</td>
|
||
|
|
<td align="left" valign="top">Database member 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">Override processing</td>
|
||
|
|
<td align="left" valign="top">Input</td>
|
||
|
|
<td align="left" valign="top">Char(1)</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
Optional Parameter Group 1:<br>
|
||
|
|
<!-- iddvc RMBR -->
|
||
|
|
<br>
|
||
|
|
|
||
|
|
|
||
|
|
<table width="100%">
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top" width="10%">7</td>
|
||
|
|
<td align="left" valign="top" width="50%">Error code</td>
|
||
|
|
<td align="left" valign="top" width="20%">I/O</td>
|
||
|
|
<td align="left" valign="top" width="20%">Char(*)</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
Optional Parameter Group 2:<br>
|
||
|
|
<!-- iddvc RMBR -->
|
||
|
|
<br>
|
||
|
|
|
||
|
|
|
||
|
|
<table width="100%">
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top" width="10%">8</td>
|
||
|
|
<td align="left" valign="top" width="50%">Find member processing</td>
|
||
|
|
<td align="left" valign="top" width="20%">Input</td>
|
||
|
|
<td align="left" valign="top" width="20%">Char(1)</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
Default Public Authority: *USE<br>
|
||
|
|
<!-- iddvc RMBR -->
|
||
|
|
<br>
|
||
|
|
Threadsafe: Conditional; see <a href="#usage_notes"> Usage Notes</a> .<br>
|
||
|
|
<!-- iddvc RMBR -->
|
||
|
|
<br>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<p>The Retrieve Member Description (QUSRMBRD) API retrieves specific
|
||
|
|
information about a single database file member and returns the information to
|
||
|
|
the calling program in a receiver variable. The length of the receiver variable
|
||
|
|
determines the amount of data returned. You can only use the QUSRMBRD API with
|
||
|
|
database file types *PF, *LF, and *DDMF.</p>
|
||
|
|
|
||
|
|
<p>You can use the QUSRMBRD API to:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>Retrieve specific information about a database file member that is
|
||
|
|
specified to a calling program.</li>
|
||
|
|
|
||
|
|
<li>Automate reorganization when the deleted record space reaches the maximum
|
||
|
|
specified.</li>
|
||
|
|
|
||
|
|
<li>Ensure that the last date the source was changed matches the date the
|
||
|
|
source was used to create the object.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3>Authorities and Locks</h3>
|
||
|
|
|
||
|
|
<dl compact>
|
||
|
|
<dt><em>Library Authority</em></dt>
|
||
|
|
|
||
|
|
<dd>*USE</dd>
|
||
|
|
|
||
|
|
<dt><em>File Authority</em></dt>
|
||
|
|
|
||
|
|
<dd>*OBJOPR</dd>
|
||
|
|
|
||
|
|
<dt><em>File Lock</em></dt>
|
||
|
|
|
||
|
|
<dd>*SHRRD</dd>
|
||
|
|
</dl>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3>Required Parameter Group</h3>
|
||
|
|
|
||
|
|
<dl>
|
||
|
|
<dt>Receiver variable</dt>
|
||
|
|
|
||
|
|
<dd>OUTPUT; CHAR(*)
|
||
|
|
|
||
|
|
<p>The receiver variable that is to receive the information requested. You can
|
||
|
|
specify that the size of the area be smaller than the format requested as long
|
||
|
|
as you specify the length of the receiver variable parameter correctly. As a
|
||
|
|
result, the API returns only the data the area can hold.</p>
|
||
|
|
</dd>
|
||
|
|
|
||
|
|
<dt>Length of receiver variable</dt>
|
||
|
|
|
||
|
|
<dd>INPUT; BINARY(4)
|
||
|
|
|
||
|
|
<p>The length of the receiver variable provided. The length of receiver
|
||
|
|
variable parameter may be specified up to the size of the receiver variable
|
||
|
|
specified in the user program. If the length of receiver variable parameter
|
||
|
|
specified is larger than the allocated size of the receiver variable specified
|
||
|
|
in the user program, the results are not predictable. The minimum length is 8
|
||
|
|
bytes.</p>
|
||
|
|
</dd>
|
||
|
|
|
||
|
|
<dt>Format name</dt>
|
||
|
|
|
||
|
|
<dd>INPUT; CHAR(8)
|
||
|
|
|
||
|
|
<p>The content and format of the information to be returned for each specified
|
||
|
|
member. The following format names are valid:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="15 85" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> MBRD0100</em></td>
|
||
|
|
<td align="left" valign="top"><em> Member name and basic source information.
|
||
|
|
This is similar to the information provided by the List Database File Members
|
||
|
|
(QUSLMBR) API using format MBRL0200.</em> See <a href="#HDRRMBRD1"> MBRD0100
|
||
|
|
Format</a> .</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> MBRD0200</em></td>
|
||
|
|
<td align="left" valign="top">Member name and expanded information. The
|
||
|
|
additional information requires more system processing and takes longer to
|
||
|
|
produce than the MBRD0100 format. See <a href="#HDRRMBRD2"> MBRD0200 Format</a>
|
||
|
|
.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> MBRD0300</em></td>
|
||
|
|
<td align="left" valign="top">Member name and full information. The additional
|
||
|
|
information requires more system processing and takes longer to produce than
|
||
|
|
the MBRD0200 format. See <a href="#HDRRMBRD3"> MBRD0300 Format</a> .</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> MBRD0400</em></td>
|
||
|
|
<td align="left" valign="top">Data space index information for a physical file
|
||
|
|
member. See <a href="#HDRRMBRD4"> MBRD0400 Format.</a></td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><img src="delta.gif" alt="Start of change">
|
||
|
|
<em> MBRD0500</em></td>
|
||
|
|
<td align="left" valign="top">Data space materialized query table information
|
||
|
|
for a physical file member. See <a href="#HDRRMBRD5"> MBRD0500 Format.</a>
|
||
|
|
<img src=
|
||
|
|
"deltaend.gif" alt="End of change"></td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
</table><br><br>
|
||
|
|
</dd>
|
||
|
|
|
||
|
|
|
||
|
|
<dt>Qualified database file name</dt>
|
||
|
|
|
||
|
|
<dd>INPUT; CHAR(20)
|
||
|
|
|
||
|
|
<p>The name of the database file containing the specified member whose
|
||
|
|
information is to be retrieved, and the library in which it is located. The
|
||
|
|
first 10 characters contain the database file name, and the second 10
|
||
|
|
characters contain the library name.</p>
|
||
|
|
|
||
|
|
<p>You can use these special values for the library name:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="15 85" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> *CURLIB</em></td>
|
||
|
|
<td align="left" valign="top">The job's current library</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> *LIBL</em></td>
|
||
|
|
<td align="left" valign="top">The library list</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
</dd>
|
||
|
|
|
||
|
|
<dt>Database member name</dt>
|
||
|
|
|
||
|
|
<dd>INPUT; CHAR(10)
|
||
|
|
|
||
|
|
<p>The name of the database member for which information is to be retrieved.
|
||
|
|
Special values follow:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="15 85" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> *FIRST</em></td>
|
||
|
|
<td align="left" valign="top">The first database member found.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> *LAST</em></td>
|
||
|
|
<td align="left" valign="top">The last database member found.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
</dd>
|
||
|
|
|
||
|
|
<dt>Override processing</dt>
|
||
|
|
|
||
|
|
<dd>INPUT; CHAR(1)
|
||
|
|
|
||
|
|
<p>Whether overrides are to be processed. 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">Overrides are not processed</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Overrides are processed</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3>Optional Parameter Group 1</h3>
|
||
|
|
|
||
|
|
<dl>
|
||
|
|
<dt>Error code</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> . If this
|
||
|
|
parameter is omitted, diagnostic and escape messages are issued to the
|
||
|
|
application.</p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3>Optional Parameter Group 2</h3>
|
||
|
|
|
||
|
|
<dl>
|
||
|
|
<dt>Find member processing</dt>
|
||
|
|
|
||
|
|
<dd>INPUT; CHAR(1)
|
||
|
|
|
||
|
|
<p>The method to use to find the member. There are two ways to find the member
|
||
|
|
for which information is to be retrieved. 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">Find the file first and then look for the member
|
||
|
|
in that file. This is the default value if this parameter is not
|
||
|
|
specified.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Find the specified member directly. This method
|
||
|
|
is more efficient when *LIBL is used for the library name and a specific member
|
||
|
|
name is specified.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p>If a specific library is used to find the member, or if the member name
|
||
|
|
specified is *FIRST or *LAST, the two ways will always find the same member. If
|
||
|
|
*LIBL is used for the library name and a specific member name is specified (not
|
||
|
|
*FIRST or *LAST), then the two ways can produce different results. See <a href=
|
||
|
|
"#FIGFNDMEX">Find Member Example</a> .</p>
|
||
|
|
|
||
|
|
<p>The find member directly method is not supported when all of the following
|
||
|
|
conditions exist:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>*LIBL is specified as the library.</li>
|
||
|
|
|
||
|
|
<li>The member name is not specified as *FIRST or *LAST.</li>
|
||
|
|
|
||
|
|
<li>The member name is not found in any of the files in the library list.</li>
|
||
|
|
|
||
|
|
<li>The first occurrence of the file in the library list is a DDM file.</li>
|
||
|
|
|
||
|
|
<li>The library name specified for the remote file (RMTFILE parameter on the
|
||
|
|
Create DDM File (CRTDDMF) command) is *LIBL.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>When this situation occurs, an error is returned from QUSRMBRD because it
|
||
|
|
cannot determine which file on the remote system on OPEN operation would find.
|
||
|
|
API users can monitor for this error and then re-issue the API call specifying
|
||
|
|
the find file first method.</p>
|
||
|
|
|
||
|
|
<p><strong><a name="FIGFNDMEX">Find Member Example</a></strong> . File F exists
|
||
|
|
in libraries LIB1 and LIB2 in the library list. If *LIBL is specified as the
|
||
|
|
library for file F and member X, option 0 will not find member X because it
|
||
|
|
does not exist in the file LIB1/F. Option 1 will find member X in the file
|
||
|
|
LIB2/F.</p>
|
||
|
|
|
||
|
|
<p><img src="RBAFX594.gif" alt="Libraries in library list"></p>
|
||
|
|
</dd>
|
||
|
|
</dl>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3><a name="HDRMBRDF">Format of the Generated Information</a></h3>
|
||
|
|
|
||
|
|
<p>The file member description can be provided in one of four formats:</p>
|
||
|
|
|
||
|
|
<ul>
|
||
|
|
<li>MBRD0100</li>
|
||
|
|
<li>MBRD0200</li>
|
||
|
|
<li>MBRD0300</li>
|
||
|
|
<li>MBRD0400</li>
|
||
|
|
<li><img src="delta.gif" alt="Start of change"> <em> </em>MBRD0500<img src=
|
||
|
|
"deltaend.gif" alt="End of change"></li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>The structure of the information returned is determined by the value
|
||
|
|
specified for the format name. For details about these formats, see the
|
||
|
|
following sections. For detailed descriptions of the fields in the list, see <a
|
||
|
|
href="#HDRMBRDD">Field Descriptions</a> .</p>
|
||
|
|
|
||
|
|
<p>If an offset equals zero in the returned information, there is no
|
||
|
|
corresponding structure associated with it.</p>
|
||
|
|
|
||
|
|
<p><a href="#FIGBRD0100">MBRD0100 Format</a> , <a href="#FIGBRD0200">MBRD0200
|
||
|
|
Format</a> , and <a href="#FIGBRD0300">MBRD0300 Format</a> show how the
|
||
|
|
information for the first three formats is organized. When more than one entry
|
||
|
|
can appear, the figure indicates this as in <strong>(A)</strong> .</p>
|
||
|
|
|
||
|
|
<p><strong><a name="FIGBRD0100">MBRD0100 Format</a></strong>
|
||
|
|
<br>
|
||
|
|
<img src="RBAFX595.gif" alt="MBRD0100 Format"></p>
|
||
|
|
|
||
|
|
<p><strong><a name="FIGBRD0200">MBRD0200 Format</a></strong>
|
||
|
|
<br>
|
||
|
|
<img src="RBAFX596.gif" alt="MBRD0200 Format"></p>
|
||
|
|
|
||
|
|
<p><strong><a name="FIGBRD0300">MBRD0300 Format</a></strong>
|
||
|
|
<br>
|
||
|
|
<img src="RBAFX597.gif" alt="MBRD0300 Format"></p>
|
||
|
|
|
||
|
|
<h3><a name="HDRRMBRD1">MBRD0100 Format</a></h3>
|
||
|
|
|
||
|
|
<p>The MBRD0100 format includes the file member list and source information
|
||
|
|
shown in the following table.</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">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Database file name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">18</td>
|
||
|
|
<td align="center" valign="top">12</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Database file library 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">Member 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">File attribute</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">48</td>
|
||
|
|
<td align="center" valign="top">30</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Source type</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">58</td>
|
||
|
|
<td align="center" valign="top">3A</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">71</td>
|
||
|
|
<td align="center" valign="top">47</td>
|
||
|
|
<td align="left" valign="top">CHAR(13)</td>
|
||
|
|
<td align="left" valign="top">Last source change or table refresh date and time</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">84</td>
|
||
|
|
<td align="center" valign="top">54</td>
|
||
|
|
<td align="left" valign="top">CHAR(50)</td>
|
||
|
|
<td align="left" valign="top">Member text description</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">134</td>
|
||
|
|
<td align="center" valign="top">86</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Source file</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
<h3><a name="HDRRMBRD2">MBRD0200 Format</a></h3>
|
||
|
|
|
||
|
|
<p>The MBRD0200 format includes the file member name and the expanded
|
||
|
|
information shown in the following table.</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%"> </td>
|
||
|
|
<td align="left" valign="top" width="60%">Everything from the MBRD0100
|
||
|
|
format</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">135</td>
|
||
|
|
<td align="center" valign="top">87</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Remote file</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">136</td>
|
||
|
|
<td align="center" valign="top">88</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Logical file or physical file</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">137</td>
|
||
|
|
<td align="center" valign="top">89</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">ODP sharing</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">138</td>
|
||
|
|
<td align="center" valign="top">8A</td>
|
||
|
|
<td align="left" valign="top">CHAR(2)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">140</td>
|
||
|
|
<td align="center" valign="top">8C</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Current number of records for all based-on
|
||
|
|
members, if less than 2,147,483,647</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">144</td>
|
||
|
|
<td align="center" valign="top">90</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Number of deleted records, if less than
|
||
|
|
2,147,483,647</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">148</td>
|
||
|
|
<td align="center" valign="top">94</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Data space size</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">152</td>
|
||
|
|
<td align="center" valign="top">98</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Access path size</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">156</td>
|
||
|
|
<td align="center" valign="top">9C</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Number of based-on physical file members</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">160</td>
|
||
|
|
<td align="center" valign="top">A0</td>
|
||
|
|
<td align="left" valign="top">CHAR(13)</td>
|
||
|
|
<td align="left" valign="top">Change date and time</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">173</td>
|
||
|
|
<td align="center" valign="top">AD</td>
|
||
|
|
<td align="left" valign="top">CHAR(13)</td>
|
||
|
|
<td align="left" valign="top">Save date and time</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">186</td>
|
||
|
|
<td align="center" valign="top">BA</td>
|
||
|
|
<td align="left" valign="top">CHAR(13)</td>
|
||
|
|
<td align="left" valign="top">Restore date and time</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">199</td>
|
||
|
|
<td align="center" valign="top">C7</td>
|
||
|
|
<td align="left" valign="top">CHAR(7)</td>
|
||
|
|
<td align="left" valign="top">Expiration date</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">206</td>
|
||
|
|
<td align="center" valign="top">CE</td>
|
||
|
|
<td align="left" valign="top">CHAR(6)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">212</td>
|
||
|
|
<td align="center" valign="top">D4</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Number of days used</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">216</td>
|
||
|
|
<td align="center" valign="top">D8</td>
|
||
|
|
<td align="left" valign="top">CHAR(7)</td>
|
||
|
|
<td align="left" valign="top">Date last used</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">223</td>
|
||
|
|
<td align="center" valign="top">DF</td>
|
||
|
|
<td align="left" valign="top">CHAR(7)</td>
|
||
|
|
<td align="left" valign="top">Use reset date</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">230</td>
|
||
|
|
<td align="center" valign="top">E6</td>
|
||
|
|
<td align="left" valign="top">CHAR(2)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">232</td>
|
||
|
|
<td align="center" valign="top">E8</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Data space size multiplier</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">236</td>
|
||
|
|
<td align="center" valign="top">EC</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Access path size multiplier</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">240</td>
|
||
|
|
<td align="center" valign="top">F0</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Member text description CCSID</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">244</td>
|
||
|
|
<td align="center" valign="top">F4</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Offset to additional MBRD0200 format
|
||
|
|
information</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">248</td>
|
||
|
|
<td align="center" valign="top">F8</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Length of additional MBRD0200 format
|
||
|
|
information</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">252</td>
|
||
|
|
<td align="center" valign="top">FC</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Current number of records for all based-on
|
||
|
|
members</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">256</td>
|
||
|
|
<td align="center" valign="top">100</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Number of deleted records</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">260</td>
|
||
|
|
<td align="center" valign="top">104</td>
|
||
|
|
<td align="left" valign="top">CHAR(6)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
<h3><a name="HDRRMBRD3">MBRD0300 Format</a></h3>
|
||
|
|
|
||
|
|
<p>The MBRD0300 format includes the file member list and the full information
|
||
|
|
shown in the following table. This includes some key fields that are applicable
|
||
|
|
only to the file (not member) one might use, and fields unique to the
|
||
|
|
member.</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%"> </td>
|
||
|
|
<td align="left" valign="top" width="60%">Everything from the MBRD0200
|
||
|
|
format</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">266</td>
|
||
|
|
<td align="center" valign="top">10A</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Join member</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">267</td>
|
||
|
|
<td align="center" valign="top">10B</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Access path maintenance</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">268</td>
|
||
|
|
<td align="center" valign="top">10C</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">SQL file type</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">278</td>
|
||
|
|
<td align="center" valign="top">116</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">279</td>
|
||
|
|
<td align="center" valign="top">117</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Allow read operation</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">280</td>
|
||
|
|
<td align="center" valign="top">118</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Allow write operation</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">281</td>
|
||
|
|
<td align="center" valign="top">119</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Allow update operation</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">282</td>
|
||
|
|
<td align="center" valign="top">11A</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Allow delete operation</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">283</td>
|
||
|
|
<td align="center" valign="top">11B</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">284</td>
|
||
|
|
<td align="center" valign="top">11C</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Records to force a write</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">288</td>
|
||
|
|
<td align="center" valign="top">120</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Maximum percent deleted records allowed</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">292</td>
|
||
|
|
<td align="center" valign="top">124</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Initial number of records</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">296</td>
|
||
|
|
<td align="center" valign="top">128</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Increment number of records</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">300</td>
|
||
|
|
<td align="center" valign="top">12C</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Maximum number of increments</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">304</td>
|
||
|
|
<td align="center" valign="top">130</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Current number of increments</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">308</td>
|
||
|
|
<td align="center" valign="top">134</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Record capacity</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">312</td>
|
||
|
|
<td align="center" valign="top">138</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Record format selector program name</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">Record format selector library name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">332</td>
|
||
|
|
<td align="center" valign="top">14C</td>
|
||
|
|
<td align="left" valign="top">BINARY(2)</td>
|
||
|
|
<td align="left" valign="top">Number of constraint indexes</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">334</td>
|
||
|
|
<td align="center" valign="top">14E</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Offset to constraint indexes information</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">338</td>
|
||
|
|
<td align="center" valign="top">153</td>
|
||
|
|
<td align="left" valign="top">CHAR(46)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">384</td>
|
||
|
|
<td align="center" valign="top">180</td>
|
||
|
|
<td align="left" valign="top">Array of CHAR(112)</td>
|
||
|
|
<td align="left" valign="top">Record format and based-on file list</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">*</td>
|
||
|
|
<td align="center" valign="top">*</td>
|
||
|
|
<td align="left" valign="top">Array of CHAR(320)</td>
|
||
|
|
<td align="left" valign="top">Constraint indexes information</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
<h3><a name="HDRRFBOFL">Record Format and Based-On File List Entry</a></h3>
|
||
|
|
|
||
|
|
<p>The second from the last entry in the MBRD0300 format is the record format
|
||
|
|
and based-on file list. There can be several entries with the information
|
||
|
|
presented in the order shown in the following table. Because there can be
|
||
|
|
several, it is not possible to list the exact offsets for the 112 bytes.
|
||
|
|
Physical files always have only one entry. To determine the number of entries
|
||
|
|
for a logical file, refer to the value in the number of based-on physical file
|
||
|
|
members field in the MBRD0200 format.</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%">Based-on physical file 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">Based-on physical file 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(10)</td>
|
||
|
|
<td align="left" valign="top">Based-on physical file member name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">30</td>
|
||
|
|
<td align="center" valign="top">1E</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Format name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">40</td>
|
||
|
|
<td align="center" valign="top">28</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Logical file record format number</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">44</td>
|
||
|
|
<td align="center" valign="top">2C</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Current number of records, if less than
|
||
|
|
2,147,483,647</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">48</td>
|
||
|
|
<td align="center" valign="top">30</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Number of deleted records, if less than
|
||
|
|
2,147,483,647</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">52</td>
|
||
|
|
<td align="center" valign="top">34</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Access path size</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">56</td>
|
||
|
|
<td align="center" valign="top">38</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Access path size multiplier</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">60</td>
|
||
|
|
<td align="center" valign="top">3C</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Access path shared</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">61</td>
|
||
|
|
<td align="center" valign="top">3D</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Access path valid</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">62</td>
|
||
|
|
<td align="center" valign="top">3E</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Access path held</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">63</td>
|
||
|
|
<td align="center" valign="top">3F</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Access path owner file name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">73</td>
|
||
|
|
<td align="center" valign="top">49</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Access path owner library name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">83</td>
|
||
|
|
<td align="center" valign="top">53</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Access path owner member name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">93</td>
|
||
|
|
<td align="center" valign="top">5D</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Access path journaled</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">94</td>
|
||
|
|
<td align="center" valign="top">5E</td>
|
||
|
|
<td align="left" valign="top">CHAR(2)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">96</td>
|
||
|
|
<td align="center" valign="top">60</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Current number of records</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">100</td>
|
||
|
|
<td align="center" valign="top">64</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Number of deleted records</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">104</td>
|
||
|
|
<td align="center" valign="top">68</td>
|
||
|
|
<td align="left" valign="top">CHAR(8)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
<h3><a name="HDRMLCINF">Constraint Indexes Information</a></h3>
|
||
|
|
|
||
|
|
<p>The last entry in the MBRD0300 format is the constraint indexes information
|
||
|
|
list. There can be several entries with the information presented in the order
|
||
|
|
shown in the following table. Because there can be several entries, it is not
|
||
|
|
possible to list the exact offsets of the 321 bytes in each entry. The CHAR(8)
|
||
|
|
fields (number of constraint logical-access-path read requests and the number
|
||
|
|
of constraint physical-access-path read requests) are actually BINARY(8) fields
|
||
|
|
and require conversion by the high-level language program that is used.</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%">Constraint library name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">10</td>
|
||
|
|
<td align="center" valign="top">A</td>
|
||
|
|
<td align="left" valign="top">BINARY(2)</td>
|
||
|
|
<td align="left" valign="top">Constraint name length</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">12</td>
|
||
|
|
<td align="center" valign="top">C</td>
|
||
|
|
<td align="left" valign="top">CHAR(258)</td>
|
||
|
|
<td align="left" valign="top">Constraint name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">270</td>
|
||
|
|
<td align="center" valign="top">10E</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Access path size</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">274</td>
|
||
|
|
<td align="center" valign="top">112</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Access path size multiplier</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">278</td>
|
||
|
|
<td align="center" valign="top">116</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Access path shared</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">279</td>
|
||
|
|
<td align="center" valign="top">117</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Access path valid</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">280</td>
|
||
|
|
<td align="center" valign="top">118</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Access path held</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">281</td>
|
||
|
|
<td align="center" valign="top">119</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of constraint logical-access-path read
|
||
|
|
requests</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">289</td>
|
||
|
|
<td align="center" valign="top">121</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of constraint physical-access-path read
|
||
|
|
requests</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">297</td>
|
||
|
|
<td align="center" valign="top">12F</td>
|
||
|
|
<td align="left" valign="top">CHAR(24)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="LEFT" valign="TOP" colspan="4"><sup>1</sup> CHAR(8) requires
|
||
|
|
conversion to BINARY(8). Values are not supported for Version 3 Release 2.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
<h3><a name="HDRADD0200">Additional MBRD0200 Format Information</a></h3>
|
||
|
|
|
||
|
|
<p>Additional information for the MBRD0200 format is accessed using the offset
|
||
|
|
to additional MBRD0200 format information and length of additional MBRD0200
|
||
|
|
format information values. The offset places the data at the end of the format
|
||
|
|
requested. There can be only one entry with the information presented in the
|
||
|
|
order shown in the following table. The CHAR(8) fields for the data space
|
||
|
|
activity statistics and for the data space index activity statistics are
|
||
|
|
actually BINARY(8) fields and require redefinition by the high-level language
|
||
|
|
program used.</p>
|
||
|
|
|
||
|
|
<p>The counts for the data space activity statistics are intended to be
|
||
|
|
approximate counts that are associated with the object since the last IPL.
|
||
|
|
These counts are intended to monitor performance statistics on the object and
|
||
|
|
are meant only to show trends in the operational use against the object.</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(224)</td>
|
||
|
|
<td align="left" valign="top" width="60%">Data space activity statistics</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">0</td>
|
||
|
|
<td align="center" valign="top">0</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of activate operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">8</td>
|
||
|
|
<td align="center" valign="top">8</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of deactivate operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">16</td>
|
||
|
|
<td align="center" valign="top">10</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of insert operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">24</td>
|
||
|
|
<td align="center" valign="top">18</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of update operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">32</td>
|
||
|
|
<td align="center" valign="top">20</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of delete operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">40</td>
|
||
|
|
<td align="center" valign="top">28</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of reset operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">48</td>
|
||
|
|
<td align="center" valign="top">30</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of copy operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">56</td>
|
||
|
|
<td align="center" valign="top">38</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of reorganize operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">64</td>
|
||
|
|
<td align="center" valign="top">40</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of access path build and rebuild
|
||
|
|
operations</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">72</td>
|
||
|
|
<td align="center" valign="top">48</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of logical read requests</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">80</td>
|
||
|
|
<td align="center" valign="top">50</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of physical read requests</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">88</td>
|
||
|
|
<td align="center" valign="top">58</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of records rejected by key selection</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">96</td>
|
||
|
|
<td align="center" valign="top">60</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of records rejected by nonkey
|
||
|
|
selection</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">104</td>
|
||
|
|
<td align="center" valign="top">68</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of records rejected by group-by
|
||
|
|
selection</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">112</td>
|
||
|
|
<td align="center" valign="top">70</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Number of distinct valid indexes</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">116</td>
|
||
|
|
<td align="center" valign="top">74</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Number of distinct invalid indexes</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">120</td>
|
||
|
|
<td align="center" valign="top">78</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Variable length data size</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">
|
||
|
|
124</td>
|
||
|
|
<td align="center" valign="top">7C</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Rollback ended state</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">125</td>
|
||
|
|
<td align="center" valign="top">7D</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Restored with partial transaction state</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">126</td>
|
||
|
|
<td align="center" valign="top">7E</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top"><a name="SPTJRNRCV"><em> Journal
|
||
|
|
receiver's name for transaction recovery</em></a></td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">136</td>
|
||
|
|
<td align="center" valign="top">88</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Journal receiver's library name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">146</td>
|
||
|
|
<td align="center" valign="top">92</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Journal receiver's ASP device description
|
||
|
|
name</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">156</td>
|
||
|
|
<td align="center" valign="top">9C</td>
|
||
|
|
<td align="left" valign="top">CHAR(36)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">192</td>
|
||
|
|
<td align="center" valign="top">C0</td>
|
||
|
|
<td align="left" valign="top">CHAR(36)</td>
|
||
|
|
<td align="left" valign="top">Data space index activity statistics</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">192</td>
|
||
|
|
<td align="center" valign="top">C0</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of logical-member access-path read
|
||
|
|
requests</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">200</td>
|
||
|
|
<td align="center" valign="top">C8</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of physical-member access-path read
|
||
|
|
requests</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">208</td>
|
||
|
|
<td align="center" valign="top">D0</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of unique partial keys for key field 1 or
|
||
|
|
number of unique full key values for an encoded vector access path. Will
|
||
|
|
contain zero for access paths that do not have unique key statistics
|
||
|
|
available.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">216</td>
|
||
|
|
<td align="center" valign="top">D8</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of unique partial keys for key fields 1
|
||
|
|
through 2. Will contain 0 if the access path is defined with only 1 key field,
|
||
|
|
the access path is an encoded vector, or the access path does not have unique
|
||
|
|
key statistics available.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">224</td>
|
||
|
|
<td align="center" valign="top">E0</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of unique partial keys for key fields 1
|
||
|
|
through 3. Will contain 0 if the access path is defined with only less than 3
|
||
|
|
key fields, the access path is an encoded vector, or the access path does not
|
||
|
|
have unique key statistics available.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">232</td>
|
||
|
|
<td align="center" valign="top">E8</td>
|
||
|
|
<td align="left" valign="top">CHAR(8) <sup>1</sup></td>
|
||
|
|
<td align="left" valign="top">Number of unique partial keys for key field 1
|
||
|
|
through 4 Will contain 0 if the access path is defined with only less than 4
|
||
|
|
key fields, the access path is an encoded vector, or the access path does not
|
||
|
|
have unique key statistics available.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">244</td>
|
||
|
|
<td align="center" valign="top">F4</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Number of overflow values</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">248</td>
|
||
|
|
<td align="center" valign="top">F8</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Number of delayed maintenance keys</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">252</td>
|
||
|
|
<td align="center" valign="top">FC</td>
|
||
|
|
<td align="left" valign="top">BINARY(4), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Logical page size</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">256</td>
|
||
|
|
<td align="center" valign="top">100</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Estimated rebuild time</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">260</td>
|
||
|
|
<td align="center" valign="top">104</td>
|
||
|
|
<td align="left" valign="top">BINARY(2), UNSIGNED</td>
|
||
|
|
<td align="left" valign="top">Code size, in bytes</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">262</td>
|
||
|
|
<td align="center" valign="top">106</td>
|
||
|
|
<td align="left" valign="top">CHAR(13)</td>
|
||
|
|
<td align="left" valign="top">Last rebuild date and time</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">275</td>
|
||
|
|
<td align="center" valign="top">113</td>
|
||
|
|
<td align="left" valign="top">CHAR(13)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="LEFT" valign="TOP" colspan="4"><sup>1</sup> CHAR(8) requires
|
||
|
|
redefinition to BINARY(8). Values are not supported for Version 3 Release
|
||
|
|
2.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
|
||
|
|
|
||
|
|
<h3><a name="HDRRMBRD4">MBRD0400
|
||
|
|
Format</a></h3>
|
||
|
|
|
||
|
|
<p>The MBRD0400 format includes information about data space indexes associated
|
||
|
|
with a physical file member as shown in the following table. Data space indexes
|
||
|
|
are part of either file members or constraints. File members or constraints
|
||
|
|
that share another file member's or constraint's data space index are
|
||
|
|
not returned. If the specified member is not a physical file member, an error
|
||
|
|
is returned from QUSRMBRD.</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">Number of data space indexes returned</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">Offset to the data space index list</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">*</td>
|
||
|
|
<td align="center" valign="top">*</td>
|
||
|
|
<td align="left" valign="top">Array of CHAR(*)</td>
|
||
|
|
<td align="left" valign="top">Data space index list</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<h3><a name="HDRRINXL">Data Space Index List Entry</a></h3>
|
||
|
|
|
||
|
|
<p>The last entry in the MBRD0400 format is the data space index list. There
|
||
|
|
can be several entries in the data space index list with the information
|
||
|
|
presented in the order shown in the following table. Names in the data space
|
||
|
|
index list are long alias names.</p>
|
||
|
|
|
||
|
|
<table border width="84%">
|
||
|
|
<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(800)</td>
|
||
|
|
<td align="left" valign="top" width="60%">Data space index owning file member
|
||
|
|
or constraint</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">0</td>
|
||
|
|
<td align="center" valign="top">0</td>
|
||
|
|
<td align="left" valign="top">BINARY(2)</td>
|
||
|
|
<td align="left" valign="top">File or constraint library name length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">2</td>
|
||
|
|
<td align="center" valign="top">2</td>
|
||
|
|
<td align="left" valign="top">CHAR(258)</td>
|
||
|
|
<td align="left" valign="top">File or constraint library name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">260</td>
|
||
|
|
<td align="center" valign="top">104</td>
|
||
|
|
<td align="left" valign="top">BINARY(2)</td>
|
||
|
|
<td align="left" valign="top">File or constraint name length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">262</td>
|
||
|
|
<td align="center" valign="top">106</td>
|
||
|
|
<td align="left" valign="top">CHAR(258)</td>
|
||
|
|
<td align="left" valign="top">File or constraint name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">520</td>
|
||
|
|
<td align="center" valign="top">208</td>
|
||
|
|
<td align="left" valign="top">BINARY(2)</td>
|
||
|
|
<td align="left" valign="top">File member name length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">522</td>
|
||
|
|
<td align="center" valign="top">20A</td>
|
||
|
|
<td align="left" valign="top">CHAR(258)</td>
|
||
|
|
<td align="left" valign="top">File member name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">780</td>
|
||
|
|
<td align="center" valign="top">30C</td>
|
||
|
|
<td align="left" valign="top">CHAR(11)</td>
|
||
|
|
<td align="left" valign="top">File member or constraint type</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">791</td>
|
||
|
|
<td align="center" valign="top">317</td>
|
||
|
|
<td align="left" valign="top">CHAR(9)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">800</td>
|
||
|
|
<td align="center" valign="top">320</td>
|
||
|
|
<td align="left" valign="top">CHAR(224)</td>
|
||
|
|
<td align="left" valign="top">Data space index statistics</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">800</td>
|
||
|
|
<td align="center" valign="top">320</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index valid</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">801</td>
|
||
|
|
<td align="center" valign="top">321</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index held</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">802</td>
|
||
|
|
<td align="center" valign="top">322</td>
|
||
|
|
<td align="left" valign="top">CHAR(6)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">808</td>
|
||
|
|
<td align="center" valign="top">328</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Data space index creation date and time</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">822</td>
|
||
|
|
<td align="center" valign="top">336</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Data space index last rebuild date and time</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">836</td>
|
||
|
|
<td align="center" valign="top">344</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Data space index last query use</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">850</td>
|
||
|
|
<td align="center" valign="top">352</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Data space index last query statistics use</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">864</td>
|
||
|
|
<td align="center" valign="top">360</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Data space index query use count</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">872</td>
|
||
|
|
<td align="center" valign="top">368</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Data space index query statistics use count</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">880</td>
|
||
|
|
<td align="center" valign="top">370</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Data space index query statistics second use
|
||
|
|
count</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">888</td>
|
||
|
|
<td align="center" valign="top">378</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Number of data space index keys</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">896</td>
|
||
|
|
<td align="center" valign="top">380</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Data space index size</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">904</td>
|
||
|
|
<td align="center" valign="top">388</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Number of unique partial keys for key field
|
||
|
|
1 or number of unique full key values for an encoded vector access path.
|
||
|
|
Will contain zero for access paths that do not have unique key statistics
|
||
|
|
available.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">912</td>
|
||
|
|
<td align="center" valign="top">390</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Number of unique partial keys for key fields
|
||
|
|
1 through 2. Will contain 0 if the access path is defined with only 1 key
|
||
|
|
field, the access path is an encoded vector, or the access path does not
|
||
|
|
have unique key statistics available.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">920</td>
|
||
|
|
<td align="center" valign="top">398</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Number of unique partial keys for key fields
|
||
|
|
1 through 3. Will contain 0 if the access path is defined with only less
|
||
|
|
than 3 key fields, the access path is an encoded vector, or the access path
|
||
|
|
does not have unique key statistics available.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">928</td>
|
||
|
|
<td align="center" valign="top">3A0</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Number of unique partial keys for key field
|
||
|
|
1 through 4 Will contain 0 if the access path is defined with only less
|
||
|
|
than 4 key fields, the access path is an encoded vector, or the access path
|
||
|
|
does not have unique key statistics available.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">936</td>
|
||
|
|
<td align="center" valign="top">3A8</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Estimated rebuild time, in seconds</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">940</td>
|
||
|
|
<td align="center" valign="top">3AC</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Number of delayed maintenance keys</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">944</td>
|
||
|
|
<td align="center" valign="top">3B0</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Number of overflow values</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">948</td>
|
||
|
|
<td align="center" valign="top">3B4</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Code size, in bytes</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">952</td>
|
||
|
|
<td align="center" valign="top">3B8</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Number of logical-member access-path read requests</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">960</td>
|
||
|
|
<td align="center" valign="top">3C0</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Number of physical-member access-path read requests</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top"><img src="delta.gif" alt="Start of change">968</td>
|
||
|
|
<td align="center" valign="top">3C8</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Days used count</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">972</td>
|
||
|
|
<td align="center" valign="top">3CC</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Last used date</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">986 </td>
|
||
|
|
<td align="center" valign="top">3DA</td>
|
||
|
|
<td align="left" valign="top">CHAR(8)</td>
|
||
|
|
<td align="left" valign="top">Reset date</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">994</td>
|
||
|
|
<td align="center" valign="top">3E2</td>
|
||
|
|
<td align="left" valign="top">CHAR(30)</td>
|
||
|
|
<td align="left" valign="top">Reserved<img src="deltaend.gif" alt="End of change"></td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1024</td>
|
||
|
|
<td align="center" valign="top">400</td>
|
||
|
|
<td align="left" valign="top">CHAR(126)</td>
|
||
|
|
<td align="left" valign="top">Data space index attributes</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1024</td>
|
||
|
|
<td align="center" valign="top">400</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index sparse</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1025</td>
|
||
|
|
<td align="center" valign="top">401</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index derived key</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1026</td>
|
||
|
|
<td align="center" valign="top">402</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index partitioned</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1027</td>
|
||
|
|
<td align="center" valign="top">403</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index maintenance</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1028</td>
|
||
|
|
<td align="center" valign="top">404</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index recovery</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1029</td>
|
||
|
|
<td align="center" valign="top">405</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index type</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1030</td>
|
||
|
|
<td align="center" valign="top">406</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index unique</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1031</td>
|
||
|
|
<td align="center" valign="top">407</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Data space index sort sequence</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1032</td>
|
||
|
|
<td align="center" valign="top">408</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Sort sequence table library name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1042</td>
|
||
|
|
<td align="center" valign="top">412</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Sort sequence table name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1052</td>
|
||
|
|
<td align="center" valign="top">41C</td>
|
||
|
|
<td align="left" valign="top">CHAR(3)</td>
|
||
|
|
<td align="left" valign="top">Sort sequence language ID</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1055</td>
|
||
|
|
<td align="center" valign="top">41F</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Sort sequence weight</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1056</td>
|
||
|
|
<td align="center" valign="top">420</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Logical page size</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1060</td>
|
||
|
|
<td align="center" valign="top">424</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Data space index key length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1062</td>
|
||
|
|
<td align="center" valign="top">426</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Number of data space index key fields</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1064</td>
|
||
|
|
<td align="center" valign="top">428</td>
|
||
|
|
<td align="left" valign="top">CHAR(82)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1150</td>
|
||
|
|
<td align="center" valign="top">47E</td>
|
||
|
|
<td align="left" valign="top">BIN(2)</td>
|
||
|
|
<td align="left" valign="top">Data space index key field names length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1152</td>
|
||
|
|
<td align="center" valign="top">480</td>
|
||
|
|
<td align="left" valign="top">CHAR(1024)</td>
|
||
|
|
<td align="left" valign="top">Data space index key field names</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<p><img src="delta.gif" alt="Start of change"> <br>
|
||
|
|
</p>
|
||
|
|
<h3><a name="HDRRMBRD5">MBRD0500 Format</a></h3>
|
||
|
|
<p>The MBRD0500 format includes information about materialized query tables associated
|
||
|
|
with a physical file member or logical file member as shown in the following
|
||
|
|
table. If the member is a physical file member, all materialized query tables
|
||
|
|
built over the physical file member and all materialized query tables built
|
||
|
|
over all logical file members that are dependent on the physical file member
|
||
|
|
will be returned. If the member is a logical file member, only materialized
|
||
|
|
query tables built directly over the logical file member are returned.</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" height="28">8</td>
|
||
|
|
<td align="center" valign="top" height="28">8</td>
|
||
|
|
<td align="left" valign="top" height="28">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top" height="28">Number of materialized query tables
|
||
|
|
returned</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">Offset to the materialized query table list</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">*</td>
|
||
|
|
<td align="center" valign="top">*</td>
|
||
|
|
<td align="left" valign="top">Array of CHAR(*)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table list</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<br>
|
||
|
|
<h3><a name="HDRRMQTL">Data Space Materialized Query Table List Entry</a></h3>
|
||
|
|
<p>The last entry in the MBRD0500 format is the materialized query table list.
|
||
|
|
There can be several entries in the materialized query table list with the information
|
||
|
|
presented in the order shown in the following table. Names in the materialized
|
||
|
|
query table list are long alias names.</p>
|
||
|
|
<table border width="84%">
|
||
|
|
<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%" height="26">0</td>
|
||
|
|
<td align="center" valign="top" width="10%" height="26">0</td>
|
||
|
|
<td align="left" valign="top" width="20%" height="26">CHAR(800)</td>
|
||
|
|
<td align="left" valign="top" width="60%" height="26">Materialized query table
|
||
|
|
owning file member</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">0</td>
|
||
|
|
<td align="center" valign="top">0</td>
|
||
|
|
<td align="left" valign="top">BINARY(2)</td>
|
||
|
|
<td align="left" valign="top">File library name length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">2</td>
|
||
|
|
<td align="center" valign="top">2</td>
|
||
|
|
<td align="left" valign="top">CHAR(258)</td>
|
||
|
|
<td align="left" valign="top">File library name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">260</td>
|
||
|
|
<td align="center" valign="top">104</td>
|
||
|
|
<td align="left" valign="top">BINARY(2)</td>
|
||
|
|
<td align="left" valign="top">File name length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">262</td>
|
||
|
|
<td align="center" valign="top">106</td>
|
||
|
|
<td align="left" valign="top">CHAR(258)</td>
|
||
|
|
<td align="left" valign="top">File name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">520</td>
|
||
|
|
<td align="center" valign="top">208</td>
|
||
|
|
<td align="left" valign="top">BINARY(2)</td>
|
||
|
|
<td align="left" valign="top">File member name length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">522</td>
|
||
|
|
<td align="center" valign="top">20A</td>
|
||
|
|
<td align="left" valign="top">CHAR(258)</td>
|
||
|
|
<td align="left" valign="top">File member name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">780</td>
|
||
|
|
<td align="center" valign="top">30C</td>
|
||
|
|
<td align="left" valign="top">CHAR(20)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">800</td>
|
||
|
|
<td align="center" valign="top">320</td>
|
||
|
|
<td align="left" valign="top">CHAR(162)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table statistics</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">800</td>
|
||
|
|
<td align="center" valign="top">320</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table enabled</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">801</td>
|
||
|
|
<td align="center" valign="top">321</td>
|
||
|
|
<td align="left" valign="top">CHAR(7)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">808</td>
|
||
|
|
<td align="center" valign="top">328</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table creation date and time</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top" height="29">822</td>
|
||
|
|
<td align="center" valign="top" height="29">336</td>
|
||
|
|
<td align="left" valign="top" height="29">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top" height="29">Materialized query table last refresh
|
||
|
|
date and time</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">836</td>
|
||
|
|
<td align="center" valign="top">344</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table last query use</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">850</td>
|
||
|
|
<td align="center" valign="top">352</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table last query statistics
|
||
|
|
use</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">864</td>
|
||
|
|
<td align="center" valign="top">360</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table query use count</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">872</td>
|
||
|
|
<td align="center" valign="top">368</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table query statistics use
|
||
|
|
count</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top" height="22">880</td>
|
||
|
|
<td align="center" valign="top" height="22">370</td>
|
||
|
|
<td align="left" valign="top" height="22">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top" height="22">Materialized query table row count</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">888</td>
|
||
|
|
<td align="center" valign="top">378</td>
|
||
|
|
<td align="left" valign="top">BINARY(8)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table size</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">896</td>
|
||
|
|
<td align="center" valign="top">380</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Last change date</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">910</td>
|
||
|
|
<td align="center" valign="top">38E</td>
|
||
|
|
<td align="left" valign="top">CHAR(14)</td>
|
||
|
|
<td align="left" valign="top">Last used date</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">924</td>
|
||
|
|
<td align="center" valign="top">39C</td>
|
||
|
|
<td align="left" valign="top">BINARY(4)</td>
|
||
|
|
<td align="left" valign="top">Days used count</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">928</td>
|
||
|
|
<td align="center" valign="top">3A0</td>
|
||
|
|
<td align="left" valign="top">CHAR(8)</td>
|
||
|
|
<td align="left" valign="top">Reset date</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">936</td>
|
||
|
|
<td align="center" valign="top">3A8</td>
|
||
|
|
<td align="left" valign="top">CHAR(40)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">976</td>
|
||
|
|
<td align="center" valign="top">3D0</td>
|
||
|
|
<td align="left" valign="top">CHAR(78)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table attributes</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">976</td>
|
||
|
|
<td align="center" valign="top">3D0</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table maintenance mode</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">977</td>
|
||
|
|
<td align="center" valign="top">3D1</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table initial data </td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">978</td>
|
||
|
|
<td align="center" valign="top">3D2</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table refresh mode</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">979</td>
|
||
|
|
<td align="center" valign="top">3D3</td>
|
||
|
|
<td align="left" valign="top">CHAR(2)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table refresh isolation level</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">981</td>
|
||
|
|
<td align="center" valign="top">3D5</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table sort sequence</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">982</td>
|
||
|
|
<td align="center" valign="top">3D6</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table sort sequence table
|
||
|
|
library name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">992</td>
|
||
|
|
<td align="center" valign="top">3E0</td>
|
||
|
|
<td align="left" valign="top">CHAR(10)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table sort sequence table
|
||
|
|
name</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1002</td>
|
||
|
|
<td align="center" valign="top">3EA</td>
|
||
|
|
<td align="left" valign="top">CHAR(3)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table sort sequence language
|
||
|
|
ID</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1005</td>
|
||
|
|
<td align="center" valign="top">3ED</td>
|
||
|
|
<td align="left" valign="top">CHAR(1)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table sort sequence weight</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1006</td>
|
||
|
|
<td align="center" valign="top">3EE</td>
|
||
|
|
<td align="left" valign="top">CHAR(48)</td>
|
||
|
|
<td align="left" valign="top">Reserved</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1054</td>
|
||
|
|
<td align="center" valign="top">41E</td>
|
||
|
|
<td align="left" valign="top">CHAR(30006)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table SELECT attributes</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1054</td>
|
||
|
|
<td align="center" valign="top">41E</td>
|
||
|
|
<td align="left" valign="top">BIN(4)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table SELECT statement CCSID</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1058</td>
|
||
|
|
<td align="center" valign="top">422</td>
|
||
|
|
<td align="left" valign="top">BIN(2)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table SELECT statement length</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="center" valign="top">1060</td>
|
||
|
|
<td align="center" valign="top">424</td>
|
||
|
|
<td align="left" valign="top">CHAR(5000)</td>
|
||
|
|
<td align="left" valign="top">Materialized query table SELECT statement</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<img src=
|
||
|
|
"deltaend.gif" alt="End of change"><br>
|
||
|
|
|
||
|
|
|
||
|
|
<h3><a name="HDRMBRDD">Field Descriptions</a></h3>
|
||
|
|
|
||
|
|
<p><strong>Access path held.</strong> Indicates if rebuild of access path is
|
||
|
|
held. More information can be found in the <a href="../cl/edtrbdap.htm">Edit
|
||
|
|
Rebuild Access Path (EDTRBDAP)</a> command in the Control Language (CL)
|
||
|
|
information. Possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">Not applicable unless the access path is for a
|
||
|
|
join logical file or keyed file. Only indexes that are not valid can be
|
||
|
|
held.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Access path is not held.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Access path is held.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Access path journaled.</strong> Whether the access path is
|
||
|
|
journaled.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">Does not apply.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Access path is not journaled.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Access path is journaled.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 2</em></td>
|
||
|
|
<td align="left" valign="top">Access path is journaled for system managed
|
||
|
|
access path protection (SMAPP).</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Access path maintenance.</strong> Specifies, for files with key
|
||
|
|
fields or join logical files, the type of access path maintenance used for all
|
||
|
|
members of the physical or logical file. The possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">Does not apply unless the access path is for a
|
||
|
|
join logical file or a keyed file.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">The access path is updated each time a record is
|
||
|
|
changed, added, or deleted from a member. Files that require unique keys are
|
||
|
|
0.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">The access path is updated when the member is
|
||
|
|
opened with records that have been added, deleted, or changed from the member
|
||
|
|
since the last time the member was opened.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 2</em></td>
|
||
|
|
<td align="left" valign="top">The access path is completely rebuilt each time a
|
||
|
|
file member is opened. The access path is maintained until the member is
|
||
|
|
closed, then the access path is deleted.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Access path owner file name.</strong> The file name that owns the
|
||
|
|
access path. This field only applies to join logical files or keyed files.</p>
|
||
|
|
|
||
|
|
<p><strong>Access path owner library name.</strong> The library in which the
|
||
|
|
file resides that owns the access path. This field only applies to join logical
|
||
|
|
files or keyed files.</p>
|
||
|
|
|
||
|
|
<p><strong>Access path owner member name.</strong> The member within the
|
||
|
|
qualified file name that owns the access path. This field only applies to join
|
||
|
|
logical files or keyed files.</p>
|
||
|
|
|
||
|
|
<p><strong>Access path recovery.</strong> Whether the access path for the
|
||
|
|
constraint, is rebuild immediately when damage to the access path is
|
||
|
|
recognized.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">Does not apply.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Does not apply.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Access path is rebuilt *IMMED.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Access path shared.</strong> Whether an access path is shared. The
|
||
|
|
possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" width="10%"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top" width="90%">Does not apply unless the access path
|
||
|
|
is for a join logical file or keyed file.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Access path is not shared by other files.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Access path is shared by other files.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Access path size.</strong> The access path size in bytes for this
|
||
|
|
file member. If the file member is not keyed, the value 0 is returned. DDM
|
||
|
|
files, which are not from a System/38 or iSeries system, return value 0.</p>
|
||
|
|
|
||
|
|
<p><strong>Access path size multiplier.</strong> The value to multiply the
|
||
|
|
access path size by to get its true size.</p>
|
||
|
|
|
||
|
|
<p><strong>Access path valid.</strong> Whether the access path is valid. The
|
||
|
|
possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">Does not apply unless the access path is for a
|
||
|
|
join logical file or a keyed file.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> Y</em></td>
|
||
|
|
<td align="left" valign="top">Index is valid.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> N</em></td>
|
||
|
|
<td align="left" valign="top">Index is not valid and must be rebuilt.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Allow delete operation.</strong> Whether records in this file can be
|
||
|
|
deleted. The possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> Y</em></td>
|
||
|
|
<td align="left" valign="top">Records in this file can be
|
||
|
|
deleted.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> N</em></td>
|
||
|
|
<td align="left" valign="top">Records in this file cannot be deleted.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Allow read operation.</strong> Whether records in the physical file
|
||
|
|
can be read. The possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> Y</em></td>
|
||
|
|
<td align="left" valign="top">Records in this file can be
|
||
|
|
read.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> N</em></td>
|
||
|
|
<td align="left" valign="top">Records in this file cannot be read.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Allow update operation.</strong> Whether records in this file can be
|
||
|
|
updated. The possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> Y</em></td>
|
||
|
|
<td align="left" valign="top">Records in this file can be
|
||
|
|
updated.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> N</em></td>
|
||
|
|
<td align="left" valign="top">Records in this file cannot be updated.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Allow write operation.</strong> Whether records can be written to
|
||
|
|
the file. The possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> Y</em></td>
|
||
|
|
<td align="left" valign="top">Records can be written to this
|
||
|
|
file.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> N</em></td>
|
||
|
|
<td align="left" valign="top">Records cannot be written to this file.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Based-on physical file library name.</strong> The library in which
|
||
|
|
the based-on physical file resides. This field is blank for a physical
|
||
|
|
file.</p>
|
||
|
|
|
||
|
|
<p><strong>Based-on physical file member name.</strong> The physical file
|
||
|
|
member this logical file member is based on. The number of elements in this
|
||
|
|
array is defined by the number of based-on physical file members field. This
|
||
|
|
field is blank for a physical file.</p>
|
||
|
|
|
||
|
|
<p><strong>Based-on physical file name.</strong> The name of the physical file
|
||
|
|
that contains the data associated with the logical file member. This field is
|
||
|
|
blank for a physical file.</p>
|
||
|
|
|
||
|
|
<p><strong>Bytes available.</strong> The number of bytes of data available to
|
||
|
|
be returned. All available data is returned if enough space is provided.</p>
|
||
|
|
|
||
|
|
<p><strong>Bytes returned.</strong> The number of bytes of data returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Change date and time.</strong> The date and time this member was
|
||
|
|
changed. This field is in the CYYMMDDHHMMSS format as follows:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<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>Code size.</strong> The length of the code assigned to each distinct
|
||
|
|
key value of an encoded vector index. If the access path is not an encoded
|
||
|
|
vector, the value 0 is returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Constraint library name.</strong> The name of the library containing
|
||
|
|
the file to which the referential constraint applies.</p>
|
||
|
|
|
||
|
|
<p><strong>Constraint name.</strong> The name of the referential constraint
|
||
|
|
that controls the insertion, deletion, and update of fields that refer to like
|
||
|
|
fields in a parent file.</p>
|
||
|
|
|
||
|
|
<p><strong>Constraint name length.</strong> The length of the referential
|
||
|
|
constraint name. The maximum length is 258 characters for delimited names and
|
||
|
|
128 characters for non-delimited names.</p>
|
||
|
|
|
||
|
|
<p><strong>Creation date and time.</strong> The date and time the member was
|
||
|
|
created. This field is in the CYYMMDDHHMMSS format, which is described in the
|
||
|
|
change date and time field description.</p>
|
||
|
|
|
||
|
|
<p><strong>Current number of increments.</strong> The number of increments that
|
||
|
|
have been added to the member size (data space size). This field is 0 for
|
||
|
|
logical files because the number of increments only applies to physical
|
||
|
|
files.</p>
|
||
|
|
|
||
|
|
<p><strong>Current number of records.</strong> The number of records that
|
||
|
|
currently exist in this member. A keyed logical file member returns the number
|
||
|
|
of index entries. A nonkeyed logical file member returns the number of records
|
||
|
|
in the based-on physical file member. If the requested physical file member is
|
||
|
|
suspended, the value 0 is returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Current number of records, if less than 2,147,483,647.</strong> The
|
||
|
|
number of records that currently exist in this member. A keyed logical file
|
||
|
|
member returns the number of index entries. A nonkeyed logical file member
|
||
|
|
returns the number of records in the based-on physical file member. If the
|
||
|
|
requested physical file member is suspended, the value -1 is returned. If the
|
||
|
|
number of records is greater than or equal to 2,147,483,647, the value -2 is
|
||
|
|
returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Current number of records for all based-on members.</strong> The
|
||
|
|
number of records that currently exist in this member. A logical member returns
|
||
|
|
the summarization of index entries. If the requested physical file member is
|
||
|
|
suspended, the value 0 is returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Current number of records for all based-on members, if less than
|
||
|
|
2,147,483,647.</strong> The number of records that currently exist in this
|
||
|
|
member. A logical member returns the summarization of index entries. If the
|
||
|
|
requested physical file member is suspended, the value -1 is returned. If the
|
||
|
|
number of records is greater than or equal to 2,147,483,647, the value -2 is
|
||
|
|
returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space activity statistics.</strong> Information on the activity
|
||
|
|
that has occurred on this member since the last IPL. All of these values are
|
||
|
|
reset to binary 0 the first time the object is used after or during an IPL.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index activity statistics.</strong> Information on the
|
||
|
|
activity that has occurred on this member access path since the last IPL. All
|
||
|
|
of these values are reset to binary 0 the first time the object is used after
|
||
|
|
or during an IPL.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index
|
||
|
|
attributes.</strong> Information on the attributes of the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index creation date and time.</strong> The date and time
|
||
|
|
this data space index was created. This is in the YYYYMMDDHHMMSS format.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index derived key.</strong> Whether the each key field
|
||
|
|
defined for the data space index has the same attributes and is directly mapped
|
||
|
|
from a field in the based on physical file member, or whether some mapping or
|
||
|
|
derivation is performed to produce the key values. 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">Data space index does not contain
|
||
|
|
derived key values.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Data space index contains derived key
|
||
|
|
values.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index held.</strong> Indicates if rebuild of the data
|
||
|
|
space index is held. More information can be found in the <a href=
|
||
|
|
"../cl/edtrbdap.htm">Edit Rebuild Access Path (EDTRBDAP)</a> command in the
|
||
|
|
Control Language (CL) information. 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">Data space index is not held.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Data space index is held.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index key length.</strong> The maximum length of the key
|
||
|
|
of the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index key field names length.</strong> The length of the
|
||
|
|
key field names.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index key field names.</strong> A list of each key field
|
||
|
|
of the data space index. Each key field name is separated by a comma and a
|
||
|
|
blank. If list of key field names will be truncated if it exceeds 1024
|
||
|
|
bytes.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index last query statistics use.</strong> The date and
|
||
|
|
time the last time this data space index was used for statistics when
|
||
|
|
optimizing a query. This is in the YYYYMMDDHHMMSS format.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index last query use.</strong> The date and time the last
|
||
|
|
time this data space index was used in a query full open. This is in the
|
||
|
|
YYYYMMDDHHMMSS format.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index last rebuild date and time.</strong> The date and
|
||
|
|
time the last time this data space index was rebuilt. This is in the
|
||
|
|
YYYYMMDDHHMMSS format.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index list.</strong> Information about all the data space
|
||
|
|
indexes build on a physical file member.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index maintenance.</strong> Specifies the type of
|
||
|
|
maintenance used for the data space index. 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 data space index is updated each time a
|
||
|
|
record is changed, added, or deleted from a member. Unique data space indexes
|
||
|
|
are 0.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">The data space index is updated when the owning
|
||
|
|
member is opened. The data space index is updated with keys that have been
|
||
|
|
added, deleted, or changed in the member since the last time the member was
|
||
|
|
opened.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 2</em></td>
|
||
|
|
<td align="left" valign="top">The data space index is completely rebuilt each
|
||
|
|
time the owning member is opened. The data space index is maintained until the
|
||
|
|
member is closed, then the data space index is invalidated.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index owning file member or constraint.</strong>
|
||
|
|
Information on the owner of the data space index. A data space index can be
|
||
|
|
owned by a file member or a constraint.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index partitioned.</strong> Whether the data space index
|
||
|
|
contains key values from a single physical file member or whether the data
|
||
|
|
space index contains key values from more than one data space. 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">Data space index is not partitioned.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Data space index is partitioned.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 2</em></td>
|
||
|
|
<td align="left" valign="top">Data space index is a multi-member logical file
|
||
|
|
data space index.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index query use count.</strong> The number of times the
|
||
|
|
index has been used in a full open of a query since the start of V5R3 or since
|
||
|
|
the count has been reset by CHGOBJD.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index query statistics use count.</strong> The total
|
||
|
|
number of times the index has been used for statistics when optimizing a query
|
||
|
|
since the start of V5R3 or since the count has been reset by CHGOBJD.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index query statistics second use count.</strong> The
|
||
|
|
number of times the index has been used for more expensive statistics when
|
||
|
|
optimizing a query since the start of V5R3 or since the count has been reset by
|
||
|
|
CHGOBJD.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index recovery.</strong> Whether the data space index is
|
||
|
|
rebuild immediately when damage to the access path is recognized after an
|
||
|
|
abnormal IPL.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Data space index is rebuilt during IPL.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Data space index is rebuilt after IPL.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 2</em></td>
|
||
|
|
<td align="left" valign="top">Data space index is not rebuilt because it is
|
||
|
|
rebuild maintenance.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index size.</strong> The size, in bytes, of the data space
|
||
|
|
index.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index sort sequence.</strong> Indicates whether the keys
|
||
|
|
in the index use a sort sequence. 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 sort sequence.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">An alternate collating sequence is used
|
||
|
|
(ALTSEQ).</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 2</em></td>
|
||
|
|
<td align="left" valign="top">A sort sequence is used (SRTSEQ).</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index sparse.</strong> Whether the data space index
|
||
|
|
contains selection criteria that limits the rows which have keys in the data
|
||
|
|
space index. 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">Data space index is not sparse.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Data space index is sparse. A data space index
|
||
|
|
may be sparse if it is owned by a logical file that contains select/omit
|
||
|
|
specifications or if it is a temporary index used for a query.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index statistics.</strong> Information on the current
|
||
|
|
statistics of the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space index type.</strong> Indicates the type of the data space
|
||
|
|
index. 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">Binary radix tree, maximum 1TB</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Binary radix tree, maximum 4GB</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 2</em></td>
|
||
|
|
<td align="left" valign="top">Encoded vector index</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index unique.</strong> Indicates whether the keys in the
|
||
|
|
data space index are unique and if not what order is maintained for duplicate
|
||
|
|
keys. 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">Unique. Null values are treated the same as other
|
||
|
|
values (only one key with a null value is allowed).</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Unique. Null values are not treated the same as
|
||
|
|
other values (any number of keys with a null value are allowed).</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top">2</td>
|
||
|
|
<td align="left" valign="top">Not unique. Duplicates are maintained first in,
|
||
|
|
first out (FIFO).</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top">3</td>
|
||
|
|
<td align="left" valign="top">Not unique. Duplicates are maintained last in,
|
||
|
|
first out (LIFO).</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 4</em></td>
|
||
|
|
<td align="left" valign="top">Not unique. Duplicates are maintained first
|
||
|
|
change, first out (FCFO).</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space index valid.</strong> Whether the data space index is
|
||
|
|
valid. 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">Data space index is not valid and must be
|
||
|
|
rebuilt.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Data space index is valid.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Data space size.</strong> The size of the space that contains the
|
||
|
|
data of the file member, in bytes. A logical file returns a 0.</p>
|
||
|
|
|
||
|
|
<p><strong>Data space size multiplier.</strong> The value to multiply the data
|
||
|
|
space size by to get its true size. Typically this is 1, but for large files,
|
||
|
|
the value may be greater than 1. If the data space size multiplier is greater
|
||
|
|
than 1, then the value in the data space size field is not the actual size of
|
||
|
|
the file.</p>
|
||
|
|
|
||
|
|
<p><strong>Database file library name.</strong> The name of the library that
|
||
|
|
contains the file.</p>
|
||
|
|
|
||
|
|
<p><strong>Database file name.</strong> The name of the file from which the
|
||
|
|
member list was retrieved.</p>
|
||
|
|
|
||
|
|
<p><strong>Date last used.</strong> The century and date this member was last
|
||
|
|
used. The date last used field is in the CYYMMDD format as follows:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">*NONE</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<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>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><img src="delta.gif" alt="Start of change"> <strong>Days used count.</strong>
|
||
|
|
The number of days the object was used. If the object does not have a last used
|
||
|
|
date, the count is 0.<img src=
|
||
|
|
"deltaend.gif" alt="End of change"></p>
|
||
|
|
<p><strong>Estimated rebuild time.</strong> The estimated time, in seconds, to
|
||
|
|
completely rebuild the access path. If the access path is being rebuilt
|
||
|
|
currently, the value is -1. If a delayed maintenance index is being caught up
|
||
|
|
currently, the value is -2. For an encoded vector index, the value is 0.</p>
|
||
|
|
|
||
|
|
<p><strong>Expiration date.</strong> The date that this member expires. This is
|
||
|
|
in the CYYMMDD format, which is the same format described for the date last
|
||
|
|
used field description.</p>
|
||
|
|
|
||
|
|
<p><strong>File attribute.</strong> The type of file found:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> PF</em></td>
|
||
|
|
<td align="left" valign="top">Physical file</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> LF</em></td>
|
||
|
|
<td align="left" valign="top">Logical file</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> DDMF</em></td>
|
||
|
|
<td align="left" valign="top">Distributed data management file</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong><img src="delta.gif" alt="Start of change">File library name length.</strong>
|
||
|
|
Length of the name of the library that contains the file member that owns the
|
||
|
|
materialized query table.</p>
|
||
|
|
<p><strong>File library name.</strong> Name of the library that contains the file
|
||
|
|
member that owns the materialized query table.</p>
|
||
|
|
<p><strong>File name length.</strong> Length of the name of the file that owns
|
||
|
|
the materialized query table.</p>
|
||
|
|
<p><strong>File name.</strong> Name of the file that owns the materialized query
|
||
|
|
table. <img src=
|
||
|
|
"deltaend.gif" alt="End of change"></p>
|
||
|
|
|
||
|
|
<p><strong>File or constraint
|
||
|
|
library name length.</strong> Length of the name of the library that contains
|
||
|
|
the file member or constraint that owns the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>File or constraint library name.</strong> Name of the library that
|
||
|
|
contains the file member or constraint that owns the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>File or constraint name length.</strong> Length of the name of the
|
||
|
|
file or constraint that owns the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>File or constraint name.</strong> Name of the file or constraint
|
||
|
|
that owns the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>File member name length.</strong> Length of the name of the file member
|
||
|
|
that owns the data space index <strong><img src="delta.gif" alt="Start of change"></strong>or
|
||
|
|
materialized query table. <img src=
|
||
|
|
"deltaend.gif" alt="End of change"> This field is zero if the data space index
|
||
|
|
is owned by a constraint.</p>
|
||
|
|
|
||
|
|
<p><strong>File member name.</strong> Name of the file member that owns the data
|
||
|
|
space index <strong><img src="delta.gif" alt="Start of change"></strong>or
|
||
|
|
materialized query table. <img src=
|
||
|
|
"deltaend.gif" alt="End of change"> This field is blank if the data space
|
||
|
|
index is owned by a constraint.</p>
|
||
|
|
|
||
|
|
<p><strong>File member or constraint type.</strong> Type of the file member or
|
||
|
|
constraint that owns the data space index. A data space index can be owned by a
|
||
|
|
file member or a constraint.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="15 85" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top">FOREIGN KEY</td>
|
||
|
|
<td align="left" valign="top">Referential integrity constraint</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> INDEX</em></td>
|
||
|
|
<td align="left" valign="top">SQL index</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> LOGICAL</em></td>
|
||
|
|
<td align="left" valign="top">Logical file member</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> PHYSICAL</em></td>
|
||
|
|
<td align="left" valign="top">Physical file member</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> PRIMARY KEY</em></td>
|
||
|
|
<td align="left" valign="top">Primary key constraint</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top">TEMPORARY</td>
|
||
|
|
<td align="left" valign="top">Temporary index</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> UNIQUE</em></td>
|
||
|
|
<td align="left" valign="top">Unique constraint</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<p><strong>Force keyed access path.</strong> Force the access path to be
|
||
|
|
keyed.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Do not force keyed access path</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Force a keyed access path</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Format name.</strong> The definition of how data is structured in
|
||
|
|
the records contained in a file. If this is a join logical file or SQL view
|
||
|
|
file, the format name is only valid for the entry in the record format and
|
||
|
|
based-on file member list array.</p>
|
||
|
|
|
||
|
|
<p><strong>Increment number of records.</strong> The maximum number of records
|
||
|
|
that are automatically added to the member when the number of records in the
|
||
|
|
member is greater than the initial member size. This field applies only to
|
||
|
|
physical files and is 0 for logical files.</p>
|
||
|
|
|
||
|
|
<p><strong>Initial number of records.</strong> The number of records that can
|
||
|
|
be written to each member of the file before the member size is automatically
|
||
|
|
extended. This field applies only to physical files and is 0 for logical
|
||
|
|
files.</p>
|
||
|
|
|
||
|
|
<p><strong>Join member.</strong> Whether the member's logical file member
|
||
|
|
combines (in one record format) fields from two or more physical file
|
||
|
|
members.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Not a join member</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Join member</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<p><strong>Journal receiver's ASP device description name.</strong> The
|
||
|
|
name of the ASP device description that contained the journal receiver's
|
||
|
|
library.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">*NONE</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Journal receiver's library name.</strong> The name of the
|
||
|
|
library that contained the journal receiver.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">*NONE</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Journal receiver's name for transaction recovery.</strong> The
|
||
|
|
earliest journal receiver that will be needed to recover using either the Apply
|
||
|
|
Journaled Changes (APYJRNCHG) or the Remove Journaled Changes (RMVJRNCHG)
|
||
|
|
command.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">*NONE</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<p><strong><img src="delta.gif" alt="Start of change"></strong><strong>Last
|
||
|
|
change date.</strong> The date the object was last changed. This field is in
|
||
|
|
the YYYYMMDDHHMMSS format. If the object has no last changed date, the field
|
||
|
|
is blank.<img src=
|
||
|
|
"deltaend.gif" alt="End of change"></p>
|
||
|
|
<p><strong>Last rebuild date and time.</strong> The data and time of the most
|
||
|
|
recent, successful rebuild or delayed maintenance catch up of the access path.
|
||
|
|
This field is in the CYYMMDDHHMMSS format, which is described in the change
|
||
|
|
date and time field description.</p>
|
||
|
|
<p><strong>Last source change or table refresh date and time.</strong> For source
|
||
|
|
files, the date and time that this source member was last changed. For SQL materialized
|
||
|
|
query tables, the date and time that the last SQL Refresh Table statement refreshed
|
||
|
|
this member. If the member has never been refreshed, this field will contain
|
||
|
|
hexadecimal zeroes. This field isin the CYYMMDDHHMMSS format, which is in the
|
||
|
|
same format as the change date and time field.</p>
|
||
|
|
<p><strong><img src="delta.gif" alt="Start of change"></strong><strong>Last
|
||
|
|
used date.</strong> The date the object was last used. This field is in the
|
||
|
|
YYYYMMDDHHMMSS format. If the object has no last used date, the field is blank.<img src=
|
||
|
|
"deltaend.gif" alt="End of change"></p>
|
||
|
|
<p><strong>Logical file or physical file.</strong> Whether the file is a logical
|
||
|
|
or physical 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">Member retrieved from a physical
|
||
|
|
file</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Member retrieved from a logical file</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Logical file record format number.</strong> The entry number in the
|
||
|
|
record format and based-on file member list. This number then corresponds to
|
||
|
|
the based-on member listed in this entry. This field only applies to logical
|
||
|
|
files and is 0 for a physical file.</p>
|
||
|
|
|
||
|
|
<p><strong>Logical page size.</strong> The number of bytes used for the access
|
||
|
|
path's logical page size. If the access path is an encoded vector, the value
|
||
|
|
0 is returned.</p>
|
||
|
|
<p><img src="delta.gif" alt="Start of change"> <strong>Materialized query
|
||
|
|
table attributes.</strong> Information on the attributes of the materialized
|
||
|
|
query table.</p>
|
||
|
|
<p><strong>Materialized query table creation date and time.</strong> The date
|
||
|
|
and time this materialized query table was created. This is in the YYYYMMDDHHMMSS
|
||
|
|
format.</p>
|
||
|
|
<p><strong>Materialized query table enabled.</strong> Whether the materialized
|
||
|
|
query table can be used for query optimization. Possible values are:</p>
|
||
|
|
<table cellpadding="5" width="889">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="3"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top" height="3">The materialized query table can
|
||
|
|
not be used for query optimization (DISABLE QUERY OPTIMIZATION).</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">The materialized query table can be used for
|
||
|
|
query optimization (ENABLE QUERY OPTIMIZATION).</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<p><strong>Materialized query table initial data.</strong> Whether data was inserted
|
||
|
|
into the materialized query table when it was created. Possible values are:</p>
|
||
|
|
<table cellpadding="5" width="863">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="25"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top" height="25">Data was not inserted into the materialized
|
||
|
|
query table was created (DATA INITIALLY DEFERRED). </td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Data was inserted into the materialized query
|
||
|
|
table was created (DATA INITIALLY IMMEDIATE). </td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<p><strong>Materialized query table last query statistics use.</strong> The date
|
||
|
|
and time the last time this materialized query table was used for statistics
|
||
|
|
when optimizing a query. This is in the YYYYMMDDHHMMSS format.</p>
|
||
|
|
<p><strong>Materialized query table last query use.</strong> The date and time
|
||
|
|
the last time this materialized query table was used in a query full open. This
|
||
|
|
is in the YYYYMMDDHHMMSS format.</p>
|
||
|
|
|
||
|
|
<p><strong>Materialized query table last refresh date and time.</strong> The date
|
||
|
|
and time this materialized query table was last refreshed. This is in the YYYYMMDDHHMMSS
|
||
|
|
format.</p>
|
||
|
|
<p><strong>Materialized query table list.</strong> Information about all the materialized
|
||
|
|
query tables built on a file member.</p>
|
||
|
|
<p><strong>Materialized query table maintenance mode.</strong> Whether the materialized
|
||
|
|
query table is maintained by the user or the system. Materialized query tables
|
||
|
|
are currently only maintained by the user. Possible values are:</p>
|
||
|
|
<table cellpadding="5" width="905">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="18"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top" height="18">The materialized query table is
|
||
|
|
maintained by the system (MAINTAINED BY SYSTEM). </td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">The materialized query table is maintained by
|
||
|
|
the user (MAINTAINED BY USER).</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<p><strong>Materialized query table owning file member.</strong> Information on
|
||
|
|
the owner of the materialized query table.</p>
|
||
|
|
<p><strong>Materialized query table query use count.</strong> The number of times
|
||
|
|
the materialized query table has been used in a full open of a query since the
|
||
|
|
start of V5R4 or since the count has been reset by CHGOBJD.</p>
|
||
|
|
<p><strong>Materialized query table query statistics use count.</strong> The total
|
||
|
|
number of times the materialized query table has been used for statistics when
|
||
|
|
optimizing a query since the start of V5R4 or since the count has been reset
|
||
|
|
by CHGOBJD.</p>
|
||
|
|
<p><strong>Materialized query table refresh isolation level.</strong> The isolation
|
||
|
|
level the SQL SELECT statement will run under during the REFRESH TABLE SQL statement.
|
||
|
|
Possible values are:</p>
|
||
|
|
<table cellpadding="5" width="743">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="2" width="64"><em> NC</em></td>
|
||
|
|
<td align="left" valign="top" height="2" width="651">No Commit. </td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="24" width="64"><em> UR</em></td>
|
||
|
|
<td align="left" valign="top" height="24" width="651">Uncommitted Read.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="24" width="64">CS</td>
|
||
|
|
<td align="left" valign="top" height="24" width="651">Cursor Stability.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="24" width="64">CL</td>
|
||
|
|
<td align="left" valign="top" height="24" width="651">Cursor Stability Keep
|
||
|
|
Locks. </td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="24" width="64">RS</td>
|
||
|
|
<td align="left" valign="top" height="24" width="651">Read Stability.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="24" width="64"><em> RR</em></td>
|
||
|
|
<td align="left" valign="top" height="24" width="651">Repeatable Read.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<p><strong>Materialized query table refresh mode.</strong> Whether the materialized
|
||
|
|
query table can be refreshed at any time using the REFRESH TABLE SQL statement.
|
||
|
|
Materialized query tables are currently only refreshed using the REFRESH TABLE
|
||
|
|
SQL statement. Possible values are:</p>
|
||
|
|
<table cellpadding="5" width="743">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top" height="18"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top" height="18">The materialized query table is
|
||
|
|
refreshed using the REFRESH TABLE SQL statement (REFRESH DEFERRED). </td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">The materialized query table is refreshed immediately
|
||
|
|
when changes are made to the tables referenced in the materialized query
|
||
|
|
table (REFRESH IMMEDIATE).</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<p><strong>Materialized query table row count.</strong> The number of rows currently
|
||
|
|
in the materialized query table.</p>
|
||
|
|
<p><strong>Materialized query table SELECT attributes.</strong> Information about
|
||
|
|
the SQL SELECT statement of the materialized query table.</p>
|
||
|
|
<p><strong>Materialized query table SELECT statement.</strong> The SQL SELECT
|
||
|
|
statement of the materialized query table. A maximum of 30000 bytes of the SQL
|
||
|
|
SELECT statement will be returned. The QDBRTVFD API can be used if the SQL statement
|
||
|
|
exceeds 30000 bytes in length.</p>
|
||
|
|
<p><strong>Materialized query table SELECT statement length.</strong> The length
|
||
|
|
of the SQL SELECT statement of the materialized query table.</p>
|
||
|
|
<p><strong>Materialized query table SELECT statement CCSID.</strong> The CCSID
|
||
|
|
of the SQL SELECT statement of the materialized query table. </p>
|
||
|
|
<p><strong>Materialized query table size.</strong> The size, in bytes, of the
|
||
|
|
materialized query table.</p>
|
||
|
|
<p><strong>Materialized query table sort sequence.</strong> Indicates whether
|
||
|
|
the keys in the materialized query table uses a sort sequence. 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 sort sequence.</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 2</em></td>
|
||
|
|
<td align="left" valign="top">A sort sequence is used (SRTSEQ).</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<p><strong>Materialized query table sort sequence table library name.</strong>
|
||
|
|
The library in which the sort sequence table resides that was used for comparisons
|
||
|
|
in the materialized query table. The field contains blanks if a sort sequence
|
||
|
|
was not used to create the materialized query table.</p>
|
||
|
|
<p><strong>Materialized query table sort sequence table name.</strong> The sort
|
||
|
|
sequence table that was used for comparisons in the materialized query table.
|
||
|
|
The field contains blanks if a sort sequence was not used to create the materialized
|
||
|
|
query table.</p>
|
||
|
|
<p><strong>Materialized query table sort sequence language ID.</strong> The language
|
||
|
|
ID that was used to identify the sort sequence table that was used for comparisons
|
||
|
|
in the materialized query table. The field contains blanks if a sort sequence
|
||
|
|
was not used to create the materialized query table.</p>
|
||
|
|
<p><strong>Materialized query table sort sequence weight.</strong> The sort sequence
|
||
|
|
weight that was used for comparisons in the materialized query table. The field
|
||
|
|
contains blanks if a sort sequence was not used to create the materialized query
|
||
|
|
table. 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">Unique weight</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Shared weight</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
<p><strong>Materialized query table statistics.</strong> Information on the current
|
||
|
|
statistics of the materialized query table. <img src=
|
||
|
|
"deltaend.gif" alt="End of change"></p>
|
||
|
|
<p><strong>Maximum number of increments.</strong> The maximum number of increments
|
||
|
|
automatically added to the member size. This field only applies to physical
|
||
|
|
files and is 0 for a logical file.</p>
|
||
|
|
|
||
|
|
<p><strong>Maximum percentage of deleted records allowed.</strong> The maximum
|
||
|
|
allowed percentage of deleted records for each member in the physical file. The
|
||
|
|
percentage check is made when the member is closed. If the percentage of
|
||
|
|
deleted records is greater than the value shown, a message is sent to the
|
||
|
|
history log. This field only applies to physical files and is 0 when either no
|
||
|
|
deleted records are allowed or the file is a logical file.</p>
|
||
|
|
|
||
|
|
<p><strong>Member name.</strong> The name of the member whose description is
|
||
|
|
being retrieved.</p>
|
||
|
|
|
||
|
|
<p><strong>Member text description.</strong> The member's text
|
||
|
|
description.</p>
|
||
|
|
|
||
|
|
<p><strong>Member text description CCSID.</strong> The CCSID for the member
|
||
|
|
text description. The job default CCSID of the current process will be used to
|
||
|
|
translate the text. For more information about CCSID, see the <a href=
|
||
|
|
"../nls/rbagsglobalmain.htm">Globalization</a> topic.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of access path build and rebuild operations.</strong> The
|
||
|
|
number of access paths, both permanent and temporary, that have been built over
|
||
|
|
this member since the last IPL.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of access path entries.</strong> The number of access path
|
||
|
|
entries the physical file has for constraints.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of activate operations.</strong> The number of times that an
|
||
|
|
open operation has been performed over this member since the last IPL.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of based-on physical file members.</strong> The number of
|
||
|
|
database file members for the logical file member. If the member is a physical
|
||
|
|
file member, the value is 0.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of constraint logical-access-path read requests.</strong> The
|
||
|
|
number of logical read requests that have been made on keys in this constraint
|
||
|
|
access path since the last IPL. This count reflects read requests issued
|
||
|
|
regardless of whether a physical read request was actually performed. Rollback
|
||
|
|
operations will affect this count.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of constraint physical-access-path read requests.</strong>
|
||
|
|
The number of read requests that resulted in actual physical I/O requests on
|
||
|
|
constraint keys in this member since the last IPL. Logical read requests do not
|
||
|
|
necessarily result in a physical read request. Rollback operations will affect
|
||
|
|
this count.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of copy operations.</strong> The number of times that this
|
||
|
|
member has been the target of a single-entry copy instruction since the last
|
||
|
|
IPL.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of data space indexes returned.</strong> The number of data
|
||
|
|
space indexes built over the physical file member. If the number of bytes provided
|
||
|
|
is less than the number of bytes available, this number is the number of data
|
||
|
|
space indexes returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of data space index keys.</strong> The number of key values
|
||
|
|
in the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of data space index key fields.</strong> The maximum number
|
||
|
|
of key fields defined in for any key in the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of days used.</strong> The number of days the member has been
|
||
|
|
used. If the member does not have a last-used date, the value 0 is
|
||
|
|
returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of deactivate operations.</strong> The number of times that a
|
||
|
|
close operation has been performed over this member since the last IPL. Note
|
||
|
|
that the difference between the number of activate operations and the number of
|
||
|
|
deactivate operations will indicate the number of currently active open
|
||
|
|
operations over this member.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of delayed maintenance keys.</strong> The number of access
|
||
|
|
path entries that will be processed during delayed maintenance catch up time.
|
||
|
|
If the access path is an encoded vector, the value 0 is returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of delete operations.</strong> The number of records deleted
|
||
|
|
from this member since the last IPL. Delete operations performed on this member
|
||
|
|
as a result of the cascade referential constraint rule will affect this count.
|
||
|
|
Applying journal entries that result in delete operations will affect this
|
||
|
|
count. Delete operations that occur during rollback will also affect this
|
||
|
|
count.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of deleted records.</strong> The number of deleted records
|
||
|
|
returned in the file member. Keyed logical files return a 0. DDM files that are
|
||
|
|
not from a System/38 or iSeries system return a 0. If the requested physical
|
||
|
|
file member is suspended, the value 0 is returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of deleted records, if less than 2,147,483,647.</strong> The
|
||
|
|
number of deleted records returned in the file member. Keyed logical files
|
||
|
|
return a 0. DDM files that are not from a System/38 or iSeries system return a
|
||
|
|
0. If the requested physical file member is suspended, the value -1 is
|
||
|
|
returned. If the number of records is greater than or equal to 2,147,483,647,
|
||
|
|
the value -2 is returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of distinct invalid indexes.</strong> The number of distinct
|
||
|
|
invalid indexes built over this member. This includes the index created if the
|
||
|
|
file is keyed, any indexes created for dependent keyed logical files, any
|
||
|
|
indexes created for dependent join logical files, any indexes created for
|
||
|
|
dependent SQL indexes, and any indexes created for unique or referential
|
||
|
|
constraints on the file. Access paths that share an index are not included.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of distinct valid indexes.</strong> The number of distinct
|
||
|
|
valid indexes built over this member. This includes the index created if the
|
||
|
|
file is keyed, any indexes created for dependent keyed logical files, any
|
||
|
|
indexes created for dependent join logical files, any indexes created for
|
||
|
|
dependent SQL indexes, and any indexes created for unique or referential
|
||
|
|
constraints on the file. Access paths that share an index are not included.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of insert operations.</strong> The number of records inserted
|
||
|
|
into this member since the last IPL. This count does not reflect records added
|
||
|
|
to a member on behalf of a single entry copy instruction. Applying journal
|
||
|
|
entries that result in inserts will affect this count.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of logical-member access-path read requests.</strong> The
|
||
|
|
number of logical read requests that have been made on keys in this member
|
||
|
|
access path since the last IPL. This count reflects read requests issued
|
||
|
|
regardless of whether a physical read request was actually performed. Rollback
|
||
|
|
operations will affect this count.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of logical read requests.</strong> The number of logical read
|
||
|
|
requests that have been made on entries in this member since the last IPL. This
|
||
|
|
count reflects read requests issued <strong>requests</strong> regardless of
|
||
|
|
whether a physical read request was actually performed. Rollback operations
|
||
|
|
will affect this count.</p>
|
||
|
|
<p><img src="delta.gif" alt="Start of change"> <strong>Number of materialized
|
||
|
|
query tables returned.</strong> The number of materialized query tables built
|
||
|
|
over the file member. If the member is a physical file member, all materialized
|
||
|
|
query tables built over the physical file member and all materialized query
|
||
|
|
tables built over all logical file members that are dependent on the physical
|
||
|
|
file member will be returned. If the member is a logical file member, only materialized
|
||
|
|
query tables built directly over the logical file member are returned. If the
|
||
|
|
number of bytes provided is less than the number of bytes available, this number
|
||
|
|
is the number of materialized query tables returned.<img src=
|
||
|
|
"deltaend.gif" alt="End of change"></p>
|
||
|
|
|
||
|
|
<p><strong>Number of member level constraint information array
|
||
|
|
entries.</strong> The number of entries in the member level constraint
|
||
|
|
information array. The maximum number of entries is 300.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of overflow values.</strong> The number of unique key values
|
||
|
|
that do not collate in sequential order in an encoded vector. If the access
|
||
|
|
path is not an encoded vector, the value 0 is returned.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of physical-member access-path read requests.</strong> The
|
||
|
|
number of read requests that resulted in actual physical I/O requests on keys
|
||
|
|
in this member since the last IPL. Logical read requests do not necessarily
|
||
|
|
result in a physical read request. Rollback operations will affect this
|
||
|
|
count.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of physical read requests.</strong> The number of read
|
||
|
|
requests that resulted in actual physical I/O requests on entries in this
|
||
|
|
member since the last IPL. Logical read requests do not necessarily result in a
|
||
|
|
physical read request. Rollback operations will affect this count.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of records rejected by group-by selection.</strong> The
|
||
|
|
number of records that were rejected by the selection that is associated with
|
||
|
|
group-by processing on the member.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of records rejected by key selection.</strong> The number of
|
||
|
|
records that were rejected by key record selection in open operations that are
|
||
|
|
associated with the member.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of records rejected by nonkey selection.</strong> The number
|
||
|
|
of records that were rejected by the nonkey record selection in open operations
|
||
|
|
that are associated with the member.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of rejected entries.</strong> The number of member entries
|
||
|
|
rejected by retrieve operations since the last IPL.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of reorganize operations.</strong> The number of times that
|
||
|
|
this member has been reorganized since the last IPL.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of reset operations.</strong> The number of times that this
|
||
|
|
member has been cleared since the last IPL. Applying journal entries that
|
||
|
|
result in clear operations will affect this count.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of unique partial keys for key field 1.</strong> The number
|
||
|
|
of unique key values considering only the first key field for keyed access
|
||
|
|
paths. If the access path is an encoded vector, this number represents the
|
||
|
|
number of full key distinct values. If this value is zero, then the unique key
|
||
|
|
statistics are not available for this access paths. The number of unique key
|
||
|
|
values are not available for access paths restored from previous releases, have
|
||
|
|
keys which contain varying length character fields, or have multiple based on
|
||
|
|
files.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of unique partial keys for key field 1 through 2.</strong>
|
||
|
|
The number of unique key values from the first two key fields for keyed access
|
||
|
|
paths. If this value is zero, then the unique key statistics are not available
|
||
|
|
for this partial key. This number is not available for access paths restored
|
||
|
|
from previous releases, containing only 1 key field, are encoded vector, have
|
||
|
|
keys which contain varying length character fields, or have multiple based on
|
||
|
|
files.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of unique partial keys for key field 1 through 3.</strong>
|
||
|
|
The number of unique key values from the first three key fields for keyed
|
||
|
|
access paths. If this value is zero, then the unique key statistics are not
|
||
|
|
available for this partial key. This number is not available for access paths
|
||
|
|
restored from previous releases, containing less than 3 key fields, are encoded
|
||
|
|
vector, have keys which contain varying length character fields, or access
|
||
|
|
paths with multiple based on files.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of unique partial keys for key field 1 through 4.</strong>
|
||
|
|
The number of unique key values from the first four key fields for keyed access
|
||
|
|
paths. If this value is zero, then the unique key statistics are not available
|
||
|
|
for this partial key. This number is not available for access paths restored
|
||
|
|
from previous releases, containing less than 4 key fields, are encoded vector,
|
||
|
|
have keys which contain varying length character fields, or access paths with
|
||
|
|
multiple based on files.</p>
|
||
|
|
|
||
|
|
<p><strong>Number of update operations.</strong> The number of records updated
|
||
|
|
in this member since the last IPL. Updates performed on the member as a result
|
||
|
|
of the set null and set default referential constraint rules will affect this
|
||
|
|
count. Applying journal entries that result in updates will affect this count.
|
||
|
|
Update operations that occur during rollback will also affect this count.</p>
|
||
|
|
|
||
|
|
<p><strong>ODP sharing.</strong> Whether the open data path (ODP) allows
|
||
|
|
sharing with other programs in the same job. 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">ODP sharing is not allowed. A
|
||
|
|
distributed data management (DDM) file that is sent to a system other than a
|
||
|
|
System/38 or iSeries system returns a 0.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">ODP sharing is allowed.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Offset to additional MBRD0200 format information.</strong> The
|
||
|
|
number of bytes from the start of the MBRD0200 format to the beginning of the
|
||
|
|
additional MBRD0200 format information.</p>
|
||
|
|
|
||
|
|
<p><strong>Offset to the data space index list.</strong> The number of bytes from
|
||
|
|
the start of the MBRD0400 format to the beginning of the data space index list.</p>
|
||
|
|
<p><img src="delta.gif" alt="Start of change"> <strong>Offset to the materialized
|
||
|
|
query table list.</strong> The number of bytes from the start of the MBRD0500
|
||
|
|
format to the beginning of the materialized query table list. <img src=
|
||
|
|
"deltaend.gif" alt="End of change"></p>
|
||
|
|
|
||
|
|
<p><strong>Offset to member level constraint information.</strong> The number
|
||
|
|
of bytes from the start of the MBRD0200 format to the beginning of the first
|
||
|
|
member level constraint information array.</p>
|
||
|
|
|
||
|
|
<p><strong>Record capacity.</strong> The actual number of records this member
|
||
|
|
can contain. The value is calculated by multiplying the increment number of
|
||
|
|
records by the maximum number of increments, and adding the initial number of
|
||
|
|
records. This field only applies to a physical file and is 0 for a logical
|
||
|
|
file.</p>
|
||
|
|
|
||
|
|
<p><strong>Record format and based-on file list.</strong> The number of
|
||
|
|
physical file members this logical file member is based on. There is a maximum
|
||
|
|
of256 entries. A physical file only has one entry. See <a href=
|
||
|
|
"#HDRRFBOFL">Record Format and Based-On File List Entry</a> for a list of the
|
||
|
|
fields contained in this list.</p>
|
||
|
|
|
||
|
|
<p><strong>Record format selector library name.</strong> The library in which
|
||
|
|
the record format selector program resides. This field is blank for physical
|
||
|
|
files.</p>
|
||
|
|
|
||
|
|
<p><strong>Record format selector program name.</strong> The name of a record
|
||
|
|
format selector program that is called when the logical file member contains
|
||
|
|
more than one logical record format.</p>
|
||
|
|
|
||
|
|
<p>The user-written selector program is called when a record is written to the
|
||
|
|
database file and a record format name is not included in the high-level
|
||
|
|
language (HLL) program. The selector program receives the record as input,
|
||
|
|
determines the record format used, and returns it to the database. This field
|
||
|
|
is blank for physical files.</p>
|
||
|
|
|
||
|
|
<p><strong>Records to force a write.</strong> The number of inserted, updated,
|
||
|
|
or deleted records that are processed before the records are forced into
|
||
|
|
auxiliary storage. A 0 indicates that records are not forced into auxiliary
|
||
|
|
storage.</p>
|
||
|
|
|
||
|
|
<p><strong>Remote file.</strong> Whether the file is a remote file. 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">Local file</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Remote file</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Reserved.</strong> An ignored field.</p>
|
||
|
|
<p><strong><img src="delta.gif" alt="Start of change">Reset date.</strong>
|
||
|
|
The date the days-used count was last reset to 0. The reset date field is in
|
||
|
|
the YYYYMMDD format. If the object has no reset date, the field is blank.<img src=
|
||
|
|
"deltaend.gif" alt="End of change"></p>
|
||
|
|
|
||
|
|
<p><strong>Restore date and time.</strong> The date and time that the member
|
||
|
|
was last restored. The restore date and time field is in the CYYMMDDHHMMSS
|
||
|
|
format, which is the same as for the change date and time field. The field
|
||
|
|
contains blanks if the member was never restored. DDM files that are not from a
|
||
|
|
System/38 or iSeries system return blanks.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<p><strong>Restored with partial transaction state.</strong> The data for this
|
||
|
|
physical-member is currently not usable, because it was restored from media
|
||
|
|
that was created using save-while-active without waiting for transaction
|
||
|
|
boundaries. Physical-member data that contains partial transactions cannot be
|
||
|
|
used until either the Apply Journaled Changes (APYJRNCHG) or the Remove
|
||
|
|
Journaled Changes (RMVJRNCHG) command is used to apply or remove the journal
|
||
|
|
changes to the member to recover the partial transactions, or the Change
|
||
|
|
Journaled Object (CHGJRNOBJ) command is used to allow the member containing
|
||
|
|
partial transactions to be used. See the field, <a href="#SPTJRNRCV">Journal
|
||
|
|
receiver's name for transaction recovery</a> , to get the name of the
|
||
|
|
earliest journal receiver that will be needed to recover using the Apply
|
||
|
|
Journaled Changes or Remove Journaled Changes command. The Change Journaled
|
||
|
|
Object command should only be used as a last resort, since the changes in the
|
||
|
|
journal receiver will not have been applied or removed completely and therefore
|
||
|
|
the member will not be at a commit boundary.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Physical-member is not in a restored with partial
|
||
|
|
transaction state.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Physical-member is in a restored with partial
|
||
|
|
transaction state.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Rollback ended state.</strong> The data for this physical-member is
|
||
|
|
currently not usable, because a rollback that was being performed against the
|
||
|
|
data for the member was ended. Physical-member data that is in a rollback ended
|
||
|
|
state cannot be used until either the member is restored, or the Change
|
||
|
|
Journaled Object (CHGJRNOBJ) command is used to allow the member containing
|
||
|
|
partial transactions to be used. The Change Journaled Object command should
|
||
|
|
only be used as a last resort, since the changes in the journal receiver will
|
||
|
|
not have been rolled back completely and therefore the member will not be at a
|
||
|
|
commit boundary.</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="5 95" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 0</em></td>
|
||
|
|
<td align="left" valign="top">Physical-member is not in a rollback ended
|
||
|
|
state.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Physical-member is in a rollback ended
|
||
|
|
state.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<p><strong>Save date and time.</strong> The date and time that this member was
|
||
|
|
last saved. The save date and time field is in the CYYMMDDHHMMSS format, which
|
||
|
|
is the same as the change date and time field. This field contains blanks if it
|
||
|
|
was never saved. DDM files that are not from a System/38 or iSeries system
|
||
|
|
return blanks.</p>
|
||
|
|
|
||
|
|
<p><strong>Sort sequence table library name.</strong> The library in which the
|
||
|
|
sort sequence table resides that was used to order the data space index keys.
|
||
|
|
The field contains blanks if a sort sequence was not used to create the data
|
||
|
|
space index.</p>
|
||
|
|
|
||
|
|
<p><strong>Sort sequence table name.</strong> The sort sequence table that was
|
||
|
|
used to order the data space index keys. The field contains blanks if a sort
|
||
|
|
sequence was not used to create the data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>Sort sequence language ID.</strong> The language ID that was used to
|
||
|
|
identify the sort sequence table that was used to order the data space index
|
||
|
|
keys. The field contains blanks if a sort sequence was not used to create the
|
||
|
|
data space index or if an alternate collating sequence was used to create the
|
||
|
|
data space index.</p>
|
||
|
|
|
||
|
|
<p><strong>Sort sequence weight.</strong> The sort sequence weight that was
|
||
|
|
used to order the data space index keys. The field contains blanks if a sort
|
||
|
|
sequence was not used to create the data space index or if an alternate
|
||
|
|
collating sequence was used to create the data space index. 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">Unique weight</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Shared weight</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<p><strong>Source file.</strong> Whether the file is a source 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">Data file</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> 1</em></td>
|
||
|
|
<td align="left" valign="top">Source file</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Source type.</strong> The type of source member if this is a source
|
||
|
|
file.</p>
|
||
|
|
|
||
|
|
<p><strong>SQL file type.</strong> The kind of SQL file type the file is. The
|
||
|
|
possible values are:</p>
|
||
|
|
|
||
|
|
<table cellpadding="5">
|
||
|
|
<!-- cols="10 90" -->
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> blank</em></td>
|
||
|
|
<td align="left" valign="top">Not an SQL file.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> TABLE</em></td>
|
||
|
|
<td align="left" valign="top">Nonkeyed physical file that contains field
|
||
|
|
characteristics.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> VIEW</em></td>
|
||
|
|
<td align="left" valign="top">Logical file over one or more tables or views.
|
||
|
|
This SQL file type provides a subset of data in a particular table or a
|
||
|
|
combination of data from more than one table or view.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td align="left" valign="top"><em> INDEX</em></td>
|
||
|
|
<td align="left" valign="top">Keyed logical file over one table that is used
|
||
|
|
whenever access to records in a certain order is to be requested
|
||
|
|
frequently.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<p><strong>Use reset date.</strong> The century and date when the days-used
|
||
|
|
count was last set to 0. This field is in the CYYMMDD format, which is the same
|
||
|
|
as for the date last used field. If the date is not available, this field is
|
||
|
|
blank.</p>
|
||
|
|
|
||
|
|
<p><strong>Variable length data size.</strong> The number of pages (4096 bytes
|
||
|
|
each) of variable length data in the data space.
|
||
|
|
<br>
|
||
|
|
</p>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3><a name="usage_notes">Usage Notes</a></h3>
|
||
|
|
|
||
|
|
<p>In multithreaded jobs, this API is not threadsafe and fails for DDM files of
|
||
|
|
type *SNA.
|
||
|
|
<br>
|
||
|
|
</p>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<h3>Error Messages</h3>
|
||
|
|
|
||
|
|
<table width="100%">
|
||
|
|
<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">CPF24B4 E</td>
|
||
|
|
<td width="85%" valign="top">Severe error while addressing parameter list.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF32DE E</td>
|
||
|
|
<td valign="top">Cannot get information about member &3 from file
|
||
|
|
&1.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF32DF E</td>
|
||
|
|
<td valign="top">Value &1 for find member parameter is not valid.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3CF1 E</td>
|
||
|
|
<td valign="top">Error code parameter is not valid.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C19 E</td>
|
||
|
|
<td valign="top">Error occurred with receiver variable specified.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C20 E</td>
|
||
|
|
<td valign="top">Error found by program &1.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C21 E</td>
|
||
|
|
<td valign="top">Format name &1 is not valid.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C22 E</td>
|
||
|
|
<td valign="top">Cannot get information about file &1.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C23 E</td>
|
||
|
|
<td valign="top">Object &1 is not a database file.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C24 E</td>
|
||
|
|
<td valign="top">Length of the receiver variable is not valid.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C25 E</td>
|
||
|
|
<td valign="top">Value &1 for file override parameter is not valid.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C26 E</td>
|
||
|
|
<td valign="top">File &1 has no members.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C27 E</td>
|
||
|
|
<td valign="top">Cannot get information about member &3 from file
|
||
|
|
&1.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C36 E</td>
|
||
|
|
<td valign="top">Number of parameters, &1, entered for this API was not
|
||
|
|
valid.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF3C90 E</td>
|
||
|
|
<td valign="top">Literal value cannot be changed.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF8100 E</td>
|
||
|
|
<td valign="top">All CPF81xx messages could be returned. xx is from 01 to
|
||
|
|
FF.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr>
|
||
|
|
<td valign="top">CPF9800 E</td>
|
||
|
|
<td valign="top">All CPF98xx messages could be returned. xx is from 01 to
|
||
|
|
FF.</td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
|
||
|
|
<br>
|
||
|
|
<br>
|
||
|
|
<hr>
|
||
|
|
API introduced: V1R3
|
||
|
|
|
||
|
|
<hr>
|
||
|
|
<center>
|
||
|
|
<table cellpadding="2" cellspacing="2" width="600">
|
||
|
|
<tr align="center">
|
||
|
|
<td valign="middle" align="center"><a href="#Top_Of_Page"> Top</a> | <a href=
|
||
|
|
"file1.htm"> Database and File APIs</a> | <a href="aplist.htm"> APIs by
|
||
|
|
category</a></td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
</center>
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|