Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!ames!ucbcad!ucbvax!RVAX.CCIT.ARIZONA.EDU!JMS%uamis From: JMS%uamis@RVAX.CCIT.ARIZONA.EDU.UUCP Newsgroups: comp.os.vms Subject: RE: New mail announcement on a VAX cluster Message-ID: <8711081558.AA08412@ucbvax.Berkeley.EDU> Date: Fri, 6-Nov-87 13:27:00 EST Article-I.D.: ucbvax.8711081558.AA08412 Posted: Fri Nov 6 13:27:00 1987 Date-Received: Wed, 11-Nov-87 02:38:45 EST Sender: daemon@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 46 Someone asked about getting mail notification on other nodes in a cluster. 1) shame on you. read the manual. on page Mail-14 of the manual is a clear description of how to do what you want to do 2) for the records: the logical name MAIL$SYSTEM_FLAGS (defined using the qualifiers /SYSTEM and /EXECUTIVE_MODE ($ define/sys/exec mail$system_flags 1) is interpreted in the following way: Bit 0 (decimal 1) Indicates that this node is part of a homogeneous cluster. Indicates that there is common SYSUAF and a common VMSMAIL for the cluster. This means that the local node need only use cluster I/O, not DECnet I/O to deliver mail to members of the cluster (you are using a cluster alias, aren't you?) Bit 1 (decimal 2) Directs mail to use the cluster breakthrough flag when using the $BRKTHRU system service. This is what the fellow that asked wants. Bit 2 (decimal 4) Directs mail to include the time in notification messages. So, if you had a homogeneous cluster and wanted cluster-wide notification of mail, do this $ define/system/exec mail$system_flags 3 jms +-------------------------------+ | Joel M Snyder | BITNET: jms@arizmis.BITNET | Univ of Arizona Dep't of MIS | Internet: jms@mrsvax.mis.arizona.edu | Tucson, Arizona 85721 | Pseudo-PhoneNET: (602) 621-2748 +-------------------------------+ ICBM: 32 13 N / 110 58 W NOTE: if you get more than one copy of this, please let me know. we may have a broken mailer somewhere on campus!