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

(MD18173) Unable to login to administrative console This problem
happened after deploying a webservice app and restarting the
server. The workspace failed to get the config root from the
ConfigRepository MBean which caused the NPE to be thrown in the
workspace, hence preventing the user from logon to the
administrative console. The servant ConfigRep client should get
the config info directly and not making a jmx on the controller
during server startup since the controller has not been fully
initialized yet and the servant can not contact the controller
at that point.

(MD18186) Customer gets a java exception trying to get the
Caller Identity if security is Enabled. When a customer tries to
get the Caller Identity by calling getCallerIdentity(), if
security is Enabled, the following java exception is thrown:

org.omg.CORBA.BAD_PARAM: com.ibm.ws.security.core.
EJSSecurityCollaborator is not serializable  minor code:
4F4D0006
at com.ibm.rmi.util.Utility.throwNotSerializableForCorba
    (Utility.java:1277)
at com.ibm.rmi.io.IIOPOutputStream.outputClassFields
    (IIOPOutputStream.java:802)
The problem is due to the fact that we're trying to serialize
an object that is not serialized ever.

(MD18201) Support Cloudscape (5.1) Network Server using DB2 JDBC
Universal Driver from within WAS z/OS.

(MD18207) Ant(ws_ant) was running in EBCDIC mode, rather than
ASCII mode.  The WebSphere subtasks however ran in ASCII.

Ant itself was running in EBCDIC mode, rather than ASCII.  The
This only affects the builting ant tasks, such as copy and filte
which tried to read files in EBCDIC, when ASCII was expected.
The WebSphere specific ant tasks are not affected, as they
previously ran in ASCII mode with EBCDIC output.

(MD18210) ClassNotFoundException generated in controller region
when an MBean listener registration occurs within a servant
region in which a NotificationFilter that is not on the
controller region classpath is specified.

Prior to this fix, when the AdminService addNotificationListener
or addNotificationListenerExtended method was invoked within
a servant region with a NotificationFilter specified, the
specified NotificationFilter was loaded into the associated
control region. If the NotificationFilter was not on the
control region classpath, a ClassNotFoundException was
generated for the NotificationFilter:

FunctionName: com.ibm.ws390.management.connector.corba.CorbaConn
              ectorImpl
   SourceId: com.ibm.ws390.management.connector.corba.CorbaConne
             ctorImpl
   Category: ENTRY
   ExtendedMessage: handleException; java.lang.ClassNotFoundExce
   ption: com.ibm.ws.console.appdeployment.ApplicationDeployment
   CollectionAction

(MD18214) Instructions for BBODIAPP show incorrect messages to
look for to verify successful completion.

Dialog generated instruction BBOCCINS, for the step BBODIAPP,
it shows incorrect messages to look for to verify successful
completion.

(MD18220) BBOSSINS instructions, step 8 is repetetive.

Dialog generated instruction BBOSSINS step #8 has the
following statement:

If an existing version of WebSphere for z/OS is in your system
LPA or linklist, OR if you choose to not put WebSphere for
z/OS V5 in the system LPA or linklist, proceed as follows:

Load the BBORTSS5 member of the following data set into the
system LPA. This member is version-specific and MUST be present
in the LPA.

&BBOLPA.

And then a few paragraphs down, it seems to repeat the same
thing:

If you already have a version of WebSphere for z/OS in LPA or
the linklist, load the BBORTSS5 member into LPA using the
SETPROG LPA command issued from the MVS console or from a
COMMNDxx parmlib member:

SETPROG LPA,ADD,MODNAME=BBORTSS5,
           DSNAME=&BBOLPA.

This is confusing.

(MD18235) Client side wsadmin failures from security set sec
 $AdminConfig getid /Cell:$cell
/Security:/
ASX7017E: Exception received while
running file "/WebSphere/V5R0M0/
AppServer/util/petstoreConfig.jacl";
exception information: com.ibm.bsf.
BSFException: error
while evaluatig Jacl expression:
com.ibm.ws.scripting.ScriptingException:
com.ibm.websphere.management.exception.
ConfigDocumentLoadException: ADMG0003E:
Failed to load document cells/SY1/
security.xml.

---- Begin backtrace for nested exception
java.lang.NullPointerException
at com.ibm.ws.security.auth.ContextManagerImpl.getUnauthentica
   tedCredential(ContextManagerImpl.java:304)
Problem occurs when attempting to retrieve the server identity
from security code running in the client. Since there is no
server identity, we are attempting to retrieve the
unauthenticated identity.

In the client side the principalname is not important,
but we get a null pointer exception using the SecConfig object,
which is not created for a Client.
Problem conclusion
APAR PQ81151 fixes various defects in WebSphere Application
Server V5.0 for z/OS.

(MD18173)  Code has been added to allow the
ServantConfigRepClient to invoke certain ConfigRep operations
locally without accessing the actual mbean thru jmx.This is
needed for the workspace code in order to access the config
information. The new changes will only allow ConfigRep read-only
operations to be invoked from the servant process and when the
zOSInitComplete is not true.

