PQ74384: 390FY -EJBDREFD COULD NOT RESOLVE ALL UNAMBIGUOUS REFERENCES WHEN THE <EJB-LINK> WAS NOT SET. | |||||||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description The 390fy program could not resolve all unambiguous references with the -ejbrefd option when the <ejb-link> information was not set up. It instead issued a BBOY0075Y indicating that it detected an empty ejb-link, hence -ejbrefd cannot be used to automatically resolve this EJB reference. While the 390fy has this limit, SMEUI's "Resolve all unambiguous References" button was able to resolve, marked the LINK column with the check mark, and filled in the JNDI name automatically with Processor EJB's jndiName. 390fy -ejbrefd should resolve all unambiguous references to properly line up with SMEUI's "Resolve all unambiguous References"Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * version 4.0.1 for z/OS and OS/390 * **************************************************************** * PROBLEM DESCRIPTION: 390fy's -ejbrefd does not resolve all * * unambiguous references where as * * SM EUI's "Resolve all unambiguous * * references" does even when <ejb-link> * * information is not present. * * * * In addition, to the reported problem * * APAR PQ74384 also addresses the * * following defect: * * * * (MD17173) JndiNames for ejb references * * and resource references are not * * converted properly using migration * * utility. * **************************************************************** * RECOMMENDATION: * **************************************************************** 390fy's -ejbrefd does not resolve all unambiguous references where as SM EUI's "Resolve all unambiguous references" does even when <ejb-link> information is not present. In addition, to the reported problem APAR PQ74384 also addresses the following defect: (MD17173) JndiNames for ejb references and resource references are not converted properly using migration utility, hence jndi-name assigned to each ejb references and resource references are not retained and user installing migrated ear file onto adminstration console application is required to provide jndi-names all over again.Problem conclusion 390fy's -ejbrefd will now handle resolving all unambiguous ejb-references even if <ejb-link> information is not provided to synchronize with current SM EUI's behavior. APAR PQ74384 provides the additional defect resolution: (MD17173) 390fy tool's meta-data conversion has been updated to handle jndi-names for both ejb references and resource references as well as retaining ID tags in ejb-jar.xml file to maintain a link between ejb-jar.xml and ibm-ejb-jar-bnd.xmi files during migration processing. APAR PQ74384 is associated with SERVICE LEVEL W401508 of WebSphere Application Server version 4.0.1 for z/OS and OS/390.Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
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 #: PQ74384
IBM Group: Software Group
Modified date: Jul 3, 2003
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.