DST

[bxmakin]

We are on AIX 5.3 with ML 03. Really do not want to upgrade to ML 04 or 05 to accomodate the Daylight Savings Fix. In any case I checked if I already had the APAR that deals with this problem. Here is what I got:

#instfix -iak IY75211
IY75211 Abstract: Daylight Saving Time default changing in 2007
IY75211 Symptom Text:
DayLight savings change for year 2007 and beyond
----------------------------
All filesets for IY75211 were found

It seems like we are OK but if I check the IBM site they mention that you have to be at ML level 04 to be able to recieve this APAR. I am bit confused. Perhaps the guy who installed our machine last year in March was able to get this APAR for ML 03. I just want be sure that it will works for us. Are we OK? Any input?

Thanks,

BX

 

[DukeSSD]

I had a play on fix central and it won't let you download the apar and stay at ML03, when you take off the ML03 restriction it downloads the following:

Fileset name Protocol Info file Byte count
bos.adt.prof.5.3.0.40 HTTP FTP Info 8776704
bos.adt.syscalls.5.3.0.40 HTTP FTP Info 45056
bos.alt_disk_install.rte.5.3.0.40 HTTP FTP Info 505856
bos.mp.5.3.0.40 HTTP FTP Info 6467584
bos.mp64.5.3.0.40 HTTP FTP Info 7394304
bos.net.tcp.client.5.3.0.40 HTTP FTP Info 16750592
bos.perf.diag_tool.5.3.0.40 HTTP FTP Info 10240
bos.perf.perfstat.5.3.0.40 HTTP FTP Info 116736
bos.perf.tools.5.3.0.40 HTTP FTP Info 4366336
bos.perf.tune.5.3.0.40 HTTP FTP Info 556032
bos.rte.boot.5.3.0.40 HTTP FTP Info 176128
bos.rte.bosinst.5.3.0.40 HTTP FTP Info 254976
bos.rte.console.5.3.0.40 HTTP FTP Info 78848
bos.rte.control.5.3.0.40 HTTP FTP Info 1275904
bos.rte.filesystem.5.3.0.40 HTTP FTP Info 4000768
bos.rte.install.5.3.0.40 HTTP FTP Info 3328000
bos.rte.libc.5.3.0.40 HTTP FTP Info 6913024
bos.rte.serv_aid.5.3.0.40 HTTP FTP Info 427008
bos.rte.tty.5.3.0.40 HTTP FTP Info 612352
bos.sysmgt.nim.client.5.3.0.40 HTTP FTP Info 1025024
bos.sysmgt.nim.master.5.3.0.40 HTTP FTP Info 1192960
bos.sysmgt.serv_aid.5.3.0.40 HTTP FTP Info 3495936
bos.sysmgt.sysbr.5.3.0.40 HTTP FTP Info 1174528
devices.chrp.base.rte.5.3.0.40 HTTP FTP Info 1148928
devices.chrp.pci.rte.5.3.0.40 HTTP FTP Info 138240
devices.chrp.vdevice.rte.5.3.0.40 HTTP FTP Info 70656
devices.tty.rte.5.3.0.40 HTTP FTP Info 5120
devices.vdevice.hvterm-protocol.rte.5.3.0.40 HTTP FTP Info 5120
devices.vdevice.hvterm1.rte.5.3.0.40 HTTP FTP Info 78848
perfagent.tools.5.3.0.40 HTTP FTP Info 11823104

All ML04 filesets. So you cannot "Stay" at ML03 and have te apar because you need ML04 filesets installed to have the fix.

So if you have the apar then you have most of ML04 but there must be a few bits missing to fully qualify as being at ML04, hence instfix and oslevel -r will still show ML03.

If you have the apar then it "should" work for you, even though you have some unrelated ML04 filesets missing.

instfix -i | grep ML
will tell where you are,
instfix -icq | grep ":-:"
will tell you what you are missing for the next ML

 

[p5wizard]

oslevel command can be used also:
oslevel -r (probably shows 5300-03)
oslevel -qr (probably lists 5300-04 also)
so
oslevel -lr 5300-04
shows the filesets which are at a too low level to qualify your AIX for full 5300-04

If you have a test server at the same level and you can play around with the date/time setting on that server, you can see what would happen at the StandardTime/DST time changeover point.


HTH,

p5wizard

 

[bxmakin]

Unfortunately I do not have a server at the same level to test. The alternative is to manually set the DST by changing the /etc/environment file according to:

http://www14.software.ibm.com/webapp/set2/sas/f/enews/2006/10/DSTupdate.html

I guess my question is if I make a manual change as an insurance and have the APAR, would that cause a conflict.

Thanks,

BX

 

[p5wizard]

No that would not conflict. E.g. if your TZ says EST5DST, you need the fix as of this year but if your TZ says EST5EDT,M3.2.0,M11.1.0 then the changeover points are defined in that string, and the begin/end of DST adhere to those values, fix installed or not.

I've been using these kind of TZ strings since way back when, never had any issue with this. Only thing is after you change a TZ in /etc/environment, you need to reboot your server for the change to become effective for all system processes (especially cron).


HTH,

p5wizard

 

[bxmakin]

Thanks p5wizard.

 

[plamb]

try oslevel -s probally says 5300-03-SP?