Job Management Partner 1/Base User's Guide

16.2.2 Integrated trace log information

The integrated trace log is created using Hitachi Network Objectplaza Trace Library (HNTRLib2) by collecting the trace information output by each program into a single output destination file. The integrated trace log contains messages with data that is more detailed than the data in the common message log information.

The default destination for the integrated trace log is as follows:

In Windows:

system-drive\Program Files\Hitachi\HNTRLib2\spool\hntr2{1|2|3|4}.log

In UNIX:

/var/opt/hitachi/HNTRLib2/spool/hntr2{1|2|3|4}.log

You can use either the hntr2util, hntr2conf, or hntr2getconf command to view or change the log file destination or size. For details, see hntr2util (Windows only), hntr2util (UNIX only), hntr2conf, or hntr2getconfin 13 Commands.

You can use a text editor to view the integrated trace log file. The following figure shows an example of the integrated trace log.

Figure 16-2 Output example of integrated trace log file

The following tables describe headers and items output to the integrated trace log file.

Table 16-1 Headers for the integrated trace log file

Header	Description
OS information	Information on the OS on which Hitachi Network Objectplaza Trace Library (HNTRLib2) is running
host-name	Name of the host on which Hitachi Network Objectplaza Trace Library (HNTRLib2) is running
Time zone	In Windows: OS time zone In UNIX: Value of the environment variable TZ for the integrated trace process If the environment variable TZ is not set, Unknown is displayed.
Start time of Hitachi Network Objectplaza Trace Library (HNTRLib2)	Time at which Hitachi Network Objectplaza Trace Library (HNTRLib2) started

Table 16-2 Output items for the integrated trace log file

Output item	Description
Number (4 digits)	Trace record sequence number. Records are individually numbered for each process that outputs log information.
Date (10 bytes)	Trace acquisition date: yyyy/mm/dd (year/month/day)
Time (12 bytes)	Trace acquisition time (local time): hh:mm:ss.sss (hour: minute: second. millisecond)
AP name (maximum of 16 bytes)	Application identification name. Process management JBS_SPMD Startup control JP1ControlSvc Authentication access control jp1BsSess Operation access control jp1BsAcl Authentication server jbssessionmgr Configuration management jbsroute Command execution (control process) jcocmdrouter Command execution (Inter-JP1/Base communication process) jcocmdcom Command execution (JP1/IM-M-JP1/Base communication process) jcocmdapi Command execution (execution control process) jcocmdexe Command execution (execution process) jcocmdcmc Plug-in service jbsplugin Plug-in (manager command) jbsrmtcmd Plug-in (agent command) plAdapter_Event Health check (for local host monitoring) jbshcd Health check (for other host monitoring) jbshchostd Event service jevservice JP1/AJS-compatible process jevsessvc Log file trap (Windows) jevtraplog Log file trap (UNIX) jevlogd Event log trap jevtrapevt SNMP trap converter jp1co_evtgw Other command names Command name
pid	Process ID. Process ID assigned by the OS.
tid	Thread ID. ID used to differentiate threads.
Message ID	Message ID described in the message output format. Message ID used for this product.
Message text	Message text output to the integrated trace log. Message text output by this product.

Note

The log time is output to the integrated trace log. The output log time is in a time zone format used by the output process.

For this reason, if you have changed the value of the environment variable TZ before you start a service or execute a command, a time value different from the value of the time zone set on the OS might be output.

[Contents][Back][Next]

All Rights Reserved. Copyright (C) 2009, Hitachi, Ltd.