No John, I was not accusing you of highjacking. But I'm not "processing" the name portions of the TZ string. I'm not going "EDT! Aha! I know what that means..." Here's the problem I am trying to solve: What goes in timezone_name?
I'm currently sticking the first three characters of TZ or a string such as EST5EDT in timezone_name, and I know that's wrong. What *should* I be doing instead? Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Gilmore Sent: Friday, September 06, 2013 4:06 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: timezone_name? It is your thread, and I have no wish to hijack it. This will therefore be my last post for it. I chose Australian local times advisedly. They illustrate the differences between Daylight|Summer|Official times and Standard ones in the northern and southern hemispheres. You mentioned that you needed to revise your 'parsing' of such strings as 'AMT4AMST', and I perhaps interpreted this too literally. If you are always handing off such strings to someone else, you need not take any responsibility for 'errors' in them. If you are going to try to make sense of them, then you need to understand such differing conventions as those embodied in MSK, Moscow Standard Time MSD, Moscow Daylight Time WET, Western European Time WEST, Western European Summer Time EST, Eastern Standard Time (United States) EDT, Eastern Daylight Time (United States) I have been down this road; and great care must, for example, be taken to disentangle the 'S' for Summer and the 'S' for Standard, assuming always that you are not delegating the responsibility for doing so to someone else. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
