How would the STARMSG pipeline detect someone typing a message at the console and hitting the ENTER key? Would it require another concurrent pipe running?
I like WAKEUP because I can set timer interrupts, reader interrupts, message interrupts, and console interrupts. ___________________________ Jim Hughes 603-271-5586 "Its kind of fun to do the impossible." (Walt Disney) ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Richard Troth Sent: Tuesday, July 01, 2008 12:12 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Best method > Is there a method of also trapping the "message" > that shows when a file is sent to the VM reader? > I need it to issue the RECEIVE properly. In the HELP WAKEUP > it seems that setting the various message > types to IUCV should work, but it doesn't seem to do that, Well ... everyone was saying "use WAKEUP" and that's good advice, but I prefer to start with Pipelines. Pipes would catch all those messages you're interested in. Your EXEC would look something like ... /* REXX */ 'CP SET IMSG IUCV' 'PIPE STARMSG | REXX MYTHING' And then MYTHING REXX might begin as ... /* REXX */ Do Forever 'PEEKTO RECORD' /* examine the record, but do not consume it */ If rc ^= 0 Then Leave /* parse the variable "record" and figger things out */ 'READTO' /* now consume that record and loop to get another */ End You can do all of this with WAKEUP. The calling semantics are different. -- R; <><
