PH04941: TRACE TRIGGERED BY TRACE FOR USE UNDER L2 DIRECTION

8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• Provide a means of triggering the writing of the current trace
  specification via an enabling and disable trace point and/or
  time duration.  This RAS enhancement is meant for use by the
  explicit direction of the IBM support team.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  *                  V8.5                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: WebSphere Application Server for z/OS   *
  *                      needs triggered trace.                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The diagnosis of some intermittent problems can be aided by the
  collection of trace just prior to the failure.  However,
  since it may be long periods of between a reoccurrence it is
  usually not acceptable to have a trace specification
  active.  It will generate too much trace.
  If the problem being diagnosed runs through code that has
  tracing then we could dynamically enable a set of trace once
  a specific trace is issued.
  The use of this enhancement will need the assistance of IBM
  Support.
  

Problem conclusion

• Code was added to allow a server to be configured to not gather
  (write) any of the traces related to the active trace
  specification until a Triggering trace point is detected.
  At that point any traces on the detecting thread will be
  written until a specified duration or a defined disabling
  trace point is issued on the same thread.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 8.5.5.15.  Please refer to the Recommended
  Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R850 PSY

     UP