With respect to Ken's point #6, below:  Adager will enforce the Image
requirement that the difference between the DDX initial and maximum capacities
be an even multiple of the increment.  DBGeneral used to not enforce this rule;
however, I've recently discovered that our current version (7.2.17) of this
product does adjust capacity settings to achieve this condition during a change
operation.  If you're using an earlier version of DBGeneral to manage DDX
capacities, you might want to check your DDX sets to ensure that this rule has
been followed.
----
Lee Gunter                    The Regence Group
Supervisor, TRG HP/MPE Systems     503.375.4498
----
Opinions expressed are solely mine.




From: Sletten Kenneth W KPWA <[log in to unmask]> on 11/30/99 06:17 PM

Please respond to Sletten Kenneth W KPWA <[log in to unmask]>


To:   [log in to unmask]
cc:    (bcc: Lee Gunter/BCBSO/TBG)
Subject:  Re: [HP3000-L] Dynamic Data Exchange and COBOL IMAGE intrinsics




About 20 minutes ago Eben Yong said:

> Thru testing, I just discovered that Image DDX data-sets do NOT
> dynamically expand when accessed thru COBOL using Image
> intrinsics.  Can someone please provide confirmation (or clarification)
> about this issue?

<snipped>

(6)   Do you have ADAGER or DBGENERAL ??  If 'Yes' is your
database tool happy with the state of your database in general
and the dataset in question in particular;  i.e.:  Does the database
pass consistency check ??...  What does it show if you go into
CHANGE CAPACITY for the dataset in question (even if you do
not actually try and change the capacity) ??


A number of revisions of TurboIMAGE ago it was discovered that
there was a problem with DETAIL datasets, if the *last* DDX
event before reaching maximum capacity did not have the
DDX increment exactly equal to the remaining delta between
current capacity and maximum capacity....  Both ADAGER and
DBGENERAL should be able to check for this case and correct
it if that is your problem....

Ken Sletten
SIGIMAGE Chair