Tim Ericson <[log in to unmask]> wrote:

>I would argue for the first case, default to 'Jumbo is OK' - I can't
>afford to have any downtime during the day to expand datasets it the
>automatic nightly process hasn't already done it. I _do_ want to be
>notified, though!  Perhaps a single-sheet tombstone-style banner on
>LP, as well as console and $stdlist notification?

Thanks for your thoughts.  I'm in the process of reviewing an overwhelming
amound of suggestions (a big "thanks" to everyone).  An intriguing
possibility is to have a scripting language so that people don't have to
"argue for the first case" (or for any other case).  Instead of ME
deciding, THE USER decides and informs me (via an Adager scripting
language) a preference regarding which of the many possible actions I
should take:

- allowing (or not allowing) Jumbo datasets (ideally fine-tuned down
  to the dataset level);

- reporting and the specific method(s) of reporting (or not reporting,
  to avoid clutter for people who don't care);

For some people, Jumbo datasets have become old-hat "legacy stuff"
(particularly for those Adager customers who have been doing it
uneventfully since 1995).  For other people, Jumbo datasets are a novelty
now and will, perhaps, become "legacy stuff" soon.  Who am I to impose MY
criteria regarding notification (or lack thereof)?  So, the scripting
methodology appeals to me.

Tim "argues" for "Jumbo is OK" (which is Adager's default, unless you
override it with ":setjcw AdagerNoJumbo 1").  I tend to agree with Tim.
Perhaps it is in my nature to be an early adopter of good technologies.
But not everyone is willing to be an early adopter!


Alfredo