Alfredo writes (and then goes off to begin coding his "Gone-to-Jumbo   
Notification project") ...

>I am in the process of adding "notification" code to
>Adager whenever it automagically converts a dataset
>from pre-jumbo to jumbo (as it has been quietly doing
>for the last three years or so -- perhaps too quietly).
>In addition to sending the "gone to Jumbo" notification to
>$stdlist, would you like me to also send it to the console?

Notification is nice but can too often be ignored or missed. Even if   
noticed would the implications be fully understood by all readers?

I think I would like to be asked if it is OK to "go to jumbo" when I   
specify a change which would cause this. When making changes   
interactively a simple Y/N response would be all that would be required.   
A page of general info including warnings about store along with the   
prompt would be nice.

For automated lights out style capacity management jobs perhaps a jcw or   
system variable which would allow me control over the "go to jumbo"   
action would be needed. If you find the jcw or variable then you would   
report the action you have taken based on its value to stdlist -- i.e. go   
to jumbo and report that you have done this or notify that no change has   
been made because permission was not given to go to jumbo. I'm not sure   
what the default behaviour should be if the jcw or variable isn't   
specified -- assume OK and go to jumbo or quit with an abnormal   
termination message that most stdlist processors could recognise? Perhaps   
the latter considering the generally conservative nature of most 3k   
shops.

Regards,
John Pickering
JWP Systems Inc