(ZOS) Trace log stream record output

View an example of the trace log stream output, with an explanation of the various attributes it contains.

If we do not want the message tag to be included in the trace log output:

1. In the administrative console, click Environment > WebSphere variables.

2. Select the appropriate scope> New.

3. Enter ras_trace_log_version in the Name field and 1 in the Value field.

4. Save and synchronize changes, and then stop, and restart the server.

Sample output from the trace log: The numbers to the left of each sample were added to specify lines. The numbers will not be in the actual output.

1| Trace: 2009/07/14 17:26:19.577 02 t=6C8B58 c=UNK key=P8 tag=jperf 
	 (13007002)
2|  ThreadId: 0000002d                                                         
3|  FunctionName: PingServlet                                                  
4|  SourceId: PingServlet                                                      
5|  Category: AUDIT                                                            
6|  ExtendedMessage: BBOO0222I: Audit Message from PingServlet      

The log stream record output fields from stream BBO.BOSSXXXX are:

Component	Description
line 1: Trace: 2009/07/14 17:26:19.577 02	Date / timestamp / 2-digit record version number
line 1: t=6C8B58	Thread address
line 1: c=UNK	Cell name
line 1: key=P8	System protection key
line 1: tag=jperf	Message tag from classification file
line 1: (13007002)	Trace specific value for this trace point
line 2: ThreadId: 0000002d	Thread ID
line 3: FunctionName:PingServlet	Function Name
line 4: SourceId:PingServlet	Source ID
line 5: Category:AUDIT	Category
line 6: ExtendedMessage: BBOO0222I: Audit Message from PingServlet	Extended Message

Each field is delimited by a blank.

(ZOS) View error log contents through the Log Browse Utility (BBORBLOG)

(ZOS) Choosing diagnostic information sources