PQ57189: THIS APAR ADDRESSES DEFECTS IN WEBSPHERE APPLICATION SERVER V4.0.1 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.1 for z/OS and OS/390.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390.                  *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ57189 addresses various problems *
*                      in WebSphere Application Server V4.0.1  *
*                      for z/OS and OS/390.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ57189 addresses the following problems in
WebSphere Application Server V4.0.1 for z/OS and OS/390:

(MD12183) When running a C++ client under the WebServer with
the WebServer environment configured to a non-IBM-1047 code
page, a CORBA::Internal exception is raised from bboocds.cpp in
IBM_name_to_OSF() with a minor code of C9C2119D. Client code
pages other than IBM-1047 are not supported for C++ clients.
However, for processing from a Java client, for example, one
running under the WebServer, the code page of the process is
not relevant.  Therefore, the code page processing done in
building the GIOP messages should not be subject to the
limitations imposed on C++ clients.  Simply put, the code which
generates the exception should be skipped in these cases.

(MD12442.03) The "WebSphere for z/OS Customization" Dialog
provides support which generates the necessary jobs and
instructions for customers migrating from WebSphere for z/OS 4.0
to WebSphere for z/OS 4.0.1. Translation of migration related
panels into Japanese needs to be done.

(MD12604) When a Control Region is terminating an attempt to
queue work to that Control Region may take an
ABENDDC3/ABENDSDC3-04160015 attempting to Resume a worker thread
that is no longer there. When the worker threads go away, the
pause elements they use when waiting for work also go away.
An attempt in bboowork.plx to resume this thread will fail.
Since this is normally a problem, we abend and dump, however in
CTL termination it is normal and should not result in a dump.

(MD12747) A conversation can not be validated after a J2EE
server instance is deleted. If the System Management End User
Interface (Administration and Operations applications) also
known as the SM EUI is used to delete a J2EE server instance
that has a J2EE resource instance defined on it, the SM EUI
will report that the conversation is not valid when the user
attempts to validate it.  This occurs because the code in
Ism_Conversation::ValidateModel() does not check the SM dialog
token for datasources (i.e., J2EE resources), J2EE components,
J2EE server instances, and datasource instances to determine
whether these objects have been flagged for deletion.

(MD12770) Several problems were encountered in the base IDLJ
support. IORs have grown, and we again ran into problems trying
to read and manipulate Object keys that contained one or more
stringified IORs during locate processing. This particular
scenario is common with Interface Repository interactions.
Symptom: COMM_FAILURE with minor code: C9C21149 in the Server
Region, with BBOU0072E RV=-1, RC=1120, RSN=00000000 and
BBOU0051E Internal communications error: REASON=C9C20C55 in the
Control Region. Differing endian in request and response. Our
previous IDLJ implementation had added some processing to cache
the codeset negotiated for the request for use when reading the
response. We included the endian in this cached encoding
information, however, the response is not required to be in the
same endian as the request, which means we essentially drop the
endian encoding information as we pass the buffer from C++
(where we know the endian of the response) to Java (where we
assume the same endian as the request). Some problems were
encountered when our SHASTA implementation was asked to create
an IDLJ stub.
Symptom: java.lang.NoSuchMethodError: <init> and
org.omg.CORBA.BAD_OPERATION.

(MD12801) After a context switch failure, if the Server Region
is allowed to stay up, the application work may become involved
in the wrong unit of recovery.

(MD12889) When a synchronization object that is registered with
a transaction throws an exception during beforeCompletion, the
transaction manager will handle that exception by marking the
transaction for rollback only. Currently, the exception and the
failing synchronization object are not traced.  This can make it
very difficult to determine why a transaction was marked for
rollback only.  An event level trace should be provided to
simplify problem determination.

(MD12932) Support for the com.ibm.CORBA.iiop.noLocalCopies JVM
property needs to be provided in WebSphere Application Server
V4.0.1 for z/OS and OS/390. The specification of this JVM
property will determine whether objects passed between
enterprise beans running in the same JVM are passed by reference
instead of by value.

The com.ibm.CORBA.iiop.noLocalCopies JVM property is specified
as:
    com.ibm.CORBA.iiop.noLocalCopies=string

By default, objects are passed by value.  If you specify any
non-null value for the variable "string," objects will be
passed by reference.

      RECOMMENDATION: Use "true" as the assignment for
      com.ibm.CORBA.iiop.noLocalCopies, which
      is consistent with WebSphere on distributed
      platforms.
Problem conclusion
APAR PQ57189 provides the following problem resolution:

(MD12183) Support was added to recognize the requests which flow
from Java clients to modify their processing with respect to
code page negotiation to ignore the native code set for the
space as it is not relevant.

(MD12442.03) Translation of "WebSphere for z/OS Customization"
Dialog migration related panels into Japanese has been provided
in this APAR.

(M12604) Modify bboowork.plx to detect stale Pause Element Token
(PET) failures on resume and if the target CTL region is
terminating, do not abend/dump for the problem.

