| Title: | Zap Technical Conference |
| Notice: | ZAP Version 5.3 is available. See note 1.1 |
| Moderator: | ZAPDEV::MACONI |
| Created: | Mon Feb 24 1986 |
| Last Modified: | Mon May 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 170 |
| Total number of notes: | 492 |
I am currently running ZAP V3.8, and was wondering if somebody may
have some suggestions for a couple of procedures. What I need to
be able to do is shutdown ZAP every morning(execept weekends) at
6:00am, and then start ZAP every evening at 6:00pm. I realize
that starting ZAP is no real problem. I can just submit the thing
to run from a batch queue. Is there a procedure that will shutdown
ZAP without requiring manual intervention?? Any comments will be
appreciated.
Thanks,
Todd B.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 47.1 | Shutdown procedure | NRADM::MACONI | The Doctor | Mon Mar 07 1988 16:45 | 15 |
The easiest solution that I can think of is a command procedure
like this:
$ DEFINE/SYSTEM/EXEC ZAP$RUN_STATUS EXIT
$ SUBMIT this_procedure /USER=SYSTEM/AFTER="06:00+1-"/QUEUE=local$batch
$ SUBMIT ZAP$DIR:ZAP$START.COM /USER=SYSTEM/AFTER="18:00"/QUEUE=local$batch
- local$batch should be defined on each node in the VAXcluster
to point to the "local" batch queue, such as GIGI$BATCH.
Once started, this should take care of the problem with the least
amount of work. I would put this procedure in SYSwatch (if you
have it installed) to insure that it keeps running.
Keith Maconi
| |||||