From:	MERC::"uunet!WKUVX1.BITNET!MacroMan"  3-APR-1993 05:27:49.72
To:	MACRO32@WKUVX1.BITNET
CC:	
Subj:	Re: Trapping OPCOM messages in Detached proc

In article <1993Mar23.212708.1640@cmkrnl.com>, jeh@cmkrnl.com writes:
> The key is VMS's pseudoterminal driver.  (I/O User's Reference Manual, Part I,
> Chapter 9 or so.)  Create a pseudoterminal, associate a mailbox with it,
 enable
> 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.

I'm trying to get this to work and am having some luck, but not
complete success.  The process I'm going through is:

1. Create a mailbox and get a channel.
2. Create a pseudo terminal and get a channel.
3. Assign a channel to the pt, associating the mailbox.
4. using the channel acquired in 3, clear nobroadcast and set
broadcast mailbox.
5. Issue a qio to the mailbox, with an ast set.
6. Enable the pt as an operator device.

In the ast:

1. Read the mailbox.
2. Issue a queue to the mailbox, with an ast set.

After 6, the AST triggers I see the "...device QUICK$FTA..."
enabled message from opcom (since I enabled the pt as a central,
disk, and tape operator I should).  I then cause another OPCOM
message to be issued (it is issued to the correct operator class
because another terminal with the same classes enabled sees it)
and the code just sits there.  The ast never triggers.  I've
poked around with ANALYZE/SYSTEM and there is an I/O operation
queued to the mailbox, user mode ASTs are enabled, ...  I'm kind
of stumped.  If anyone has a fragment of working code that I
could look at I'ld appreciate it.

Thanks
--
Dick Munroe                             Internet: munroe@dmc.com
Doyle Munroe Consultants, Inc.          UUCP: ...uunet!thehulk!munroe
267 Cox St.                             Office: (508) 568-1618
Hudson, Ma.                             FAX: (508) 562-1133

GET CONNECTED!!! Send mail to info@dmc.com to find out about DMConnection.