Doug Werth  <[log in to unmask]> wrote:

>I can see several issues you will have to contend with on your project.

I depend on my friends to bring these issues up.


>While you can put many messages on the console and in the stdlist about it
>they may never be seen. Of course, any DBA who alters a database without
>checking the results is negligent and you can't blame any database tool for
>that. Nonetheless those who have autopilot methods of expanding datasets
>just may not see the messages.

The idea is not to blame anyone but to HELP as many people as possible.  We
might as well accept reality and, therefore, acknowledge the fact that
people are neither "interested in" nor "good at" scanning a bunch of boring
messages (whether on the console or on $stdlist).  Computer programs are
EXCELLENT for these kinds of tasks.


Besides a fascinating story on IBM console-message "management" and
"mismanagement", Doug proposed:

>... One way around this that I have used
>is to have a program process handle another program. The son process calls
>the PRINTOPREPLY. The father process monitors the son process. Every so many
>minutes it re-displays the original question and reminds the user that a
>reply is outstanding.

This still relies on somebody EVENTUALLY catching the message via physical
eyeballs :-)


>This method would most likely not work for Alfredo because the job may be
>running as part of an unattended data center where other jobs would back up
>in the queue waiting for the Adager job to log off. To start a new thread
>then I ask then following question:
>
>How do others set off bells and whistles? JobRescue is one obvious solution.
>It could scan for the message that Adager writes to the stdlist. Any other
>ideas?

Doug has hit the jackpot.  To quote from what I wrote a couple of
paragraphs above:

        We might as well accept reality and, therefore, acknowledge the fact
        that people are neither "interested in" nor "good at" scanning a
        bunch of boring messages (whether on the console or on $stdlist).
        Computer programs are EXCELLENT for these kinds of tasks.

So, I will be very thankful for any ideas along these lines.  I'll be happy
to program whatever is the most useful thing into Adager, but I need the
collective help of HP3000-L to zero-in on such "most useful thing".

I can broadcast "news" using any channel ($stdlist, console, files of any
kind and flavor, and so on) but the fundamental question is, "will anyone
listen and act appropriately as a result?"


Thank you for your thoughts,



Alfredo                            http://www.adager.com