Problem with WAKEUP

[Aria Bamdad]

Hi,

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 up,
it will be missed!

Has anyone else seen this problem?

Thanks in advance.
Aria

[Rich Greenberg]

On: Tue, Feb 14, 2006 at 05:54:53PM -0500,Aria Bamdad Wrote:

} Hi,
}
} 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 up,
} it will be missed!
}
} Has anyone else seen this problem?

Inside your loop, do you change the SET SMSG settings? If so, move them
outside the loop. Whats happening is that the second item arrives when
you have SMSG set to normal so it just lost. Leave SET SMSG IUCV in
effect and then the second one will get cued and handled when it returns
from handling the timer pop.

This is mainly an educated guess, based on:
1) Never having seen the problem.
2) Doing the SET SMSG IUCV outside the main loop.

--
Rich Greenberg N6LRT Marietta, GA, USA richgr atsign panix.com + 1 770 321 6507
Eastern time zone. I speak for myself & my dogs only. VM'er since CP-67
Canines:Val, Red & Shasta (RIP),Red, husky Owner:Chinook-L
Atlanta Siberian Husky Rescue. www.panix.com/~richgr/ Asst Owner:Sibernet-L

[Jim Bohnsack]

I may have seen something like that. I have WAKEUP driven VMSCHED machines
that had, what may have been the same problem. They were receiving system
backup related files, such as other system's directories, SYSTEM CONFIG's,
allocation maps and things that you'd really like to have and they were
getting them at about the same time. I suspected that I/O interrupts would
queue up while something else was being processed such as receiving or
sending a large file such as a source directory. Some interrupts would be
lost, but I don't remember what. At the time that files were coming in and
going out, timer events were happening from the TIMES file. I "fixed" the
problem by spreading out some of the activity. It wasn't a very glamorous
or clever fix, but it was pragmatic and worked perfectly.
Jim

At 09:13 PM 2/14/2006, you wrote:
>On: Tue, Feb 14, 2006 at 05:54:53PM -0500,Aria Bamdad Wrote:
>
>} Hi,
>}
>} 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 up,
>} it will be missed!
>}
>} Has anyone else seen this problem?
>
>Inside your loop, do you change the SET SMSG settings? If so, move them
>outside the loop. Whats happening is that the second item arrives when
>you have SMSG set to normal so it just lost. Leave SET SMSG IUCV in
>effect and then the second one will get cued and handled when it returns
>from handling the timer pop.
>
>This is mainly an educated guess, based on:
>1) Never having seen the problem.
>2) Doing the SET SMSG IUCV outside the main loop.
>
>--
>Rich Greenberg N6LRT Marietta, GA, USA richgr atsign panix.com + 1 770 321
>6507
>Eastern time zone. I speak for myself & my dogs only. VM'er since CP-67
>Canines:Val, Red & Shasta (RIP),Red, husky Owner:Chinook-L
>Atlanta Siberian Husky Rescue. www.panix.com/~richgr/ Asst Owner:Sibernet-L

Jim Bohnsack
Cornell Univ.
[phone]

[Kris Buelens]

1. There is no need for the CP SET SMSG IUCV. Our RXSERVER doesn't use it
2. If WAKEUP is reset in the loop: between the CP SET and WAKEUP, SMSG's
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

Kris,
IBM Belgium, VM customer support

> Hi,

> 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 up,
> it will be missed!

> Has anyone else seen this problem?

> Thanks in advance.
> Aria

[Aria Bamdad]

I should have been more clear.. I am not doing the SET SMSG within the
loop. Here is what I have

'CP SET SMSG IUCV'
do forever
"WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
<do some work based on why we woke up>
end

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 to
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 WAKEUP
command flush out any pending SMSG messages?

Aria.


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 use it
>2. If WAKEUP is reset in the loop: between the CP SET and WAKEUP, SMSG's
>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
>
>Kris,
>IBM Belgium, VM customer support
>
>> Hi,
>
>> 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 up,
>> it will be missed!
>
>> Has anyone else seen this problem?
>
>> Thanks in advance.
>> Aria

[Bruce Hayden]

I think you should remove SMSG from the wakeup options. When you use
the SMSG option, I think WAKEUP does a SET SMSG ON and then handles
receives the messages via VMCF. What you want is to receive the
messages via IUCV, so leave the CP SET SMSG IUCV but code your wakeup
command as
"WAKEUP +00:10 (NOEXT IUCVMSG"

