Ted continues the thread:

> Thus it was written in the epistle of Joseph Rosenblatt,
> > I was checking database capacities in DBUTIL,

> What's going on is that DBSCI is an old tool which doesn't
> know about Dynamic Dataset Expansion (DDX).  ....

I'll take this opportunity to post of one my periodic cautions
in the area of database tools and their use against the latest
current and soon-to-be-delivered versions of TurboIMAGE:

DDX is only one of many recent fundamental enhancements
to IMAGE;  MDX, B-Trees, JUMBO datasets are other examples.
Coming "soon" will be more major internal structural changes:

Max number of datasets going from 199 to 250.
Max number of items going from 1023 to 1234.
Max number of paths in a MASTER going from 16 to 64.
Block-oriented "EntryByName" to 32-bit "EntryByNumber"
   (EntryByNumber change will require database migration).

If you try and run obsolete tools like DBSCI or old versions of
other tools against versions of TurboIMAGE with some or all
of the above new features, if said tool does not recognize that
it is not capable of dealing with the new features and tries to
run anyway, you are gambling with your professional life !!!

Adager and DB General and I think current version of Flexibase
(I am less familiar with the last product) are the only tools I know
of where you can depend on them being up to date if you have
their latest versions;  *or* they will tell you if you need a newer
version to work with the version of IMAGE that you are running.

Note that while it is still officially "supported" (in the classic HP
definition of the term) , HP has clearly stated that they have "No
plans" to implement any further enhancements to DBCHANGE.
DBCHANGE does not support MDX, B-Trees, or JUMBO's now,
and is not expected to ever do so....  let alone EntryByNumber.

Ken Sletten
SIGIMAGE Chair