PK11507: SECURITY COMPONENT TRACEPOINT 0E012049 CONTAINS INCORRECT TRACE ELEMENT

 A fix is available

Obtain the fix for this APAR



APAR status
Closed as program error.

Error description
Trace point 0E012049 contains incorrect use of the
macro to print the method name and results in incorrect
data in the trace entry:
.
Trace: yyyy/mm/dd (time) 01 t=(tcb) c=UNK key=S2 (0E012049)
  Description: Successful Exit from ->
                             SecurityManager::secureSocketInit
  Connect Protocol: TLSV1
  Connect Cipher: 0A
  Socket Handle: 682050392
  29310e00       <--- incorrect hex code instead of method
                        name secure_socket_init
.
Depending on what the storage points to, it could cause the
server to abend if TRACEDETAIL includes the security component
tracing, E , i.e. TRACEDETAIL=E or ras_trace_detail=E
Local fix
If trace detail is needed for the security component, enable
the trace but also exclude this one tracepoint.
.
through modify commands to enable dynamically, set
TRACEDETAIL=E
along with
TRACE_EXCLUDE_SPECIFIC=0E012049
.
or with custom properties / environment variables, set
ras_trace_detail=E
along with
ras_trace_exclude_specific=0E012049
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V5.0 for z/OS                                *
****************************************************************
* PROBLEM DESCRIPTION: TRACEDETAIL set for tracing security    *
*                      module (E) occasionally caused an       *
*                      ABEND in the server.                    *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
A call to the WebSphere trace API was coded in such a way that
an internal error could occur in the call under certain
unpredictable circumstances.  The internal error resulted in
a dump.  Tracepoints which are affected include:
ras_trace_specific=0E012047, 0E012049 and 0E012057.
Problem conclusion
The call to the WebSphere trace API was modified so that the
data parameters were wrappered with a macro definition that
forced the data to conform to the API specification.

APAR PK11507 is associated with SERVICE LEVEL W502034 of
WebSphere Application Server V5.0 for z/OS.
Temporary fix Comments
APAR information
APAR number PK11507
Reported component name WEBSPHERE FOR Z
Reported component ID 5655I3500
Reported release 500
Status CLOSED PER
PE NoPE
HIPER NoHIPER
Special Attention NoSpecatt
Submitted date 2005-09-07
Closed date 2005-09-28
Last modified date 2005-11-02

APAR is sysrouted FROM one or more of the following:
PK11426

APAR is sysrouted TO one or more of the following:

Modules/Macros
BBOUBINF          

Publications Referenced

Fix information
Fixed component name WEBSPHERE FOR Z
Fixed component ID 5655I3500

Applicable component levels
R500 PSY UK07674    UP05/10/01 P F509

  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


Current web document: swg1PK11507.html
Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK11507
IBM Group: Software Group
Modified date: Nov 2, 2005