PQ73311: 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 PQ73311 addresses various problems *
*                      in WebSphere Application Server V4.0.1  *
*                      for z/OS and OS/390.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
APAR PQ73311 addresses the following problems in
WebSphere Application Server V4.0.1 for z/OS and OS/390:

(MD16275) There is a need to improve diagnostics for time outs.
An IPCS command is needed to display relevent times in the flow
of Request from the control region through dispatch in the
server region.  This will aid customers in determining why their
requests have been timed out.

(MD16490) When detailed tracing (TRACEDETAIL or TRACESPECIFIC)
is turned on in the Systems Management (SM) server, periodic
failures of the server occur.  The typical symptoms are that
the failure occurs during application deployment, with the
following message appearing in the SYSPRINT for the SM server:
  BBOU0036W Processing for signal 'SIGABND' (18) with
  abend=00EC3000 rsncode=000C0001 si_code='ABND_REAL'(170)
  si_errno=0 si_addr=00000000 , in current thread
The SM server region takes as many as three SVC dumps (the first
for ABEND IN PC ROUTINE BBO3CTXP), then restarts.
If the deployment is via the SM EUI, the SM EUI connection to
the server fails with message:
   BBON0151E CORBA system exception, server still connected.
After all this, the SM server restarts and normal work can
continue.  The problem will not reoccur until after the next
conversation activation completes, so the failed application
deploy can be redone.

A line of code in bboitrc.h which was gathering information to
put in IM trace entries was causing the failure.  This code was
running whenever ANY detailed tracing was being done - even if
not an IM trace (TRACEDETAIL=(5)), so any detailed trace could
lead to the failure.

(MD16622) A C++ subclass added an attribute to the Object but
did not override the "new/delete" operators of its parents.
When the new attribute is set it reaches beyond the allocated
object storage and causes a storage overlay.  This overlay
caused LE Heap check services to fail (a zero was stored into
the free chain).
Problem conclusion
APAR PQ73311 provides the following problem resolution:

(MD16275) Code has been modified in the ORB_Request (bbooorbr.h)
to gather timestamps for Requests on entry and exit from the
WAS address spaces.  An additional option was added to the
IPCS command, CBDATA, to provide summary information as it
relates to the Request, given a TCB address.  The new
option is "TCB(tcbaddress)". An example invocation is:
"VERBX CBDATA 'ASID(3B) TCB(9DFE88)'".

(MD16490) The line of code in bboitrc.h was removed and the
value it was gathering (Context value) will no longer be
included in the IM detailed trace.

(MD16622) Code has been modified in TimerDaemonThread
(bbootmot.h), subclass of ACR_ExecutionThread (bbooacrt.h), to
implement the operator new(size_t size) and operator
delete(void *elementPtr) methods.  This will ensure that the
correct size of the TimerDaemonThread object is used on its
storage allocation.

The following publication was revised as a result
of APAR PQ73311:
________________________________________________________________
WebSphere Application Server V4.0.1 for z/OS and OS/390
Messages and Diagnosis
GA22-7837-06
________________________________________________________________
This APAR requires 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:


http://www.ibm.com/software/webservers/appserv/zos_os390
/library.html
________________________________________________________________
Appendix A, pg. 456 (append)
ASID(asid-number) TCB(tcb_address)
Formats Request summary information for a task. Displays Request
summary information.
______________________________________________________________

APAR PQ73311 is associated with SERVICE LEVEL W401504 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.
Temporary fix Comments
APAR information
APAR number PQ73311
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Submitted date 2003-04-17
Closed date 2003-04-29
Last modified date 2003-06-05

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 UQ76441    UP03/05/06 P F305

  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 #: PQ73311
IBM Group: Software Group
Modified date: Jun 5, 2003