C.2 Environment setting parameters whose defaults were changed to recommended values in version 11-00

This section describes the environment setting parameters for which defaults were changed to recommended values in JP1/AJS3 version 11-00.

The table below describes the actions to be taken and the conditions to be applied due to the use of the defaults (recommended values) in version 11-00 or later. Using the information as criteria, determine whether to use defaults for operation, and change parameter settings as needed.

Organization of this subsection

(1) Environment settings related to the scheduler service
(2) Environment settings related to the job execution environment
(3) Environment settings related to event/action control

(1) Environment settings related to the scheduler service

The table below describes the environment setting parameters (among those related to the scheduler service) for which defaults were changed to recommended values in JP1/AJS3 version 11-00.

Cautionary note:: In the case of performing an upgrade installation to upgrade JP1/AJS3 version 10-50 or earlier to JP1/AJS3 version 11-00 or later, the defaults of the environment setting parameters of the old version are inherited by the new version. If, however, a scheduler service is added, the defaults (recommended values) in version 11-00 or earlier are applied only to the new scheduler service. When you use JP1/AJS3 version 11-00 or later and add a scheduler service, review the parameter settings if you want to apply the settings provided by version 10-50 or earlier.

Table C‒4: Environment setting parameters related to the scheduler service
No.	Definition key	Environment setting parameter	Default in version 10-50 or earlier	Default in version 11-00 or later	Operation and conditions of using the defaults in version 11-00 or later
1	`JP1_DEFAULT\JP1AJSMANAGER\scheduler-service-name`	`"UNITDEFDIVIDEUPDATE"`	`no`	`yes`	When units are operated, data writing to the database is performed in a split manner. This can avoid errors resulting from a shortage of exclusive resources. When `no` is specified for this parameter in an environment of version 10-50 or earlier, no problem will occur even by using the old setting.
2	`JP1_DEFAULT\JP1AJSMANAGER\scheduler-service-name`	`"AJSPRINTSORTUNITINF"`	`no`	`yes`	The relation line information output by using the `ajsprint` command is sorted. This function is convenient for comparing output results with each other. If you want to use the output format applied in version 10-50 or earlier, specify `no`. for this parameter.

To Page Top

(2) Environment settings related to the job execution environment

The table below lists the environment setting parameters (among those related to the job execution environment) for which defaults were changed to recommended values in JP1/AJS3 version 11-00.

Cautionary note:: In the case of performing an upgrade installation to upgrade JP1/AJS3 version 10-50 or earlier to JP1/AJS3 version 11-00 or later, the defaults of the environment setting parameters of the old version are inherited by the new version. In addition, regarding the defaults of the environment setting parameters that were added in version 11-00, the defaults will be set so that the product behaves in the same way as it did prior to the upgrade. Review the settings to change them to recommended values.

