B From:	MERC::"uunet!WKUVX1.BITNET!MacroMan"  3-APR-1993 14:59:09.54 To:	MACRO32@WKUVX1.BITNET  CC:	2 Subj:	Re: Trapping OPCOM messages in Detached proc  O In article <1993Apr2.221620.1384@dmc.com>, munroe@dmc.com (Dick Munroe) writes: G > In article <1993Mar23.212708.1640@cmkrnl.com>, jeh@cmkrnl.com writes: N >> The key is VMS's pseudoterminal driver.  (I/O User's Reference Manual, Part  I, K >> Chapter 9 or so.)  Create a pseudoterminal, associate a mailbox with it,   enable O >> it as an opcom terminal ($SNDOPR system service), set it for nobroadcast and % >> broadcast mailbox ($QIOW SETMODE).  > = > Presumably you CLEAR nobroadcast and SET broadcast mailbox.   H No, I really did mean to SET nobroadcast (this does not inhibit would-beO broadcast messages from going to the associated mailbox, if _BRDCATMBX is set).     > I'm trying to get this to work  A No, you're not, you're doing something else.  Says so right here:   *         > and am having some luck, but not>         > complete success.  The process I'm going through is:	         > 0         > 1. Create a mailbox and get a channel.8         > 2. Create a pseudo terminal and get a channel.A         > 3. Assign a channel to the pt, associating the mailbox. G >>>>>>  > 4. using the channel acquired in 3, clear nobroadcast and set          > broadcast mailbox.9         > 5. Issue a qio to the mailbox, with an ast set. 1         > 6. Enable the pt as an operator device.   
 > In the ast:  >  > 1. Read the mailbox.3 > 2. Issue a queue to the mailbox, with an ast set.  > > > After 6, the AST triggers I see the "...device QUICK$FTA..."B > enabled message from opcom (since I enabled the pt as a central,@ > disk, and tape operator I should).  I then cause another OPCOMB > message to be issued (it is issued to the correct operator classA > because another terminal with the same classes enabled sees it) 8 > and the code just sits there.  The ast never triggers.  6 Yep - this is what happens if you don't set _NOBRDCST.  L Go back and change the code to set the nobroadcast bit, the way i originallyJ told you (I DID mention that I had working code that did this, didn't I?), and try it again.   K Oh, one other point:  The channel you get from PTD$CREATE shouldn't be used H (at least according to the doc) for doing the $QIO SETMODE.  You need toK use $GETDVI to get the device name, then assign another channel to the same K device (with the assoc'd mailbox), and use THAT channel in your $QIO calls. : Sounds like you're already doing this, but just in case...  =         --- Jamie Hanrahan, Kernel Mode Systems, San Diego CA O drivers, internals, networks, applications, and training for VMS and Windows NT M uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and J Chair, Programming and Internals Working Group, U.S. DECUS VMS Systems SIGB Internet:  jeh@cmkrnl.com  Uucp: uunet!cmkrnl!jeh  CIS: 74140,2055