PK71393: ADMINAPP.GETDEPLOYSTATUS() SHOWS INCORRECT RESULT ON EXPANSION FAILURE.

Fixes are available

APAR status

Closed as program error.

Error description

WebSphere z/OS, AdminApp.getDeployStatus() shows incorrect
result on expansion failure.
..
The following is a brief explanation on the AppExpansion
and getDeployStatus behavior, which will be helpful
for me to explain the cause for the failing scenario.
..

AppExpansion:
---------------------------------------------------------
During Sync, if an application file is identified as
updated/added/removed, then it will
create "<appname>.marker" file, once the expansion is
completed, successfully it will delete the
"<appname>.marker" file

if app expansion fails, it will be logged in the
marker file.
-------------------------------------------------------
getDeployStatus:
 ---------------------------------------------------------
 on the Node getDeployStatus will set the "expansion"
 attribute based on  the existence and  contents of
 the .marker file
 1) if marker file is normal set expansion=inprogres
 2) if it contains error message , will set
    expansion=error
 3) if the file doesn't exists set
    expansion= notprocessing

 Based on the expansion attribute it will set the
 "distribution" attribute,
 1) for #1 and #2 it will set distribution=false,
 2) incase expansion= notprocessing, it will compare
    the application file contents of the Dmgr and
    Node config repositories, if both are synchronized
    distribution attribute will be set as true; else
    false.
-----------------------------------------------------------
In customers' failing scenario, even if app
expansion fails the marker file having the error was
deleted, hence expansion attribute was set as "notprocessing"
and since the config repositories (Dmgr and Node) were
synchronized successfully,  distribution attribute ws set
as "true".
During marker file check it says
---------------------------------------------------------
Trace: 2008/06/24 20:35:03.350 01 t=8BAB58 c=UNK key=P2
   ThreadId: 00000017
   FunctionName: com.ibm.ws.management.component.
   AdminOperationsMBean
   SourceId: com.ibm.ws.management.component.
   AdminOperationsMBean
   Category: FINEST
   ExtendedMessage: marker name:
/was/wasconf/STF2WAQ/WAQNDE21/AppServer/profiles/
default/wstemp/appsync/
TestApp8.marker
 Trace: 2008/06/24 20:35:03.350 01 t=8BAB58 c=UNK key=P2 (
   ThreadId: 00000017
   FunctionName: com.ibm.ws.management.component.
   AdminOperationsMBean
   SourceId: com.ibm.ws.management.component.
    AdminOperationsMBean
   Category: FINEST
   ExtendedMessage:  marker file doesnt exist
   calling J2CApp
-------------------------------------------------------------
If we resolve the scenario that deletes the marker file, the
getDeployStatus() issue will get resolved, automatically.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of WebSphere Application Server   *
*                  V6.0.1 for z/OS                             *
****************************************************************
* PROBLEM DESCRIPTION: AdminApp.getDeployStatus() was          *
*                      showing incorrect  status for failed    *
*                      application expansion.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The application expansion status on the Node can be queried
using wsadmin command AdminApp.getDeployStatus() and JMX API
AppManagementProxy.getDistributionStatus(); the query will
return the status as string,
'WebSphere:cell=mycell,node=mynode,distribution=true,expansion=n
otprocessing'.
In the above string ?distribution? flag will have the value
?true?, if the application expansion was completed
successfully,it will have ?false?, otherwise. In Network
Deployment environments, sometimes the distribution flag was
set to ?true? even though the application expansion failed for
some reasons.

In Network Deployment environments application expansion is an
asynchronous operation, a marker file will be created, before
starting the application expansion process and the same will
be deleted on successful completion. Incase the expansion
failed the marker file will be updated to indicate the failure.
During distribution status query, if the marker exists the
distribution flag will be set to  ?false? and based on the
content of the marker file expansion flag will be set to
?inprogress? or ?failed?.

The marker file will be deleted in a cleanup call; the cleanup
call will be invoked during garbage collection, as well. In
the failing scenarios, initially, the marker file was updated
to indicate the failure; but, later in the cleanup call from
garbage collection it assumes that expansion was completed
successfully and deletes the marker file, which caused the
distribution query to return a incorrect status.

Problem conclusion

Since the marker file is the key to decide on application
expansion status, the fix refined the marker file
manipulation, ensuring that it is not deleted for failed
application expansions.

APAR PK71393 currently targeted for inclusion in Service
Level (Fix Pack) 6.0.2.33 of WebSphere Application Server V6.0.1
for z/OS.

Please refer to URL:
//www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
for Fix Pack availability.

Temporary fix

Comments

APAR Information

APAR number
PK71393
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
601
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-09-02
Closed date
2008-11-18
Last modified date
2009-03-16

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

PK80110 PK82639

Fix information

Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500

Applicable component levels

R601 PSY UK43592
UP09/02/11 P F902

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.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.0.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021

Tips

PK71393: ADMINAPP.GETDEPLOYSTATUS() SHOWS INCORRECT RESULT ON EXPANSION FAILURE.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R601 PSY UK43592

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

Share your feedback

Need support?