PQ47185: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0 FOR Z/OS AND OS/390.

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
This APAR addresses defects in WebSphere Application Server
V4.0 for z/OS and OS/390.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390.                    *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ47185 addresses various problems *
*                      in WebSphere Application Server V4.0    *
*                      for z/OS and OS/390.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ47185 addresses the following
problems in WebSphere Application Server
V4.0 for z/OS and OS/390:

If checkJavaException(env) is called with a NULL env pointer
a SIGSEGV and a dump are produced with no indication of what
caused the dump or the SIGSEGV.

ABENDEC3 Reason 09020001 can occur when issuing messages before
initialization complete in an unauthorized space. When
issuing a message, usually to indicate a problem, before
the MVS object is initialized, message processing tries to
initialize the object.  However, doing this may result in an
attempt to anchor a bacb off the assb.  If the problem we are
reporting is that the space is not sufficiently authorized, we
will abend trying to do something that requires authorization
as we try to tell you we aren't authorized properly.

When a stateful bean is activated, its db2 record must be
deleted (destructive read). This is necessary so that proper
stateful session semantics can be ensured by the server. A case
where this is necessary is the case where a server containing a
stateful session  bean abnormally terminates and then gets
restarted.  The direct IOR (which means we had an activate once
policy in effect) causes control to flow  back to the same
server, only the state of the stateful session bean has been
lost.  This is not correct. Similar cases exist when only the
server region abnormally terminates. This applies to activate
once (i.e. passivation "on cache full") stateful sessions only.

SystemException with minor code C9C2110F can be received after a
long delay when an ORB_Request (bbooorbr.cpp) is queued to WLM
with Temporal Affinity.  The target server region was in the
process of terminating.  The queued request was never selected
by the terminating server region.  An ORB recovery routine
eventually responding back to the client
(ORB_Request_Registry::cleanupWLM_Q_AlarmPopped, bbooorrg.h)
with a CORBA::SystemException with a minor code of C9C2110F
(RAS_MINOR_ORB_ORRG_EXCEPT_WLM_POP, bboocrd.h).

Object files in the following list of DLLs are currently created
with nocsect names:

BBOPLC BBOPLHI BBOPLS BBOPLSJ BBOPLSJI BBOMPEC BBOMPES
BBOMAPIC BBOMAPIS

These DLLs need to be deleted and recreated with object files
containing csect names so that they are serviceable.

There exists a requirement of suppying values for the
following properties: java.naming.security.principal and
java.naming.security.credentials in the jvm.properties files
for Systems Management and first J2EE Servers. This requirement
should be removed.

Although the initial configuration enables both userid password
and userid passticket for all system servers, there is no
security preference associated with passticket. Therefore the
settings as they are displayed in the Systems Management EUI are
incomplete. There is no known error situation that relates to
this inconsistency.

Using lowercase field names in the J2EE resource instance
definitions in the Administration GUI causes runtime exceptions.

When a J2EE Application that has a resource reference gets
deployed a second time, and during this deployment the resource
reference is resolved to a different J2EE Resource, then there
is a second J2EE Resource connection object created for the
bean. The code that creates these connection objects should
first delete the list of existing ones before adding new ones.

The job that performs migration of the xml file that was
generated with WebSphere Application Server Enterprise Edition
OS/390 Component Broker Version 3.02. Prepare For Coldstart to
WebSphere Application Server V4.0 for z/OS and OS/390 bootstrap
input fails to migrate all of the server instances for System
Management, Naming and Interface Repository. There is a problem
in the way the migration job used the XML Parser API and
therefore loses every second server instance of runtime servers
like System Managament, Naming and Interface Repository.

