SYSRUTH@UTORPHYS.BITNET.UUCP (02/19/87)
First of all, to stop shutdown message broadcasting, you need to define a logical name in your PROCESS (NOT SYSTEM) logical name table. This is SHUTDOWN$INFORM_NODES , and if you give it the value of the local node name, it will only notify the local node on shutdown. Secondly, about other OPCOM messages. I don't know how you have it set up at your site, but here we start OPCOM in the systartup.com and then do a reply/enable as well. If you set it so that this reply/enable is a reply/enable/node, that should have the effect of not broadcasting to the entire cluster (I haven't tried it, but the documentation would lead me to suspect this might do it). If that doesn't work, the only other way is to disable cluster (and possibly central) messages on the other node. This can also be done from systartup.com. However it can occasionally be useful to get messages on the other machine. If something happens to one of the console devices and/or the system, you can still see what is happening via the other node. By disabling cluster messages locally (rather than preventing their broadcast in the first place), you have the option later of re-enabling them. Remember when you log onto OPA0, if you do a reply/disable while logged on, it will stay in effect after you log off unless you do a reply/enable again before logging off. I am not sure whether it will effect cluster-wide broadcast, however. ^affect While we're on the subject of OPCOM and REPLY, does anyone out there know how to find out which username is enabled as which operator (OPER1, OPER2, etc.)? Ruth Milner Systems Manager University of Toronto Physics SYSRUTH@UTORPHYS (BITNET)