1.2.4 List of log files and directories
- Organization of this subsection
(1) Log files and directories in Windows
Table 1-4 to Table 1-7 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:
-
Mgr_Path
-
If the installation folder is the default installation folder or is in a folder protected by the system#1:
%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2
-
If the installation folder is other than the above:
JP1/AJS3 - Manager-installation-folder
The default installation folder is system-drive\Program Files (x86)\HITACHI\jp1ajs2.
-
-
Agt_Path
-
If the installation folder is the default installation folder or is in a folder protected by the system#1:
%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2
-
If the installation folder is other than the above:
JP1/AJS3 - Agent-installation-folder
The default installation folder is system-drive\Program Files (x86)\HITACHI\jp1ajs2.
-
-
View_Path
%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS2V
-
Web_Path
-
If the installation folder is the default installation folder or is in a folder protected by the system#1:
%ALLUSERSPROFILE%#2\Hitachi\JP1\JP1_DEFAULT\JP1AJS3web
-
If the installation folder is other than the above:
JP1/AJS3 - Web Console-installation-folder
The default installation folder is system-drive\Program Files\HITACHI\jp1ajs3WEB.
-
- #1
-
A folder protected by the system is the path to a folder in any of the following:
-
system-drive\Windows
-
system-drive\Program Files
-
system-drive\Program Files (x86)
-
- #2
-
The default for %ALLUSERSPROFILE% is system-drive\ProgramData.
In a cluster system, unless otherwise specified, make the substitutions shown in the following table for the indicated abbreviations.
Log output folder in a cluster system |
|
---|---|
Mgr_Path |
shared-disk-name\jp1ajs2 |
Agt_Path |
shared-disk-name\jp1ajs2 |
Web_Path |
shared-disk-name\jp1ajs3web |
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.
- #1
-
The unit is kilobytes unless otherwise specified. 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 JP1/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 JP1/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 vary depending on how JP1/AJS3 has been installed.
-
If JP1/AJS3 09-00 or later has been installed as a new installation:
jpqmanexec{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.log
-
If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_man{1|2|3|4|5|6|7|8|9|10|11|12|13|14|15}.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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #11
-
You can change the disk space size. To do so, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #12
-
In a cluster system, the file names are different:
-
jajs_maintain_manager_[logical-host-name]{1|2|3|4}.log
-
jajs_maintain_[scheduler-service-name]_[logical-host-name]{1|2|3|4}.log
-
- #13
-
In a cluster system, the file names are different:
-
jpqautocond_[logical-host-name]{1|2|3|4}.log
-
schedule\ajsautocond_[logical-host-name]{1|2|3|4}.log
-
- #14
-
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.
- #15
-
You can change the disk space size. To do so, use the jajs_config 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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #16
-
You can change the disk space size by using the ajsqltrsetsz command.
- #17
-
In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.
-
If JP1/AJS3 09-00 or later has been installed as a new installation:
jpqagtexec{1|2|3|4|5|6|7|8}.log
-
If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_agt{1|2|3|4|5|6|7|8}.log
-
- #18
-
In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.
-
If JP1/AJS3 09-00 or later has been installed as a new installation:
jpqagtexecmon{1|2|3|4|5|6|7|8}.log
-
If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_agtmon{1|2|3|4|5|6|7|8}.log
-
- #19
-
In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.
-
If JP1/AJS3 09-00 or later has been installed as a new installation:
jpqcliexec{1|2}.log
-
If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system.
jpqExecLog_cli{1|2}.log
-
- #20
-
You can change the disk space size. To do so, see 20.7 Setting for the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide.
- #21
-
You can change the disk space size. To do so, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #22
-
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.
- #23
-
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}\JP1AOMMANAGER] and [{JP1_DEFAULT|logical-host-name}\JP1AOMAGENT] definition keys.
- #24
-
You can change the disk space size by using the ajsqlexecsetsz command. For details about this command, see ajsqlexecsetsz in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.
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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #25
-
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.
- #26
-
The latest execution result is output to the log file numbered 01. When the command is executed, log files are renamed by incrementing their numbers by 1, and a new log file with 01 is created. If the command is executed when a log file with the largest allowed number already exists, the log information in that log file is discarded.
- #27
-
The size of the file increases without limit. Save or delete information in the file as necessary.
- #28
-
The latest execution result is output to the log file with the largest number. If the command is executed when a log file with the largest allowed number already exists, the information in the log file numbered 01 is discarded.
- #29
-
Information is also output to a folder on the physical host in a cluster system. Therefore, you can change the value of Mgr_Path even in a cluster system by specifying the value in the WaitInfFileOutDir environment setting parameter for the [JP1_DEFAULT\JP1AOMAGENT] definition key.
- #30
-
You can change the disk space size. To do so, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #31
-
If a relay agent exists, log data is output to the relay agent. If a relay agent does not exist, log data is output to the manager host.
- #32
-
You can change the disk space size. To do so, see 20.3 Setting up the system management environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #1
-
The unit is kilobytes unless otherwise specified. 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 JP1/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 3.4.5 Estimating the size of the logs output by execution in the JP1/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 for the AJSQL_LOGSIZE environment setting parameter by using the jajs_config command.
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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #10
-
You can change the disk space size by using the ajsqltrsetsz command.
- #11
-
In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.
-
If JP1/AJS3 09-00 or later has been installed as a new installation:
jpqagtexec{1|2|3|4|5|6|7|8}.log
-
If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system
jpqExecLog_agt{1|2|3|4|5|6|7|8}.log
-
- #12
-
In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.
-
If JP1/AJS3 09-00 or later has been installed as a new installation:
jpqagtexecmon{1|2|3|4|5|6|7|8}.log
-
If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system
jpqExecLog_agtmon{1|2|3|4|5|6|7|8}.log
-
- #13
-
In a cluster system, the file names vary depending on how JP1/AJS3 has been installed.
-
If JP1/AJS3 09-00 or later has been installed as a new installation:
jpqcliexec{1|2}.log
-
If JP1/AJS3 has been installed as an upgrade installation from JP1/AJS2:
If logical hosts have been configured before the upgrade installation, the file names used with JP1/AJS2 are inherited as the log file names in the cluster system
jpqExecLog_cli{1|2}.log
-
- #14
-
You can change the disk space size. To do so, see 20.7 Setting for the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide.
- #15
-
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.
- #16
-
You can change the disk space size by using the ajsqlexecsetsz command. For details about this command, see ajsqlexecsetsz in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.
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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #17
-
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.
- #18
-
The latest execution result is output to the log file numbered 01. When the command is executed, log files are renamed by incrementing their numbers by 1, and a new log file with 01 is created. If the command is executed when a log file with the largest allowed number already exists, the log information in that log file is discarded.
- #19
-
Information is also output to a folder on the physical host in a cluster system. Therefore, you can change the value of Agt_Path even in a cluster system by specifying the value in the WaitInfFileOutDir environment setting parameter for the [JP1_DEFAULT\JP1AOMAGENT] definition key.
- #20
-
You can change the disk space size. To do so, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #21
-
If a relay agent exists, log data is output to the relay agent. If a relay agent does not exist, log data is output to the manager host.
- #22
-
You can change the disk space size. To do so, see 20.3 Setting up the system management environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #23
-
This log file is used exclusively by JP1/AJS3 - Agent Minimal Edition. JP1/AJS3 - Agent does not output log data to this file.
- #24
-
You can change the disk space size. To do so, see G.2(3) Estimating the job execution history log file in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #1
-
The unit is kilobytes unless otherwise specified.
- #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.
The Default disk space and Maximum disk space columns indicate the disk space that is allocated to a log file if only one unit is started.
- #4
-
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.
- #5
-
The value in {1|2} indicates the log file number, which is fixed at 2.
If the size of the file specified with 1 reaches the upper limit, data continues to be output to the file specified by 2. If the size of the file specified by 2 also reaches the upper limit, the information in the file specified by 1 is deleted and data continues to be output to the file specified by 1.
- #6
-
If the multiuser remote desktop connection function is enabled, the output destination changes to the folder below. Note that OS-user-name does not include domain information.
View_Path\log\OS-user-name
For details about the multiuser remote desktop connection function, see 11.2.7 Allowing multiple users to concurrently use JP1/AJS3 - View via remote desktop connections in the JP1/Automatic Job Management System 3 Operator's Guide.
- #1
-
The unit is kilobytes unless otherwise specified.
- #2
-
You can change the disk space size. To do so, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
(2) Log files and directories in UNIX
Table 1-9 and Table 1-11 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.
Value in Table 1-9 and Table 1-11 |
Log output directory in a cluster system |
---|---|
/var/opt/jp1ajs2/ |
shared-disk-name/jp1ajs2 |
/var/opt/jp1ajs3web/ |
shared-disk-name/jp1ajs3web |
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.
- #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 JP1/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 JP1/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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #12
-
You can change the disk space size. To do so, see 3.4.5 Estimating the size of the logs output by execution in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #13
-
The file names are different in a cluster system:
-
jajs_maintain_manager_[logical-host-name]{1|2|3|4}.log
-
jajs_maintain_[scheduler-service-name]_[logical-host-name]{1|2|3|4}.log
-
- #14
-
The file names are different in a cluster system:
-
jpqautocond_[logical-host-name]{1|2|3|4}.log
-
ajsautocond_[logical-host-name]{1|2|3|4}.log
-
- #15
-
You can change the disk space size by using the ajscmtrsetsz command. If you do not use the JP1/AJS3 Console Manager function or the JP1/AJS3 Console Agent function, no trace log file is created.
- #16
-
You can change the disk space size. To do so, change the value specified for the AJSQL_LOGSIZE environment setting parameter by using jajs_config command. 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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #17
-
You can change the disk space size by using the ajsqltrsetsz command.
- #18
-
You can change the disk space size. To do so, see 20.4 Setting up the scheduler service environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #19
-
You can change the disk space size. To do so, see 20.7 Setting for the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide.
- #20
-
You can change the disk space size by using the ajsqlexecsetsz command. For details about this command, see ajsqlexecsetsz in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.
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 JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #21
-
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.
- #22
-
The latest execution result is output to the log file numbered 01. When the command is executed, log files are renamed by incrementing their numbers by 1, and a new log file with 01 is created. If the command is executed when a log file with the largest allowed number already exists, the log information in that log file is discarded.
- #23
-
The size of the file increases without limit. Save or delete information in the file as necessary.
- #24
-
The latest execution result is output to the log file with the largest number. If the command is executed when a log file with the largest allowed number already exists, the information in the log file numbered 01 is discarded.
- #25
-
You can change the disk space size. To do so, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #26
-
If a relay agent exists, log data is output to the relay agent. If a relay agent does not exist, log data is output to the manager host.
- #27
-
You can change the disk space size. To do so, see 20.3 Setting up the system management environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #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 JP1/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 JP1/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 for the AJSQL_LOGSIZE environment setting parameter by using jajs_config command. 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 JP1/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 20.7 Setting for the JP1/AJS3 definition pre-check function in the JP1/Automatic Job Management System 3 Configuration Guide.
- #14
-
You can change the disk space size by using the ajsqlexecsetsz command. For details about this command, see ajsqlexecsetsz in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.
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 JP1/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.
- #16
-
The latest execution result is output to the log file numbered 01. When the command is executed, log files are renamed by incrementing their numbers by 1, and a new log file with 01 is created. If the command is executed when a log file with the largest allowed number already exists, the log information in that log file is discarded.
- #17
-
You can change the disk space size. To do so, see 20.10 Setting up the queueless job execution environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #18
-
If a relay agent exists, log data is output to the relay agent. If a relay agent does not exist, log data is output to the manager host.
- #19
-
You can change the disk space size. To do so, see 20.3 Setting up the system management environment in the JP1/Automatic Job Management System 3 Configuration Guide.
- #20
-
This log file is used exclusively by JP1/AJS3 - Agent Minimal Edition. JP1/AJS3 - Agent does not output log data to this file.
- #21
-
You can change the disk space size. To do so, see G.2(3) Estimating the job execution history log file in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.
- #1
-
The unit is kilobytes unless otherwise specified.
- #2
-
You can change the disk space size. To do so, see 4.6.1(1) Log sizes and the number of log files output by the Web Console server in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.