PQ79157: JNDI NAMES GENERATED BY 390FY API DOES NOT MATCH THOSE PRODUCED BY THE SM-EUI TOOL.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
The 390fy with the old switch -JNDIejbp does NOT use the
<display-name> but it uses ejbJarFile name (minus ".jar"
extension). AND the SM-EUI uses the jar <display-name> but it
drops the ".jar" extention.
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 new option           *
*                      -JNDIejbpb when the EjbJar file's       *
*                      <display-name> ends with ".jar" for     *
*                      WebSphere Application Server V4.01 for  *
*                      zOS and OS/390.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Default JNDI name generated by SMEUI's original JNDI name
creation routine not only uses <display-name> of EjbJar's
ejb-jar.xml, but it also trims the ".jar" extension
from the <display-name>. Therefore, 390fy's new option to
generate SMEUI's original JNDI name via -JNDIejbpb should not
only remove ".jar" extension from wrapper EjbJar's JNDI name,
but should also remove ".jar" characters from its <display-name>
if it ends with it regardless of whether EjbJar's ejb-jar.xml
uses its archive name within its <display-name> or not to make
sure the JNDI generation algorithm works exactly like SMEUI's
original JNDI generation routine.

If ejbJar's <display-name> = "Policy EjbJar" then:
SMEUI = /PLEX1/BBOASR4/PolicyIVP/Policy EjbJar/P...
390fy -JNDIejbpb = /PLEX1/BBOASR4/Policy EjbJar/PolicyIVP/P...
then it looks ok.

But if <display-name> = "PolicyIVP.jar" then:
SMEUI = /PLEX1/BBOASR4/PolicyIVP/PolicyIVP/P...
390fy -JNDIejbpb = /PLEX1/BBOASR4/PolicyIVP.jar/PolicyIVP/P...
and therefore inconsistent.
Problem conclusion
390fy's option, -JNDIejbpb, must be fixed to generate the
original SM EUI's default JNDI name by always trimming ".jar"
extension from <display-name> of its EjbJar module's deployment
descriptor, ejb-jar.xml.

APAR PQ79157 is associated with SERVICE LEVEL W401604 of
WebSphere Application Server version 4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ79157
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-10-02
Closed date 2003-10-22
Last modified date 2003-11-02

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 UQ81361    UP03/10/28 P F310

  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 #: PQ79157
IBM Group: Software Group
Modified date: Nov 2, 2003