On 2/15/06, Aria Bamdad <***@biostat.bsc.gwu.edu> wrote:
> I should have been more clear.. I am not doing the SET SMSG within the
> loop. Here is what I have
>
> 'CP SET SMSG IUCV'
> do forever
> "WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
> <do some work based on why we woke up>
> end
>
> 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 to
> 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 WAKEUP
> command flush out any pending SMSG messages?

--
Bruce Hayden
IBM Global Services zSeries Linux
Endicott, NY

[Colleen Brown]

Aria,
The first time you invoke WAKEUP with the IUCVMSG option, you will
load WAKEUP's IUCV interrupt handler. It is always a good Idea to invoke
WAKEUP once outside your loop with something like WAKEUP +00 (IUCVMSG .
This will wake up immediately and will load the IUCVMSG handler. Then,
when you get into your loop, you should be all set.
Also, you can set SMSG ON or set SMSG to IUCV. WAKEUP can handle
both VMCF and IUCV interrupts. When you set SMSG to IUCV I believe you
only need the IUCVMSG option. Also, NOEXT is not needed anymore.

Colleen M Brown
IBM z/VM and Related Products Development and Service



Aria Bamdad <***@biostat.bsc.gwu.edu>
Sent by: VM/ESA and z/VM Discussions <VMESA-***@LISTSERV.UARK.EDU>
02/15/2006 09:12 AM
Please respond to
VM/ESA and z/VM Discussions


To
VMESA-***@LISTSERV.UARK.EDU
cc

Subject
Re: Problem with WAKEUP






I should have been more clear.. I am not doing the SET SMSG within the
loop. Here is what I have

'CP SET SMSG IUCV'
do forever
"WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
<do some work based on why we woke up>
end

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 to
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 WAKEUP
command flush out any pending SMSG messages?

Aria.


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 use
it
>2. If WAKEUP is reset in the loop: between the CP SET and WAKEUP, SMSG's
>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
>
>Kris,
>IBM Belgium, VM customer support
>
>> Hi,
>
>> 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
up,
>> it will be missed!
>
>> Has anyone else seen this problem?
>
>> Thanks in advance.
>> Aria

[Aria Bamdad]

I found the cause!!!

Somewhere in the exec, I have a call to NETSTAT command. It appears
that if a message arrives at just the right time, while I am doing
the NETSTAT, I lose the message.

Is this expected?

Aria.
On Wed, 15 Feb 2006 09:44:20 -0500 Colleen Brown said:
>
>Aria,
> The first time you invoke WAKEUP with the IUCVMSG option, you will
>load WAKEUP's IUCV interrupt handler. It is always a good Idea to invoke
>WAKEUP once outside your loop with something like WAKEUP +00 (IUCVMSG .
>This will wake up immediately and will load the IUCVMSG handler. Then,
>when you get into your loop, you should be all set.
> Also, you can set SMSG ON or set SMSG to IUCV. WAKEUP can handle
>both VMCF and IUCV interrupts. When you set SMSG to IUCV I believe you
>only need the IUCVMSG option. Also, NOEXT is not needed anymore.
>
>Colleen M Brown
>IBM z/VM and Related Products Development and Service
>
>
>
>Aria Bamdad <***@biostat.bsc.gwu.edu>
>Sent by: VM/ESA and z/VM Discussions <VMESA-***@LISTSERV.UARK.EDU>
>02/15/2006 09:12 AM
>Please respond to
>VM/ESA and z/VM Discussions
>
>
>To
>VMESA-***@LISTSERV.UARK.EDU
>cc
>
>Subject
>Re: Problem with WAKEUP
>
>
>
>
>
>
>I should have been more clear.. I am not doing the SET SMSG within the
>loop. Here is what I have
>
>'CP SET SMSG IUCV'
>do forever
> "WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
> <do some work based on why we woke up>
>end
>
>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 to
>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 WAKEUP
>command flush out any pending SMSG messages?
>
>Aria.
>
>
>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 use
>it
>>2. If WAKEUP is reset in the loop: between the CP SET and WAKEUP, SMSG's
>>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
>>
>>Kris,
>>IBM Belgium, VM customer support
>>
>>> Hi,
>>
>>> 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
>up,
>>> it will be missed!
>>
>>> Has anyone else seen this problem?
>>
>>> Thanks in advance.
>>> Aria
>

[Fran Hensler]

I have the same problem. In my SMSG routine I do a DIOOT and an FTP.
If an SMSG comes in while that process is going on then I lose it.

/Fran Hensler at Slippery Rock University of Pennsylvania USA
***@zvm.sru.edu +1.724.738.2153
"Yes, Virginia, there is a Slippery Rock"

On Wed, 15 Feb 2006 10:06:33 -0500 Aria Bamdad said:
>I found the cause!!!
>
>Somewhere in the exec, I have a call to NETSTAT command. It appears
>that if a message arrives at just the right time, while I am doing
>the NETSTAT, I lose the message.
>
>Is this expected?
>
>Aria.

[Fran Hensler]

Sorry, fat fingers meant to type "DITTO and FTP"
/Fran

On Wed, 15 Feb 2006 10:54:40 EST Fran Hensler said:
>I have the same problem. In my SMSG routine I do a DIOOT and an FTP.
>If an SMSG comes in while that process is going on then I lose it.
>
>/Fran Hensler at Slippery Rock University of Pennsylvania USA
> ***@zvm.sru.edu +1.724.738.2153
> "Yes, Virginia, there is a Slippery Rock"
>
>On Wed, 15 Feb 2006 10:06:33 -0500 Aria Bamdad said:
>>I found the cause!!!
>>
>>Somewhere in the exec, I have a call to NETSTAT command. It appears
>>that if a message arrives at just the right time, while I am doing
>>the NETSTAT, I lose the message.
>>
>>Is this expected?
>>
>>Aria.

[Rich Greenberg]

On: Wed, Feb 15, 2006 at 11:03:14AM -0500,Fran Hensler Wrote:

} Sorry, fat fingers meant to type "DITTO and FTP"
} /Fran
}
} On Wed, 15 Feb 2006 10:54:40 EST Fran Hensler said:
} >I have the same problem. In my SMSG routine I do a DIOOT and an FTP.
} >If an SMSG comes in while that process is going on then I lose it.

