APAR status |
Closed as documentation error.
| Error description
LOCAL FIX:
The product.xml file and the admin console will show the
correct fixpack level but not the OS.
There is no reason for concern that these filesets are of a
new size/date and that the OS does not reflect the new
Fixpack.
.
This is true of all operating systems with WAS ptf
installations. As far as making it so that the ptf install
will adjust OS registry settings.. that is somewhat of a large LOCAL FIX:The product.xml file and the admin console will show thecorrect fixpack level but not the OS.There is no reason for concern that these filesets are of anew size/date and that the OS does not reflect the newFixpack..This is true of all operating systems with WAS ptfinstallations. As far as making it so that the ptf installwill adjust OS registry settings.. that is somewhat of a large Local fix
design decision... and would involve a future architecture
change.
.
This apar is created to have this position documented. Problem summary
The installation program for ptfs are not designed to
touch the OS of the particular platform. It
merely unpacks new files from the zip to the new
fileset.
The OS "registry" of filesets for any platform
therefore will not reflect that the ptf level
is, say, 3.5.2, but rather will stay
at 3.5.0 after ptf 2 install. In order for this
OS piece to be updated, it would involve a
"philosophy" change in how the ptfs
are being installed. Our ptf installations
are fairly uncomplicated and by the most recent
plans will remain so. The xmlconfig file for
WAS and the console will show the version
with the ptf included. There is no cause for
concern that the OS fixpack level does not reflect
fixpack level.
This should be documented in ptf install
release notes.Made request for doc change. Problem conclusion
of ptf install process on updating OS fileset levels. Temporary fixComments
APAR information | APAR number | PQ48085 | Reported component name | WAS ADVANCED AI | Reported component ID | 5648C8400 | Reported release | 350 | Status | CLOSED DOC | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-04-23 | Closed date | 2001-04-26 | Last modified date | 2001-04-26 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|