7.2.2 Integrated trace logs

Integrated trace logs are provided by Hitachi Network Objectplaza Trace Library (HNTRLib2) as collections of trace information output by individual programs at a specific output destination. They contain messages related to start and termination of ITSLM.

The output destinations of integrated trace logs are as follows:

system-drive:\Program Files\HITACHI\HNTRLib2\spool\hntr2N^#.log

system-drive:\Program Files(x86)\HITACHI\HNTRLib2\spool\hntr2N^#.log

#: N is a number from 1 through 4.

The following tables describe the header information and the items output to the integrated trace logs.

Table 7‒4: Header information output to the integrated trace logs
No.	Header	Description
1	OS information	Information about the OS on which HNTRLib2 is running.
2	Host name	Information about the host on which HNTRLib2 is running.
3	Time zone	OS's time zone.
4	HNTRLib2 start time	Time HNTRLib2 started.

Table 7‒5: Items output to the integrated trace logs
No.	Output item	Description
1	`number` (4 digits)	Each trace record's sequence number. This numbering is initialized for each process that outputs logs.
2	`date` (10 bytes)	Date the trace was output, in the following format: `YYYY/MM/DD` (`year/month/date`)
3	`time` (12 bytes)	Time (local time) the trace was output, in the following format: `hh:mm:ss.sss` (`hour:minute:second.millisecond`)
4	`application-program-name` (maximum of 16 bytes)	Name that identifies the application. The following application program names are output by ITSLM: `JP1ITSLMProcCtrl` `JP1ITSLMView` `JP1ITSLMUsrResp` `JP1ITSLMWebSysAn` `JP1ITSLMPerColct` `JP1ITSLMRmiSrv` `JP1ITSLMDao` `JP1ITSLMAdaptor` `command-identifier`^#
5	`pid`	Process ID set by the OS
6	`tid`	ID identifying the thread
7	`message-ID`	Message identifier
8	`message-text`	Message text

#: If the message was output by a command, the identifier of the command is output. For the identifiers that are output, see the descriptions of functions in 9. Commands.

The log output time that is included in the integrated trace logs is based on the time zone of the process that output the log. Therefore, if you change the value of the TZ environment variable and start services or execute commands, the output time might not be based on the time zone of the OS.

Output example:

The following shows an output example of integrated trace log information:

**** Microsoft WindowsNT6.1(Build:7600)                           host01           TZ=(local)-9:00                  2011/04/20 19:51:04.437
     yyyy/mm/dd hh:mm:ss.sss                      pid      tid      message-id            message(LANG=0x0411)
0000 2011/04/20 19:53:57.639     JP1ITSLMView     000010FC J33D2EED KNAS15300-I           Logged in. User name = super

To Page Top