If you have CA products available, check out KWAKEUP. It handles everything that WAKEUP does and does it better. For example, it gives you an option to put the information about the event causing the interrupt into REXX variables. There is no need to clear the stack of wakeup entries that did not cause the interrupt. It also does not have any necessity of having an artificial pre-midnight wakeup. An interval can be started on one day and not trigger the interrupt until some future date. It is WAKEUP compatible should you choose to go that route.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Wakser, David > Sent: Tuesday, July 01, 2008 7:24 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Best method > > Thanks, Bob. I haven't used WAKEUP for many years, so I'll try it. > > David Wakser > > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Bob Bates > Sent: Tuesday, July 01, 2008 10:21 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Best method > > Absolutely, > Use the WAKEUP module. > > I have a program that waits for reader files and > messages. The waiting part looks like: > > > do forever > 'WAKEUP +30 (RDR IUCVMSG' > saverc = rc > select > when saverc = 4 then > "process reader file" > when saverc = 5 then > "process a message" > > You might want to change the +30 if all it does is wait for > reader files. See HELP WAKEUP for details >
