| If this is a PUSH style of informing users, why not use MAIL? Create a command
procedure that edits NOTICE.TXT, and mails the updated copy to a list of system
users.
If this is a PULL style of informing users, create a batch job that resubmits
itself with the create date of the last notice.txt mailed. If a new notice.txt
is there, it mails it and resubmits with a new date. You can then make this
available to the users. Them that don't run it do so at their own risk.
|
|
Mail is one answer, but we choose not to use mail for a couple of
reasons. One is that many people don't have time to weed through mail first
thing. Another reason is that when the window is on their screen they are forced
to respond by either reading it or quitting out of the window. If for some
reason for example the system needs to shut down in 20 min., at least they will
see the window, but they may ignore a new mail informational message as they may
be in the middle of something else. Also, and most importantly, it doesn't
explain why I'm left with these PID's that I need to manually delete.
-.1 is not a solution. I would prefer to execute this in the manner stated in
.0 if possible. If not, then maybe I need an alternative.
Dan
|
| Re: .0
What command are you actually using to create the DECterm windows?
Create/term/detach would create a logged in window at the DCL prompt on *your*
account, which I assume isn't what you want.
This works for me with no problem: the process goes away when I Quit. I'm
not sure why this doesn't work when you do it. I suggest that you submit a
QAR. In the meantime, you might want to ask people to use the LOGOUT command
instead of Quit'ing from the Commands menu.
-- Bob
|