HLC5962@TAMVENUS.BITNET (Lee Cox) (09/05/87)
While looking at the help file for SET BROADCAST, I noticed a set of parameters [NO]USER1-[NO]USER16. After experimenting, I discovered that setting NOUSER1 stopped anyone from using the SEND command on me (no more interrupted editing sessions) while setting NOUSER2 stopped the same from remote nodes. Unfortunately, no one here, even after looking through several tons of orange binders, can figure out what the rest of the USERxx parameters do. Anybody know? ************************************************************************ Lee Cox TTTTTTTTTTTTTTTT US Mail: P.O. Box 1915 TT TT TT College Station, TX 77841-1915 TT AT&TNet: (409)260-0775 A TT M M BITNet: N074AN@TAMVM1 A A TT MM MM TEXNet: THOR::HLC5962 AAAAA TT M M M ARPANet: N074AN%TAMVM1@WISCVM.WISC.EDU A A TT M M SPAN/HEPNet: UTADNX::UTSPAN::THOR::HLC5962 A A TTTT M M ************************************************************************
KHF@JHUIGF.BITNET (09/05/87)
Re: Lee Cox's 5-sep-87 question on the USERn parameters for SET BROADCAST. It is my understanding that those parameters are all available for use by any non-DEC software. In this case, JNET makes use of USER1 and USER2 by simply checking their state before passing along the messages to a given process. You can use any or all of them for your own local applications, as long as they don't interfere with other local/third-party software you are using (or plan to use). Any well-documented package SHOULD tell you if it is using (or rather, can use) those parameters. Please correct me if I'm wrong, anyone, but this is the way I understand the situation. ------------------------------------------------------------------------------- Ken Fasman U.S. Mail: Bard Laboratories of Neurophysiology Johns Hopkins School of Medicine 725 N. Wolfe St. Baltimore MD 21205 Telephone: (301) 955-8330 BITNET: KHF@JHUIGF "My opinions, especially the wrong ones, are strictly my own." -------------------------------------------------------------------------------
carl@CITHEX.CALTECH.EDU.UUCP (09/07/87)
> While looking at the help file for SET BROADCAST, I noticed a set of > parameters [NO]USER1-[NO]USER16. After experimenting, I discovered that > setting NOUSER1 stopped anyone from using the SEND command on me (no more > interrupted editing sessions) while setting NOUSER2 stopped the same from > remote nodes. Unfortunately, no one here, even after looking through > several tons of orange binders, can figure out what the rest of the USERxx > parameters do. Anybody know? Look on pages SYS-31 and SYS-32 of the SYSTEM SERVICES manual. Here it defines the classes of broadcast messages. In particular, classes USER1 through USER16 are defined as: These class names can be used by user-written images. Apparently JNET from Joiner Associates uses classes USER1 and USER2 as you've described. The other 14 classes may be unused on your system.
vaughan@canisius.UUCP (Tom Vaughan) (09/08/87)
In article <8709051837.AA00230@ucbvax.Berkeley.EDU>, KHF@JHUIGF.BITNET writes: > Re: Lee Cox's 5-sep-87 question on the USERn parameters for SET BROADCAST. > > It is my understanding that those parameters are all available for use by any > non-DEC software. In this case, JNET makes use of USER1 and USER2 by simply By the way, the set broadcast for Jnet is documented in the Jnet manuals. Also set broadcast=nouser3 will eliminate those wonderful file progress messages you receive when sending mail to other nodes. It stops all bitnet status messages. So beware, it also prevents your querys from being delivered back to ya. -------------- -------------- DEC VAX 11/750; 4.3 BSD UNIX & DEC VAX 8650; VMS 4.5 BITNET : vaughan@canisius UUCP : {cmc12,hao,harpo}!seismo!rochester!rocksvax!sunybcs!canisius!vaughan or ...{allegra,decvax,watmath}!sunybcs!canisius!vaughan CSNET : vaughan%canisius@CSNET-relay US MAIL: Thomas Vaughan/ Dept. of Comp. Sci./ Canisius College/ 2001 Main St./ Buffalo N.Y. 14208 -------------- --------------
GLOOR@CSGHSG5A.BITNET.UUCP (09/08/87)
The SET BROAD USERn command is intended for use in user written programs or third party products like Jnet. There is no VMS DCL command which makes use of it. Thats why you can't find any documentation in the orange binders. If you take the green-grey Jnet binder (Jnet V3.0) you'll find it documented on page 6-4 in the user's guide. Fist of all the system manger has to define the logical name JAN_BRD_BASE to enable the ability to turn broadcast messages on and off. JAN_BRD_BASE must translate to USERn. Depending on USERn the user will be able to set three broadcast classes for Jnet: USERn, USERn+1 and USERn+2. Let's say JAN_BRD_BASE is defined as USER1 then the following will be valid: - USER1 defines messages from local users - USER2 defines messages from remote users - USER3 defines network messages and command responses Sincerely, Peter
MCGUIRE@GRIN2.BITNET (09/10/87)
> Date: Sat, 5 Sep 87 08:03 CDT > From: Lee Cox <HLC5962%TAMVENUS.BITNET@WISCVM.WISC.EDU> > Subject: SET BROADCAST > > While looking at the help file for SET BROADCAST, I noticed a set of > parameters [NO]USER1-[NO]USER16. After experimenting, I discovered that > setting NOUSER1 stopped anyone from using the SEND command on me (no more > interrupted editing sessions) while setting NOUSER2 stopped the same from > remote nodes. Unfortunately, no one here, even after looking through > several tons of orange binders, can figure out what the rest of the USERxx > parameters do. Anybody know? Orange binder: System Services References Manual, $BRKTHRU service. USER1..16 are reserved for user-written images. Now get out the little green binder! :-) You are running Jnet networking software. Jnet uses USER1..3 to control whether or not the host daemon broadcasts network messages to you. USER1 controls local user messages. USER2 controls remote user messages. USER3 controls messages not from any user (such as SENT FILE... messages). Jnet can be configured by using logical names to look at class names other than USER1..3. ---- Ed McGuire, Systems Coordinator, Grinnell College, MCGUIRE@GRIN2.BITNET