Java 6 64-bit fixes since GA
| APAR # | Fullversion | Java6_64.sdk fileset level | Service refresh |
|---|---|---|---|
| IV41153 | pap6460sr13fp2-20130424_01 | 6.0.0.415 | SR13 FP2 |
| IV38128 | pap6460sr13fp1-20130325_01 | 6.0.0.406 | SR13 FP1 |
| IV37595 | pap6460sr13ifx-20130303_02 | 6.0.0.396 | SR13+IV37419 |
| IV30537 | pap6460sr12-20121025_01 | 6.0.0.385 | SR12 |
| IV25564 | pap6460sr11-20120806_01 | 6.0.0.375 | SR11 |
| IV16489 | pap6460sr10fp1-20120321_01 | 6.0.0.345 | SR10 FP1 |
| IV11711 | pap6460sr10-20111208_01 | 6.0.0.325 | SR10 |
| IV11550 | pap6460sr9fp3-20111122_05 | 6.0.0.295 | SR9 FP3 |
| IV02740, IV02220 | pap6460sr9fp2-20110627_03 | 6.0.0.280 | SR9 FP2 |
| IZ95707 | pap6460sr9fp1-20110208_03 | 6.0.0.265 | SR9 FP1 |
| IZ95184 | pap6460sr9ifix-20110211_02 | 6.0.0.255 | SR9+IZ94423 |
| IZ89820 | pap6460sr9-20101125_01 | 6.0.0.250 | SR9 |
| IZ78668 | pap6460sr8fp1-20100624_01 | 6.0.0.215 | SR8 FP1 |
| IZ74891 | pap6460sr8-20100409_01 | 6.0.0.200 | SR8 |
| IZ67338 | pap6460sr7-20091215_02 | 6.0.0.175 | SR7 |
| IZ62671 | pap6460sr6-20090925_01 | 6.0.0.150 | SR6 |
| IZ52818 | pap6460sr5-20090529_04 | 6.0.0.125 | SR5 |
| IZ50167 | pap6460sr4ifx-20090417_02 | 6.0.0.110 | SR4+IZ48590 |
| IZ37674 | pap6460sr3-20081106_07 | 6.0.0.75 | SR 3 |
| IZ30726 | pap6460sr2-20080818_01 | 6.0.0.50 | SR 2 |
| IZ20752 | pap6460sr1-20080419_01 | 6.0.0.25 | SR 1 |
All fixes are available separately from Fix Central by selecting these options:
- Product Group: System p
- Product: AIX
- Version: Select your operating system version
- Fix type: Fix search
Search for fixes using the APAR number shown in the table.
For a list of defects that have been fixed for this Java release, see Java 6 64-bit AIX defect fix list
Are fixes cumulative?
Typically, APARs are not cumulative, because each APAR corresponds to fixes for a subset of Java6_64 filesets. Different APARs can have different subsets of Java6_64 filesets. However, the individual Java6_64 filesets will contain cumulative fixes. Check the version.release.modification.fix (vrmf) number to compare fileset levels. For example, the fixes in fileset 6.0.0.75 contain or supercede the fixes delivered in fileset 6.0.0.50 and below.
How do I know if I have installed the latest code?
There are different ways to determine the level of code on your system:
- You can check and compare the build date of your Java installation by using the command:
/usr/java6_64/jre/bin/java -fullversion - You can check to see if a particular APAR is installed on your system by using the command:
instfix -ivk APAR_NUMBER - You can check the Java6_64 filesets installed on your system by using the command:
lslpp -L | grep Java6_64. The list produced by this command might show filesets that are optional, such as java6_64.samples or java6_64.source. The java6_64.sdk fileset is the only fileset you need.