| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I have been thinking about the use of Batch for keeping alarms alive
and have some things that I am not sure how to deal with. I thought I
would stick them in here and see if anyone has some ideas.
Ok, I have my batch job up and it has alarms enabled and all is fine.
Now, how do I tell it about the new alarms I just created?
I can easily see how to start up the alarms in batch. But how do I
safely stop them (since I have to exit the DECmcc job running in batch
to enable new alarms at this time)? I am concerned that a simple
STOP PROCESS or a DELETE/QUE/ENTRY (which I presume forces a ^Y on
any image running before deleting the process) runs the risk that
the process could have some files open for write or modify and be in
the process of doing so when the process is terminated.
s/rob
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 583.1 | how about interim procedures | GOSTE::CALLANDER | Thu Jan 03 1991 11:32 | 31 | |
Actually there are ways around this; I know in the class a few months
back I said I would post the procedures I had written (then I got
very ill), well I will try to do it real soon.
Something to think about when writing the procedure is that you
don't have to have all of the alarms (initally at least) enabled
and evaluating within the same procedure. If you remember the ones
I gave you they only ran for a specified period of time before exiting
MCC (to clean up any potential memory loss) and then restarted.
What you can do as you create new rules is to enable them in a seperate
job (set to terminate the same time that your other procedure is
set to terminate), and then modify the com file used by your main
procedure so that the next time it restarts it will pick up the
new rules.
Procedure 1 -- has all of your defined rules and enables them; with
the procedure exiting and restarting again say once
a week
Procedure 2 -- would be a temporary procedure running all of your
new rules until the end of the "week"
If Procedure 1 runs an MCC com file for enabling of the rules then
while procedure 2 is running, the enable command procedure used
by procedure 1 can be modified to automatically pick up the new
rules next time it restarts.
Does this make sence?
jill
| |||||
| 583.2 | New rules are covered now. Thanks. | NSSG::R_SPENCE | Nets don't fail me now... | Thu Jan 03 1991 13:20 | 3 |
Yup, thanks Jill.
s/rob
| |||||
| 583.3 | see notes 124.11-12-13 | ROM01::LILLI | Thu Jan 24 1991 04:33 | 1 | |