Communicator 3000 MPE/iX Release 6.0 (Platform Software Release C.60.00) (30216-90269)

Chapter 10 167
Technical Articles
IMAGE/SQL with TurboIMAGE/XL Enhancements
How to tell if you already have this problem. If you use DDX,
check each detail data set enabled for DDX. Remember, the problem is
associated only with the detail data sets which have undergone
dynamic expansion.
You can check for this condition as follows:
1. Use the FORM SETS command of QUERY, which gives the Current
Capacity (CC) and Blocking Factor (BF) of each data set.
:query
HP32216D.03.11 QUERY/3000 TUE, NOV 4, 1997, 3:20 PM
COPYRIGHT HEWLETT-PACKARD CO. 1976
>b=dbusa
PASSWORD = >>
MODE = >>1
>form sets
DATA BASE: DBUSA TUE, NOV 4, 1997, 3:20 PM
DATA BASE LANGUAGE ATTRIBUTE: NATIVE-3000
ITEM CURRENT ENTRY ENTRY BLOCKING
SETS: TYPE COUNT CAPACITY COUNT LENGTH FACTOR
PEPU01 D 3 1010 11 12 10
2. Calculate the IMAGE EOF of a DDX data set using the following
formula:
(CC + (BF-1))/BF
For example:
IMAGE EOF = (1010 + (10-1))/10 = 101
3. Verify this calculated EOF with the MPE EOF given by the
command :LISTF dbnamenn,2 where dbnamenn is the file name of
that DDX data set.
:listf dbusa01,2
ACCOUNT= TESTACCT GROUP= DDX
FILENAME CODE -----------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
DBUSA01 PRIV 256W FB 51 200 1 112 2 4
4. If the two EOFs do not match, there is a problem.
In the example, MPE EOF of 51 and IMAGE EOF of 101 do not
match—the problem exists.
The SHOW DBUSA CAPACITY command of DBUTIL gives capacity
parms:
No. of %Max -----------Capacity------------- Dyn
Data Set Name Type Entries Cap Maximum Current Initial Increment Exp:
PEPU01 D 11 1 2000 1010 10 500 YES