(MD12747) Code in Ism_Conversation::ValidateModel() was modified
to check the SM dialog token for datasource, J2EE component,
J2EE server instance, and datasource instance objects.  If the
dialog token for one of these object types indicates that it is
flagged for deletion, the object is not considered in the
validation process.

(MD12770) Function was added to allow handling of arbitrarily
large objectkeys (as long as entire message is within defined
limit).

A change was made to the processing of inbound response to
handle potentially different endian encoding than used for
request. Traces have been added to display what encoding is
being used to read a message.

Changes were made to accommodate creation of IDLJ stubs
within SHASTA. All IR-related stubs converted to IDLJ stubs for
interop. Because the JDK provides an _IDLTypeStub, we are forced
to make all of our IR-related stubs (in the base org.omg.CORBA
package)into IDLJ stubs to avoid marshalling problems. This is
directly related to inheritance issues, and should not cause a
problem for customers using idlc generated stubs.

(MD12081) Code has been added to issue an ABENDEC3 (ABEND EC3)
with a new reason code of x'090D0003' (RSN=090D0003) when a
failure is detected in switching the RRS Context Token
(CTXSWCH).  This will cause the Server Region or Control Region
to terminate.

(MD12889) An event level trace entry has been provided that
displays the synchronization object that raised an exception and
the exception that was thrown.

(MD12932) The APAR provides support for the
com.ibm.CORBA.iiop.noLocalCopies JVM property.

The following publication was revised as a result
of APAR PQ57189:
________________________________________________________________

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:


http://www.ibm.com/software/webservers/appserv/
________________________________________________________________
________________________________________________________________

WebSphere Application Server V4.0.1 for z/OS and OS/390
Messages and Diagnosis
GA22-7837-02
________________________________________________________________
Chapter 13, pg. 385 (new message)

C9C21265
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center
________________________________________________________________
Chapter 13, pg. 385 (new message)

C9C21266
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center
________________________________________________________________
Chapter 13, pg. 385 (new message)

C9C21267
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center
________________________________________________________________
Chapter 13, pg. 385 (new message)

C9C21268
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center
________________________________________________________________
Chapter 13, pg. 385 (new message)

C9C21269
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center
________________________________________________________________
Chapter 13, pg. 385 (new message)

C9C2126A
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center
________________________________________________________________
Chapter 13, pg. 385 (new message)

C9C2126C
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center
________________________________________________________________
Chapter 13, pg. 385 (new message)

C9C2126D
Explanation: IBM Internal Only
User Response: Contact the IBM Support Center
________________________________________________________________
Chapter 13, pg. 538 (new message)
EC3 090D0003
Explanation: A non-zero return code was received from the RRS
Context Service CTXSWCH which was issued by the
RRSContext::Switch routine. The RRS Context Services return
code is in register 0 at the time of the abend.  The address
of the RRS Context Token involved is in register 2 at the time
of the abend.
User Response: Use the RRS Context Services return code to
determine the cause of the failure.
________________________________________________________________
________________________________________________________________

  Document Name: WebSphere Application Server V4.0.1 for
                 z/OS and OS/390:
                 Assembling Java(tm) 2 Platform, Enterprise
                 Edition (J2EE(tm)) Applications
  Document Number: SA22-7836-02

  Update Table 14 on page 240 with the following rows:

  +---------------------------------+----------+----------+
  | JVM PROPERTY=<DEFAULT>          | J2EE     | MOFW     |
  |                                 | SERVER   | SERVER   |
  |                                 | INSTANCE | INSTANCE |
  +---------------------------------+----------+----------+
  | com.ibm.CORBA.iiop.noLocalCopies| O        |          |
  | =                               |          |          |
  +---------------------------------+----------+----------+
  | org.omg.CORBA.ORBInitialHost =  | O        | O        |
  | RESOLVE_IPNAME                  |          |          |
  +---------------------------------+----------+----------+
  | org.omg.CORBA.ORBInitialPort =  | O        | O        |
  | 900                             |          |          |
  +---------------------------------+----------+----------+

  Also on page 240, add the following JVM property
  descriptions:

  com.ibm.CORBA.iiop.noLocalCopies=string
      Determines whether objects passed between enterprise
      beans running in the same JVM are passed by reference
      instead of by value.

      By default, objects are passed by value.  If you
      specify any non-null value for the variable "string,"
      objects will be passed by reference.

      RECOMMENDATION: Use "true" as the assignment, which
      is consistent with WebSphere on distributed
      platforms.

      ATTENTION!  Passing objects by reference allows the
      caller to observe changes made to parameters by the
      called method.  Though passing objects by reference
      results in a significant performance improvement, it
      is at the cost of removing data integrity safeguards.
      Use this option with extreme caution.

      EXAMPLE:

        com.ibm.CORBA.iiop.noLocalCopies=true

  org.omg.CORBA.ORBInitialHost=host_name
      The Internet Protocol name that a z/OS or OS/390
      client, or server region acting as a client, uses to
      access the bootstrap server (that is, when the client
      or server region invokes the
      resolve_initial_references method). The default is
      the value specified by the RESOLVE_IPNAME environment
      variable, which is the Internet Protocol name
      associated with the System Management Server (the
      default bootstrap server).  If RESOLVE_IPNAME is not
      set, the value is the system on which the client or
      server region is running.

      Use this property to specify a bootstrap server
      running on a remote system.

      NOTE:  The TCP/IP port number for
      org.omg.CORBA.ORBInitialHost is defined by
      org.omg.CORBA.ORBInitialPort.

      The value of org.omg.CORBA.ORBInitialHost can be up
      to 255 characters.

      EXAMPLE:

        org.omg.CORBA.ORBInitialHost=MYHOST.COM

  org.omg.CORBA.ORBInitialPort=host_port
      Specifies the TCP/IP port number for the host name
      specified on org.omg.CORBA.ORBInitialHost.  Use this
      property to specify a bootstrap server running on a
      remote system.

      The default is 900.

      EXAMPLE:

        org.omg.CORBA.ORBInitialPort=1900

