Job Management Partner 1/Automatic Job Management System 3 Troubleshooting

[Contents][Glossary][Index][Back][Next]


1.2.4 List of log files and directories

Organization of this subsection
(1) Log files and directories in Windows
(2) Log files and directories in UNIX

(1) Log files and directories in Windows

Tables 1-4 to 1-6 describe the log file names and folder names of the scheduler logs and the trace logs for each function in JP1/AJS3 for Windows.

The Log name column lists the names of the logs created by JP1/AJS3.

In Log file and folder names column, the following abbreviations are used for folders:

  1. Mgr_Path (for Windows Server 2008): %ALLUSERSPROFILE%#\HITACHI\JP1\JP1_DEFAULT\JP1AJS2
  2. Mgr_Path (for Windows Server 2003): JP1/AJS3 - Manager-installation-folder
    The default path is system-drive\Program Files\Hitachi\jp1ajs2.
  3. Agt_Path (for Windows Server 2008): %ALLUSERSPROFILE%#\HITACHI\JP1\JP1_DEFAULT\JP1AJS2
  4. Agt_Path (for Windows Server 2003): JP1/AJS3 - Agent-installation-folder
    The default path is system-drive\Program Files\Hitachi\jp1ajs2.
  5. View_Path (for Windows 7, Windows Server 2008, and Windows Vista): %ALLUSERSPROFILE%#\HITACHI\JP1\JP1_DEFAULT\JP1AJS2V
  6. View_Path (for Windows Server 2003 and Windows XP Professional): JP1/AJS3 - View-installation-folder
    The default path is system-drive\Program Files\Hitachi\jp1ajs2v.
  7. Base_Path: JP1/Base-installation-folder
    The default path is system-drive\Program Files\Hitachi\jp1base.
  8. CM_Path (for Windows Server 2008): %ALLUSERSPROFILE%#\HITACHI\JP1\JP1_DEFAULT\JP1AJS2CM
  9. CM_Path (for Windows Server 2003): JP1/AJS3 Console-installation-folder
    The default path is system-drive\Program Files\Hitachi\jp1ajs2cm.

#
The default value for %ALLUSERSPROFILE% is as follows:

For View_Path:
system-drive\ProgramData

For Mgr_Path, Agt_Path, and CM_Path:
  • When the installation folder is the default folder or a folder located under a folder protected by the system:
    system-drive\ProgramData
  • When the installation folder is any other kind of folder:
    installation-folder-of-product
Folder protected by the system indicates the following path:
  • For 32-bit Windows
    Under the system-drive\Program Files folder
  • For 64-bit Windows
    Under the system-drive\Program Files (x86) folder
  • When both the 32-bit and 64-bit versions of Windows are used
    Under the system-drive\Windows folder

In a cluster system, unless otherwise specified, make the substitutions shown in the following table for the indicated abbreviations.

Table 1-3 Log output folders in a cluster system

Abbreviation in Table 1-4 to Table 1-6 Log output folder in a cluster system
Mgr_Path shared-disk-name\jp1ajs2
Agt_Path shared-disk-name\jp1ajs2
Base_Path shared-disk-name\jp1base

The Default disk space column indicates the disk space allocated to a log file when the default environment settings is used for operation, and is the total disk space size when there are multiple log files. If the user has not changed the size of a log file, the disk space indicated in the table is the disk space allocated to that log file.

The Maximum disk space column indicates the maximum amount of disk space that a log file uses. This value includes changes to definitions, and is the total disk space size when there are multiple log files. The values in this column are the maximum values for log files whose size varies according to the definitions.

The Timing for switching files column indicates either a limit or the point at which JP1/AJS3 switches the log file (output file for the log) to another file. A value in this column indicates that there are multiple log files, and that the file with the oldest update date is overwritten when the maximum disk space has been reached.

Table 1-4 Log files and folders in JP1/AJS3 - Manager (for Windows)

