2.9.2 Details of the environment setting parameters for JP1/AJS3 shared information
- Organization of this subsection
(1) "LARGEFILEUSE" = "{yes|no}"
Use this parameter to specify whether the file monitoring job monitors large files and the judgment job determines if there are any large files.
For details, see 6.3.17 Enabling monitoring of a large file in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.3.12 Enabling monitoring of a large file in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).
- Specifiable values
-
- yes
-
The file monitoring job monitors files larger than 2 GB and the judgment job determines if there are any files larger than 2 GB.
- no
-
The file monitoring job cannot monitor files that are larger than 2 GB. If you specify no, but specify a file larger than 2 GB as a monitoring target, an error message is output to the integrated trace log when execution of the file monitoring job terminates abnormally. For this reason, do not specify a file larger than 2 GB as a monitoring target.
The judgment job cannot determine if there are any files larger than 2 GB. If you specify a file larger than 2 GB in a judgment condition when you have specified no, the judgment job determines that there are no large files.
- Default value
-
no
- Recommended value
-
Set the value appropriate for the operating environment.
- When the setting takes effect
-
After JP1/AJS3 is restarted
(2) "SYSLOGJOBMSG" = "{none|error}"
Use this parameter to specify whether to also output error messages appearing during the execution of jobs to syslog.
For details, see 15.6.1 Settings for outputting error messages for jobs to syslog in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.
- Specifiable values
-
- none
-
Error messages appearing during the execution of jobs are not output to syslog. The status of JP1/AJS3 is monitored by the integrated trace log.
- error
-
Error messages appearing during the execution of jobs are output to the syslog file, which is used to monitor the error status of JP1/AJS3. However. even if you specify this value, you must not stop the integrated trace log process.
If you specify error for this parameter, a message reporting abnormal job termination (KAVS0265-E) is output to syslog, regardless of whether the scheduler service setting contains JOBSYSLOG (outputs, to syslog, messages related to starting and ending a job).
The following table lists the messages that are output based on the values specified for the SYSLOGJOBMSG and JOBSYSLOG environment setting parameters.
- Legend:
-
--: Not applicable
- Default value
-
none
- Recommended value
-
Default value
- When the setting takes effect
-
After JP1/AJS3 is restarted
(3) "MACROCHANGEFAIL" = "{yes|no}"
Use this parameter to specify whether to set Failed to start as the status if expansion of the passing information in a macro variable fails when a job is executed.
For details, see 6.2.10 Setting the action to be taken if the value of a macro variable cannot be passed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows) or 15.2.10 Setting the action to be taken if the value of a macro variable cannot be passed in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX).
- Specifiable values
-
- yes
-
If the expansion of the passing information in a macro variable fails when a job is executed, the status set is Failed to start, and an error message is output to the integrated trace log and as execution result details so that you can check the macro variable that could not be expanded.
- no
-
Even if the expansion of the passing information in a macro variable fails when a job is executed, the system treats the information defined in the macro variable as a character string and continues processing.
- Default value
-
no
- Recommended value
-
Default value
- When the setting takes effect
-
After JP1/AJS3 is restarted
(4) "ADMACLIMIT" = "{yes|no}"
Use this parameter to set the operation permission for units for JP1 users mapped to OS users with administrator permissions or superuser permissions.
- Specifiable values
-
- yes
-
Access is controlled according to the permission level set for a JP1 user irrespective of the OS user to whom the JP1 user is mapped.
- no
-
A JP1 user mapped to an OS user with administrator permissions or superuser permissions can perform all operations irrespective of the permission level.
- Default value
-
no
- Recommended value
-
Set the value appropriate for the operating environment.
- When the setting takes effect
-
After JP1/AJS3 is restarted
(5) "CONNECTIONRESTRICTION" = "{none|manager|agent|all}"
Use this parameter to specify whether the connection source restriction function for restricting connection to JP1/AJS3 is to be enabled or disabled.
If the database configuration of JP1/AJS3 is a compatible ISAM configuration, the setting of this environment setting parameter is ignored.
- Specifiable values
-
- none
-
The setting in the manager connection permission configuration file and the setting in the agent connection permission configuration file are disabled.
- manager
-
The setting in the manager connection permission configuration file is enabled, and the setting in the agent connection permission configuration file is disabled.
This value cannot be specified in JP1/AJS3 - Agent.
- agent
-
In JP1/AJS3 - Manager, the setting in the agent connection permission configuration file is enabled, and the setting in the manager connection permission configuration file is disabled.
In JP1/AJS3 - Agent, the setting in the agent connection permission configuration file is enabled.
- all
-
In JP1/AJS3 - Manager, the setting in the manager connection permission configuration file and the setting in the agent connection permission configuration file are enabled.
In JP1/AJS3 - Agent, the setting in the agent connection permission configuration file is enabled.
- Default value
-
none
- Recommended value
-
Set the value appropriate for the operating environment.
- When the setting takes effect
-
If both the JP1/AJS3 service and the JP1/AJS3 Queueless Agent service have stopped, when either service restarts
- Cautionary notes
-
-
Change this environment setting parameter if both the JP1/AJS3 service and the JP1/AJS3 Queueless Agent service have stopped, and then, after making the change, start the services.
If you changed this environment setting parameter while either the JP1/AJS3 service or the JP1/AJS3 Queueless Agent service was running, stop both services and then start them.
-
If you specify a value other than none for this environment setting parameter, and the environment settings file storage folder does not contain the connection permission configuration file corresponding to the specified value, or the connection permission configuration file cannot be read, the JP1/AJS3 service or the JP1/AJS3 Queueless Agent service terminates abnormally.
-
(6) "LOGIPV6INFOALL" = "{yes|no}"
Use this parameter to specify whether to add IPv6 addresses to the messages output to logs such as the integrated trace log, event log, and syslog and to messages detailing execution results.
The IPv6 addresses are added to the messages shown below. For details about messages, see the manual Job Management Partner 1/Automatic Job Management System 3 Messages 1.
KAVT0009-E, KAVT0145-E, KAVT0268-W, KAVT0293-W, KAVT0559-E, KAVT0606-W, KAVT0612-W, KAVT0613-W, KAVT8343-W
- Specifiable values
-
- yes
-
IPv6 addresses are added to the messages.
- no
-
IPv6 addresses are not added to the messages.
- Default value
-
no
- Recommended value
-
Default value
- When the setting takes effect
-
After JP1/AJS3 is restarted