PK15281: CURRENT_SERVICE_LEVEL IS NOT BEING SET DURING BACKOUT | |||||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description This customer experienced back-level adminconsole code, although the PTF apply seemed fine. During the diagnosis of this problem, it was determined that the customer had performed a backout at one point: but the CURRENT_SYSTEM_LEVEL was not set to reflect the PTF level nor was the webuiapply.marker file erased during the backout. Therefore, the subsequent PTF apply was not updating the adminconsole to the newer PTF level. . The code attempted to create the directory to put the marker file. This directory should contain the CURRENT_SERVICE_LEVEL as part of the path, so it should have something like "W502xxx.ptf" as the last directory in the path. This path is generated at runtime as part of the script running and it uses the value of the CURRENT_SERVICE_LEVEL. But, what was seen in this customer's logs was the following: mkdir: FSUM6404 directory "/<was_home>/DeploymentManager/ properties/service/backup/": EDC5117I File exists. The end of the path does not have "W502xxx.ptf" so the CURRENT_SERVICE_LEVEL is not set to anything. It should be something like .../service/backup/W502xxx.ptf instead. . Furthermore, from the log: wsadmin update has rc of: 0 creating marker file that Backout was OK. rm: FSUM9195 cannot unlink entry "/<was_home>/DeploymentManager/properties/service/backup// webuiapply.marker": EDC5129I No such file or directory. Return code from update of administrative console is: 0 The above error was caused due to the CURRENT_SYSTEM_LEVEL again missing in the path (where the double "//" are located in the aforementioned path, the "W502xxx.ptf" should have been inserted).Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The Administrative console might not * * be at the current service level if * * a PTF service level was backed out and * * subsequent PTFs are later installed. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Administrative console might not be at the current service level if a PTF service level was backed out and subsequent PTFs are later installed. The Post Installer's "backoutPTF.sh" shell script, which is used to back out a PTF, is providing incorrect service level state data to the Adminsitrative console during the back out process. This incorrect state data causes the Administrative console to not get updated when subsequent PTFs are installed.Problem conclusion Correct the backoutPTF.sh shell script to provide the correct service level state data to the Administrative console during a PTF back out. APAR PK15281 is currently targeted for inclusion in SERVICE LEVEL W502039 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK15281.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK15281
IBM Group: Software Group
Modified date: Apr 5, 2006
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.