Many pieces of information needed to be duplicated between
the WebSphere environment files and the jvm.properties files in
order for the server to run properly. The fact that there was
duplicate data, means that the data could get out of sync and
cause a failure. A mechanism where environment variables from
WebSphere Application Server environment file are made
available to Java WebSphere runtime needs to be provided.
Problem conclusion
-In checkJavaException(env)a test on the env pointer before
the pointer is used  to see if it NULL and if the env
pointer is NULL an RAS_ASSERT2 is performed with a minor code
"RAS_MINOR_SHASTA_InternalError" which indicates that
a SHASTA internal error has occured.  The RAS_ASSERT2 also
indicates that the env pointer is NULL.
-Message processing requiring the MVS object to find the system
name in the CVT has been changed to not use the MVS object to
find the CVT.
-Stateful Session beans are now removed from the backing store
after successful activation. If the Server is stopped normally
all Stateful Session beans are now passivated.
-Code has been added to re-queue the request without WLM
Temporal Affinity if the target server region terminates prior
to selecting the queued request.  This may allow the request
to be sucessfully dispatched (depending on the state of the
target Bean) in another server region.
-DLLs BBOPLC, BBOPLHI, BBOPLS, BBOPLSJ, BBOPLSJI
BBOMPEC, BBOMPES, BBOMAPIC, BBOMAPIS, will be deleted and
recreated with named object files so that they are serviceable.
-Code has been added to remove the requirement of suppying
values for the following properties:
java.naming.security.principal and
java.naming.security.credentials in the jvm.properties files
for Systems Management and first J2EE Servers. It also removes
these properties from the LDAP boot object returned from
resolve_initial_references. The customer who encountered the
problem had different principal and credentials for LDAP
than the LDAP boot object supplied and they were unable to
get their EJB's registered in the LDAP server. The failing
messages would be:
BBOU0652E NAMING REGISTRATION FAILED FOR SERVER xxxxxxxx
where xxxxxxxx is the server name that an EJB application
was deployed in. The java.naming.security.principal and
java.naming.security.credentials properties now have to be in
the Systems Management Server current.env only.

-The creation of the LDAP upper tree structure was moved from
the startup of the first J2EE server to the WebSphere bootstrap
process. The following properties:java.naming.security.principal
java.naming.security.credentials are now only required in the
Systems Management Server current.env. They are put there during
bootstrap process from the initial.env
-The initial configuration xml file has been changed to security
preference associated with passticket.
Since the initial configuration xml file has been changed, the
fix is available whenever an initial bootstrap is performed.
-Code has been added to translate lowercase field names to
uppercase for J2EE resource instance definitions.
-The code that creates connection objects has been changed to
first delete tje list of existing objects before adding new
ones.
-The migration job which proceses the xml file that is generated
with WebSphere Application Server Enterprise Edition OS/390
Component Broker Version 3.02 Prepare For Coldstart to WebSphere
Application Server V4.0 for z/OS and OS/390 bootstrap has be
corrected to migrate all of the server instances for System
Management, Naming and Interface Repository.
-The runtime function that obtains property information for the
WebSphere java runtime will now optionally look in the
WebSphere environment files associated with a server in order
to obtain information. Once obtained the information is then
cached in the jvm to reduce the performance overhead of
obtaining this information.
-If the information remains located in the jvm.properties file
this would be used first. The customer can then move all IBM
supplied properties to the environment file, with the exception
of the following properties which are needed for the jvm to
properly start.
 1) com.ibm.ws390.trace.settings
 2) java.naming.factory.url.pkgs
 3) java.naming.factory.initial