Table C‒5: Environment setting parameters related to the job execution environment
No.	Definition key	Environment setting parameter	Default in version 10-50 or earlier	Default in version 11-00 or later	Operation and conditions of using the defaults in version 11-00 or later
1	`JP1_DEFAULT\JP1AJS2\SCHEDULER\QUEUE\MANAGER\Job` `JP1_DEFAULT\JP1NBQMANAGER\Job`	`"ReceiveFileSizeStatus"`	`0`	`3`	If the size of received files reaches the upper limit, file reception processing is stopped. You do not need to change the setting from the default when the size of the files received at job execution does not exceed 5 megabytes^#1 during operation. Use the default as is. If the size of the files received at job execution exceeds 5 megabytes^#1, the data exceeding the upper-limit size might be discarded or not received. Also, if a passing information setting job is executed by using a standard output file over 5 megabytes^#1, information might not be inherited correctly. See 6.2.7 Placing restrictions on file reception (in Windows) and 15.2.7 Placing restrictions on file reception (in UNIX), and change the setting as needed.
2	`JP1_DEFAULT\JP1NBQAGENT\Job`	`"LoadUserProfile"`^#2	`0`	`1`	The user profile information about the OS user who executes a job is read when the job is executed. Specify `1` for operation to avoid the abnormal end of a job that requires a user profile.
3		`"IsAccessTokenCache"`^#2	`0`	`2`	Access tokens are reused during job execution. A desktop heap area is allocated for each OS user. Specify `1` or `2` for this parameter when the value of the `LoadUserProfile` environment setting parameter is `1`.
4		`"MergeEnvMode"`^#2	`0`	`1`	If the setting of a system environment variable overlaps the setting of an environment variable in the job definition, the environment variable in the job definition is ignored. Specify `0` for this parameter when you have specified environment variables for the job and want to operate the job in the same way as the job in the old environment or on other hosts in the system.
5	`JP1_DEFAULT\JP1NBQAGENT\Network`	`"NotfyJobStateCount"`	`288`	`2`	This parameter specifies the number of retries of job result file transmission. Use the default to prevent job execution from being delayed by the load of communication retries that could last for a long time.
6	`JP1_DEFAULT\JP1NBQCLIENT\Process`	`"PassingInfoUsePreRc"`	`1`	`0`	When a passing information setting job is used, this parameter is used to set the return value of the passing information setting job itself, regardless of the return value of the preceding job. Specify `1` for this parameter when you use a passing information setting job and want to operate the job in the same way as the job in the old environment or on other hosts in the system.
7	`JP1_DEFAULT\JP1NBQAGENT\Job`	`"SendFileSizeStatus"`	--^#3	`3`	If the size of transmitted files reaches the upper limit, file transmission processing is stopped. You do not need to change the setting from the default when the size of the files transmitted at job execution does not exceed 3 megabytes^#4 during operation. Use the default as is. If the size of the files transmitted at job execution exceeds 3 megabytes^#4, the data exceeding the upper-limit size might be discarded or not transmitted. Also, if a passing information setting job is executed by using a standard output file over 3 megabytes^#4, information might not be inherited correctly. See 6.2.27 Placing restrictions on file transmission (in Windows) and 15.2.24 Placing restrictions on file transmission (in UNIX), and change the setting as needed.

#1: You can set the upper limit of the size of received files in the LimitReceiveFileSize environment setting parameter. The default is 5 (megabytes). If the parameter setting has been changed from the default, replace the default (5 megabytes) with the new value in the description herein.
#2: Only for Windows
#3: Because the environment setting parameter was added in version 11-00, no value is set, but the product behaves as if 0 is set.
#4: You can set the upper limit of the size of received files in the LimitSendFileSize environment setting parameter. The default is 3 (megabytes). If the parameter setting has been changed from the default, replace the default (3 megabytes) with the new value in the description herein.

To Page Top

(3) Environment settings related to event/action control

The table below lists the environment setting parameters (among those related to event/action control) for which defaults were changed to recommended values in JP1/AJS3 version 11-00.

Cautionary note:: In the case of performing an upgrade installation to upgrade JP1/AJS3 version 10-50 or earlier to JP1/AJS3 version 11-00 or later, the defaults of the environment setting parameters of the old version are inherited by the new version. Review the settings to change them to recommended values.

Table C‒6: Environment setting parameters related to event/action control
No.	Definition key	Environment setting parameter	Default in version 10-50 or earlier	Default in version 11-00 or later	Operation and conditions of using the defaults in version 11-00 or later
1	`JP1_DEFAULT\JP1AJS2\SCHEDULER\EV\MANAGER` `JP1_DEFAULT\JP1AOMMANAGER` `JP1_DEFAULT\JP1AOMAGENT`	`"FileWriteMode"`	`nosync`	`sync`	Synchronized writing is executed whenever a file is updated. This method of writing increases reliability but lowers system performance. This setting is appropriate for the operations in which priority is given to reliability, such as in the case of cluster operations. The setting of this parameter must be unified in the system (in the manager and all agents).
2		`"ResolveAgentInfo"`	`host`	`exec`	With this setting of this parameter, you can omit the operation on the manager host required when the IP address of an agent host is changed. You do not need to restart the JP1/AJS3 service in the manager host. The setting of this parameter must be unified in the system (in the manager and all agents).
3	`JP1_DEFAULT\JP1AOMAGENT`	`"RetryAgtStartNotification"`	`N`	`Y`	If transmission of a startup notification fails, it is retried. Always specify `Y` (enabling) for this parameter because this function serves to automatically recover the system from an error.

To Page Top