Master dataset expansion is still not very stable, and we stay away from it here.

Detail expansion works good, except we had one GOTCHA here this week.  We are an AMISYS shop, and our databases are LARGE, so I thought I would save a bunch of space and reduce the size of my details by turning on dynamic expansion.  This worked great IMAGE wise, but AMISYS chokes and dies.  The reason is that AMISYS uses the old mode 202 DBINFO call to check out the capacity - #entries to see if there is enough room.  Well, the mode 202 DBINFO returns the present capacity, not the maximum capacity like mode 205, so the programs blew up bigtime with OUT OF ROOM messages, even though there was gobs of room in them.

Another nasty is that dynamic expansion will not work for JUMBO datasets, which is a shame because that is where you can save the most space.


Wyell Grunwald
Senior Technical Analyst
Geisinger Health System
100 North Academy Avenue
Suite 30-33
Danville, Pennsylvania  17822-3033

Phone:  570-271-7342
Fax:  570-271-5162
Ext:  7342
[log in to unmask]

>>> Peter Osborne <[log in to unmask]> Friday, July 07, 2000 12:38:56 PM >>>
Hello All,

I know very little about Image Databases so you'll have to bare with me. I
am trying out the Auto-Expansion feature on one of my databases at it seems
to work great on both detail sets, as well as automatic masters. It fails
to expand an automatic master if it is the primary key of the detail data
set you are adding records to. Is this a limitation of the auto-expansion
feature or might there be a patch or do I not have it configured properly.
I am running on a very unpatched 6.0.

Thanks for your time,

Peter Osborne
Carleton Technologies