|
We are on V3R7 and I think we were on C97042 at the time - this was on 6/18/97. Neil Palmer wrote: > > Jeffrey - just curious, > What OS/400 release are you running and what PTF cum level are you at ? > ...Neil > > Jeffrey M. Carey wrote: > > > > This happened to us too, except it caused a few more problems! Our > > development system was set to 8/23/28 after a IBM hardware update. > > Unfortunately, our CE didn't change it. So the system came up as > > 8/23/28 and we only noticed because every user with a password > > expiration interval other than *NOMAX had expired passwords! After all, > > they hadn't changed them in 31 years! Note that this happened even > > though we hadn't applied any PTF's - so the "inital system date" of > > 8/23/28 is the same even after the Y2K PTF's - when they updated to make > > 28 = 2028, they apparently didn't change the date of 0 = 08/23/28. > > > > We still have the QHST log out there - if you do a DSPLOG these entries > > show up at the END of the log - they are in the future! > > > > Even if your CE immediately changes this date, there will be at least > > one QHST out there - the very first IPL will create one. You can look > > in QSYS for a file like QHST28236A and delete it - that's the future > > log. Definitely do so before 8/23/2028! > > > > Neil Palmer wrote: > > > > > > OK - here's a W.A.G. > > > At some point in time you had service done on your system (maybe the >control > > > panel was replaced) and the first IPL defaulted to the 08/23/28 default >date. > > > This was noticed and corrected. You keep your QHST logs for a while, and > > > have since applied the V3R6 PTF's for Year 2000 support. Now the system > > > thinks this log file is for 2028 instead of 1928, and therefore never >deletes > > > it when cleanup is run. > > -- > ... Neil Palmer AS/400~~~~~ > ... NxTrend Technology -Canada ____________ ___ ~ > ... Markham, Ontario, Canada |OOOOOOOOOO| ________ o|__||= > ... Phone: (905) 731-9000 x238 |__________|_|______|_|______) > ... url:http://www.NxTrend.com oo oo oo oo OOOo=o\ > ... mailto:NPalmer@NxTrend.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > * This is the Midrange System Mailing List! To submit a new message, * > * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * > * this list send email to MAJORDOMO@midrange.com and specify * > * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * > * should be directed to the list owner / operator: david@midrange.com * > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * * should be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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.