1.2.1 System failure log

System failure log refers to the information logged for system problems. This information is used by system administrators.

System failure log consists of the common message log and the integrated trace log.

Organization of this subsection

(1) Common message log
(2) Integrated trace log

(1) Common message log

The common message log is output to the Windows event log file or the syslog file.

To Page Top

(2) Integrated trace log

The integrated trace log contains the trace information that is output by different programs via Hitachi Network Objectplaza Trace Library (HNTRLib2). This information is stored in output files. The integrated trace log contains more detailed messages than those provide by the common message log.

The integrated trace log is output to integrated trace log files.

For details about how to obtain the integrated trace log, see the Job Management Partner 1/Base User's Guide.

The integrated trace log is output to the following files by default:

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
#: For 64-bit versions of Windows, replace Program Files with Program Files (x86).

You can specify the type of system failure log to be collected in the integrated trace log. To do this, use the jajs_config command to specify the type of information to be logged in the HNTRLOGLEVEL environment setting parameter.

For JP1/AJS3 Console, specify the type of information to be logged in the HNTRLOGLEVEL environment setting parameter in the environment settings files (ajs2cm.conf, ajs2ca.conf). For details about HNTRLOGLEVEL, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

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

Figure 1‒2: Example of output to an integrated trace log file

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

Table 1‒1: Meaning of headers in the integrated trace log file
Header	Explanation
OS information	The OS on which Hitachi Network Objectplaza Trace Library (HNTRLib2) is running.
Host name	The name of the host on which Hitachi Network Objectplaza Trace Library (HNTRLib2) is running.
Time zone	In Windows: The time zone set for the OS. In UNIX: The value of the `TZ` environment variable for the integrated trace log. If the `TZ` environment variable is not specified, `Unknown` is displayed.
Time HNTRLib2 started	The time that Hitachi Network Objectplaza Trace Library (HNTRLib2) started

Table 1‒2: Meaning of the output items in the integrated trace log file
Output item	Explanation
Number (4 digits)	The sequence number of the trace record. A number is assigned for each process for which information is logged.
Date (10 bytes)	The date the trace was collected: `yyyy/mm/dd` (year/month/day)
Time (12 bytes)	The local time the trace was collected: `hh:mm:ss.sss` (hour:minutes:seconds.milliseconds)
Application name (16 bytes or less)	The name of an application (application identification name). JP1/AJS3 generally outputs the following application names: The JP1/AJS3 service: JAJS_SPMD The scheduler process: ajsmasterd The flow control process: ajsflowd (ajsflowd.exe for Windows) The job submit process: ajssubd (ajssubd.exe for Windows) The job completion wait process: ajssubwd (ajssubwd.exe for Windows) The job execution control status notification process: jpqnfyfd (jpqnfyfd.exe for Windows) The schedule control process: ajsschd The event/action control manager process: jpomanager The event/action control agent process: jpoagent The execution interval control process: jpocwttmMain The event (JP1 events, log traps, etc.) monitoring process: jpoeventwatch The event/action control submanager process: jpomgrsub The event/action control subagent process: jpoagtsub The job execution control process: jpqmon The job execution control manager process: jpqman The job execution control agent process: jpqagt The network control process: ajsinetd The process that starts when a user logs in to JP1/AJS3 - View: ajsmonsvr The JP1/AJS3 - Queueless Agent service (queueless agent process): ajsqlagtd The JP1/AJS3 - Queueless File Transfer service (queueless file transfer process): ajsqlftpd The JP1/AJS3 Check Manager service: ajschkmand (ajschkmand.exe for Windows) The JP1/AJS3 Check Agent service: ajschkagtd The JP1/AJS3 Console Manager service: ajscminetd The JP1/AJS3 Console Agent service: ajscainetd Other processes and commands: The process or command name
pid	The process ID assigned by the OS. A pid is output as a hexadecimal number.
tid	The thread ID that identifies a thread. A tid is output as a hexadecimal number.
Message ID	A message ID appearing in 1.2.1 Format of output messages in the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1. The message IDs in this log are only those used by JP1/AJS3.
Message text	The text of a message output to the integrated trace log. The message texts in this log are those output by JP1/AJS3.

Important note: The time that information is recorded in the integrated trace log is the time in the time zone to which the source process belongs. If a user changes the value of the TZ environment variable and then starts a service or executes a command, the time of log information might not match the time zone set for the OS.

To Page Top