Jamie,

Yes, we ran into this too.  Whenever a message box is displayed by any
application, the foreground application cannot run until the message box
is dismissed.  If you simply run the ADSM Scheduler in the background, then
it will not be interrupted by message boxes.

..Paul
--
On Thu, 9 Feb 1995 13:45:01 PST you said:
On Thu, 9 Feb 1995 13:45:01 PST you said:
>I am, still, experimenting with ADSM from a Mac, a PowerMac 7100 which is
>creating its own unique set of issues...but I digress.. The other evening as I
>left work I sent a file to our printer (routed through our Novell file server
>print queue) and started the ADSM Scheduler program.
>
>When I arrived the next morning I saw the message from our file server telling
>me that my file had printed and asking me to respond with an "OK" (click the
>OK button) and I also saw that the ADSM Scheduler program had gotten no
>further than I left it. The backups hadn't run.
>
>My guess is that my Mac was "hung" waiting for me (someone) to respond to the
>printer message and so did not respond when the ADSM Server tried to initiate
>a session in the middle of the night.
>
>I would guess the same problem would occur if, for example, the server was
>brought down for maintenance (a message gets sent to everyone) after one had
>started the ADSM Scheduler. This seems like a common situation and one which
>may confound the works.
>
>Has anyone else had this problem? And, if so, how did you work around it?
>
>Thanks,
>                                      Jamie Sonsini
>                                      IS&C, Computer Center
>                                      UC Santa Barbara