PQ72277: NOT GIVING A VALID SERVER NAME WHEN RUNNING BBOWCUPD, CAUSES MISLEADING MESSAGES TO BE PRINTED IN THE SYSOUT.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
When running BBOWCUPD, if an invalid server name is given as
an argument, the sysout gives no indication that any error has
happened.  Instead, it appears very close to normal, and even
prints out the message:
   "Return code from Commit Conversation is: 0"
This gives the user the illusion, that the job ran successfully,
and that RemoteWebContainer has been successfully redeployed.
Local fix
If BOTH of the following messages are NOT printed out, then it
is likely that, while the job may have run successfully, the
RemoteWebContainer application was not redeployed:
 "Returncode from Replace Web Container on server X is: 0"
  ...
 "Returncode from Commit Conversation is: 0"
Where X is the name of the SERVER that you specified when
starting BBOWCUPD.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 version 4.0.1 for z/OS and OS/390.           *
****************************************************************
* PROBLEM DESCRIPTION: Not giving a valid Server Name when     *
*                      running BBOWCUPD job, cause misleading  *
*                      messages to be printed in the SYSOUT.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When running BBOWCUPD, if an invalid server name is given as
an argument, the sysout gives no indication that any error has
happened.  Instead, it appears very close to normal, and even
prints out the message:
"Return code from Commit Conversation is: 0"
This gives the user the illusion, that the job ran successfully,
and that RemoteWebContainer has been successfully redeployed.
Problem conclusion
The following error message will be issued when an invalid
Server Name is given as an argument for the BBOWCUPD job.

"Server X is not a valid J2EE Server.", where X is the input
Server Name.

APAR PQ72277 is associated with SERVICE LEVEL W401510 of
WebSphere Application Server version 4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ72277
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-03-20
Closed date 2003-07-29
Last modified date 2003-08-06

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJSSMI03          

Fix information
Fixed component name WEBSPHERE OS/39
Fixed component ID 5655A9800

Applicable component levels
R401 PSY UQ78989    UP03/08/01 P F307

  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


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ72277
IBM Group: Software Group
Modified date: Aug 6, 2003