Hi Harry, That's what I thought, and it makes sense. I seem to recall writing some REXX programs a few years back using PIPE and STARMSG to handle the communications between virtual machines and not liking that the PIPE must remain active, always, or you drop the communications layer of the programming. The nice thing about WAKEUP is that it stays resident as a nucleus extension unless/until you explicitly terminate it.
Of course, at the end of the day use whichever method works best for you. :) -Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of A. Harry Williams Sent: Tuesday, July 31, 2007 1:59 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Possible Causes of HCPMFS057I On Tue, 31 Jul 2007 11:32:40 -0400 Michael Coffin said: > >I know a lot of people are using the PIPE STARMSG stage to process IUCV >messages these days, but does that stay resident to collect SMSGs after >the PIPE terminates and passes control to the host program? Of course not. The Pipe has terminated. That's why you process the message in the Pipe. Remember that pipelines are about processing the data, not to be inside of a Rexx Do loop. Turn your Rexx Do loop into a series of Pipe stages and all works for the best. > >-Mike /ahw