-The jvm.properties file is now intended for customer use,
they may store property information in this file which can be
obtained via the SYSTEM.getProperty("property") method on the
system object.
---------------------------------------------------------------
APAR PQ47185 results in the following changes to documentation:
 NOTE:  Periodically, we refresh the documentation on our
 Web site, so the changes might have been made before you
 read this text.  To access the latest on-line
 documentation, go to the product library page at:
  www.ibm.com/software/webservers/appserv/
 The following document must change:
  Document Name: WebSphere Application Server V4.0 for z/OS
                 and OS/390 Installation and Customization
  Document Number: GA22-7834-00
 In Chapter 3, "Steps for modifying the configuration.env
 file," table on page 91 and 92, add these rows:

  +---------------------------+---------------------------+
  | com.ibm.ws.naming.ldap.   | <ibm-wsnTree=t1,o=<org>,  |
  | containerdn=dn            | c=<country>>              |
  +---------------------------+---------------------------+
  | By default, the system expects the value to be        |
  | ibm-wsnTree=t1,o=WASNaming,c=us.If you take the       |
  | default, delete this environment variable.  If you've |
  | modified the organization or country in your          |
  | bboldif.cb file, use the same value on this           |
  | environment variable.                                 |
  +---------------------------+---------------------------+
  | com.ibm.ws.naming.ldap.   | <domain name>             |
  | domainname=               |                           |
  +---------------------------+---------------------------+
  | By default, the system expects the value to be the    |
  | domain name of the sysplex on which Naming Server is  |
  | running. If you want the default, delete this         |
  | environment variable. If you want a different domain  |
  | name, specify it.                                     |
  +---------------------------+---------------------------+
  | java.naming.security.     | <password>                |
  | credentials=password      |                           |
  +---------------------------+---------------------------+
  | The password must match the password defined for the  |
  | administrator access ID (default is WASAdmin) by the  |
  | LDAP initialization file (bboldif.cb).                |
  +---------------------------+---------------------------+
  | java.naming.security.     | <userid>                  |
  | principal=dn              |                           |
  +---------------------------+---------------------------+
  | The distinguished name must match the one defined for |
  | the administrator access ID (default is WASAdmin) by  |
  | the LDAP LDIF file (bboldif.cb).                      |
  +-------------------------------------------------------+
  In "Steps for preparing and starting phase 1 of the
  bootstrap from your console" on page 93 and 94, add this
  step after step 1:

  2.  If the LDAP server is not running, start it. EXAMPLE:

        S BBOLDAP

  In "Appendix A. Environment files," table on page 341:

  o   Delete the row containing
      java.naming.factory.initial.

  o   Change the optional designation for
      java.naming.security.credentials and
      java.naming.security.principal from the Naming Server
      to the System Management server.

  Also in Appendix A, change the descriptions of the
  following environment variables to read:

  com.ibm.ws.naming.ldap.containerdn=
      ibm-wsnTree=t1,o=org,c=country
      The starting point of WsnName tree. Only the Naming
      server uses this environment variable. By default,
      the system expects the value to be "
      ibm-wsnTree=t1,o=WASNaming,c=us". If you take the
      default, delete this environment variable from your
      environment file.

      This value must match the value specified in LDAP
      initialization file (our sample is bboldif.cb).  If
      you've modified the organization or country in your
      bboldif.cb file, use the same value on this
      environment variable. Note that case does not matter
      in LDAP, though it does matter for the environment
      variables. The "o=,c=" portion must also be specified
      as a suffix in bboslapd.conf. For example:

        suffix   "o=WASNaming,c=us"

      TIP:  The suffix statement appears as:

        suffix         "<ws_rdn>"

      in the sample bboslapd.conf we ship.

      EXAMPLE:

        com.ibm.ws.naming.ldap.containerdn=
        ibm-wsnTree=t1,o=WASNaming,c=us

  com.ibm.ws.naming.ldap.domainname= domain name
      Uniquely identifies the host root and is the basis
      for partitioning the JNDI global name space. Only the
      Naming server uses this environment variable.  By
      default, the system expects the value to be the
      domain name of the sysplex on which Naming Server is
      running. If you want the default, delete this
      environment variable from the environment file. If
      you want a different domain name, specify it. The
      default is the sysplex name.  EXAMPLE:

        com.ibm.ws.naming.ldap.domainname=plex1

  com.ibm.ws.naming.ldap.masterurl= LDAP://IP_name:  port
      The LDAP Server IP Name and port number. Only the
      Naming server uses this environment variable. By
      default, the system expects the IP name to be the
      same as the system on which the Naming Server runs
      and the port to be 1389. If your LDAP server is
      running on a system other then the one the Naming
      Server runs on or uses a port other than 1389, update
      this environment variable.  Otherwise, delete this
      environment variable.  EXAMPLE:

        com.ibm.ws.naming.ldap.masterurl=ldap://wsldap:1389

  java.naming.security.credentials=password
      The password used by the distinguished name specified
      by java.naming.security.principal.  The password must
      match the password defined for the administrator
      access ID (default is WASAdmin) by the LDAP
      initialization file during initial system
      customization. IBM provides the WASAdmin access ID in
      a sample LDIF file called bboldif.cb. The default
      value is "secret".  EXAMPLE:

        java.naming.security.credentials=secret

      RECOMMENDATION: You should change the IBM-supplied
      password.

  java.naming.security.principal=distinguished_name
      Distinguished name (user ID) defined to have write
      access to WsnName directory. Specify this only if you
      want to provide read/write access to all JNDI users.
      The distinguished name must match the one defined for
      the administrator access ID (default is WASAdmin) by
      the LDAP LDIF file during initial system
      customization. IBM provides the WASAdmin access ID in
      a sample LDAP initialization file called bboldif.cb.
      The default value is "cn=WASAdmin,o=WASNaming,c=us ".
      EXAMPLE:

        java.naming.security.principal=
        cn=WASAdmin,o=WASNaming,c=us

      RECOMMENDATION: We suggest you keep the WASAdmin
      access ID.

