Nothing's wrong your suggestion.  It's better and I'll change my code.

Background:
IIRC it's just that I had it written to go through the spring of 2042 (the 
fall of 2042 is after the TOD clock wraps).  Then I discovered that 
CPSYNTAX accepts dates in 2042, but CP balks at IPL for any dates after 
2041.  [CPSYNTAX only checks syntax, there can still be other problems in 
SYSTEM CONFIG that only an IPL will discover.]   So I added the "Leave" 
while reporting it to IBM, figuring that getting an APAR/PTF would be easy 
for this minor problem; then I could remove the Leave.  But IBM asked 
(reasonably) if they could fix it in some future release with an internal 
update rather than go the APAR/PTF route.  Given that we have a plenty of 
time before 2042 and IBM has better things to work on that something 35 
years from now, I agreed.   I never looked at that part of the code again.

Mike (Future candidate for U.S. Grand Poo-Bah, and still missing Val 
Breault's posts on VMSHARE) Walter  
Hewitt Associates 
Any opinions expressed herein are mine alone and do not necessarily 
represent the opinions or policies of Hewitt Associates.



"Shimon Lebowitz" <[EMAIL PROTECTED]> 

Sent by: "The IBM z/VM Operating System" <[email protected]>
03/09/2007 05:56 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>



To
[email protected]
cc

Subject
Re: TIMEZONE






>   Do ix=2007 to 2042        /* What years do we want to cover?      */
>       If ix=2042 then Leave  /* Old TOD clock wrapped in August 2042 */

Is this the Poohbah coding style?
What is wrong with this? 
   Do ix=2007 to 2041    /* don't make me "leave" you at 2042 */

Shimon



 
The information contained in this e-mail and any accompanying documents may 
contain information that is confidential or otherwise protected from 
disclosure. If you are not the intended recipient of this message, or if this 
message has been addressed to you in error, please immediately alert the sender 
by reply e-mail and then delete this message, including any attachments. Any 
dissemination, distribution or other use of the contents of this message by 
anyone other than the intended recipient 
is strictly prohibited.


Reply via email to