PQ78454: 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 PQ78454 addresses various defects  *
*                      in WebSphere Application Server V5.0    *
*                      for z/OS.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ78454 addresses the following defects in
WebSphere Application Server V5.0 for z/OS:

(MD17701) In the zSAS Transport config view of the
administrative console,the field AllowUnauthenticated Clients
can not be set to false.

Navigate to: Security-> Authentication Protocol ->
zSAS Transport config view.  The default value is set to true.
However, the box is not checked. The value of the field can not
be set to false from the administrative console.

(MD17713) When trying to modify the Memory to Memory Session
settings through the administrative console a
NullPointerException was thrown.

The exception:

java.lang.NullPointerException
    at com.ibm.ws.console.servermanagement.webcontainer.
PersistenceDetailAction.perform(PersistenceDetailAction.java:218
    at org.apache.struts.action.ActionServlet.

Was thrown when navigating to:Application Servers -> <server> ->
Web Container -> Session Management ->
Distributed Enviroment Settings -> Memory to Memory.

The administrative console was incorrectly checking if the
product was base versus ND and not building the DRS components.

(MD17732) NO_PERMISSION exceptions are returned to z/OS and
non-z/OS clients on InitialContext creation. When
nonauthenticated_clients_allowed=0 for z/OS Server. If the
client is a z/OS WebSphere client the request that will fail
is getProperies request on the WsnNameService object.

The exception occurs because the INS IORs are build by the
client without security tags. This is because the client does
not know which protocols are supported by the server. The z/OS
server was retuning a NO_PERMISSION exception as the response
because it was expecting security information in the request
because nonauthenticated_clients_allowed=0.

(MD17739) After configuring ICSF (Integrated cryptographic
services facility) as the authentication mechanism the control
region fails to start.

In SecurityConfig.setValues(..) in the control block used by
ICSF, a property is set as ICSF then later set as CUSTOM.
ICSF should be maintained as the property.  Additionally,
ICSFServerObject should be calling the static methods for
UserRegistryImpl.checkPWGetOSCred and UserRegistryImpl.validate
otherwise a ClassCastExcpetion will be thrown during admin
console login.

(MD17748) java.lang.NullPointerException seen in
TxEEComponentImpl during startup of DeploymentManager server.

The following stack trace is displayed during the startup of
the DeploymentManager:
java.lang.NullPointerException
 at com.ibm.ws.runtime.component.TxEEComponentImpl.start(TxEECo

The exception results from TxEEComponentImpl being started
before the EJBContainer.  This is a normal condition in the
deployment manager.  The exception does not affect the function
of the deployment manager.

(MD17753) After loging into the administrative console the User
ID shows up as a negative number. User IDs are stored as hashes
on the filesystem for security reasons.  This hash was
accidentially shown to the user as the User ID.

(MD17794) Clicking on Performance Monitoring Service link
(within administrative console) causes 500 error with the
following stacktrace:

java.lang.NullPointerException
  at java.util.StringTokenizer.<init>(StringTokenizer.java(Comp
    iled Code))

The Admin Service within a servant process routes MBean
requests to the Admin Service within the associated controller
process. Previously, if an exception occurred within the
controller Admin Service, the servant Admin Service caught the
exception and hid the fact that an exception was thrown within
the controller Admin Service. The caller of the servant Admin
Service would then erroneously conclude that the operation was
successful and attempt to take action on the return value of
the operation.

(MD17795) The naming code throws a class cast exception while
trying to create a Root Master NC (Naming Context).

The following is a sample of  client side trace showing problem.
 PersistentNam < getMasterRootNC: URL
    corbaname::BOSSXXXX.PLEX1.L2.IBM.COM:9100/NameServiceTreeRoo
 PersistentNam < getMasterRootNC: Could not get master root NC
                          java.lang.ClassCastException

The class cast exception also shows up in the Server traces.

(MD17800) A ClassCastException occurs during a Java
Write-To-Operator if a non-Ws390-type TraceEventListener
registers with the Ws390-type TraceEventGenerator.
Problem conclusion
APAR PQ78454 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD17701) Correction has been made to the actionGen class to set
the values to the right fields of the form object.

(MD17713) Administrative console support was modified such that
the correct check was put in place, and the DRS panels are
viewable.

(MD17732) Code was updated to allow requests on the INS objects
supported by z/OS without requiring security context in the
request.

(MD17739) Support was modified to maintain the ICSF property.
Also, changed the calls to UserRegistryImpl.checkPWGetOSCred(..)
and UserRegistryImpl.validate(..) from ICSFServerObject to use
the static equilvalents.

(MD17748) Code was added to handle the absense of the
EJBContainer during TxEEComponentImpl startup.

(MD17753) Code was added to correctly show the User ID on the
administrative console.

(MD17794) With this fix, the servant Admin Service no longer
hides an exception that occurred within the controller Admin
Service from its caller. The caller of the servant Admin Service
is now made aware that the operation failed.

(MD17795) Support was modified such that the object is narrowed
and cast correctly.

(MD17800) Added type-checking to ensure correct type before
casting.

APAR PQ78454 is associated with SERVICE LEVEL W501000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ78454
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-09-14
Closed date 2003-09-17
Last modified date 2003-10-03

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOCASYD BBOCBYTO BBOCLSAC BBOCLSUR BBODASRP BBODASRS
BBODASRU BBODCFG BBODCFG2 BBODCPYC BBODCPY2 BBODEF
***This field was truncated. To obtain
the full apar record, please contact
your local support center.***    

Publications Referenced

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

Applicable component levels
R500 PSY UQ80303    UP03/09/25 P F309

  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: swg1PQ78454.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 #: PQ78454
IBM Group: Software Group
Modified date: Oct 3, 2003