PQ73910: DEFAULT JNDI NAME FOR 390FY -JNDIEJBP SHOULD BE IDENTICAL TO THEDEFAULT JNDI NAME GENERATED IN THE SMEUI.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
The default JNDI name for 390fy -JNDIejbp is supposed to be
identical to the default JNDI name generated in the SMEUI.
  Currently, SM EUI uses the 'display name' as application name
while 390fy, however, uses the file name of the ear file (minus
the .ear suffix). Thus, when the file name of the ear file is
not the display name, the default JNDI name for 390fy -JNDIejbp
is different to the default JNDI name generated in the SMEUI.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 version 4.0.1 for z/OS and OS/390            *
****************************************************************
* PROBLEM DESCRIPTION: Default JNDI name is different between  *
*                      SM EUI and 390fy's -JNDIejbp option for *
*                      WebSphere Application Server V4.01 for  *
*                      zOS and OS/390.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The default JNDI name assignment for 390fy -JNDIejbp should
have been identical to the default JNDI name generated in the
SM EUI. Currently, SM EUI uses the <display-name> of
application's application.xml and <display-name> of ejbJar's
ejb-jar.xml, while 390fy uses HFS safe earfile name (minus
".ear" extension) and ejbJarFile name (minus ".jar" extension).
Hence, customers who are using both SM EUI as well as 390fy
(through SM Scripting API) to install their application based on
default JNDI assignment experience constant deregistration and
registration of their EJBs when the same application is
installed using SM EUI and then SM Scripting API and vice versa.
Problem conclusion
New option, -JNDIejbpb, will be provided under current Direct
Deployment Tool, 390fy, to generate original SM EUI's default
JNDI name. Also, SM EUI will be updated to provide both the
original default JNDI name generator as well as new default JNDI
name that correspond to 390fy's current -JNDIejbp option.

APAR PQ73910 is associated with SERVICE LEVEL W401508 of
WebSphere Application Server version 4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ73910
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-05-06
Closed date 2003-06-25
Last modified date 2003-07-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 UQ77997    UP03/06/28 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


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