Sorry Richard: WAKEUP is actively grabbing messages: even when your long running program is active, WAKEUP's first level interrupt handler is active too. WAKEUP will queue the IUCV messages in its own storage. It is not only CP that queues. When WAKEUP can't catch up CP queues too. The minimum CP queue is 256 (even if you ask for less on the IUCV *MSG statement). Messages on top of that are displayed at the console, as if WAKEUP weren't there. I tested this years ago when we encountered problems with messages that seemed to get lost
2007/3/30, Schuh, Richard <[EMAIL PROTECTED]>:
If you have a long running program, WAKEUP is not actively grabbing the messages; they are being queued by CP. They do not get eaten until the program ends. The problem is what happens if the number of messages received is greater than the number that CP will queue. The messages discarded may include something important. Regards, Richard Schuh ------------------------------ *From:* The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] *On Behalf Of *Kris Buelens *Sent:* Thursday, March 29, 2007 3:08 PM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: MSGTRAP/Trapping MSGs Why did nobody mention WAKEUP? Not the same as TERM HOLD OFF: the messages will be eaten by WAKEUP and be displayed afterwards. WAKEUP +0 (IUCVMSG ... perform the work start a REXX EXEC that basically performs: do forever 'WAKEUP +0 (IUCVMSG' if rc=2 then leave parse pull theMsg ; say TheMsg end 'WAKEUP RESET' 2007/3/29, Neale Ferguson < [EMAIL PROTECTED]>: One thing I don't like about NOTERM is that output from the "virtual HMC" (i.e. messages generated by SERVC instruction) ignores the NOTERM option and appears on the console. On Thu, 2007-03-29 at 10:19 -0700, Schuh, Richard wrote: > Yes, there is the NOTERM option. Yet another way would be to simply > disconnect the machine after starting the program (with the console > spooled, of course). -- Kris Buelens, IBM Belgium, VM customer support
-- Kris Buelens, IBM Belgium, VM customer support
