1.2.4 Trace log
A trace log contains trace information that can be used in investigating how a problem has occurred and in determining how time was required to execute each process when a problem has occurred.
The JP1/AJS3 trace information is output to multiple trace log files. The internal format of each trace log file is not public information. In addition, a text editor cannot be used to view the files because the files are binary files.
- Organization of this subsection
(1) Scheduler trace
There are two types of scheduler trace log files as follows:
-
Common scheduler trace log file
Trace log file to which trace information of all scheduler services is output.
The scheduler trace information on the physical host and all logical hosts is output to a single trace log file.
A JP1/AJS3 - Manager host uses one file, which wraps around to the beginning when the end of the file is reached. The default file size is 20,480 kilobytes. The logging format is binary.
-
Scheduler trace log file of each scheduler service
The scheduler trace information of scheduler service is output to this log file in units of scheduler service.
Trace log file to which trace information on a scheduler service is output.
One log file is used for each scheduler service. When the maximum file size is reached, the log records in the file wrap around. The default file size is 20,480 kilobytes. The logging format is binary.
For details about how to output trace log data for individual scheduler services, see 6.1.5 Setting to output a scheduler trace log per scheduler service in the JP1/Automatic Job Management System 3 Configuration Guide (for Windows), or 15.1.5 Setting to output a scheduler trace log per scheduler service in the JP1/Automatic Job Management System 3 Configuration Guide (for UNIX).
Note that you can use the ajstrsetsz command to increase the trace log file size.
For details about this command, see ajstrsetsz in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
(2) Job execution trace
The trace log data related to job execution control is divided by function and recorded in separate files on the JP1/AJS3 - Manager and JP1/AJS3 - Agent hosts. For details about the names of files, see 1.2.5 List of log files and directories.
(3) Event and action trace
The trace log data related to event/action control is divided by function and recorded in separate files on the JP1/AJS3 - Manager and JP1/AJS3 - Agent hosts. For details about the names of these files, see 1.2.5 List of log files and directories.
(4) Queueless job trace
A JP1/AJS3 - Manager host uses one file, which wraps around to the beginning when the end of the file is reached. A JP1/AJS3 - Agent host also uses one file that wraps around to the beginning when the end of the file is reached. The default file size is 15,360 kilobytes. The logging format is binary. You can change the size of these trace log files by using the ajsqltrsetsz command. For details about this command, see ajsqltrsetsz in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.
(5) Other traces
-
JP1/AJS3 Check Manager and JP1/AJS3 Check Agent, which pre-check definitions, each use one trace log file that wraps around to the beginning when the end of the file is reached. The default file size is 3,072 kilobytes. The logging format is binary. You can change the size of these trace log files by using the ajschktrsetsz command. For details about this command, see ajschktrsetsz in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.
-
A JP1/AJS3 - Manager host or a JP1/AJS3 - Agent host logs trace information related to system management in multiple trace log files for each function. For details about the names of files, see 1.2.5 List of log files and directories. The default size of each file is 384 kilobytes.