| 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 |
Any chance of getting a version of Zap with all of it's files
cluster-wide? (Ie. ZAP.DAT, ZAP.LOG, ZAP.MSG).
It would make maintenance alot easier. (I don't fancy a Zap-maint
job sitting each node-specific queue!).
It would also make life easier when tailoring parameters in ZAP.DAT.
Most installation probably run each system in an installation with
a common set of params. (and message files, for that matter).
Thoughts?
Regards,
--Martin.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 43.1 | Sharing is available | NRADM5::MACONI | The Doctor | Tue Dec 01 1987 09:05 | 19 |
Currently, Version 3.7 (or lower) can be run with common files.
However, it uses logical names (which are node specific) to control
how it is run. This means that you can share all data, but the
Zap maintenance procedure must be run on EACH node individually.
Currently, I am working on Version 4.0. I would like to use shared
global sections for communications. I have not yet determined how
it will behave in a VAXcluster. I am looking at different strategies
to share the information without incurring too heavy a workload
(DECnet links would be expensive to keep open all the time).
For now, just place the ZAP files in SYS$COMMON:[ZAP] and you can
share the one set of files (ZAP.LOG will still be specific).
* Please note that the directory structure (SYS$SYSROOT:[ZAP]) is
now required for V3.7 in preparation for V4.0.
Keith Maconi
| |||||