PQ49250: SOME WAS 4.0 CTRACE ENTRIES ARE

APAR status
Closed as fixed if next.

Error description
The following trace ids are not formatted properly in CTRACE
output:
13007002
13007003
04006027
0400602C
04048005
04048006
04048007
0700C008
0A004001
0A004002
0800A058
080EF004
080EF005
080EF006
080F0004
080F0005
080F0006
080F1004
080F1005
080F1006
080F2004
080F2005
Local fix
Run with TRACEBUFFLOC=SYSPRINT.  Properly formatted trace
entries will be written to SYSPRINT, but this takes a lot of
spool space.
.
The TRACEBUFFLOC parameter is an environment variable set in
the current.env associated with the server where tracing is
requested.
Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0 for z/OS and OS/390                     *
****************************************************************
* PROBLEM DESCRIPTION: Some trace records in the CTRACE output *
*                      are not formatted in a manner which     *
*                      make the data easily readable. Support  *
*                      needs to be added to format the trace   *
*                      data correctly.                         *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following trace ids are not defined and formatted properly
in CTRACE output:
13007002 13007003 04006027 0400602C 04048005 04048006
04048007 0700C008 0A004001 0A004002 0800A058 080EF004
080EF005 080EF006 080F0004 080F0005 080F0006 080F1004
080F1005 080F1006 080F2004 080F2005

CTRACE users will see entries like the
following, (trace ID 13007002 example data):

An entry contains an undefined ID: 13007002,
hex format will be used.
SY1       N/A       13007002  00:14:57.272682  N/A
    0002009E  34A0078D  24000039  00000008  | ................ |
    0000006C  000C0302  97969389  83A8D596  | ...%....policyNo |
    00120402  6DD1D796  938983A8  C2D6C994  | ...._JPolicyBOIm |
    97930009  0A02C1E4  C4C9E300  2E0B02C2  | pl....AUDIT....B |
    C2D6D1F0  F0F0F240  D7969389  83A84095  | BOJ0002 Policy n |
    A4948285  9940F3F3  6BF3F3F3  409682A3  | umber 33,333 obt |
    81899585  844B4040  40                  | ained.           |

Support needs to be added to format the trace data correctly.
Problem conclusion Temporary fix Comments
This APAR is being closed FIN with concurrence from the
submitting customer. A solution to this problem will be
delivered in a WebSphere Application Server for z/OS
and OS/390 release within the next 18 months.
APAR information
APAR number PQ49250
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 400
Status CLOSED FIN
PE NoPE
HIPER NoHIPER
Submitted date 2001-05-31
Closed date 2001-07-05
Last modified date 2001-07-05

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels
R400 PSN    UP


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 #: PQ49250
IBM Group: Software Group
Modified date: Jul 5, 2001