Dave, Try using CVTLDTO instead of CVTTZ.
Rob Scott Rocket Software, Inc 275 Grove Street Newton, MA 02466 617-614-2305 [EMAIL PROTECTED] http://www.rs.com/portfolio/mxi_g2 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of David Cole Sent: 26 June 2007 12:40 To: [email protected] Subject: Re: Finding the last IPL time (Why I wanted to know) Thanks for the additional info, Mark. What I was specifically looking for was the local time of the IPL, so the SMCA fields seem to be the ticket. I have discovered that the CVTTZ field (for converting from UTC time to local time) is not reliable. We run a FLEX-ES system on a laptop here. The system suffers from MAJOR clock drift. The TOD clock will drift out of true by a couple of DAYS per week! So for auto-scheduling purposes, I periodically need to issue a SET DATE/CLOCK command to correct the local time. Since doing that, I've discovered that the CVTTZ field does get updated, but not by a large enough value. (I'm guessing that it gets updated by the clock change but not by the date change.) Anyway, I also discovered that my SCHEDRUN program's clock knowledge was getting screwed up. When I looked at the code, I found that it was basing all of its date arithmetic upon TOD clock values adjusted by the CVTTZ value. Well, because the CVTTZ was not coping with the massive SET DATE/CLOCK change commands, the resulting scheduling was wrong two. So I've been recoding SCHEDRUN's clock knowledge to use local time (TIME BIN,ZONE=LT) as well as the System routines for time/date conversions (STCKCONV and CONVTOD). One of the things that SCHEDRUN needs to know is the local time of the last IPL, hence my initial query. Dave Cole REPLY TO: [EMAIL PROTECTED] Cole Software WEB PAGE: http://www.colesoft.com 736 Fox Hollow Road VOICE: 540-456-8536 Afton, VA 22920 FAX: 540-456-6658 At 6/25/2007 03:36 PM, you wrote: >As mentioned, my IPLINFO exec displays it - using those fields from the >SMCA. They have been there *a long time*. > >But there is also a field in the IPA - IPAICTOD - defined as when >system initialization ended. It is slightly before the time in the SMCA and >is GMT, not local. IPAICTOD also matches what you see when you use the >"D IPLINFO" operator command. > >Another place it is, that I have seen defined as "when initialization >began", is the SHID_TODCL field in the SHID. It is also in GMT. > >Regards, > >Mark >-- >Mark Zelden >Sr. Software and Systems Architect - z/OS Team Lead Zurich North >America / Farmers Insurance Group: G-ITO >mailto:[EMAIL PROTECTED] z/OS and OS390 expert at >http://searchDataCenter.com/ateExperts/ >Systems Programming expert at http://expertanswercenter.techtarget.com/ >Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
