PQ75404: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V5.0 FOR Z/OS.

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V5.0 for z/OS.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ75404 addresses various defects  *
*                      in WebSphere Application Server V5.0    *
*                      for z/OS.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ75404 addresses the following defects in
WebSphere Application Server V5.0 for z/OS:

(MD17154) When a WebSphere V5.0 for z/OS Daemon starts, it
looks for the WebSphere V4.0.1 BGVT which it has to have to
anchor the pointer to the .* estae extension that LE will
look for.  If it doesn't exist, it creates one.  There is also
a cpool that the 4.01 daemon assumes is created if the BGVT is
there, so the WebSphere V5.0 Daemon goes ahead  and creates that
too, just in case we start a 4.01 config. The cell pool is 100
cells of 8K each.

(MD17160) Remote non-WAS Server fails with UNKNOWN/MARSHAL
exception and details about being unable to demarshal value from
stream. A message about sending runtime context being
unavailable or missing m,ay also be seen.

These issues are seen because beause marshalling objects by
value is subject to problems if the classes used for
marshalling/demarshalling are different between the
sender/receiver. CORBA protocols specify an optional service
context, SendingContextRuntime, that contains an IOR for a
special object that the message recipient can call back to in
order to retrieve additional information about the marshalled
value type in order to demarshal it.

(MD17184) The following page references should be removed
from administrative console as they are not supported:
1) "IBM Service Logs' from the JMS Server
   additional properties page
2) "Number of threads" field on the JMS
   Native Process page

(MD17190) On the administrative console, the JMS Native Process
Page shows the following field labeled incorrectly. "Server
Short Name <text field> Short name of JMS Server." The field
displays the name of the JMS queue manager and not the server
short name and hence needs to be changed to "JMS Queue Manager
<text field> Name of JMS Queue Manager."

(MD17190.1) Administrative console is missing JMS server short
name due to missing property name in the server.xml.  WebSphere
dialog needs to change jms server short name property from
"was.shortname" to "was.shortName" in jms server stanza in
server.xml.

(MD17192) Incorrect message (could.not.stop.server) was issued
on the administrative console when selecting the immediateStop
button even though the server did stop.

(MD17196) An incorrect error message is displayed when an
exception is thrown running with Java 2 Security Enabled. User
should Ignore a message that starts with "CAUGHT Java Security
EXCEPTION in zOS" and advices you to open a defect against the
WAS.Security component.

(MD17229) Synchronization of updates from the Deployment
Manager to the Node Agent fails with SSL handshake
errors: unknown certificate when security is enabled.
Problem conclusion
APAR PQ75404 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD17154) Support has been modified to use 1 cell for the
primary extent and then 100 cells for the secondary.  This will
reduce the overhead if an installation never starts WebSphere
V4.0.1 but leave the pool there and ready to go if needed.

(MD17160) SendingContextRuntime service context has been added
in the APAR.

(MD17184) In the administrative console, page references have be
removed for:

1) "IBM Service Logs' from the JMS Server
   additional properties page
2) "Number of threads" field on the JMS
   Native Process page

(MD17190) The text changes were made to the plugin.nlsprops file
to correctly display field "JMS Queue Manager <text field> Name
of JMS Queue Manager." on the JMS Native Process Page.

(MD17190.1) Dialog was modified to change the "jms server
stanza" skeleton file (BBOWJMST) from "was.shortname" to
"was.shortName".

(MD17192) Support was modified to correctly emit the nodeagent
processStopped correctly.

(MD17196) The erroneous message which advices the user to
to open a defect against the WAS.Security component has been
removed.

(MD17229) Support was added to synchronize keystores
and RACF Keyrings.

APAR PQ75404 is associated with SERVICE LEVEL W500101 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ75404
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 2003-06-18
Closed date 2003-06-18
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
BBOUBINF          

Publications Referenced

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

Applicable component levels
R500 PSY UQ77804    UP03/06/25 P F306

  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: swg1PQ75404.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 #: PQ75404
IBM Group: Software Group
Modified date: Aug 6, 2003