Any non-trivial things would best be done by another SVM kicked off by
the WAKEUP process.

--
Rich Greenberg N6LRT Marietta, GA, USA richgr atsign panix.com + 1 770 321 6507
Eastern time zone. I speak for myself & my dogs only. VM'er since CP-67
Canines:Val, Red & Shasta (RIP),Red, husky Owner:Chinook-L
Atlanta Siberian Husky Rescue. www.panix.com/~richgr/ Asst Owner:Sibernet-L

[Aria Bamdad]

Alan,

It is happening in NETSTAT and I am losing the SMSG. I have a small
test program that shows it. In fact when a message is lost, the
sender gets an error that the receiver is not authorized or not receiving
messages.

Shall I call this in?

Aria.
On Wed, 15 Feb 2006 10:49:03 -0500 Alan Altmark said:
>On Wednesday, 02/15/2006 at 10:06 EST, Aria Bamdad
><***@biostat.bsc.gwu.edu> wrote:
>> I found the cause!!!
>>
>> Somewhere in the exec, I have a call to NETSTAT command. It appears
>> that if a message arrives at just the right time, while I am doing
>> the NETSTAT, I lose the message.
>>
>> Is this expected?
>
>NETSTAT uses VMCF and issues HNDEXT SET (without an interrupt code since
>it also handles #CP EXT). But that should not be interfering with IUCV
>messages since CMS steals those for the HNDIUCV service (which is used by
>WAKEUP). If NETSTAT is eating non-VMCF messages, that would be a bug.
>
>Alan Altmark
>z/VM Development
>IBM Endicott

[Tom Duerbusch]

In earlier releases of VM, I had a problem when doing a wakeup on reader
option.

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
reader.

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
CP?

Tom Duerbusch
THD Consulting

>>> ***@biostat.bsc.gwu.edu 2/15/2006 8:12 AM >>>
I should have been more clear.. I am not doing the SET SMSG within
the
loop. Here is what I have

'CP SET SMSG IUCV'
do forever
"WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
<do some work based on why we woke up>
end

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
to
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
WAKEUP
command flush out any pending SMSG messages?

Aria.


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
use it
>2. If WAKEUP is reset in the loop: between the CP SET and WAKEUP,
SMSG's
>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
>
>Kris,
>IBM Belgium, VM customer support
>
>> Hi,
>
>> 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
up,
>> it will be missed!
>
>> Has anyone else seen this problem?
>
>> Thanks in advance.
>> Aria

[Aria Bamdad]

Tom,

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.

Aria.
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
>option.
>
>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
>reader.
>
>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
>CP?
>
>Tom Duerbusch
>THD Consulting
>
>>>> ***@biostat.bsc.gwu.edu 2/15/2006 8:12 AM >>>
>I should have been more clear.. I am not doing the SET SMSG within
>the
>loop. Here is what I have
>
>'CP SET SMSG IUCV'
>do forever
> "WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
> <do some work based on why we woke up>
>end
>
>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
>to
>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
>WAKEUP
>command flush out any pending SMSG messages?
>
>Aria.
>
>
>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
>use it
>>2. If WAKEUP is reset in the loop: between the CP SET and WAKEUP,
>SMSG's
>>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
>>
>>Kris,
>>IBM Belgium, VM customer support
>>
>>> Hi,
>>
>>> 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
>up,
>>> it will be missed!
>>
>>> Has anyone else seen this problem?
>>
>>> Thanks in advance.
>>> Aria

[Schuh, Richard]

I suspect that both are working as designed. You running 2 programs that are trying to use a single-user interface. This is a conflict that probably cannot be fixed without a major overhaul of the interface and programs that use it.

The loss of the message is undoubtedly due to NETSTAT discarding it as an unknown message/command.

Regards,
Richard Schuh

-----Original Message-----
From: VM/ESA and z/VM Discussions [mailto:VMESA-***@LISTSERV.UARK.EDU] On Behalf Of Aria Bamdad
Sent: Wednesday, February 15, 2006 8:58 AM
To: VMESA-***@LISTSERV.UARK.EDU
Subject: Re: Problem with WAKEUP

Alan,

It is happening in NETSTAT and I am losing the SMSG. I have a small
test program that shows it. In fact when a message is lost, the
sender gets an error that the receiver is not authorized or not receiving
messages.

Shall I call this in?

Aria.
On Wed, 15 Feb 2006 10:49:03 -0500 Alan Altmark said:
>On Wednesday, 02/15/2006 at 10:06 EST, Aria Bamdad
><***@biostat.bsc.gwu.edu> wrote:
>> I found the cause!!!
>>
>> Somewhere in the exec, I have a call to NETSTAT command. It appears
>> that if a message arrives at just the right time, while I am doing
>> the NETSTAT, I lose the message.
>>
>> Is this expected?
>
>NETSTAT uses VMCF and issues HNDEXT SET (without an interrupt code since
>it also handles #CP EXT). But that should not be interfering with IUCV
>messages since CMS steals those for the HNDIUCV service (which is used by
>WAKEUP). If NETSTAT is eating non-VMCF messages, that would be a bug.
>
>Alan Altmark
>z/VM Development
>IBM Endicott

[Tom Duerbusch]

Great! As I said, earlier releases....

But now I'm in the habbit of writting REXX with wakeup with my old
assumptions, it may take a while for me to change my thought
processes<G>. Much less change the execs.

Tom Duerbusch
THD Consulting

>>> ***@biostat.bsc.gwu.edu 2/15/2006 11:00 AM >>>
Tom,

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.

Aria.
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
>option.
>

[Aria Bamdad]

SOLVED!!!

Bruce (and others) thank you for your comments. The solution was
as Bruce said, to remove the SMSG from the WAKEUP command.

My test program that did fail before no longer does so. I do a
SET MSG IUCV and then WAKEUP (IUCVMSG.

Having the WAKEUP (SMSG IUCVMSG was the problem.

Thanks again.

Aria.
On Wed, 15 Feb 2006 12:47:56 -0500 Bruce Hayden said:
>I think you should remove SMSG from the wakeup options. When you use
>the SMSG option, I think WAKEUP does a SET SMSG ON and then handles
>receives the messages via VMCF. What you want is to receive the
>messages via IUCV, so leave the CP SET SMSG IUCV but code your wakeup
>command as
>"WAKEUP +00:10 (NOEXT IUCVMSG"
>
>On 2/15/06, Aria Bamdad <***@biostat.bsc.gwu.edu> wrote:
>> I should have been more clear.. I am not doing the SET SMSG within the
>> loop. Here is what I have
>>
>> 'CP SET SMSG IUCV'
>> do forever
>> "WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
>> <do some work based on why we woke up>
>> end
>>
>> 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 to
>> 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 WAKEUP
>> command flush out any pending SMSG messages?
>
>--
>
>Bruce Hayden
>IBM Global Services zSeries Linux
>Endicott, NY

[Fran Hensler]

And my problem is solved too.

I added 'CP SET SMSG IUCV'

I changed from WAKEUP ( SMSG
to WAKEUP ( IUCVMSG

I am no longer losing stacked SMSGs after 6 years of trying.
This list is great!

/Fran Hensler at Slippery Rock University of Pennsylvania USA
***@zvm.sru.edu +1.724.738.2153
"Yes, Virginia, there is a Slippery Rock"


On Wed, 15 Feb 2006 15:21:58 -0500 Aria Bamdad said:

>SOLVED!!!
>
>Bruce (and others) thank you for your comments. The solution was
>as Bruce said, to remove the SMSG from the WAKEUP command.
>
>My test program that did fail before no longer does so. I do a
>SET MSG IUCV and then WAKEUP (IUCVMSG.
>
>Having the WAKEUP (SMSG IUCVMSG was the problem.
>
>Thanks again.
>
>Aria.
>On Wed, 15 Feb 2006 12:47:56 -0500 Bruce Hayden said:
>>I think you should remove SMSG from the wakeup options. When you use
>>the SMSG option, I think WAKEUP does a SET SMSG ON and then handles
>>receives the messages via VMCF. What you want is to receive the
>>messages via IUCV, so leave the CP SET SMSG IUCV but code your wakeup
>>command as
>>"WAKEUP +00:10 (NOEXT IUCVMSG"
>>
>>On 2/15/06, Aria Bamdad <***@biostat.bsc.gwu.edu> wrote:
>>> I should have been more clear.. I am not doing the SET SMSG within the
>>> loop. Here is what I have
>>>
>>> 'CP SET SMSG IUCV'
>>> do forever
>>> "WAKEUP +00:10 ( SMSG NOEXT IUCVMSG"
>>> <do some work based on why we woke up>
>>> end
>>>
>>> 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 to
>>> 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 WAKEUP
>>> command flush out any pending SMSG messages?
>>
>>--
>>
>>Bruce Hayden
>>IBM Global Services zSeries Linux
>>Endicott, NY

[Aria Bamdad]

On Wed, 15 Feb 2006 16:18:39 EST Fran Hensler said:
>And my problem is solved too.
>
>I added 'CP SET SMSG IUCV'
>
>I changed from WAKEUP ( SMSG
> to WAKEUP ( IUCVMSG
>
>I am no longer losing stacked SMSGs after 6 years of trying.
>This list is great!

The power of the 'Collective'. The Brog knew what they were doing!!

[Daniel P. Martin]

Ed Zell wrote:
>>> I am no longer losing stacked SMSGs after 6 years of trying.
>>> This list is great!
>>>
>
>
>
>> The power of the 'Collective'. The Brog knew what they were doing!!
>>
>
>
> And as Chuckie might say ..... Resistance is futile
>
>
> Ed Zell
> Illinois Mutual Life
> .
>
"Resistance is futile. You will be virtualized."

OK, as the moderator I have to smack myself for contributing to this
thread now...

-dan.

[Gregg C Levine]

Hello from Gregg C Levine
Isn’t that supposed to be Borg? And they said it first. But yes this
list is terrific.
---
Gregg C Levine ***@worldnet.att.net
---
"Remember the Force will be with you. Always." Obi-Wan Kenobi

> -----Original Message-----
> From: VM/ESA and z/VM Discussions [mailto:VMESA-
> ***@LISTSERV.UARK.EDU] On Behalf Of Ed Zell
> Sent: Wednesday, February 15, 2006 4:54 PM
> To: VMESA-***@LISTSERV.UARK.EDU
> Subject: Re: Problem with WAKEUP
>
> >> I am no longer losing stacked SMSGs after 6 years of trying.
> >> This list is great!
>
>
> > The power of the 'Collective'. The Brog knew what they were
doing!!
>
>
> And as Chuckie might say ..... Resistance is futile
>
>
> Ed Zell
> Illinois Mutual Life
> .
>
>
> CONFIDENTIAL NOTICE: This communication, including any attachments,
is
> intended only for the use of the individual or entity to which it is
addressed and
> contains information which may be confidential. If you are not the
intended
> recipient, any distribution or copying of this communication is
strictly prohibited. If
> you have received this communication in error, notify the sender
immediately,
> delete the communication and destroy all copies. Thank you for your
compliance.