The following is in my VMUTIL EXEC.  I am not sure if it came this way
or someone before me added it:

DO_SOMETHING:                                                          
ARG INLINE                                                             
IF TIME() >= '23:57:30' THEN DO        /* MUST WAIT PAST MIDNIGHT */   
                ADDRESS COMMAND 'CP SLEEP 3 MIN'                       
/*              ADDRESS COMMAND 'CP SPOOL CONSOLE CLOSE'          */   
END                                                                    

AND a few lines later . . .

SMSG_ARRIVED:

ARG INLINE

IF TIME() >= '23:57:30' THEN DO        /* MUST WAIT PAST MIDNIGHT */

                ADDRESS COMMAND 'CP SLEEP 3 MIN'

/*                ADDRESS COMMAND 'CP SPOOL CONSOLE CLOSE'      */

END


Thank you,
Scott R Wandschneider
Senior Systems Programmer
Infocrossing
Office 402.963.8905

> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On Behalf
> Of Jim Bohnsack
> Sent: Thursday, October 09, 2008 9:56 AM
> To: IBMVM@LISTSERV.UARK.EDU
> Subject: Re: VMUTIL loop
> 
> Scott--I put into my * TIMES file the following statement to handle
this
> problem:
> 
> ==/==/== 23:59:00 10/09/08 CP SLEEP 2 MIN
> 
> Note that the date is set by WAKEUP at the time the event occurs.
Just
> be sure that when you put this into your TIMES file it's a date that
has
> already occurred.
> 
> Jim
> 
> Scott Rohling wrote:
> > ------=_Part_99668_10155136.1223560304947
> > Content-Type: text/plain; charset=ISO-8859-1
> > Content-Transfer-Encoding: 7bit
> > Content-Disposition: inline
> >
> > I've noticed that our console logs for VMUTIL are huge...  it seems
that
> > just before midnight - it starts spewing this message:
> >
> > DMSCYW2246I*
> > DMSCYW2246I*
> > DMSCYW2246I*
> > DMSCYW2246I*
> > DMSCYW2246I*
> > DMSCYW2246I*
> > DMSCYW2246I*
> > DMSCYW2246I*
> > DMSCYW2246I*
> > DMSCYW2246I*
> >
> > For thousands of lines -- and then at midnight all is well..   There
is a
> > MIDNIGHT function in VMUTIL SCHEDULE that I commented out, just in
case this
> > was causing the issue - but that didn't help.
> >
> > Anybody else use VMUTIL and see this?
> >
> > Thanks -
> >
> > Scott Rohling
> >
> > ------=_Part_99668_10155136.1223560304947
> > Content-Type: text/html; charset=ISO-8859-1
> > Content-Transfer-Encoding: 7bit
> > Content-Disposition: inline
> >
> > <div dir="ltr">I&#39;ve noticed that our console logs for VMUTIL are
> huge...&nbsp; it seems that just before midnight - it starts spewing
this
> message:<br><br>DMSCYW2246I* <br>DMSCYW2246I* <br>DMSCYW2246I*
> <br>DMSCYW2246I* <br>
> > DMSCYW2246I* <br>DMSCYW2246I* <br>DMSCYW2246I* <br>DMSCYW2246I*
> <br>DMSCYW2246I* <br>DMSCYW2246I* <br><br>For thousands of lines --
and then
> at midnight all is well..&nbsp;&nbsp; There is a MIDNIGHT function in
VMUTIL
> SCHEDULE that I commented out, just in case this was causing the issue
- but
> that didn&#39;t help.<br>
> > <br>Anybody else use VMUTIL and see this?<br><br>Thanks -
<br><br>Scott
> Rohling<br><br></div>
> >
> > ------=_Part_99668_10155136.1223560304947--
> >
> >
> 
> --
> Jim Bohnsack
> Cornell University
> (972) 596-6377 home/office
> (972) 342-5823 cell
> [EMAIL PROTECTED]

Reply via email to