PQ94334: ADDNODE UTILITY RETURNS WITHOUT INDICATING ERROR (RETURN CODE ZERO).

 Fixes are available

5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for AIX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Windows
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for HP-UX
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Solaris
5.1.1.6: WebSphere Application Server Version 5.1.1 Cumulative Fix 6
5.1.1.7: WebSphere Application Server Version 5.1.1 Cumulative Fix 7
5.1.1.4: WebSphere Application Server Version 5.1.1 Cumulative Fix 4
5.1.1.8: WebSphere Application Server 5.1.1 Cumulative Fix 8 for Linux
6.0.1: WebSphere Application Server Version 6.0 Refresh Pack 1



APAR status
Closed as program error.

Error description
AddNode utility returns without indicating error (return code
zero). However, the related logs indicate that errors/exceptions
occurred. Reporting of problem via error codes is incorrect.

The result of this is that if the Customer does not review the
logs, then they may continue operation without knowing that
addnode had actually failed. This would be of particular note
should set-up be undertaken programmatically.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: This problem affects customers who use the   *
*                 addNode script provided with WebSphere       *
*                 Application Server (Network Deploy) Version  *
*                 5.x and 60. Also, MQ systems on OS/400.      *
****************************************************************
* PROBLEM DESCRIPTION: Exception catch statement blocks did    *
*                      not update method return code. Thus     *
*                      propagation of incorrect return code    *
*                      would result in user observing zero     *
*                      return code from execution, whilst      *
*                      logs indicated errors.                  *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Upon handling an exception, the method return code was not
updated correctly in all feasible paths. Thus it was possible
for program to (incorrectly) complete with zero return code,
whilst errors are reported in logs.
Problem conclusion
Minor alterations required to source trees for various releases
to ensure that return codes are correctly updated. Simplified
logical flow through methods to assist program analysis; added
debug statement blocks to assist future servicing of product.
Temporary fix Comments
APAR information
APAR number PQ94334
Reported component name WAS NETWRK DEPL
Reported component ID 5630A3601
Reported release 00A
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2004-09-16
Closed date 2004-10-06
Last modified date 2004-10-06

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
MSGING          

Publications Referenced

Fix information

Applicable component levels
R003 PSY    UP
R00A PSY    UP
R00H PSY    UP
R00I PSY    UP
R00P PSY    UP
R00S PSY    UP
R00W PSY    UP
R103 PSY    UP
R10A PSY    UP
R10H PSY    UP
R10I PSY    UP
R10P PSY    UP
R10S PSY    UP
R10W PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 00A
Software edition:
Reference #: PQ94334
IBM Group: Software Group
Modified date: Oct 6, 2004