APAR PQ47185 is associated with SERVICE LEVEL W400007 of
WebSphere Application Server V4.0 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ47185
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2001-03-21
Closed date 2001-04-12
Last modified date 2001-05-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOAPCEI BBOAPCWI BBOAPIAI BBOAPIOI BBOAPXLI BBOAXCEI
BBOAXIAI BBOBOA BBOCEIOP BBOCPOCB BBOCSESS BBOCSMRS
BBOCSSES BBODASR BBODASRR BBODDAUT BBOFAPPS BBOFDBC
BBOIAPPS BBOIBTO BBOIDRMI BBOIGTID BBOIHCOI BBOIHDOI
BBOIIMAI BBOIIMLI BBOIKEYS BBOILEI BBOILOCK BBOILPCI
BBOILPI BBOILSEI BBOILSMI BBOIMOI BBOIMORI BBOIRDBI
BBOIROOT BBOIRSCN BBOISOI BBOISTOR BBOITMLI BBOI3PLI
BBOJBOUI BBOJBOUS BBOJJU BBOJSBDA BBOLRT BBOLSREQ
BBOLSS BBOMAPPS BBOMBOOT BBOMCDM BBOMDDLO BBOMGADM
BBOMIB02 BBOMIB04 BBOMIB06 BBOMIB10 BBOMIB15 BBOMIB19
BBOMIB23 BBOMIB27 BBOMIB33 BBOMIB37 BBOMIB41 BBOMIB45
BBOMIB48 BBOMIB58 BBOMIB62 BBOMIB64 BBOMIB66 BBOMIB68
BBOMIB70 BBOMIB80 BBOMIB81 BBOMIB82 BBOMIB83 BBOMIB84
BBOMIB85 BBOMIB86 BBOMID33 BBOMID82 BBOMIEVA BBOMIMRI
BBOMSBOI BBOMSBO1 BBOMSBO2 BBOMSBO3 BBOMSBO4 BBOMSBO5
BBOMSBO6 BBOMSBO7 BBOMSBO8 BBOMSCO BBOMSCSR BBOMSYSI
BBOMUTIL BBOOBOAI BBOOBOAT BBOOBOKC BBOOCOMM BBOOCRHT
BBOOCSIT BBOOCSM BBOOEJSB BBOOGCOD BBOOGSVD BBOOGTID
BBOOIMPR BBOOIREQ BBOOOBJ BBOOOPI BBOOORB BBOOORBP
BBOOORBR BBOOORBX BBOOORRG BBOOORSA BBOOORSF BBOOOUTP
BBOOPDGI BBOORB BBOOREQ BBOORIRI BBOOROBJ BBOOSMFT
BBOOSMOI BBOOSMOS BBOOSRQA BBOOSRR BBOOSRWT BBOOTCLN
BBOOTMOT BBOOTMQ BBOOTMTR BBOOTRD BBOOTTI BBOOWCSR
BBOPAPPS BBOPBOI BBOPBSC BBORCARM BBOREXIT BBORLOG
BBORTBUF BBORTO BBOSEXSI BBOSLAPP BBOSLHMI BBOSNAPP
BBOSNFED BBOSNNSJ BBOSQAPP BBOSQRDB BBOSQXKI BBOSSCOB
BBOSSC1I BBOSSC2I BBOSSDMA BBOSSECM BBOSSESS BBOSSIOR
BBOSSKMA BBOSSKUT BBOSSOUT BBOSSRIB BBOSTMI BBOSTOI
BBOSTXI BBOTAPPS BBOTCOLB BBOTIF BBOTLRAC BBOTRI
BBOTRIS BBOTRRM BBOTSRM BBOTSUR BBOTSUW BBOTSUWD
BBOTTBCU BBOTTCN BBOTTCR BBOTTCU BBOTTF BBOTTIDF
BBOTTJCU BBOTTLS BBOTTM BBOTTMCI BBOTTMCR BBOTTMM
BBOTTMSR BBOTTRC BBOTTRS BBOTTSCU BBOTTSR BBOTTSVC
BBOTTSYI BBOTTTR BBOTTZZZ BBOUBINF BBOZ0227 BBOZ0229
BBOZ0266 BBOZ0267 BBOZ02 ***This field was
truncated. To obtain the full apar
record, please contact your local support
center.***          

Fix information
Fixed component name WASKBASE
Fixed component ID 5655A9801

Applicable component levels
R400 PSY UQ53185    UP01/04/20 P F104

  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: 400
Software edition:
Reference #: PQ47185
IBM Group: Software Group
Modified date: May 2, 2001