PK05901: WEBSPHERE APPLICATION IS WRITTEN TO THE HFS STRUCTURE TWICE AFTER A SUCCESSFUL DEPLOYMENT OR UPDATE

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Customer deploys or updates an application.  After a successful
deploy or update the EAR file is successfully unpacked and
stored in the HFS ( .../installedApps) directory.  However, a
few minutes later, the EAR file gets stored in the HFS
installedApps directory again.  What happened is that the
application's marker file (.../wstemp/appsync/<applname>.marker)
is not being processed as expected.  It looks like the marker
file gets created with a length of 1.  After the sync occurs,
the marker file is deleted, then a new one is created with a
length of 9 (which normally denotes an error).  Because that
marker file is there, the application is being written to the
HFS again (possibly during the next synchronization).
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: After a successful application update,  *
*                      the application files are written a     *
*                      second time to the installedApps        *
*                      subdirectory.                           *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When an application is updated, the updated files are re-written
to the installedApps subdirectory when the next node sync occurs
on a WebSphere ND cell.   There is no need for this second write
since the application has already been expanded.  After the
second expansion, no further expansions occur.

The second expansion has the effect of overwriting any manual
changes made to the installed application files by the user.
Problem conclusion
The application processing was modified to not recreate the
application marker file when performing an application update.

APAR PK05901 is associated with SERVICE LEVEL W502030 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK05901
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-05-17
Closed date 2005-05-23
Last modified date 2005-06-02

APAR is sysrouted FROM one or more of the following:
PK05379

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UK03726    UP05/05/28 P F505

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Current web document: swg1PK05901.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 #: PK05901
IBM Group: Software Group
Modified date: Jun 2, 2005