PQ55519: $LDAP ERROR CODE 32 NO SUCH OBJECT 'IBM-WSNNAME=DOMAIN'

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
During communucation from a distributed client to WebSphereV4
on OS/390 exception
javax.naming.NameNotFoundException: @LDAP: error code 32
No Such Object remaining name 'ibm-wsnName=domain'
is thrown when trying to create a new InitialContext object with
the following code:
        h.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,
  "com.ibm.websphere.naming.WsnInitialContextFactory");
        h.put(Context.PROVIDER_URL, "iiop://<IPAddress>:900");
         Context ctx = new InitialContext(h);
The searching for "ibm-wsnname=domain" part of the name space
is due to a mismatch between the Advanced Edition (distributed)
name space and WebSphere for OS/390 name space. In the
distributed name space there exists an alias called "domain"
that points to the "legacyRoot" piece of the name space which
exists in the name spaces for distributed as well as z/OS.
What doesn't exist in the z/OS name space is the alias called
"domain".
Local fix
There is a work around. In the following code you have:
       h.put(javax.naming.Context.INITIAL_CONTEXT_FACTORY,
 "com.ibm.websphere.naming.WsnInitialContextFactory");
       h.put(Context.PROVIDER_URL, "iiop://<IPAddress>:900");
       Context ctx = new InitialContext(h);
 .
where you are specifying properties
javax.naming.Context.INITIAL_CONTEXT_FACTORY and
Context.PROVIDER_URL.
Specify one more property
com.ibm.websphere.naming.namespaceroot
and give it a value of bootstraphostroot, i.e.:
  h.put("com.ibm.websphere.naming.namespaceroot",
  "bootstraphostroot");
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390.                  *
****************************************************************
* PROBLEM DESCRIPTION: Differences in WebSphere Advanced       *
*                      Edition and WebSphere Application       *
*                      Server V4.0.1 for z/OS and OS/390 JNDI  *
*                      JNDI tree structure result in           *
*                      intermediate context 'domain' not found *
*                      exceptions.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When issuing InitialContext from a java client
on NT and correctly filling in
javax.naming.Context.INITIAL_CONTEXT_FACTORY and
javax.naming.Context.PROVIDER_URL, and including the jar
file that WebSphere Application Server
V4.0.1 for z/OS and OS/390 provides as a sample for distributed
java clients, WebSphere Advance Edition clients attempting to
access a WebSphere 390 LDAP name space get the following
exception:

javax.naming.NameNotFoundException:  LDAP: error code 32 -
No Such Object remaining name 'ibm-wsnName=domain'

"domain" is not part of the WebSphere 390 name space, but is
part of WebSphere Advanced Edition's name space. "domain" in the
WebSphere Advanced Edition's name space is just an alias to the
"legacyRoot" part of the name space, which is in both WebSphere
Advanced Edition's and the WebSphere 390 name space.  Even
though "domain" points to "legacyRoot" in the WebSphere
390 name space, the lack of having "domain" alias physically in
the WebSphere 390 name space causes the lookup to fail.
Problem conclusion
This APAR introduces an alias into the WebSphere 390 LDAP name
space which defines the context 'domain', allowing WebSphere
Advance Edition client programs to access the WebSphere 390
domain.

APAR PQ55519 is associated with SERVICE LEVEL W401024 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ55519
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-12-06
Closed date 2002-02-20
Last modified date 2002-08-28

APAR is sysrouted FROM one or more of the following:

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

Modules/Macros
BBOJTREE BBOUBINF BBOWSLPD BBOZ0664 BBOZ0812 BBOZ0813
BBOZ0982 BBOZ0983        

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R401 PSY UQ62966    UP02/03/12 P F203

  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 #: PQ55519
IBM Group: Software Group
Modified date: Aug 28, 2002