Log name Log file and folder names Logged information Default disk space#1 Maximum disk space#1 Timing for switching files#2
System management log Mgr_Path\log\JAJS_SPMD{1|2|3}.log Trace information related to starting, stopping, and checking the status of the JP1/AJS3 service#3 384 384 128
Mgr_Path\log\JAJS_SPMD_COMMAND{1|2|3}.log 384 384 128
Mgr_Path\log\JAJS_SERVICE{1|2|3}.log 384 384 128
Scheduler information log#4 Mgr_Path\log\schedule\scheduler-service-name\ajs-log{1|2}.log Operating information related to jobnets, jobs, and scheduler services (when scheduler information is logged separately for each scheduler service) 20,480 4,000,000 Size of the scheduler information log file specified in the environment settings
(10,240)
Mgr_Path\log\ajs-host-log{1|2}.log Operating information related to jobnets, jobs, and scheduler services (when scheduler information is logged for the entire host) 20,480 4,000,000 Size of the scheduler information log file for the host specified in the environment settings
(10,240)
ajsinetd internal log#5, #23 Mgr_Path\log\ajsinetd{1|2}.log Internal information related to the network control process#3 256 4,000,000 Size of the ajsinetd internal log
(128)
Trace log#5, #6 Mgr_Path\log\tracelog Trace information and information about operations related to scheduler services and jobnets#3, #8 20,480 2,097,151 Wraparound
Job execution manager log#10 Mgr_Path\log\schedule\scheduler-service-name\jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log#9 Trace information related to the job execution control manager process when a job is executed#3 15,360 524,288 Log size specified during log setup
(1,024)
Mgr_Path\log\jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log#9
Job execution agent log#10 Mgr_Path\log\jpqagtexec{1|2|3|4|5|6|7|8}.log#18 Trace information related to the job execution control agent process when a job is executed#3 15,360 524,288 Log size specified during log setup
(512)
Mgr_Path\log\jpqagtexecmon{1|2|3|4|5|6|7|8}.log#19 15,360 524,288
Job execution client log#10 Mgr_Path\log\jpqcliexec{1|2}.log#20 Execution trace information related to jpqxxxx commands and JpqxxxxAPI functions#3 1,024 524,288 Log size specified during log setup
(512)
Job execution status report log#10 Mgr_Path\log\schedule\scheduler-service-name\jpqnfyexec{1|2}.log#21 Trace information related to job execution control communication when a job is executed#3 1,024 524,288 Log size specified during log setup
(512)
Event/action control manager log#7 Mgr_Path\log\schedule\scheduler-service-name\jpomanager{1|2|3|4|5|6}.log#24 Trace information related to the event/action control manager when an event job is executed#3 12,288 16,777,216
(16 gigabytes)
Log size specified during log setup
(2,048)
Mgr_Path\log\jpomanager{1|2|3|4|5|6}.log#25
Mgr_Path\log\schedule\scheduler-service-name\jpomgrsub{1|2|3|4|5|6|7|8}.log#24 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Mgr_Path\log\jpomgrsub{1|2|3|4|5|6|7|8}.log#25
Event/action control agent log#7 Mgr_Path\log\jpoagent{1|2|3|4|5|6|7|8}.log#25 Trace information related to the event/action control agent when an event job is executed#3 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Mgr_Path\log\jpoagtsub{1|2|3|4|5|6|7|8}.log#25 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Event monitoring log#7 Mgr_Path\log\jpoeventwatch{1|2|3|4|5|6|7|8}.log#25 Execution trace information related to the JP1 event monitoring job, Windows event log monitoring job, and log file monitoring job#3 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Event search log#7 Mgr_Path\log\jpoevsearch{1|2}.log#25 Trace information related to event searching before the JP1 event reception monitoring job is executed#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
File monitoring log#7 Mgr_Path\log\jpocwtflMain{1|2|3|4|5|6}.log#25 Execution trace information related to the file monitoring job#3 12,288 16,777,216
(16 gigabytes)
Log size specified during log setup
(2,048)
Execution interval control log#7 Mgr_Path\log\jpocwttmMain{1|2|3|4|5|6}.log#25 Execution trace information related to the execution interval control job#3 1,536 16,777,216
(16 gigabytes)
Log size specified during log setup
(256)
Mail monitoring log (common)#7 Mgr_Path\log\jpocwtmlmain{1|2}.log#25 Execution trace information related to the mail reception monitoring job and mail transmission job when the mail linkage function is used#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mgr_Path\log\jpomlapisend{1|2}.log#5 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mgr_Path\log\jpomlapirec{1|2}.log#5 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mgr_Path\log\jpomlapisend2{1|2}.log#5 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mgr_Path\log\jpomlapirec2{1|2}.log#5 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mail monitoring log (when mail linkage is performed on the desktop)#7 Mgr_Path\log\jpomldsk{1|2}.log#5 Execution trace information related to the mail reception monitoring job and mail transmission job when the mail linkage function is used#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mail monitoring log (when mail linkage is performed in the service)#7 Mgr_Path\log\jpomlsrv{1|2}.log#5 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
NNM linkage log Mgr_Path\log\jpoovlink{1|2}.log#5 Trace information related to monitoring HP NNM is used#3 512 512 256
Job execution internal log#10 Mgr_Path\log\jpqagent\jpqagt_{00|01|02|03|04|05|06|07}.log --#8 4,096 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\jpqagent\jpqmon_{00|01|02|03|04|05|06|07}.log --#8 4,096 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\jpqagent\jpqnjpagt_{00|01|02|03|04|05|06|07}.log --#8 4,096 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\jpqagent\jpqnjpdata_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Job execution internal log#10 Mgr_Path\log\jpqclient\jpqclient_{00|01|02|03|04|05|06|07|08|09}.log --#8 10,240 1,048,576 Log size specified during log setup
(1,024)
Mgr_Path\log\jpqclient\jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log --#8 10,240 1,048,576 Log size specified during log setup
(1,024)
Mgr_Path\log\jpqclient\jpqnjpdata_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Job execution internal log#10 Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqman_{00|01|02|03}.log --#8 2,048 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\jpqmanager\jpqman_{00|01|02|03}.log
Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqmandb_{00|01|02|03}.log --#8 2,048 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\jpqmanager\jpqmandb_{00|01|02|03}.log
Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqmannjp_{00|01|02|03}.log --#8 2,048 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\jpqmanager\jpqmannjp_{00|01|02|03}.log
Mgr_Path\log\schedule\scheduler-service-name\jpqmanager\jpqnjpdata_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\jpqmanager\jpqnjpdata_{00|01}.log
Job execution internal log#10 Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnotify_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnotifynjp_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Mgr_Path\log\schedule\scheduler-service-name\jpqnotify\jpqnjpdata_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Job execution environment database reorganization log Mgr_Path\database\queue\CONDENSE{1|2}.log -- 1,024 1,024 512
Scheduler database reorganization log Mgr_Path\database\schedule\scheduler-service-name\CONDENSE{1|2}.log -- 1,024 1,024 512
Event/action common log#5, #7 Base_Path\log\jpocommonerr{1|2}.log --#3 2,048 2,097,152
(2 gigabytes)
Log size specified during log setup
(1,024)
Event/action common error log#5 Base_Path\log\jpoproccomerr{1|2}.log --#3 256 256 128
jajs_migrate command trace log Mgr_Path\log\jajs_migrate_logical-host-name_{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log#28 Trace information related to the command that changes the system environment from JP1/AJS2 to JP1/AJS3 10 200 When the jajs_migrate command is executed
jajs_setup command trace log#3, #5 Mgr_Path\log\jajs_setup_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log Trace information related to the command that specifies environment settings 200 200 When the jajs_setup command is executed
jajs_config command trace log Mgr_Path\log\jajs_config_{1|2}.log Trace information related to the command that specifies an environment setting parameter 1 256 128
jajs_setup_cluster command trace log#3, #5 Mgr_Path\log\jajs_setup_cluster_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#28 Trace information related to the command that configures a cluster environment 200 200 When the jajs_setup_cluster command is executed
Queueless log#16 Mgr_Path\log\ajsql-log{1|2}.log Information related to the jobs executed by the queueless agent service 16,384 4,000,000 Queueless log file size specified in environment settings (8,192)
Queueless trace log#5, #17 Mgr_Path\log\tracelog.ql Execution trace information related to queueless jobs and commands related to execution control of queueless jobs#3, #8 15,360 2,097,151 Wraparound
Queueless job execution internal log#26 Mgr_Path\log\ajsqlexeclog#27 Execution trace information related to queueless jobs#3, #8 24,576 2,097,151 Wraparound
Mgr_Path\log\ajsqlexeclog_ftpd 10,240 2,097,151 Wraparound
JP1/AJS3 Console Manager trace log#5, #11 CM_Path\log\tracelog.cm --#8 3,072 2,097,151 Wraparound
JP1/AJS3 Console Agent trace log#5, #12 Mgr_Path\log\tracelog.ca --#8 3,072 2,097,151 Wraparound
Maintenance log#5 Mgr_Path\log\jajs_maintain_manager{1|2|3|4}.log#13 Information related to database reorganization that is executed during maintenance#3 1,484 1,484 When maintenance is performed
Mgr_Path\log\jajs_maintain_[scheduler-service-name]{1|2|3|4}.log#13 1,484 1,484 When maintenance is performed
Automatic reorganization log#5 Mgr_Path\log\jpqautocond{1|2|3|4}.log#14 Information related to database reorganization that is executed during automatic reorganization#3 764 764 When automatic reorganization is performed
Mgr_Path\log\ajsautocond{1|2|3|4}.log#14 764 764 When automatic reorganization is performed
Definition check log#22 Mgr_Path\log\ajscheck{1|2}.log Information related to definition pre-checks 8,192 4,000,000 Definition check log file size specified in the environment settings
Definition check trace log#15 Mgr_Path\log\tracelog.ch Trace information related to definition pre-checks#8 3,072 2,097,151 Wraparound
Execution log for embedded database operation commands Mgr_Path\log\embdb\ajsembdboplog[embedded-database-setup-ID]{1|2|3|4}.log Information related to execution of commands manipulate the embedded database 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbrorg[host-name][scheduler-service-name]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbreclaim[host-name][scheduler-service-name]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbaddarea[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbaddlog[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbstop[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbstart[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbcancel[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbunset[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbbuild[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbsetup[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbstatus[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbinstl{1|2|3|4}.log 4,096 4,096 1,024
Mgr_Path\log\embdb\ajsembdbuninstl{1|2|3|4}.log 4,096 4,096 1,024
Agent management trace log#5 Mgr_Path\log\ajsagttrace --#3, #8 20,480 20,480 Wraparound
Agent management log Mgr_Path\log\ajsagtmd{1|2}.log Agent information for agent management control 8,192 8,192 4,096
Communication control trace log Mgr_Path\log\tracelog-nw --#3, #8 20,480 20,480 Wraparound

#1
The unit is kilobytes. The value in parentheses is the kilobyte value expressed in gigabytes.

#2
The unit is kilobytes. The value in parentheses in this column indicates the default timing for switching log files.

#3
The format of the logged information is not publicly available outside the company.

#4
You can change the disk space size. To do so, use the jajs_config command to specify the desired value in the LOGSIZE environment setting parameter.
For details about how to estimate the required disk space, see 3.4.1 Estimating the size of scheduler log files in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#5
Information is also output to the default folder in a cluster system.

#6
You can change the disk space size by using the ajstrsetsz command.

#7
You can change the disk space size. To do so, see 3.4.3 Estimating the size of the log information output by event jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#8
The information is in binary format and cannot be read.

#9
In a cluster system, the file names are different:
jpqExecLog_man{1|2|3|4|5|6|7|8|9|10|11|12}.log

#10
You can change the disk space size. To do so, see 7.1.4 Estimating the size of the logs output by the execution environment for QUEUE jobs and submit jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#11
You can change the disk space size by using the ajscmtrsetsz command. If you do not use the JP1/AJS3 Console Manager function, no trace log file is created.

#12
You can change the disk space size by using the ajscatrsetsz command. If you do not use the JP1/AJS3 Console Agent function, no trace log file is created.

#13
In a cluster system, the file names are different:
  1. jajs_maintain_manager_[logical-host-name]{1|2|3|4}.log
  2. jajs_maintain_[scheduler-service-name]_[logical-host-name]{1|2|3|4}.log

#14
In a cluster system, the file names are different:
  1. jpqautocond_[logical-host-name]{1|2|3|4}.log
  2. schedule\ajsautocond_[logical-host-name]{1|2|3|4}.log

#15
You can change the disk space size by using the ajschktrsetsz command. If you do not use the JP1/AJS3 Check Manager function or the JP1/AJS3 Check Agent function, no trace log file is created.

#16
You can change the disk space size. To do so, use the jbssetcnf command to specify the desired value in the AJSQL_LOGSIZE environment setting parameter.
For details about how to estimate the required disk space, see 7.2.1(1) Estimating the size of the queueless log file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#17
You can change the disk space size by using the ajsqltrsetsz command.

#18
In a cluster system, the file names are different:
jpqExecLog_agt{1|2|3|4|5|6|7|8}.log

#19
In a cluster system, the file names are different:
jpqExecLog_agtmon{1|2|3|4|5|6|7|8}.log

#20
In a cluster system, the file names are different:
jpqExecLog_cli{1|2}.log

#21
In a cluster system, the file names are different:
jpqExecLog_nfy{1|2}.log

#22
You can change the disk space size. To do so, see 2.5 Setting for the JP1/AJS3 definition pre-check function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

#23
You can change the disk space size. To do so, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

#24
You can change the log output folders. To do so, change the value specified in the AJSLOGDIR environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name] definition key.

#25
You can change the Mgr_Path part differs depending on the value specified in the WaitInfFileOutDir environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1AOM\MANAGER] and [{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT] definition keys.

#26
You can change the disk space size by using the ajsqlexecsetsz command. For details about this command, see ajsqlexecsetsz in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
For details about how to estimate the required disk space, see 7.2.1(3) Estimating the size of the internal execution logs for queueless jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#27
The file name is different in a cluster system:
  Mgr_Path\log\ajsqlexeclog-[logical-host-name]
If the full path name is 256 bytes or more, [logical-host-name] becomes the first 30 bytes of the logical host name.

#28
The value n starts at 1 and is then incremented. The file with the largest number contains the latest execution result.
 

Table 1-5 Log files and folders in JP1/AJS3 - Agent (for Windows)

Log name Log file and folder names Logged information Default disk space#1 Maximum disk space#1 Timing for switching files#2
System management log Agt_Path\log\JAJS_SPMD{1|2|3}.log Trace information related to starting, stopping, and checking the status of the JP1/AJS3 service#3 384 384 128
Agt_Path\log\JAJS_SPMD_COMMAND{1|2|3}.log 384 384 128
Agt_Path\log\JAJS_SERVICE{1|2|3}.log 384 384 128
Job execution agent log#10 Agt_Path\log\jpqagtexec{1|2|3|4|5|6|7|8}.log#11 Trace information related to the job execution control agent process when a job is executed#3 15,360 524,288 Log size specified during log setup
(512)
Agt_Path\log\jpqagtexecmon{1|2|3|4|5|6|7|8}.log#12 15,360 524,288 Log size specified during log setup
(512)
Job execution client log#10 Agt_Path\log\jpqcliexec{1|2}.log#13 Execution trace information related to jpqxxxx commands and JpqxxxxAPI functions#3 1,024 524,288 Log size specified during log setup
(512)
Event/action control agent log#4 Agt_Path\log\jpoagent{1|2|3|4|5|6|7|8}.log#16 Trace information related to the event/action control agent when an event job is executed#3 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Agt_Path\log\jpoagtsub{1|2|3|4|5|6|7|8}.log#16 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Event monitoring log#4 Agt_Path\log\jpoeventwatch{1|2|3|4|5|6|7|8}.log#16 Execution trace information related to the JP1 event monitoring job, Windows event log monitoring job, and log file monitoring job#3 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Event search log#4 Agt_Path\log\jpoevsearch{1|2}.log#16 Trace information related to event searching before the JP1 event reception monitoring job is executed#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
File monitoring log#4 Agt_Path\log\jpocwtflMain{1|2|3|4|5|6}.log#16 Execution trace information related to the file monitoring job#3 12,288 16,777,216
(16 gigabytes)
Log size specified during log setup
(2,048)
Execution interval control log#4 Agt_Path\log\jpocwttmMain{1|2|3|4|5|6}.log#16 Execution trace information related to the execution interval control job#3 1,536 16,777,216
(16 gigabytes)
Log size specified during log setup
(256)
Mail monitoring log (common)#4 Agt_Path\log\jpocwtmlmain{1|2}.log#16 Execution trace information related to the mail reception monitoring job and mail transmission job when the mail linkage function is used#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Agt_Path\log\jpomlapisend{1|2}.log#6 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Agt_Path\log\jpomlapirec{1|2}.log#6 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Agt_Path\log\jpomlapisend2{1|2}.log#6 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Agt_Path\log\jpomlapirec2{1|2}.log#6 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mail monitoring log (when mail linkage is performed on the desktop)#4 Agt_Path\log\jpomldsk{1|2}.log#6 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mail monitoring log (when mail linkage is performed in the service)#4 Agt_Path\log\jpomlsrv{1|2}.log#6 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
NNM linkage log Agt_Path\log\jpoovlink{1|2}.log#6 Trace information related to monitoring when HP NNM is used#3 512 512 256
Job execution internal log#7 Agt_Path\log\jpqagent\jpqagt_{00|01|02|03|04|05|06|07}.log --#5 4,096 1,048,576 Log size specified during log setup
(512)
Agt_Path\log\jpqagent\jpqmon_{00|01|02|03|04|05|06|07}.log --#5 4,096 1,048,576 Log size specified during log setup
(512)
Agt_Path\log\jpqagent\jpqnjpagt_{00|01|02|03|04|05|06|07}.log --#5 4,096 1,048,576 Log size specified during log setup
(512)
Agt_Path\log\jpqagent\jpqnjpdata_{00|01}.log --#5 1,024 1,048,576 Log size specified during log setup
(512)
Job execution internal log#7 Agt_Path\log\jpqclient\jpqclient_{00|01|02|03|04|05|06|07|08|09}.log --#5 10,240 1,048,576 Log size specified during log setup
(1,024)
Agt_Path\log\jpqclient\jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log --#5 10,240 1,048,576 Log size specified during log setup
(1,024)
Agt_Path\log\jpqclient\jpqnjpdata_{00|01}.log --#5 1,024 1,048,576 Log size specified during log setup
(512)
Event/action common log#4, #6 Base_Path\log\jpocommonerr{1|2}.log --#3 2,048 2,097,152
(2 gigabytes)
Log size specified during log setup
(1,024)
Event/action common error log#6 Base_Path\log\jpoproccomerr{1|2}.log --#3 256 256 128
jajs_config command trace log Mgr_Path\log\jajs_config_{1|2}.log Trace information related to the command that specifies an environment setting parameter 1 256 128
jajs_setup_cluster command trace log#3, #6 Mgr_Path\log\jajs_setup_cluster_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#28 Trace information related to the command that configures a cluster environment 200 200 When the jajs_setup_cluster command is executed
Queueless log#9 Agt_Path\log\ajsql-log{1|2}.log Information related to jobs executed by the queueless agent service 16,384 4,000,000 Queueless log file size specified in the environment settings (8,192)
Queueless trace log#6, #10 Agt_Path\log\tracelog.ql Execution trace information related to queueless jobs and commands related to execution control of queueless jobs#3, #5 15,360 2,097,151 Wraparound
Queueless job execution internal log#17 Agt_Path\log\ajsqlexeclog#18 Execution trace information related to queueless jobs#3, #5 24,576 2,097,151 Wraparound
Definition check log#15 Agt_Path\log\ajscheck{1|2}.log Information related to definition pre-checks 8,192 4,000,000 Definition check log file size specified in the environment settings
Definition check trace log#8 Agt_Path\log\tracelog.ch Trace information related to definition pre-checks#5 3,072 2,097,151 Wraparound

#1
The unit is kilobytes. The value in parentheses is the kilobytes value expressed in gigabytes.

#2
The unit is kilobytes. The value in parentheses in this column indicates the default timing for switching log files.

#3
The format of the logged information is not publicly available outside the company.

#4
You can change the disk space size. To do so, see 3.4.3 Estimating the size of the log information output by event jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#5
The information is in binary format and cannot be read.

#6
Information is also output to the default folder in a cluster system.

#7
You can change the disk space size. To do so, see 7.1.4 Estimating the size of the logs output by the execution environment for QUEUE jobs and submit jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#8
You can change the disk space size by using the ajschktrsetsz command. If you do not use the JP1/AJS3 Check Agent function, no trace log file is created.

#9
You can change the disk space size. To do so, change the value specified in the AJSQL_LOGSIZE environment setting parameter.
For details about how to estimate the required disk space, see 7.2.1(1) Estimating the size of the queueless log file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#10
You can change the disk space size by using the ajsqltrsetsz command.

#11
The file names are different in a cluster system:
jpqExecLog_agt{1|2|3|4|5|6|7|8}.log

#12
The file names are different in a cluster system:
jpqExecLog_agtmon{1|2|3|4|5|6|7|8}.log

#13
The file names are different in a cluster system:
jpqExecLog_cli{1|2}.log

#14
The file names are different in a cluster system:
jpqExecLog_nfy{1|2}.log

#15
You can change the disk space size. To do so, see 2.5 Setting for the JP1/AJS3 definition pre-check function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

#16
You can change the Agt_Path part differs depending on the value specified in the WaitInfFileOutDir environment setting parameter for the [{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT] definition key.

#17
You can change the disk space size by using the ajsqlexecsetsz command. For details about this command, see ajsqlexecsetsz in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
For details about how to estimate the required disk space, see 7.2.1(3) Estimating the size of the internal execution logs for queueless jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#18
The file name is different in a cluster system:
  Agt_Path\log\ajsqlexeclog-[logical-host-name]
If the full path name is 256 bytes or more, [logical-host-name] becomes the first 30 bytes of the logical host name.
 

Table 1-6 Log files and folders in JP1/AJS3 - View (for Windows)

Log name Log file and folder names Logged information Default value#1 Maximum value#1 Timing for switching files
JP1/AJS3 - View log View_Path\log\ajs.log --#2 -- 1,024 When JP1/AJS3 - View terminates
JP1/AJS3 - View information log#3 View_Path\log\ajs2view#nnnn_{1|2}.log --#2 1,024 524,288 Maximum log file size specified in the Preferences dialog box
JP1/AJS3 Console View log View_Path\log\ajscon. --#2 -- 1,024 When JP1/AJS3 Console View terminates
JP1/AJS3 Console View information log#3 View_Path\log\ajs2coview#nnnn_{1|2}.log --#2 1,024 524,288 Maximum log file size specified in the Preferences dialog box
NNM linkage log View_Path\log\jpoovlink{1|2}.log (only for Windows Server 2003 and Windows XP Professional) Trace information related to monitoring when HP NNM is used#2 512 512 256

#1
The unit is kilobytes.

#2
The format of the logged information is not publicly available outside the company.

#3
When multiple units are started, a value in the range from 0001 to 9999 is assigned to nnnn of #nnnn_. When only one unit is started, #nnnn_ is omitted.
You can change the disk space size. To do so, open the Preferences dialog box of JP1/AJS3 - View, and on the Other page, change the value in the Max. log file size text box.
For JP1/AJS3 Console View, use the same procedure in the Preferences dialog box of JP1/AJS3 Console View.

(2) Log files and directories in UNIX

Table 1-8 and Table 1-9 describe the log file names and the directory names of the scheduler logs and the trace logs for each function in JP1/AJS3 for UNIX.

The Log name column lists the names of the logs created by JP1/AJS3.

The Log file and directory names column lists the names of the JP1/AJS3 log files in full-path-name form.

In a cluster system, consider the path names indicate the directories in the Log output directory in a cluster system column in the following table unless otherwise specified.

Table 1-7 Log output directories in a cluster system

Value in Table 1-8 and Table 1-9 Log output directory in a cluster system
/var/opt/jp1ajs2/ shared-disk-name/jp1ajs2
/var/opt/jp1base/ shared-disk-name/jp1base

The Default disk space column indicates the disk space allocated to a log file when the default environment setting is used for operation, and is the total disk space size when there are multiple log files. If the user has not changed the size of a log file, the disk space indicated in the table is the disk space allocated to that log file.

The Maximum disk space column indicates the maximum disk space that a log file uses. This value includes changes to definitions, and is the total disk size when there are multiple log files. The values in this column are the maximum values for log files whose size varies according to the definitions.

The Timing for switching files change column indicates either a limit or the point at which JP1/AJS3 switches the log file (output file for the log) to another file. A value in this column indicates that there are multiple log files and that the file with the oldest update date is overwritten when the maximum disk space is reached. A value in parentheses indicates the default timing for switching log files.

Table 1-8 Log files and directories of JP1/AJS3 - Manager (for UNIX)

Log name Log file and directory names Logged information Default disk space#1 Maximum disk space#1 Timing for switching files#2
System management log /var/opt/jp1ajs2/log/JAJS_SPMD{1|2|3}.log Trace information related to starting, stopping, and checking the status of the JP1/AJS3 service#3 384 384 128
/var/opt/jp1ajs2/log/JAJS_SPMD_COMMAND{1|2|3}.log 384 384 128
Scheduler information log#4 /var/opt/jp1ajs2/log/schedule/scheduler-service-name/ajs-log{1|2}.log#21 Operating information related to jobnets, jobs, and scheduler services (when scheduler information is logged separately for each scheduler service) 20,480 4,000,000 Size of the scheduler information log specified in environment settings
(10,240)
/var/opt/jp1ajs2/log/ajs-host-log{1|2}.log Operating information related to jobnets, jobs, and scheduler services (when scheduler information is logged for the entire host) 20,480 4,000,000 Size of the scheduler information log for the host specified in the environment settings
(10,240)
ajsinetd internal log#5, #19 /var/opt/jp1ajs2/log/ajsinetd{1|2}.log Internal information related to the network control process#3 256 4,000,000 Size of the ajsinetd internal log
(128)
Trace log#5, #6 /var/opt/jp1ajs2/log/tracelog Trace information and information about operations related to scheduler services and jobnets#3, #8 20,480 2,097,151 Wraparound
Job execution manager log#11 /var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log Trace information related to the job execution control manager process when a job is executed#3 15,360 524,288 Log size specified during log setup
(1,024)
/var/opt/jp1ajs2/log/jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log
Job execution agent log#11 /var/opt/jp1ajs2/log/jpqagtexec{1|2|3|4|5|6|7|8}.log Trace information related to the job execution control agent process when a job is executed#3 4,096 524,288 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagtexeccld{1|2|3|4|5|6|7|8}.log 4,096 524,288 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagtexecdmn{1|2|3|4|5|6|7|8}.log 4,096 524,288 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagtexecmon{1|2|3|4|5|6|7|8}.log 4,096 524,288 Log size specified during log setup
(512)
Job execution client log#11 /var/opt/jp1ajs2/log/jpqcliexec{1|2}.log Execution trace information related to jpqxxxx commands and JpqxxxxAPI functions#3 1,024 524,288 Log size specified during log setup
(512)
Job execution status report log#11 /var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqnfyexec{1|2}.log Trace information related to job execution control communication when a job is executed#3 1,024 524,288 Log size specified during log setup
(512)
Event/action control manager log#7 /var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpomanager{1|2|3|4|5|6}.log Trace information related to the event/action control manager when an event job is executed#3 12,288 16,777,216
(16 gigabytes)
Log size specified during log setup
(2,048)
/var/opt/jp1ajs2/log/jpomanager{1|2|3|4|5|6}.log
/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpomgrsub{1|2|3|4|5|6|7|8}.log 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
/var/opt/jp1ajs2/log/ jpomgrsub{1|2|3|4|5|6|7|8}.log
Event/action control agent log#7 /var/opt/jp1ajs2/log/jpoagent{1|2|3|4|5|6|7|8}.log Trace information related to the event/action control agent when an event job is executed#3 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
/var/opt/jp1ajs2/log/jpoagtsub{1|2|3|4|5|6|7|8}.log 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Event monitoring log#7 /var/opt/jp1ajs2/log/jpoeventwatch{1|2|3|4|5|6|7|8}.log Execution trace information related to the JP1 event monitoring job and log file monitoring job#3 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Event search log#7 /var/opt/jp1ajs2/log/jpoevsearch{1|2}.log Trace information related to event searching before the JP1 event reception monitoring job is executed#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
File monitoring log#7 /var/opt/jp1ajs2/log/jpocwtflMain{1|2|3|4|5|6}.log Execution trace information related to the file monitoring job#3 12,288 16,777,216
(16 gigabytes)
Log size specified during log setup
(2,048)
Execution interval control log#7 /var/opt/jp1ajs2/log/jpocwttmMain{1|2|3|4|5|6}.log Execution trace information related to the execution interval control job#3 1,536 16,777,216
(16 gigabytes)
Log size specified during log setup
(256)
Mail monitoring log#7 /var/opt/jp1ajs2/log/jpocwtmlmain{1|2}.log Execution trace information related to the mail reception monitoring job when the mail linkage function is used#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mail delivery log#7 /var/opt/jp1ajs2/log/jpomailrecv{1|2}.log Execution trace information related to the mail reception monitoring job when the mail delivery function of mail linkage is used#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
NNM linkage log /var/opt/jp1ajs2/log/jpoovlink{1|2}.log#5 Trace information related to monitoring when HP NNM is used#3 512 512 256
Job execution internal log#11 /var/opt/jp1ajs2/log/jpqagent/jpqagt_{00|01|02|03|04|05|06|07}.log --#8 4,096 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagent/jpqmon_{00|01|02|03|04|05|06|07}.log --#8 4,096 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagent/jpqnjpagt_{00|01|02|03|04|05|06|07}.log --#8 4,096 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagent/jpqnjpdata_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Job execution internal log#11 /var/opt/jp1ajs2/log/jpqclient/jpqclient_{00|01|02|03|04|05|06|07|08|09}.log --#8 10,240 1,048,576 Log size specified during log setup
(1,024)
/var/opt/jp1ajs2/log/jpqclient/jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log --#8 10,240 1,048,576 Log size specified during log setup
(1,024)
/var/opt/jp1ajs2/log/jpqclient/jpqnjpdata_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Job execution internal log#11 /var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanager/jpqman_{00|01|02|03}.log --#8 2,048 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqmanager/jpqman_{00|01|02|03}.log
/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanager/jpqmandb_{00|01|02|03}.log --#8 2,048 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqmanager/jpqmandb_{00|01|02|03}.log
/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanager/jpqmannjp_{00|01|02|03}.log --#8 2,048 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqmanager/jpqmannjp_{00|01|02|03}.log
/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqmanager/jpqnjpdata_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqmanager/jpqnjpdata_{00|01}.log
Job execution internal log#11 /var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqnotify/jpqnotify_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqnotify/jpqnotifynjp_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/schedule/scheduler-service-name/jpqnotify/jpqnjpdata_{00|01}.log --#8 1,024 1,048,576 Log size specified during log setup
(512)
Job execution environment database reorganization log /var/opt/jp1ajs2/database/queue/CONDENSE{1|2}.log -- 1,024 1,024 512
Scheduler database reorganization log /var/opt/jp1ajs2/database/schedule/scheduler-service-name/CONDENSE{1|2}.log -- 1,024 1,024 512
Event/action common log#5, #7 /var/opt/jp1base/log/jpocommonerr{1|2}.log --#3 2,048 2,097,152
(2 gigabytes)
Log size specified during log setup
1,024
Event/action common error log#5 /var/opt/jp1base/log/jpoproccomerr{1|2}.log --#3 256 256 128
jajs_migrate command trace log /var/opt/jp1ajs2/log/jajs_migrate_logical-host-name_{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20}.log#24 Trace information related to the command that changes the system environment from JP1/AJS2 to JP1/AJS3 10 200 When the jajs_migrate command is executed
jajs_setup command trace log#3, #5 /var/opt/jp1ajs2/log/jajs_setup_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log Trace information related to the command that specifies environment settings 200 200 When the jajs_setup command is executed
jajs_config command trace log /var/opt/jp1ajs2/log/jajs_config_{1|2}.log Trace information related to the command that specifies an environment setting parameter 1 256 128
jajs_setup_cluster command trace log#3, #5 /var/opt/jp1ajs2/log/jajs_setup_cluster_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#28 Trace information related to the command that configures a cluster environment 200 200 When the jajs_setup_cluster command is executed
jp1ajs2_setup_cluster command trace log#9 /var/opt/jp1ajs2/log/JAJS_SETUP/logical-host-name/jajs_setup.log#10 Trace information related to the command that sets up a logical host#3 10 100 None
jajs_killall.cluster command trace log shared-dircetory/jp1ajs2/log/jajs_killall.cluster_logical-host-name.{1|2|3|4|5}.log Trace information related to the command that kills a process associated with a logical host#3 50 50 When the jajs_killall.cluster command is executed
Queueless log#17 /var/opt/jp1ajs2/log/ajsql-log{1|2}.log Information related to jobs executed by the queueless agent service 16,384 4,000,000 Queueless log file size specified in the environment settings (8,192)
Queueless trace log#5, #18 /var/opt/jp1ajs2/log/tracelog.ql Execution trace information related to queueless jobs and commands related to execution control of queueless jobs#3, #8 15,360 2,097,151 Wraparound
Queueless job execution internal log#22 /var/opt/jp1ajs2/log/ajsqlexeclog#23 Execution trace information related to queueless jobs#3, #8 24,576 2,097,151 Wraparound
/var/opt/jp1ajs2/log/ajsqlexeclog_ftpd 10,240 2,097,151 Wraparound
JP1/AJS3 Console Manager trace log#5, #12 /var/opt/jp1ajs2cm/log/tracelog.cm --#8 3,072 2,097,151 Wraparound
JP1/AJS3 Console Agent trace log#5, #13 /var/opt/jp1ajs2/log/tracelog.ca --#8 3,072 2,097,151 Wraparound
Maintenance log#5 /var/opt/jp1ajs2/log/jajs_maintain_manager{1|2|3|4}.log#14 Information related to database reorganization that is executed during maintenance#3 1,484 1,484 When maintenance is performed
/var/opt/jp1ajs2/log/jajs_maintain_[scheduler-service-name]{1|2|3|4}.log#14 1,484 1,484 When maintenance is performed
Automatic reorganization log#5 /var/opt/jp1ajs2/log/jpqautocond{1|2|3|4}.log#15 Information related to database reorganization that is executed during automatic reorganization#3 764 764 When automatic reorganization is performed
/var/opt/jp1ajs2/log/ajsautocond{1|2|3|4}.log#15 764 764 When automatic reorganization is performed
Definition check log#20 /var/opt/jp1ajs2/log/ajscheck{1|2}.log Information related to definition pre-checks 8,192 4,000,000 Definition check log file size specified in the environment settings
Definition check trace log#16 /var/opt/jp1ajs2/log/tracelog.ch Trace information related to definition pre-checks#8 3,072 2,097,151 Wraparound
Execution log for embedded database operation commands /var/opt/jp1ajs2/log/embdb/ajsembdboplog[embedded-database-setup-ID]{1|2|3|4}.log Information related to the execution of commands for manipulating the embedded database 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbrorg[host-name][scheduler-service-name]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbreclaim[host-name][scheduler-service-name]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbaddarea[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbaddlog[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbstop[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbstart[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbcancel[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbunset[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbbuild[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbsetup[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbstatus[embedded-database-setup-ID]{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbinstl{1|2|3|4}.log 4,096 4,096 1,024
/var/opt/jp1ajs2/log/embdb/ajsembdbuninstl{1|2|3|4}.log 4,096 4,096 1,024
Agent management trace log#5 /var/opt/jp1ajs2/log/ajsagttrace --#3, #8 20,480 20,480 Wraparound
Agent management log /var/opt/jp1ajs2/log/ajsagtmd{1|2}.log Agent information for agent management control 8,192 8,192 4,096
Communication control trace log /var/opt/jp1ajs2/log/tracelog-nw --#3, #8 20,480 20,480 Wraparound

#1
The unit is kilobytes. The value in parentheses is the kilobytes value expressed in gigabytes.

#2
The unit is kilobytes. The value in parentheses in this column indicates the default timing for switching log files.

#3
The format of the logged information is not publicly available outside the company.

#4
You can change the disk space size. To do so, use the jajs_config command to change the value specified in the LOGSIZE environment setting parameter.
For details about how to estimate the required disk space, see 3.4.1 Estimating the size of scheduler log files in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#5
Information is also output to the default directory in a cluster system.

#6
You can change the disk space size by using the ajstrsetsz command.

#7
You can change the disk space size. To do so, see 3.4.3 Estimating the size of the log information output by event jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#8
The information is in binary format and cannot be read.

#9
The jp1ajs2_setup_cluster command trace log contains information that is logged when a logical host is set up. The log size does not increase during operation.

#10
If a logical host already exists and you create another logical host, a log directory is created under the name of the new logical host.

#11
You can change the disk space size. To do so, see 7.1.4 Estimating the size of the logs output by the execution environment for QUEUE jobs and submit jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#12
You can change the disk space size by using the ajscmtrsetsz command. If you do not use the JP1/AJS3 Console Manager function, no trace log file is created.

#13
You can change the disk space size by using the ajscatrsetsz command. If you do not use the JP1/AJS3 Console Agent function, no trace log file is created.

#14
The file names are different in a cluster system:
  1. jajs_maintain_manager_[logical-host-name]{1|2|3|4}.log
  2. jajs_maintain_[scheduler-service-name]_[logical-host-name]{1|2|3|4}.log

#15
The file names are different in a cluster system:
  1. jpqautocond_[logical-host-name]{1|2|3|4}.log
  2. ajsautocond_[logical-host-name]{1|2|3|4}.log

#16
You can change the disk space size by using the ajschktrsetsz command. If you do not use the JP1/AJS3 Check Manager function or the JP1/AJS3 Check Agent function, no trace log file is created.

#17
You can change the disk space size. To do so, change the value specified in the AJSQL_LOGSIZE environment setting parameter. For details about how to estimate the required disk space, see 7.2.1(1) Estimating the size of the queueless log file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#18
You can change the disk space size by using the ajsqltrsetsz command.

#19
You can change the disk space size. To do so, see 2.2 Setting up the scheduler service environment in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

#20
You can change the disk space size. To do so, see 2.5 Setting for the JP1/AJS3 definition pre-check function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

#21
The file names are different in a cluster system:
  shared-disk-name/jp1ajs2/log/schedule/ajs[scheduler-service-ID-number]-log{1|2}.log

#22
You can change the disk space size by using the ajsqlexecsetsz command. For details about this command, see ajsqlexecsetsz in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
For details about how to estimate the required disk space, see 7.2.1(3) Estimating the size of the internal execution logs for queueless jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#23
The file name is different in a cluster system:
  /var/opt/jp1ajs2/log/ajsqlexeclog-[logical-host-name]
If the full path name is 256 bytes or more, [logical-host-name] becomes the first 30 bytes of the logical host name.

#24
The value n starts at 1 and is then incremented. The file with the largest number contains the latest execution result.
 

Table 1-9 Log files and directories in JP1/AJS3 - Agent (for UNIX)

Log name Log file and directory names Logged information Default disk space#1 Maximum disk space#1 Timing for switching files#2
System management log /var/opt/jp1ajs2/log/JAJS_SPMD{1|2|3}.log Trace information related to starting, stopping, and checking the status of the JP1/AJS3 service#3 384 384 128
/var/opt/jp1ajs2/log/JAJS_SPMD_COMMAND{1|2|3}.log 384 384 128
Job execution agent log#9 /var/opt/jp1ajs2/log/jpqagtexec{1|2|3|4|5|6|7|8}.log Trace information related to the job execution control agent process when a job is executed#3 4,096 524,288 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagtexeccld{1|2|3|4|5|6|7|8}.log 4,096 524,288 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagtexecdmn{1|2|3|4|5|6|7|8}.log 4,096 524,288 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagtexecmon{1|2|3|4|5|6|7|8}.log 4,096 524,288 Log size specified during log setup
(512)
Job execution client log#9 /var/opt/jp1ajs2/log/jpqcliexec{1|2}.log Execution trace information related to jpqxxxx commands and JpqxxxxAPI functions#3 1,024 524,288 Log size specified during log setup
(512)
Event/action control agent log#4 /var/opt/jp1ajs2/log/jpoagent{1|2|3|4|5|6|7|8}.log Trace information related to the event/action control agent when an event job is executed#3 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
/var/opt/jp1ajs2/log/jpoagtsub{1|2|3|4|5|6|7|8}.log 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Event monitoring log#4 /var/opt/jp1ajs2/log/jpoeventwatch{1|2|3|4|5|6|7|8}.log Execution trace information related to the JP1 event monitoring job and log file monitoring job#3 8,192 16,777,216
(16 gigabytes)
Log size specified during log setup
(1,024)
Event search log#4 /var/opt/jp1ajs2/log/jpoevsearch{1|2}.log Trace information related to event searching before the JP1 event reception monitoring job is executed#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
File monitoring log#4 /var/opt/jp1ajs2/log/jpocwtflMain{1|2|3|4|5|6}.log Execution trace information related to the file monitoring job#3 12,288 16,777,216
(16 gigabytes)
Log size specified during log setup
(2,048)
Execution interval control log#4 /var/opt/jp1ajs2/log/jpocwttmMain{1|2|3|4|5|6}.log Execution trace information related to the execution interval control job#3 1,536 16,777,216
(16 gigabytes)
Log size specified during log setup
(256)
Mail monitoring log#4 /var/opt/jp1ajs2/log/jpocwtmlmain{1|2}.log Execution trace information related to the mail reception monitoring job when the mail linkage function is used#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
Mail delivery log#4 /var/opt/jp1ajs2/log/jpomailrecv{1|2}.log Execution trace information related to the mail reception monitoring job when the mail delivery function of mail linkage is used#3 256 16,777,216
(16 gigabytes)
Log size specified during log setup
(128)
NNM linkage log /var/opt/jp1ajs2/log/jpoovlink{1|2}.log#6 Trace information related to monitoring when HP NNM is used#3 512 512 256
Job execution internal log#9 /var/opt/jp1ajs2/log/jpqagent/jpqagt_{00|01|02|03|04|05|06|07}.log --#5 4,096 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagent/jpqmon_{00|01|02|03|04|05|06|07}.log --#5 4,096 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagent/jpqnjpagt_{00|01|02|03|04|05|06|07}.log --#5 4,096 1,048,576 Log size specified during log setup
(512)
/var/opt/jp1ajs2/log/jpqagent/jpqnjpdata_{00|01}.log --#5 1,024 1,048,576 Log size specified during log setup
(512)
Job execution internal log#9 /var/opt/jp1ajs2/log/jpqclient/jpqclient_{00|01|02|03|04|05|06|07|08|09}.log --#5 10,240 1,048,576 Log size specified during log setup
(1,024)
/var/opt/jp1ajs2/log/jpqclient/jpqclientnjp_{00|01|02|03|04|05|06|07|08|09}.log --#5 10,240 1,048,576 Log size specified during log setup
(1,024)
/var/opt/jp1ajs2/log/jpqclient/jpqnjpdata_{00|01}.log --#5, #8 1,024 1,048,576 Log size specified during log setup
(512)
Event/action common log#4, #6 /var/opt/jp1base/log/jpocommonerr{1|2}.log --#3 2,048 2,097,152
(2 gigabytes)
Log size specified during log setup
(1,024)
Event/action common error log#6 /var/opt/jp1base/log/jpoproccomerr{1|2}.log --#3 256 256 128
jajs_config command trace log /var/opt/jp1ajs2/log/jajs_config_{1|2}.log Trace information related to the command that specifies an environment setting parameter 1 256 128
jajs_setup_cluster command trace log#3, #6 /var/opt/jp1ajs2/log/jajs_setup_cluster_{01|02|03|04|05|06|07|08|09|10|11|12|13|14|15|16|17|18|19|20}.log#28 Trace information related to the command that configures a cluster environment 200 200 When the jajs_setup_cluster command is executed
jp1ajs2_setup_cluster command trace log#7 /var/opt/jp1ajs2/log/JAJS_SETUP/logical-host-name/jajs_setup.log#8 Trace information related to the command that sets up a logical host#3 10 100 None
jajs_killall.cluster command trace log shared-directory/jp1ajs2/log/jajs_killall.cluster_logical-host-name.{1|2|3|4|5}.log Trace information related to the command that kills a process associated with a logical host#3 50 50 When jajs_killall.cluster is executed
Queueless log#11 /var/opt/jp1ajs2/log/ajsql-log{1|2}.log Information related to the jobs executed by the queueless agent service 16,384 4,000,000 Queueless log file size specified in the environment settings (8,192)
Queueless trace log#6, #12 /var/opt/jp1ajs2/log/tracelog.ql Execution trace information related to queueless jobs and commands related to execution control of queueless jobs#3, #5 15,360 2,097,151 Wraparound
Queueless job execution internal log#14 /var/opt/jp1ajs2/log/ajsqlexeclog#15 Execution trace information related to queueless jobs#3, #5 24,576 2,097,151 Wraparound
Definition check log#13 /var/opt/jp1ajs2/log/ajscheck{1|2}.log Information related to definition pre-checks 8,192 4,000,000 Definition check log file size specified in the environment settings
Definition check trace log#10 /var/opt/jp1ajs2/log/tracelog.ch Trace information related to definition pre-checks#8 3,072 2,097,151 Wraparound

#1
The unit is kilobytes. The value in parentheses is the kilobytes value expressed in gigabytes.

#2
The unit is kilobytes. The value in parentheses in this column indicates the default timing for switching log files.

#3
The format of the logged information is not publicly available outside the company.

#4
You can change the disk space size. To do so, see 3.4.3 Estimating the size of the log information output by event jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#5
The information is in binary format and cannot be read.

#6
Information is also output to the default directory in a cluster system.

#7
The jp1ajs2_setup_cluster command trace log contains information that is logged when a logical host is set up. The log size does not increase during operation.

#8
If a logical host already exists and you create another logical host, a log directory is created under the name of the new logical host.

#9
You can change the disk space size. To do so, see 7.1.4 Estimating the size of the logs output by the execution environment for QUEUE jobs and submit jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#10
You can change the disk space size by using the ajschktrsetsz command. If you do not use the JP1/AJS3 Check Agent function, no trace log file is created.

#11
You can change the disk space size. To do so, change the value specified in the AJSQL_LOGSIZE environment setting parameter. For details about how to estimate the required disk space, see 7.2.1(1) Estimating the size of the queueless log file in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#12
You can change the disk space size by using the ajsqltrsetsz command.

#13
You can change the disk space size. To do so, see 2.5 Setting for the JP1/AJS3 definition pre-check function in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 2.

#14
You can change the disk space size by using the ajsqlexecsetsz command. For details about this command, see ajsqlexecsetsz in 3. Commands Used for Special Operation in the manual Job Management Partner 1/Automatic Job Management System 3 Command Reference 2.
For details about how to estimate the required disk space, see 7.2.1(3) Estimating the size of the internal execution logs for queueless jobs in the Job Management Partner 1/Automatic Job Management System 3 System Design (Configuration) Guide.

#15
The file name is different in a cluster system:
  /var/opt/jp1ajs2/log/ajsqlexeclog-[logical-host-name]
If the full path name is 256 bytes or more, [logical-host-name] becomes the first 30 bytes of the logical host name.

[Contents][Back][Next]


[Trademarks]

Copyright (C) 2009, 2010, Hitachi, Ltd.
Copyright (C) 2009, 2010, Hitachi Solutions, Ltd.