APAR PQ57189 is associated with SERVICE LEVEL W401019 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ57189
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2002-01-28
Closed date 2002-02-10
Last modified date 2002-03-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 BBOAPRMI BBOAPXLI
BBOAXCEI BBOAXIAI BBOBOA BBOCASYD BBOCASYH BBOCEIOP
BBOCLSAC BBOCLSCC BBOCLSES BBOCLSPC BBOCLSSA BBOCLSUE
BBOCLSUR BBOCORBA BBOCPOCB BBOCSESS BBODASRC BBODASRF
BBODASRP BBODASRQ BBODASRS BBODASRU BBODBGVT BBODDAUT
BBODSDRG BBODSREG BBOFDBM BBOFDKB BBOFI01S BBOFI02S
BBOFI03S BBOFI04S BBOFI05S BBOFI06S BBOFI07S BBOFI08S
BBOFRAS BBOIBOIM BBOIBOI2 BBOIDRMI BBOIGTID BBOIIMA
BBOIIMC BBOIIMF BBOIIMS BBOIKEYS BBOINJPN BBOIPOOL
BBOIRDB BBOITLS BBOI3PLI BBOJJU BBOLRAS BBOLRT
BBOLRTU BBOLSREQ BBOLSS BBOLSYS BBOMDDLI BBOMDDLO
BBOMDDLV BBOMDDLX BBOMDDLZ BBOMGSCO BBOMIBO BBOMICP
BBOMIDO BBOMIJPN BBOMIMEX BBOMIMG BBOMIMO BBOMIPK
BBOMR BBOMRBO BBOMRDO BBOMRMO BBOMRPK BBOMSBO2
BBOMSCO BBOMSCOX BBOMSCP BBOMSCR BBOMSDO BBOMSMO
BBOMSPK BBOMUTIL BBOOACRT BBOOBIND BBOOBOAI BBOOBOAM
BBOOBOAT BBOOCOMM BBOOCRHT BBOOCSIT BBOOCSM BBOOCVN
BBOODCTX BBOOEJSB BBOOEQGQ BBOOGSCO BBOOIREQ BBOOJORB
BBOOOLTI BBOOOPIP BBOOOPIX BBOOORB BBOOORBP BBOOORBR
BBOOORBX BBOOOUTP BBOOPCCR BBOORB BBOORCTX BBOORDTA
BBOOREQ BBOOSBND BBOOSBOA BBOOSCHD BBOOSMF BBOOSMFC
BBOOSMFP BBOOSMFT BBOOSRAB BBOOSRBF BBOOSRM BBOOSRQA
BBOOSRQF BBOOSRR BBOOSRWT BBOOSSMF BBOOSSNQ BBOOSSRR
BBOOSSTP BBOOSUBD BBOOSWRK BBOOTMOT BBOOTMTM BBOOTRD
BBOOTTIP BBOOTTIX BBOOWORK BBOPBO BBOPCBS BBOPCH
BBOPCO BBOPDO BBOPMO BBOPPK BBORABND BBORADMP
BBORARM BBORDEQ BBORENQ BBOREXIT BBORFRES BBORFRR
BBORGETS BBORJLOG BBORJTR BBORJTRC BBORJWTO BBORLEXT
BBORMCDP BBORMCDX BBOROBML BBOROBMS BBOROMDL BBOROSMD
BBOROTTI BBORPTRC BBORRMC BBORRMGR BBORSDMP BBORSLOG
BBORTDF1 BBORTIME BBORTRCD BBORTSRB BBOSEXT BBOSICI
BBOSLAD BBOSLCL BBOSLDO BBOSLHM BBOSLLO BBOSLMC
BBOSLMO BBOSLPK BBOSLRA BBOSLRL BBOSLSO BBOSLUT
BBOSLXL BBOSM BBOSNCN BBOSNCO BBOSNDO BBOSNLN
BBOSNMO BBOSNPK BBOSNS ***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
R401 PSY UQ62691    UP02/02/16 P F202

  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 #: PQ57189
IBM Group: Software Group
Modified date: Mar 2, 2002