(MD18186) The problem occurs because the getCallerIdentity
method in com.ibm.ws.security.core.SecurityCollaborator is
creating an anonymous inner class implementation of the abstract
java.security.Identity class.  When the Identity class is
returned to the client, all it's outer classes are serialized
as well and these classes are not serializable. The fix is to
provide a concrete implementation of Identity.

(MD18201) Support Cloudscape (5.1) Network Server Using DB2 JDBC
Universal Driver from within WAS z/OS.

****************************************************************

Defect MD18201, shipped in Cumulative Fix W502000, requires the
following documentation change:

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:

www.ibm.com/software/webservers/appserv/zos_os390/library.html
________________________________________________________________

The changes are to rdat_minreq.html and also to
tdat_cloudscape_setup.html.

rdat_minreq.html now includes a note which reads:
Datasources defined under the DB2 for z/OS Local JDBC
Provider (RRS), must not be accessed from within the same JVM
as datasources defined under any of the JDBC providers using
the DB2 (version 8) Universal JDBC Driver. This means that
the datasources must not be used from within the same server,
and that similar considerations must be taken for client
datasource usage.
In particular, datasources defined under the Cloudscape
(5.1) Network Server Using Universal JDBC Driver Provider must
not be used from the same server as datasources defined under
the DB2 for z/OS Local JDBC Provider (RRS).
The reason for this restriction is that the DB2 Universal
JDBC Driver uses the same package and class names
(com.ibm.db2.jcc.DB2ConnectionPoolDataSource)
as the DB2 for z/OS Local JDBC Provider (RRS). To understand
this design, consider that the DB2 Universal JDBC Driver is
the DB2 V8-level replacement for the DB2 V7-level JDBC driver
used by the DB2 for z/OS Local JDBC Provider (RRS).

tdat_cloudscape_setup.html now includes a note which reads:
Datasources defined under the DB2 for z/OS Local JDBC
Provider (RRS), must not be accessed from within the same
JVM as datasources defined under any of the JDBC providers
using the DB2 (version 8) Universal JDBC Driver. This means
that the datasources must not be used from within the same
server, and that similar considerations must be taken for
client datasource usage.
In particular, datasources defined under the Cloudscape
(5.1) Network Server Using Universal JDBC Driver Provider
must not be used from the same server as datasources defined
under the DB2 for z/OS Local JDBC Provider (RRS).
The reason for this restriction is that the DB2 Universal
JDBC Driver uses the same package and class names
(com.ibm.db2.jcc.DB2ConnectionPoolDataSource)
as the DB2 for z/OS Local JDBC Provider (RRS). To understand
this design, consider that the DB2 Universal JDBC Driver is
the DB2 V8-level replacement for the DB2 V7-level JDBC
driver used by the DB2 for z/OS Local JDBC Provider (RRS).

(MD18207) The shell script ws_ant was modified to allow ant to
run as expected in ASCII mode.

****************************************************************

Defect MD18207, shipped in Cumulative Fix W502000, requires the
following documentation change:

NOTE: Periodically, we refresh the documentation on our
Web site, so the changes might have been made before you
read this text. To access the latest on-line
documentation, go to the product library page at:

www.ibm.com/software/webservers/appserv/zos_os390/library.html
________________________________________________________________

The change is to filename rovr_antapi.html entitled Ant
tasks which now includes a paragraph that reads:
When building a BufferedReader to read information from
Standard in (System.in) on z/OS, you need to take into account
character encoding:

WebSphere Distributed
 BufferedReader stdin = new BufferedReader(new
 InputStreamReader(System.in));

WebSphere for z/OS
 String encoding = System.getProperty("ws.input.encoding");
 BufferedReader stdin = new BufferedReader(new
 InputStreamReader(System.in, encoding));

(MD18210) With this fix, when the AdminService
addNotificationListener or addNotificationListenerExtended
method is invoked within a servant region with a
NotificationFilter specified, the specified NotificationFilter
is no longer loaded into the associated controller region.

(MD18214) Dialog skeleton BBOCCINS will be update to show the
correct messages to verify for successful completion for the
BBODIAPP step.

(MD18220) For text in question, dialog skeleton BBOSSINS will
be update to read as follow:

If an existing version of WebSphere for z/OS is in your system
LPA or linklist, OR if you choose to not put WebSphere for
z/OS V5 in the system LPA or linklist, proceed as follows:

Load the BBORTSS5 member of the data set

&BBOLPA.

into the system LPA using the SETPROG LPA command issued from
the MVS console or from a COMMNDxx parmlib member:

 SETPROG LPA,ADD,MODNAME=BBORTSS5,
           DSNAME=&BBOLPA.

(MD18235) Support has been modified to ensure that
getUnauthenticated Client call can handle a client environment
in which no SecurityConfig object exists.

APAR PQ81151 is associated with SERVICE LEVEL W502000 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PQ81151
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-11-19
Closed date 2003-12-07
Last modified date 2004-01-03

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOALLOC BBOBOA BBOCBRAC BBOCCFMT BBOCCINJ BBOCCINS
BBOCCTF BBOCCTT BBOCEIOP BBOCENCP BBOCGIOP BBOCHS
***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 UQ82902    UP03/12/15 P F312

  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: swg1PQ81151.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 #: PQ81151
IBM Group: Software Group
Modified date: Jan 3, 2004