PQ62857: IN WSCP-XMLCONFIG OPERATION WSCP DID NOT RELAY THE XMLCONFIG EXIT CODE

 Fixes are available

4.0.5: WebSphere Application Server Version 4.0 Fix Pack 5 (Version 4.0.5)
System Management Component Cumulative Fix for 4.0.2/4.0.3/4.0.4 /4.0.5



APAR status
Closed as program error.

Error description
1.When WSCP throws an exception we are getting correct exit code
WSCP0021E: Failed to import configuration from file customer.xml
# echo $?
51
#
2.But we are not getting correct exit code ,When we use WSCP-XM
WSCP-XMLConfig Option
Infocenter 4.X
6.6.0.2.2.4.6: Importing and exporting a configuration by using
XMLConfig.The XML Configuration Management Tool (XMLConfig) can
be invoked from within wscp. The syntax is as follows:

wscp> XMLConfig export file_name [-partial file_name]
wscp> XMLConfig import file_name [-substitute list]
$ $WAS_HOME/bin/wscp.sh -p /mw/websphere/etc/v40.wscp.rc -c "XML
Config import /websphere/samples.xml"

[5/29/02 9:45:59:781 CEST]194a4e DataSourceCon X XMLC0007E: Fail
create DataSource : petstoreDatasourceXMLC0043E:..........
$ echo $?
0
$

3.Here We are getting exception from XMLConfig and WSCP is not
aware of this and giving exit code  0
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All WebSphere Application Server 4.x users.  *
****************************************************************
* PROBLEM DESCRIPTION: When wscp is invoked with XMLConfig     *
*                      option, the return code is always 0.    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Even if earlier fixes to wscp are applied and the system
property, wscp.useNewRetCode, is set, the return code from
wscp, when the -XMLConfig option is used is always 0.  This
statement is not totally correct but is largely correct
because XMLConfig does not throw exceptions to report an
error (in most cases).
Problem conclusion
The code now checks an internal counter for
XMLConfig to see whether or not errors occurred.
Temporary fix
Test fix available on wasdoc0:/apars/PQ62857/4.02
Comments
APAR information
APAR number PQ62857
Reported component name WEBSPHERE AE SO
Reported component ID 5630A2202
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-07-03
Closed date 2002-08-21
Last modified date 2002-08-21

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
WSCP          

SRLS

Fix information
Fixed component name WEBSPHERE AE SO
Fixed component ID 5630A2202

Applicable component levels
R400 PSY    UP


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ62857
IBM Group: Software Group
Modified date: Aug 21, 2002