Subject: RE: WAIT
From: Kovac, Jim (jkovac@uhc.com)
Date: Tue Feb 09 2010 - 17:16:11 EST
Can I play the devil's advocate here? Having been reading this list for quite some time, I was initially shocked when Dave said he wasn't going to be able to pull it off in REXX because of the interrupt request. I could not recall any other time that he has said such a thing. I was relieved when, after his coffee I assume, he came back and said it could be done.... Here's my dilemma, by doing the loop on the number of seconds, sleeping for a second, and then checking for an interrupt, wouldn't you be 'wait'ing too long? Would it be more accurate to initially calculate when the wait should terminate and then do your loop of sleeping for a second until you reached the calculated end time? Let's say I wanted to wait for 9 hours for some reason (CICS is down for a maintenance window - I know bad example) and I am on a slow processor. If I looped 32,400 times and each time I waited one second and then checked for an interrupt, would this not be more like 9 hours and 10 minutes? Sorry, I am just feeling a little cantankerous today. In all seriousness, please let me take this time to tell each and every one of you who monitor this list, Thank You for all you have given all of those of us who do more listening than contributing! As much as I love VSE, my current role doesn't afford me the opportunity to tinker with it much, so living it through all of you is the next best thing. Jim Kovac UnitedHealthcare UHG-IT Midwest IT <snip> PARSE ARG SECONDS . DO I = 1 TO SECONDS SLEEP(1) END EXIT 0 </snip> This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
This archive was generated by hypermail 2b25 : Fri Mar 19 2010 - 03:35:08 EST