PQ71508: 390fy utility for applications that use multiple DB2 subsystems.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
390fy default mappings for resref are not usable when connecting
to multiple DB2 subsystems.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: During server initialization, EJBs      *
*                      containing <env-entry> deployment       *
*                      descriptor without its optional         *
*                      <env-entry-value> field creates         *
*                      NullPointerException during java:comp   *
*                      namespace initialization with this      *
*                      EnvEntry without its EnvEntryValue      *
*                      specified.                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
During server initialization, more specifically, during EJB's
deployment descriptor initialization, EJBs that contain
<env-entry> with <env-entry-value> value set to null or not set
at all will cause EJB container to generate NullPointerException
specifically during java:comp namespace initialization using
missing env-entry-value. Since <env-entry-value> is an optional
item during application assembly phase but is a required item
during deployment, direct deployment tool should provide options
to allow modifications to <env-entry-value> field during deploy.
Problem conclusion
Support has been added for putting an ability into the direct
deployment tool to allow <env-entry-value> update.

A separate document, entitled "WebSphere Application Server
V4.0.1 for z/OS: Direct Deployment Tool/390fy," is available
for this APAR. To download the document, go to the following Web
site, then click "Product information."


http://www.ibm.com/software/webservers/appserv/zos_os390/
support.html

At a later time, the information in this document will be
integrated into the WebSphere for z/OS formal
publications.  To access the latest publications, go to
the product library page at:


http://www.ibm.com/software/webservers/appserv/zos_os390/
library.html

APAR PQ71508 is associated with SERVICE LEVEL W401502 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ71508
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-02-27
Closed date 2003-03-21
Last modified date 2003-04-03

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ75293    UP03/03/29 P F303

  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 #: PQ71508
IBM Group: Software Group
Modified date: Apr 3, 2003