I do use wakeup with the RDR option and have not seen the problem
you mention. If a reader file exists, wakeup always exit with the
appropriate return code.
As for SMSG messages, they are suppose to be stacked if you are
in or out of the wakeup module when they arrive.
On Wed, 15 Feb 2006 10:32:43 -0600 Tom Duerbusch said:
>In earlier releases of VM, I had a problem when doing a wakeup on reader
>It would wake up and start processing the reader. But if new rdr files
>came in while I was processing, they wouldn't get processed, and when I
>went back into wakeup, it wouldn't return until another file hit the
>In this example, some of it was due to bad coding, as I did a Q RDR ALL
>when I returned from wakeup, and didn't look for any other files when I
>was done processing. But part of it, was due to wakeup only checking
>for something comming into the reader, not something already there. I
>can see the reasons for this.
>With wakeup on IUCV, if you are not in the wakeup module when the IUCV
>communication is attempted, wouldn't the communication fail and it is up
>to the sender to try again? Or is IUCV communication somehow stacked by
>>>> ***@biostat.bsc.gwu.edu 2/15/2006 8:12 AM >>>
>I should have been more clear.. I am not doing the SET SMSG within
>loop. Here is what I have
>'CP SET SMSG IUCV'
> "WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
> <do some work based on why we woke up>
>There are no other SET SMSG commands in the code. Allthe work done is
>in the same exec and do not involve RACF, etc.
>I do issue a new WAKEUP every time the loop is repeated because I need
>sleep for at most 10 seconds. I don't see any other way to do with
>without having an external wakeup times file. Would issuing the
>command flush out any pending SMSG messages?
>On Wed, 15 Feb 2006 06:43:29 +0100 Kris Buelens said:
>>1. There is no need for the CP SET SMSG IUCV. Our RXSERVER doesn't
>>2. If WAKEUP is reset in the loop: between the CP SET and WAKEUP,
>>won't be handled
>>3. You don't say what you do every 10 minutes. RAC(F) commands for
>>example also use VMCF, and that "kills" any pending SMSG
>>IBM Belgium, VM customer support
>>> I am having a problem with the WAKEUP command missing SMSG messages
>>> when the messages arrive just before a scheduled wakeup time.
>>> I have suspected this for years but never had a chance to look at
>>> it closely. I am now able to reproduce the problem. Here is what
>>> I have in a loop on a DVM:
>>> 'CP SET SMSG IUCV'
>>> "WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
>>> The machine is to do something every 10 seconds or when it receives
>>> an SMSG. If the SMSG arrives **JUST** before the 10 second timer is
>>> it will be missed!
>>> Has anyone else seen this problem?
>>> Thanks in advance.