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've noticed that our console logs for VMUTIL are huge... 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.. 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.<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]
