Not sure it's quite that simple - I too have had issues using FILE and
IUCVMSG within VMUTIL. Been awhile but I think the cause stems from this
(HELP WAKEUP):
When FILE is specified, WAKEUP will always stack the line from the file
(or a null line if no line was found) before exiting, even if the cause of
the WAKEUP was not timer expiration. The stacked line has the following
format:
* recno record-from-file
where recno is the record number of the line in the file, and
record-from-file is as much of the record as will fit on the stack.
As I recall - I would have these entries in the stack, which then had to be
tossed as they weren't 'real' timer entries.
There are some code examples under HELP WAKEUP that might help ...
Scott Rohling
On Wed, Sep 22, 2010 at 8:48 AM, Frank M. Ramaekers
<[email protected]>wrote:
> Just one “WAKEUP (SMSG FILE”. Test the RC to see which interrupted it.
>
>
>
>
>
> Frank M. Ramaekers Jr.
>
>
>
>
> ------------------------------
>
> *From:* The IBM z/VM Operating System [mailto:[email protected]] *On
> Behalf Of *Mark Workman
> *Sent:* Wednesday, September 22, 2010 9:46 AM
> *To:* [email protected]
> *Subject:* Problems with WAKEUP
>
>
>
> I am fairly new to VM and having some problems with WAKEUP.
>
> I have a server that runs a WAKEUP EXEC that uses the FILE parameter. I
> need to run an additional WAKEUP EXEC that uses the SMSG parameter.
>
> My question is can I incorporate the 'WAKEUP (SMSG' in the same FOREVER
> loop as the other WAKEUP EXEC? I am seeing errors that make me think this
> will not work this way. Or do I have to create another server to run my
> other WAKEUP EXEC (i.e. 1 server runs the WAKEUP (FILE and another server
> runs the WAKEUP (SMSG) ?
>
> Thanks in advance,
>
> Mark Workman
> Shelter Insurance Companies
> 573.214.4672
> [email protected]
>
>
>
> This e-mail is intended only for its addressee and may contain information
>
> that is privileged, confidential, or otherwise protected from disclosure. If
>
> you have received this communication in error, please notify us immediately by
>
> e-mailing [email protected]; then delete the original message.
>
> _____________________________________________________ This message contains
> information which is privileged and confidential and is solely for the use
> of the intended recipient. If you are not the intended recipient, be aware
> that any review, disclosure, copying, distribution, or use of the contents
> of this message is strictly prohibited. If you have received this in error,
> please destroy it immediately and notify us at [email protected].
>
