|
Hi, The problem with the way IBM handled the effective date of the time zone change, (by adding new *TIMZON objects), is that eventually they will run out of time zones. If you look at the format of the time zone object names in QSYS, almost all of the characters are used. (I would add a chart, but it wouldn't replicate to the list.) This was a good design, because the names were both (mostly) obvious and meaningful. (After someone took a few minutes to explain the format to you.) There's basically only one additional character to handle problems like Indiana Hawaii and Arizona (not that I have any problems with Rob or Wayne Evans). As time passes, and time zones morph (and both will happen [God willing]), there will be more are more time zone changes, and we will run out of the nine character limit for time zone changes, at which point IBM will either have to: o violate their own time zone naming rules (*UGLY) o re-use "old" and presumably unused ones. The proper solution (IMHO) is to modify time zone objects to have an "effective date of change" field, with additional rules, changing this from what is now essentially a one dimensional array to a two dimensional array. Although this change would not have been "cheap" from an IBM effort perspective, it would have been a significantly better enduring design. Other issues would have been what date format is used in the time zone itself, and how do you change that when the system value QDATFMT is changed, but IBM does seem to be able to handle this effectively (although I must confess that I have never changed QDATFMT for anyone! in the remainder of the system. Given what IBM has done, I don't think that realistically there's any going back to a better design. Anything you would likely do would probably break more users than fix them:-(((((((( Just a little history: o The correct name is "Daylight Saving Time", not "Daylight SavingS Time". o It was first proposed in 1784 by Benjamin Franklin as "Daylight Candle Saving Time". (This guy was no dummy.) o It was first adopted in 1918 to save energy during WW1, and was repealed a year later (after the war concluded) because of rural complaints. (Farmers, et. all.) o It was re-adopted year round in 1942 to save energy during WW2, although Michigan and Ohio didn't buy in. Many states used "Double Daylight Saving Time" then in the summer! I don't have good facts on his, but if you do, please forward them along. o In 1966, Congress standardized DST, but Indiana, Hawaii and Arizona balked. o If you're 50 or older, you will likely remember when Richard Nixon moved the country to DST during the Arab Oil Embargo in January 1974. (Dem Arabs thought they had the biggest monopoly in world, but nobody told them that Bill Gates was coming!) o In 1986, it was extended from six months to seven, but I don't remember details. o Effective this year, it goes to eight months, with one of the benefits being an extra hour of light on the evening of Halloween! Isn't that more wanted you wanted to know! If anyone wants a copy of my COMMON pitch (which has not yet been updated for the 2007 change) or COMMON Connect article, please send me private mail. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 "i" comes before "p", "x" and "z" e gads Our system's had more names than Elizabeth Taylor! 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com http://www.as400connection.com "Jeff Crosby" <jlcrosby@dilgard foods.com> To Sent by: "'Midrange Systems Technical midrange-l-bounce Discussion'" s+barsa=barsacons <midrange-l@xxxxxxxxxxxx> ulting.com@midran cc ge.com Subject RE: Time change this weekend. 03/06/2007 08:24 AM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> Jim, After reading information at the link you posted, and following link after link after link after link in typical IBM fashion, I don't really know what is supposed to be done, if anything. (Aside: Does anyone else ever feel like they're going in circles when following IBM support link? I keep thinking the next link will give me that Aha! Experince and I will understand what IBM is trying to say.) Does iNav have a problem with time zones? Is it java within iNav that has a problem? Is it java on PCs period? Is it only if you've written applications in java? Is it IBM supplied 'applications' in iNav that have a problem? Is it something I need to do at each PC that has iNav? If so, why not an iSeries Access service pack? I admit I am totally lost trying to determine what I am supposed to do. -- Jeff Crosby Dilgard Frozen Foods, Inc. P.O. Box 13369 Ft. Wayne, IN 46868-3369 260-422-7531 The opinions expressed are my own and not necessarily the opinion of my company. Unless I say so.
-----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz Sent: Monday, March 05, 2007 4:35 PM To: Midrange Systems Technical Discussion Subject: Re: Time change this weekend. to anyone who has ignored the last few weeks of Daylight Savings postings http://www-03.ibm.com/servers/eserver/iseries/software/globali zation/dst.html No one answered my post this morning so I assume all have either updated iSeries Navigator separately or just don't care if it's understanding of time is unpatched (just because it's a pc doesn't mean the Win fix fixes it) http://www-03.ibm.com/servers/eserver/iseries/access/ jim franz ----- Original Message ----- From: <rob@xxxxxxxxx> To: <midrange-l@xxxxxxxxxxxx> Sent: Monday, March 05, 2007 4:13 PM Subject: Time change this weekend.Enjoy the time change this weekend (some of you). Found out that our plants in Mexico change on a different date. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com -- This is the Midrange Systems Technical Discussion(MIDRANGE-L) mailinglist To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
-- This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
