20.5.2 Details of the environment setting parameters for the job execution environment

(1) WorkPath (for manager process)

The name of the work directory used when the manager process is running. Use this parameter to specify the name of the work directory used to manage job execution. Specify a full path name.

If there is not enough space on the disk that contains the default directory, specify a directory on a disk that has enough space.

Format

"WorkPath" = "name-of-work-directory-used-when-manager-process-is-running"

Specifiable values

A character string of no more than 180 bytes

Default value

In Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

• For a physical host:

  %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp

  The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

  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)

• For a logical host:

  shared-folder\jp1ajs2\tmp

In Windows, if the installation folder is other than the above:

• For a physical host:

  JP1/AJS3-Manager-installation-folder\tmp

• For a logical host:

  shared-folder\jp1ajs2\tmp

In UNIX:

• For a physical host:

  /var/opt/jp1ajs2/tmp

• For a logical host:

  shared-directory/jp1ajs2/tmp

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(2) IsHA (for manager process)

Use this parameter to specify the definition for setting up a cluster environment for the job execution control manager process. Specify this parameter only to stop cluster use.

Format

"IsHA" = dword:definition-for-cluster-environment-setup-for-the-manager-process

Specifiable values

0

Specifies to stop cluster use.

1

If you execute setup when operating a cluster system, this value is automatically set to the parameter for the physical and logical hosts.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(3) DatabasePath

Use this parameter to specify the name of the directory used to store the ISAM file, which is the file to which job execution environment information or job information is written. Specify a full path name.

If there is not enough space on the disk that contains the default directory, specify a directory on a disk that has enough space.

Format

"DatabasePath" = "name-of-the-directory-used-to-store-the-database"

Specifiable values

A character string of no more than 180 bytes

Default value

In Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

• For a physical host:

  %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\database\queue

  The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

  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)

• For a logical host:

  shared-folder\jp1ajs2\database\queue

In Windows, if the installation folder is other than the above:

• For a physical host:

  JP1/AJS3-Manager-installation-folder\database\queue

• For a logical host:

  shared-folder\jp1ajs2\database\queue

In UNIX:

• For a physical host:

  /var/opt/jp1ajs2/database/queue

• For a logical host:

  shared-directory/jp1ajs2/database/queue

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

In UNIX:

Do not create a symbolic link for a file created in the directory specified in this parameter. Reorganization will break the link because the file is re-created. If you want to create a symbolic link, use the directory specified in this parameter instead.

Do not use NFS or a network drive as the directory to be specified here.

For this parameter, you cannot specify a directory mounted on an NFS file system or a similar file system connected to a network or a network drive.

To Page Top

(4) PreserveTerm

Use this parameter to specify the number of days that job execution results are retained.

Change this value as necessary if the number of executed jobs will exceed 20,000 before the specified number of retention days (recommended value) expires.

The settings for this parameter are not applied to event jobs.

Format

"PreserveTerm" = dword:number-of-days-job-information-retained

Specifiable values

A hexadecimal value (in days) from 0 to 3E7 (0 to 999 in decimal)

If you specify dword:00000000 (zero days), the execution result information is deleted when execution of the job is complete.

For details about the setting of the retention period for job information when the specified value is 0, see 7.1.9 Setting the retention period for job information in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Default value

dword:00000007 (7 days)

During a new installation and setup of JP1/AJS3, dword:00000001 is set.

Recommended value

dword:00000001 (one day)

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The number of days that job information is retained is the number of days that job information saved in the job execution environment database is retained. If you decrease the number of retention days, there is no effect on the number of saved generations of a jobnet that are managed by the scheduler database.

After you reduce the number of retention days, if a large amount of job information is to be deleted at the next standard time for deleting job information or at JP1/AJS3 service restart, this process might conflict with the job information deletion processing. In such a case, the job execution performance might degrade, or the system load might increase.

Be careful when changing this parameter, such as changing the value if fewer jobs are being executed or gradually reducing the number of retention days for job information.

In a standard configuration, the number of jobs that can be registered in the database for QUEUE jobs and submit jobs is less than 200,000.

The job execution result information that is registered in the database is the result information for the number of jobs executed for the number of retention days plus one more day. For example, if the number of jobs executed in one day is 10,000, and the number of retention days is 10 days, the information for 110,000 jobs is registered.

Specify the number of retention days for job information so that the number of job execution results that are to be registered in the database is less than 200,000.

To Page Top

(5) StandardTime

Use this parameter to specify the time at which job execution result information is to be deleted. Note, however, that the job execution result information is also deleted when the JP1/AJS3 service starts. In this case, the system uses the JP1/AJS3 service start time as the base time to delete all job execution result information that is older than the number of days specified for retaining the information. Thereafter, the system deletes the job execution result information at the time specified in this parameter.

If job execution performance degrades because many jobs are executed while job information is being deleted, change the base time to at time when fewer jobs are being executed.

You can also specify settings so that job information is not deleted when the JP1/AJS3 service is started. For details, see 7.1.10 Setting for disabling deletion of job information when JP1/AJS3 starts in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

The setting for this parameter is not applied to event jobs.

Format

"StandardTime" = dword:standard-time-at-which-job-information-deleted

Specifiable values

Using 0:00 as the base time, specify a relative time in hexadecimal from 0:00 to 23:59 (in minutes).

For example, to set 1:00, specify dword:0000003c (1:00 = 60 minutes).

Default value

dword:00000000 (0:00)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(6) FlashOption

Use this parameter to specify whether to permit synchronous writing when an ISAM file is updated.

Format

"FlashOption" = dword:data-file-update-mode

Specifiable values

0

Data is written to a disk in response to OS buffering. There is no synchronization with JP1/AJS3 processing.

Specify 0 when job execution performance is more important than the reliability of database access in the job execution environment provided by writing data to a disk with OS buffering. However, in a cluster configuration, specifying this value is not recommended because reliability degrades.

1

Synchronous writing is always performed when a file is updated. This writing mode improves reliability, but reduces performance.

Default value

dword:00000001 (synchronization mode)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(7) DeleteFlashOption

Use this parameter to specify whether to delete job information in asynchronous mode.

For details about job information deletion processing, see 7.1.8 Option for deleting job information asynchronously in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Format

"DeleteFlashOption" = dword:asynchronous-option-for-job-information-deletion

Specifiable values

0

Job information is deleted in asynchronous mode.

1

Job information is deleted in synchronous mode.

Default value

dword:00000001 (1 in decimal) (synchronous mode)

During a new installation and setup of JP1/AJS3, 0 is set.

Recommended value

dword:00000000 (0 in decimal) (asynchronous mode)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(8) PreserveMinute

Use this parameter to specify how long you want to retain job information after a job has been executed when 0 is specified as the number of days for retaining job information.

For details about job information deletion processing, see 7.1.9 Setting the retention period for job information in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide or 7.1.8 Option for deleting job information asynchronously in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Format

"PreserveMinute" = dword:retention-period-for-job-information-when-the-number-of-days-for-retaining-job-information-is-0

Specifiable values

A hexadecimal value (in minutes) from 0000000A to 000005A0 (10 to 1,440 in decimal)

Default value

dword:0000000A (10 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(9) StartUpDelete

Use this parameter to specify whether to suppress job information deletion at JP1/AJS3 service startup when 1 or more is specified as the number of days for retaining job information.

For details about job information deletion processing, see 7.1.10 Setting for disabling deletion of job information when JP1/AJS3 starts in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide or 7.1.8 Option for deleting job information asynchronously in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Format

"StartUpDelete" = dword:option-for-suppressing-job-information-deletion-at-JP1/AJS3-service-startup

Specifiable values

0

When the JP1/AJS3 service starts, the processing that deletes job information deletes job information whose retention period (number of days) has expired when the standard time for deleting job information arrives.

When the JP1/AJS3 service starts, job information whose retention period has expired in the period from the standard time for deleting job information to the time that the JP1/AJS3 service started is not deleted.

If job information was not deleted when the previous standard time for deleting job information arrived because the JP1/AJS3 service was not running, job information whose retention period had expired when the base time arrived might remain. If so, only the remaining job information is deleted when the JP1/AJS3 service starts.

1

When the JP1/AJS3 service starts, job information deletion processing deletes all job information whose retention period has expired at the time that the JP1/AJS3 service starts.

When the JP1/AJS3 service starts, job information is also deleted if the retention period of the job information has expired in the period from the standard time for deleting job information to the time that the JP1/AJS3 service started.

If job information was not deleted when the previous standard time for deleting job information arrived because the JP1/AJS3 service was not running, job information whose retention period had expired when the base time arrived might remain. If so, any remaining job information is also deleted when the JP1/AJS3 service starts.

2

Job information deletion processing that occurs when the JP1/AJS3 service starts is suppressed. However, if the JP1/AJS3 service is set to stop at the same time as the standard time for deleting job information, do not specify this value.

Note that if the JP1/AJS3 service is not running when the standard time for deleting job information arrived, job information whose retention period had expired when the base time arrived will never be deleted. As a result, the disk space required by the job execution environment database increases, and this increase might prevent the JP1/AJS3 service from starting, or prevent a job from being executed.

Default value

dword:00000001 (1 in decimal)

During a new installation and setup of JP1/AJS3, 0 is set.

Recommended value

dword:00000000 (0 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(10) ColdStartMode

Use this parameter to specify whether to initialize the job information of the job execution environment database when the JP1/AJS3 service is cold-started.

Format

"ColdStartMode" = "{clear|noclear}"

Specifiable values

clear

The job information of the job execution environment database is initialized when the JP1/AJS3 service is cold-started, unless there has been a scheduler service that has been set to not start automatically.

noclear

The job information of the job execution environment database is not initialized when the JP1/AJS3 service is cold-started. Specify this value when you want current operation to be consistent with that of 06-71 or earlier, which does not initialize the database.

Default value

clear

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(11) MaximumQueue

Use this parameter to specify the maximum number of queues that can be defined.

Change this parameter as necessary if the number of queues defined for the manager might exceed the recommended value.

Format

"MaximumQueue" = dword:maximum-number-of-definedable-queues

Specifiable values

A hexadecimal value from 1 to 2000 (1 to 8,192 in decimal)

Default value

dword:00000096 (150 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The maximum number of queues that can be used on one manager includes the number of default queues used on the agent. The maximum number of agents specified in the MaximumAgent environment setting parameter equals the maximum number of default queues. Specify a larger value in the MaximumQueue environment setting parameter than the value specified in the MaximumAgent environment setting parameter.

The following shows the relationship between the maximum number of queue definitions you specify here and the maximum number of queues that can be used on one manager:

value-specified-for-the-MaximumQueue-environment-setting-parameter (a value greater than the value in the MaximumAgent environment setting parameter) = maximum-number-of-queues-that-can-be-used-on-one-manager

To Page Top

(12) MaximumContentJob

Use this parameter to specify the maximum number of jobs that the system can hold in its work area.

Change this value as necessary if the system has to register and execute a large number of jobs in a short period.

When you start the JP1/AJS3 service, the system allocates a job information area in memory that can accommodate information for the number of jobs specified here. Specify a value that is sufficient to cover the peak number of queuing jobs during operation.

If all job information areas are being used (when the same number of jobs as the value specified for this parameter are queued), the submit processing fails. In addition, the value of this parameter is applied only to queuing jobs and running jobs. The value is not applied to jobs that have ended, event jobs, and judgment jobs.

Format

"MaximumContentJob" = dword:maximum-number-of-jobs-in-the-system

Specifiable values

• For the job execution control manager of the scheduler service

  A hexadecimal value from 1 to 9C3F (1 to 39,999 in decimal)

• For the job execution control manager of the submit job

  A hexadecimal value from 1 to 14000 (1 to 81,920 in decimal)

Default value

• For the job execution control manager of the scheduler service

  dword:00001770 (6,000 in decimal)

• For the job execution control manager of the submit job

  dword:000007D0 (2,000 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

• If you change this parameter, also change the value of the AlartContentJob environment setting parameter (the number of warning jobs in the system) as needed.

• The output messages and the job status differ depending on the value set for the maximum number of jobs set for the following system. Specify the value according to your operational requirements.

  For the job execution control manager of the scheduler service

  - If you specify that the maximum value is from hexadecimal 1 to 9C3F (decimal 1 to 39,999), and the number of registered jobs reaches the specified maximum number, the following KAVU4520-W message will be output: The job cannot be registered because the system already reached the maximum number of jobs (maximum-number), as stipulated in environment setting (logical-host-name).

  However, if you specify the maximum value to be hexadecimal 9C40 or more, (decimal 40,000 or more), the KAVU4520-W message will not be output.

  - If a very large number of jobs are concentrated in a short period, and the total number of queuing jobs and running jobs exceeds 40,000, JP1/AJS3 will not be able to assign job numbers, and the jobs will fail to start.

  Therefore, for the maximum number of jobs, specify a number from hexadecimal 1 to 9C3F (decimal 1 to 39,999).

• The maximum number of job numbers per scheduler service is 40,000 regardless of the number of scheduler services in the system. Note that this is the maximum number of jobs to which job numbers can be assigned, and is not the maximum value of a number that can be assigned as a job number.

To Page Top

(13) AlartContentJob

Use this parameter to specify the threshold at which a warning message will be output according to the use status of the job information area in the work area of the system.

If you change the value of the MaximumContentJob environment setting parameter (maximum number of jobs in the system), for this parameter specify a value smaller than the value of the MaximumContentJob parameter.

If you specify for this parameter a value greater than the value of the MaximumContentJob parameter, the JP1/AJS3 service will not be able to start.

The value of this parameter is applied only to queuing jobs and running jobs. The value is not applied to jobs that have ended, event jobs, and judgment jobs.

Format

"AlartContentJob" = dword:number-of-warning-jobs-in-the-system

Specifiable values

• For the job execution control manager of a scheduler service

  A hexadecimal value from 1 to 9C3F (1 to 39,999 in decimal)

• For the job execution control manager of a submit job

  A hexadecimal value from 1 to 14000 (1 to 81,920 in decimal)

Default value

• For the job execution control manager of a scheduler service

  dword:000012C0 (4,800 in decimal)

• For the job execution control manager of a submit job

  dword:00000640 (1,600 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(14) AlarmContentJobEventInterval

Interval for issuing a JP1 event when the number of jobs in the Now queuing or Now running status being monitored exceeds the number of warning jobs specified for the AlartContentJob environment setting parameter.

After the first JP1 event is issued, during the interval set by this setting value, even if the monitored value is equal to or greater than the number of warning jobs specified for the AlartContentJob environment setting parameter, a JP1 event will not be issued. Even after the time specified for this setting value passes, if the monitored value continues to be equal to or greater than the number of warning jobs, a JP1 event will again be output at intervals set by this setting value.

Format

"AlarmContentJobEventInterval" = dword:interval-for-issuing-a-JP1-event

Specifiable values

A hexadecimal value from 0 to 5A0 (0 to 1,440 in decimal)

If you do not want to issue a JP1 event, specify 0.

Default value

dword:00000000 (0 in decimal)

During a new installation and setup of JP1/AJS3, 5 is set.

Recommended value

Set 1 or a greater value according to the operating environment.

When the setting takes effect

When the scheduler service starts

To Page Top

(15) ReceiveFileSizeStatus

Use this parameter to specify the behavior when the size of a file being received reaches the upper limit.

For details, see 6.2.7 Placing restrictions on file reception (for Windows) or 15.2.7 Placing restrictions on file reception (for UNIX).

Format

"ReceiveFileSizeStatus" = dword:behavior-when-the-received-file-size-reaches-the-upper-limit

Specifiable values

0

The upper limit for received files size is checked. If the upper limit is reached, the following message is output, but all file data is received. Even if the file size exceeds the upper limit, the job status does not change, and the job end status on the agent host is inherited.

• For a result file:

  Message KAVU2260-I

  Message KAVU4294-I

• For a transfer file:

  Message KAVU2243-I

1

The upper limit for received files size is checked. If the upper limit is reached, receive processing is canceled and the job status changes.

A result file is received until the upper limit for file size (LimitReceiveFileSize environment setting parameter) is reached. Thereafter, data that exceeds the upper limit is discarded, and the end status changes to Ended abnormally. For a transfer file, no file data is received, and the end status changes to Failed to start. For details about the return code and end status, see 6.2.7(3) Operation performed if the size of received files exceeds the maximum (for Windows) or 15.2.7(3) Operation performed if the size of received files exceeds the maximum (for UNIX).

If the upper limit has been reached, the following message is output:

• For a result file:

  Message KAVU4296-E

• For a transfer file:

  Message KAVU2244-E

2

The upper limit for received file size is checked. If the upper limit is reached, receive processing is canceled, and the job status changes.

Result files are received until the upper limit for file size (LimitReceiveFileSize environment setting parameter) is reached. Thereafter, data that exceeds the upper limit is discarded, and the end status changes to Ended with warning. However, if the job status on the agent host is Ended abnormally, that status is inherited. For a transfer file, the end status changes to Failed to start, and no file data is received. For the return code and end status, see 6.2.7(3) Operation performed if the size of received files exceeds the maximum (for Windows) or 15.2.7(3) Operation performed if the size of received files exceeds the maximum (for UNIX).

If the upper limit has been reached, the following message is output:

• For a result file:

  Message KAVU4295-W

• For a transfer file:

  Message KAVU2244-E

3

The upper limit for received files size is checked. If the upper limit is reached, receive processing is canceled.

Result files are received until the upper limit for file size (LimitReceiveFileSize environment setting parameter) is reached. Thereafter, all file data that exceeds the upper limit is discarded. For a transfer file, all file data is discarded. The end status on the agent host is inherited as the end status for the job. For the return code and end status, see 6.2.7(3) Operation performed if the size of received files exceeds the maximum (for Windows) or 15.2.7(3) Operation performed if the size of received files exceeds the maximum (for UNIX).

If the upper limit is reached, the following message is output:

• For a result file:

  Message KAVU4294-I

• For a transfer file:

  Message KAVU2243-I

This specification allows a job to end normally even if the limit is exceeded. However, because the files that are created are not complete, you must make sure beforehand that the incomplete files will not cause any problems if they are referenced and used in a succeeding job.

Default value

dword:00000000 (0 in decimal)

During a new installation of JP1/AJS3, dword:00000003 (3 in decimal) is set.

Recommended value

dword:00000003 (3 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(16) LimitReceiveFileSize

Use this parameter to specify the upper limit for the size of received files.

If the size of a transfer file or a result file used when a job is executed exceeds the value estimated for operation, limit the size of files received by the manager host. We recommend that you set a limit of approximately five megabytes, depending on operational requirements.

If multiple transfer files are to be sent at one time, this setting enables the total size of the files to be checked against the limit. The value used to check a result file is the total of the sizes of the standard output file and the standard error output file.

Note that the limit might be subject to an error in a range of plus or minus several hundred bytes.

The following shows how to estimate file size (in bytes):

_{File count}

(file-name-length + file-size + (12 x file-line-count) + 100)

For details, see 6.2.7 Placing restrictions on file reception (for Windows) or 15.2.7 Placing restrictions on file reception (for UNIX).

Format

"LimitReceiveFileSize" = dword:limit-on-file-size

Specifiable values

A hexadecimal value (in bytes) from 80000 to 40000000 (524,288 to 1,073,741,824 in decimal)

Default value

dword:00500000 (5,242,880 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

• This setting is rounded in increments of 8000 (32,768 in decimal). For example, if you specify 80001 (524,289 in decimal), the valid value is 88000 (557,056 in decimal).

• For action jobs, if the size of the information to be output by JP1/AJS3 is less than the lowest value in the range that can be specified (524,288 bytes), no information is output. Note, however, that the size could be less if you run a job in UNIX and standard error output is output for a login script of a job execution OS user or the system.

To Page Top

(17) ReceiveFileOption

Use this parameter to specify whether to prevent duplicated reception of the job result file.

For details, see 6.2.6 Preventing duplicated reception of job result files (for Windows) or 15.2.6 Preventing duplicated reception of job result files (for UNIX).

Format

"ReceiveFileOption" = dword:definition-for-preventing-duplicated-reception-of-the-job-result-file

Specifiable values

0

Duplicated reception of the job result file is not prevented.

1

Duplicated reception of the job result file is prevented.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(18) QueuingJobRecoveryTime

Use this parameter to specify the recovery time for queuing jobs when an agent has failed.

For details, see 6.2.12 Changing the wait time for recovery when an agent has failed (for Windows) or 15.2.12 Changing the wait time for recovery when an agent has failed (for UNIX).

Format

"QueuingJobRecoveryTime" = dword:recovery-time-for-queuing-jobs-when-agent-has-failed

Specifiable values

A hexadecimal value (in seconds) from 0000001E to 00000E10 (30 to 3,600 in decimal).

A period of no jobs being executed might occur. This is possible if the system detects a job error several tens of seconds after the error occurred because the system monitors job errors at intervals of several tens of seconds.

Default value

dword:00000258 (600 in decimal, which is 10 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you are using the job distribution delay reduction function, for this environment setting parameter, specify a value less than the value specified the AGMERRAGTSTATRESETTIME environment setting parameter for agent monitoring.

If you are using the default values for the following environment setting parameters for communication control, specify a value that is at least 300 seconds less than the value specified for the AGMERRAGTSTATRESETTIME environment setting parameter. If a value has been changed from its default value, specify a value that is less than the value calculated by using the estimation formula.

Environment setting parameters for communication control^#

• "ClientConnectTimeout" = dword:connection-timeout-period

• "ClientRetryInterval" = dword:connection-retry-interval

• "ClientRetryCount" = dword:number-of-connection-retries

Estimation formula for the QueuingJobRecoveryTime environment setting parameter:

a - b x (c + d) - 300

a: The AGMERRAGTSTATRESETTIME environment setting parameter

b: The ClientRetryCount environment setting parameter (number of connection retries)

c: The ClientConnectTimeout environment setting parameter (connection timeout period)

d: The ClientRetryInterval environment setting parameter (connection retry interval)

#

If the environment setting parameters for the following definition keys have been changed, you will need to estimate a value. Specify JP1_DEFAULT for the physical host. For logical-host-name, specify the name of a logical host.

• [{JP1_DEFAULT|logical-host-name}\JP1AJS2\HOST\NETWORK]

• [{JP1_DEFAULT|logical-host-name}\JP1AJS2\HOST\NETWORK\QUEUEMANAGER]

• [{JP1_DEFAULT|logical-host-name}\JP1AJSMANAGER\scheduler-service-name\NETWORK\QUEUEMANAGER]

To Page Top

(19) ExecutingJobRecoveryTime

Use this parameter to specify the recovery time for running jobs when an agent has failed.

For details, see 6.2.12 Changing the wait time for recovery when an agent has failed (for Windows) or 15.2.12 Changing the wait time for recovery when an agent has failed (for UNIX).

Format

"ExecutingJobRecoveryTime" = dword:recovery-time-for-running-jobs-when-agent-has-failed

Specifiable values

A hexadecimal value (in seconds) from 0000001E to 00000E10 (30 to 3,600 in decimal)

Default value

dword:00000258 (600 in decimal, which is 10 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

By default, the system checks the status of running jobs a maximum of three times before it detects a job abnormality. If you specify a value that is smaller than the agent monitoring interval for this parameter, the wait time for recovery elapses before the system checks the status of running jobs. In that case, the system checks the status of running jobs a maximum of two times. The detailed calculation of the total time required to detect a failure is as follows:

Total-time-elapsing-before-a-failure-is-detected

(agent-monitoring-interval x 1)

+ (communication-time x 2)

+ length-of-time-between-the-failure-occurrence-and-the-first-check-of-the-job-status

If you reduce the agent monitoring interval, the retry interval for TCP/IP connection errors, and the number of retries, the total time elapsing before a failure is detected decreases further.

For details about setting the agent monitoring interval, see (29) ObserveInterval.

For details about setting the retry interval and number of retries for TCP/IP connection errors, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Polling using the agent monitoring interval is executed for each agent host. If you shorten the agent monitoring interval and increase the number of pollings, the number of times communication occurs increases in proportion to the number of agent hosts. Keep this in mind when you change the agent monitoring interval. Similar care is also required when you change the retry interval and the number of retries for TCP/IP connection errors.

To Page Top

(20) MaximumExecJobLogOption

Use this parameter to specify whether to output a message confirming that the maximum number of concurrently executable jobs has been reached.

For details, see 6.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached (for Windows) or 15.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached (for UNIX).

Format

"MaximumExecJobLogOption" = dword:setting-for-whether-to-output-a-message-confirming-that-the-maximum-number-of-concurrently-executable-jobs-has-been-reached

Specifiable values

0

A message confirming that the maximum number of concurrently executable jobs has been reached, is not output.

1

A message confirming that the maximum number of concurrently executable jobs has been reached, is output.

Default value

dword:00000000 (0 in decimal)

During a new installation of JP1/AJS3, dword:00000001 (1 in decimal) is set.

Recommended value

dword:00000001 (1 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(21) MaximumExecJobLogInterval

Use this parameter to specify the interval for outputting a message to confirming that the maximum number of concurrently executable jobs has been reached.

After the first KAVU4310-I message is output, the next KAVU4310-I message is not output for the period specified here (10 minutes by default) even though jobs remain queued. If jobs still remain queued when the specified interval has elapsed, another KAVU4310-I message is output as specified.

For details, see 6.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached (for Windows) or 15.2.13 Outputting a message that reports that the maximum number of concurrently executable jobs has been reached (for UNIX).

Format

"MaximumExecJobLogInterval" = dword:interval-for-outputting-a-message-confirming-that-the-maximum-number-of-concurrently-executable-jobs-has-been-reached

Specifiable values

A hexadecimal value (in seconds) from 0000003C to 00015180 (60 to 86,400 in decimal)

Default value

dword:00000258 (600 in decimal, which 10 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(22) PreventChangeJobOrder

Use this parameter to specify whether to prevent changes to the execution order of submit jobs.

For details, see 7.1.11 Setting for preventing changes in the submit job execution order in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Format

"PreventChangeJobOrder" = dword:setting-for-preventing-changes-to-the-execution-order-of-submit-jobs

Specifiable values

0

Changes to the execution order of submit jobs are not prevented.

1

Changes to the execution order of submit jobs are prevented.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

Specifying 1 for the PreventChangeJobOrder environment setting parameter only changes the job distribution processing. In addition to this setting, you must perform the following steps to prevent changes from being made to the execution order of submit jobs:

• Make sure that only one agent is connected to the queue to which jobs are submitted.

• Specify 1 for the maximum number of concurrently executable jobs for the agent.

Note that, because this setting controls the job execution order, job performance might be reduced by several percent.

To Page Top

(23) EnumJobSaveMemory

Use this parameter to specify whether to reduce the memory consumed by the job execution control manager when job information is enumerated.

For details, see 7.1.12 Setting to reduce memory usage by the job execution control manager (jpqman) when enumerating job information in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Format

"EnumJobSaveMemory" = dword:setting-for-reducing-memory-consumed-by-the-job-execution-control-manager-when-job-information-is-enumerated

Specifiable values

0

The job execution control manager consumes memory as needed for the number of enumerated job information items when job information is enumerated.

1

The memory consumed by the job control manager is reduced when job information is enumerated.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The following are estimates of memory consumption when job information is enumerated:

• When 0 is set

  The maximum amount of memory consumed is about 100 KB per job.

• When 1 is set

  The maximum amount of memory consumed is about 60 MB, regardless of the number of jobs for which information is enumerated.

To Page Top

(24) ExecutingJobChangeStatus

Use this parameter to specify whether to place all running jobs in the end status when a communication error occurs. Specify a hexadecimal value.

For details about definitions, see 6.2.20 Placing all running jobs in an end status when a communication error occurs (for Windows) or 15.2.19 Placing all running jobs in an end status when a communication error occurs (for UNIX).

Format

"ExecutingJobChangeStatus" = dword:setting-for-placing-all-running-jobs-in-the-end-status-when-a-communication-error-occurs

Specifiable values

0

Specify this value to place the jobs in the end status one by one if a communication error occurs during system monitoring of running jobs by polling.

1

Specify this value to place only those jobs on the execution agent among the jobs that are being executed in the same queue in the end status if a communication error occurs during the system monitoring of running jobs by polling.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(25) ConnectTimeout (for job execution control manager)

Use this parameter to specify the timeout period for communication over TCP/IP connections from the manager process for job execution control to the status reporting process for job execution control.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"ConnectTimeout" = dword:definition-of-the-TCP/IP-connection-timeout-value-on-the-job-execution-control-manager

Specifiable values

A hexadecimal value (in milliseconds) from 00002710 to 000927C0 (10,000 to 600,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal, which is 90 seconds)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

• If you decrease the connection timeout value, a timeout might occur before the connection is completed, resulting in a TCP/IP communication connection error.

• Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this parameter is reached.

• This environment setting parameter is not used for communication over TCP/IP from the manager host to the agent host. For details about the environment setting parameters for communication from the manager host to the agent host (to deliver or forcibly terminate jobs, or to check the status of jobs or agents), see 20.8 Setting up the communication control environment.

To Page Top

(26) CommunicateRetryCount (for job execution control manager)

Use this parameter to specify the number of retries for communication over TCP/IP connections from the manager process for job execution control to the status reporting process for job execution control.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"CommunicateRetryCount" = dword:definition-of-the-number-of-retries-for-a-TCP/IP-connection-error-for-the-job-execution-control-manager

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

• If you increase the value for number of retries too much, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

• This environment setting parameter is not used for communication over TCP/IP from the manager host to the agent host. For details about the environment setting parameters for communication from the manager host to the agent host (to deliver or forcibly terminate jobs, or to check the status of jobs or agents), see 20.8 Setting up the communication control environment.

To Page Top

(27) CommunicateRetryInterval (for job execution control manager)

Use this parameter to specify the interval of retries for communication over TCP/IP connections from the manager process for job execution control to the status reporting process for job execution control.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"CommunicateRetryInterval" = dword:definition-of-the-TCP/IP-connection-error-retry-interval-on-the-job-execution-control-manager

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (1 to 300 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

• If you decrease the retry interval to so that it is too small, the communication retry interval will be too short. As a result, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

• This environment setting parameter is not used for communication over TCP/IP from the manager host to the agent host. For details about the environment setting parameters for communication from the manager host to the agent host (to deliver or forcibly terminate jobs, or to check the status of jobs or agents), see 20.8 Setting up the communication control environment.

To Page Top

(28) MaximumAgent

Use this parameter to specify the maximum number of agents that execute jobs requested by the JP1/AJS3 - Manager used to define jobs.

Change this value as necessary if the number of agents defined for the manager could exceed the recommended value.

An attempt to connect to more job-execution agents than the number of agents specified here will be rejected by the system.

Format

"MaximumAgent" = dword:maximum-number-of-definable-agents

Specifiable values

A hexadecimal value from 1 to 400 (1 to 1,024 in decimal)

Default value

dword:00000032 (50 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(29) ObserveInterval

Use this parameter to specify the interval for monitoring the agent on which you want to execute a job.

Change this parameter as necessary if you have adjusted the period of time for monitoring agent errors.

Format

"ObserveInterval" = dword:agent-monitoring-interval

Specifiable values

A hexadecimal value (in seconds) from 3C to 15180 (60 to 86,400 in decimal)

Default value

dword:0000012C (300 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(30) AutoCreate

Use this parameter to specify whether to enable the function that automatically defines an agent.

You can use this function only if you execute PC jobs, Unix jobs, flexible jobs^#, HTTP connection jobs, and action jobs, other than queueless jobs, that have been defined in a jobnet, or execute submit jobs that have been defined by using the jpqjobsub command. This function cannot be used for queue jobs and event jobs.

#

For flexible jobs, replace execution agent with relay agent.

Even if the execution of a job fails, the created execution agent or agent is not lost. Also, execution agents or agents are still available even after a JP1/AJS3 restart.

• About a execution agents that is to be created

  The following are attributes of an execution agent to be created:

  • Name of the execution host: Same as the execution agent name

  • Maximum number of concurrently executable jobs: 5 for a full 24 hours

  • Job transfer restriction status: Enabled

  • Description: None

  You can change the attributes of an execution agent by using the ajsagtalt command. For details about the ajsagtalt command, see ajsagtalt in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference.

• About an agent that is to be created

  The following is the attribute of an agent to be created:

  • Maximum number of concurrently executable jobs: 5 for a full 24 hours

  The following are the attributes of the default queue of an agent to be created:

  • Maximum number of jobs: 100

  • Maximum number of warnings: 80

  • Queue entrance status: open

  • Queue exit status: open

  • Connection agent: local agent host

  • Priority of the agent: 1

  You can change the attributes of the agent and default queue by using the jpqagtalt, jpqquealt, jpqqueopen, jpqqueclose, jpqagtlink, and jpqagtunlink commands. For details about these commands, see 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

You can customize beforehand the attributes of an execution agent or agent that will be created by using the function that automatically defines an agent from the common definition information. For details, see 6.2.3 Customizing the execution agent or agent attribute values created by the automatic agent definition function (for Windows) or 15.2.3 Customizing the execution agent or agent attribute values created by the automatic agent definition function (for UNIX).

If you specify this parameter, the settings apply to all the execution agent or agent attributes that are created by using the automatic agent definition function.

Format

"AutoCreate" = dword:control-flag-for-automatic-definition-of-an-agent

Specifiable values

0

No execution agents or agents are automatically defined.

1

Execution agents or agents are automatically defined.

If you specify 1, the automatic agent definition function is enabled for all the jobs that the job execution control manager for which this parameter is specified handles.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

• Use this function only if absolutely necessary, such as when an error occurs on an existing execution agent or agent (job execution environment) and you need to quickly create a substitute execution agent or agent so that a job can be executed. Under normal circumstances, you should create a execution agent or agent before executing a job. If you need to add execution agents during operation, use the ajsagtadd command. If you need to add agents, use the jpqimport or jpqagtadd command.

• When the function that automatically defines an agent is enabled, you need to execute a job as a JP1 user with both JP1_JPQ_User and JP1_JPQ_Admin permissions.

To Page Top

(31) AutoCreateExecJobs

Use this parameter to specify the maximum number of concurrently executable jobs that a execution agent or agent created when the agent host is defined automatically can execute.

The concurrency level specified in this parameter is valid for a full 24 hours. To specify the concurrency level for 30-minute intervals, use the ajsagtalt command to change the value. For details about the ajsagtalt command, see ajsagtalt in 3. Commands Used for Normal Operations in the manual JP1/Automatic Job Management System 3 Command Reference. If you want to specify the concurrency level for 30-minute intervals for agent, use the jpqagtalt command to change the value. For details about the jpqagtalt command, see jpqagtalt in 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

Format

"AutoCreateExecJobs" = dword:maximum-number-of-concurrently-executable-jobs-when-an-agent-host-is-defined-automatically

Specifiable values

A hexadecimal value from 1 to 00000400 (1 to 1,024 in decimal)

Default value

dword:00000005 (5 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(32) AutoCreateMaxJobs

Use this parameter to specify the maximum number of jobs in the default queue that is created when the agent host is defined automatically.

Format

"AutoCreateMaxJobs" = dword:maximum-number-of-jobs-when-the-agent-host-is-defined-automatically

Specifiable values

A hexadecimal value from 1 to FFFFFFFF (1 to 4,294,967,295 in decimal)

Default value

dword:00000064 (100 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(33) AutoCreateWarnJobs

Use this parameter to specify a warning value for the number of jobs in the default queue that is created when the agent host is defined automatically.

Format

"AutoCreateWarnJobs" = dword:warning-value-for-the-number-of-jobs-when-the-agent-host-is-defined-automatically

Specifiable values

A hexadecimal value from 1 to FFFFFFFF (1 to 4,294,967,295 in decimal)

Default value

dword:00000050 (80 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(34) AutoCreatePriority

Use this parameter to specify the agent priority for the default queue that is created when the agent host is defined automatically.

Format

"AutoCreatePriority" = dword:agent-priority-when-the-agent-host-is-defined-automatically

Specifiable values

A hexadecimal value from 1 to 00000010 (1 to 16 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(35) LeastRecentlyUsed

Use this parameter to specify the method for determining the agent host to which jobs are to be distributed.

For details, see 6.2.9 Setting the method for determining the agent host to which a job will be delivered (for Windows) or 15.2.9 Setting the method for determining the agent host to which a job will be delivered (for UNIX). If you specify a value for queuing jobs and for submit jobs, see 7.1.7 Method of determining the agent host to which a job is distributed in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

Format

"LeastRecentlyUsed" = dword:definition-of-method-for-determining-the-agent-host-to-which-jobs-are-distributed

Specifiable values

0

If there are multiple agents that have the same priority and agent usage rate, the system determines the job distribution destination agent host regardless of the idle time since the job was last distributed.

1

If there are multiple agents that have the same priority and agent usage rate, the system distributes a job to the agent host that has been idle for the longest time since a job was last distributed.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(36) MaximumResource

Use this parameter to specify the maximum number of execution-locked resources used to suppress the concurrent execution of jobs.

When the JP1/AJS3 service is started, an area for execution-locked resource information that is equivalent to the value specified in this parameter is reserved in memory.

The value of this parameter is not applied to event jobs.

You cannot use the execution-locked resources for the jobs defined in a jobnet. You can, however, use them for submit jobs that have been defined by using the jpqjobsub command.

For details about the command, see 4. Commands Used for Special Operation in the manual JP1/Automatic Job Management System 3 Command Reference.

Change this value as necessary if the maximum number of defined execution-locked resources that can be added by executing the jpqresadd command is insufficient.

Format

"MaximumResource" = dword:maximum-number-of-definable-execution-locked-resources

Specifiable values

A hexadecimal value from 1 to 2000 (1 to 8,192 in decimal)

Default value

dword:00000032 (50 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(37) WorkPath (for agent process)

The name of the work directory used when an agent process is running. Use this parameter to specify the name of the work directory to be used to execute jobs on the host. Specify a full path name.

If there is not enough space on the disk that contains the default directory, specify a directory on a disk that has enough space.

Format

"WorkPath" = "name-of-the-work-directory-used-when-an-agent-process-is-running"

Specifiable values

A character string of no more than 180 bytes

Default value

In Windows, if the installation folder is the default installation folder or is in a folder protected by the system:

• For a physical host:

  %ALLUSERSPROFILE%\Hitachi\JP1\JP1_DEFAULT\JP1AJS2\tmp

  The default value of %ALLUSERSPROFILE% is system-drive\ProgramData.

  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)

• For a logical host:

  shared-folder\jp1ajs2\tmp

In Windows, if the installation folder is other than the above:

• For a physical host:

  JP1/AJS3 - Manager: JP1/AJS3-Manager-installation-folder\tmp

  JP1/AJS3 - Agent: JP1/AJS3-Agent-installation-folder\tmp

• For a logical host:

  shared-folder\jp1ajs2\tmp

In UNIX:

• For a physical host:

  /var/opt/jp1ajs2/tmp

• For a logical host:

  shared-directory/jp1ajs2/tmp

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(38) IsHA (for agent process)

Use this parameter to specify the definition for setting up a cluster environment for a job execution control agent process. Specify this parameter only to stop cluster use.

Format

"IsHA" = dword:definition-for-cluster-environment-setup-for-agent-processes

Specifiable values

0

Specifies to stop cluster use.

1

If you execute setup when operating a cluster system, this value is automatically set to the parameter for the physical and logical hosts.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(39) IsExecFindExecutable

Use this parameter to specify whether to execute the execution file of a job using a long file name without conversion to a short file name.

For details, see 6.2.15 Executing a job by using a long file name.

Format

"IsExecFindExecutable" = dword:definition-for-executing-a-job-with-a-long-file-name

Specifiable values

0

An execution file name is converted to a short file name.

1

An execution file name is not converted to a short file name. The job is executed with a long file name.

Default value

dword:00000000 (0 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(40) LoadUserProfile

Use this parameter to specify whether to load the user profile information of the OS user who executes a job when a job is executed.

For details, see 6.2.16 Executing a job that requires a user profile.

Format

"LoadUserProfile" = dword:definition-for-whether-to-load-the-user-profile

Specifiable values

0

The user profile information is not loaded.

1

The user profile information is loaded.

If you set 1 for this parameter, set 1 or 2 for the IsAccessTokenCache environment setting parameter.

Default value

dword:00000000 (0 in decimal)

During a new installation of JP1/AJS3, dword:00000001 (1 in decimal) is set.

Recommended value

dword:00000001 (1 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(41) IsAccessTokenCache

Use this parameter to specify whether to reuse an access token when a job is executed.

Set 1 or 2 for this parameter when you set 1 for the LoadUserProfile environment setting parameter to load user profile information.

For details, see 6.2.17 Reusing access tokens for job execution.

Format

"IsAccessTokenCache" = dword:setting-for-reusing-an-access-token-when-a-job-is-executed

Specifiable values

0

Specify this value to acquire an access token each time a job is executed and then to release the token after the job is executed.

With this setting, a desktop heap area is allocated each time a job is executed, and is then released after the job is executed.

1

Specify this value to reuse an access token to execute a job if an access token with the same user name, domain name, and password was saved when the previous job was executed.

With this setting, all OS users who execute jobs share the desktop heap area, and the desktop heap area is released when the JP1/AJS3 service stops.

2

Specify this value to reuse an access token to execute a job if an access token with the same user name, domain name, and password was saved when the previous job was executed.

With this setting, a desktop heap area is allocated for each OS user who executes the job, and is then released when the JP1/AJS3 service stops.

With any of these settings, if a job is executed by the OS user who started the JP1/AJS3 service, the desktop heap area that was allocated when the JP1/AJS3 service started is shared.

Default value

dword:00000000 (0 in decimal)

During a new installation of JP1/AJS3, dword:00000002 (2 in decimal) is set.

Recommended value

dword:00000002 (2 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(42) ENABLE_LONG_EXT (for job)

Use this parameter to specify whether to execute a job specified for an executable file whose extension is 4 bytes or more in the application associated with the executable-file extension when Standard has been specified for Exec. service.

For details, see 6.2.18 Executing a job whose executable file name has an extension longer than three bytes.

Format

"ENABLE_LONG_EXT" = dword:setting-value

Specifiable values

0

Although the executable-file extension is 4 bytes or more, the job specified for the file is executed in the application that is associated with the first three digits of the executable-file extension.

If the system cannot find the application that is associated with the first three digits of the extension, the job does not start.

1

If the executable-file extension is 4 bytes or more, the job is executed in the application that is associated with the extension.

However, if Standard is specified for Exec. service, the job is executed with a long file name when the executable file is executed with an extension of 4 bytes or more.

Default value

dword:00000000 (0 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(43) IsLimitCoreSize

Use this parameter to specify whether to limit the core-file size for each process of a job that is executed from JP1/AJS3.

Format

"IsLimitCoreSize" = dword:limit-flag-for-the-maximum-core-file-size-for-each-process

Specifiable values

0

The core file size for each process of a job is not limited.

1

The core file size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(44) LimitCoreSize

Use this parameter to specify the maximum core-file size for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitCoreSize environment setting parameter to limit the maximum core file size.

Format

"LimitCoreSize" = dword:maximum-core-file-size-for-each-process

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set of the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

To Page Top

(45) IsLimitDataSize

Use this parameter to specify whether to limit the data-segment size for each process of a job that is executed from JP1/AJS3.

Format

"IsLimitDataSize" = dword:limit-flag-for-maximum-data-segment-size-for-each-process

Specifiable values

0

The data-segment size for each process of a job is not limited.

1

The data-segment size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(46) LimitDataSize

Use this parameter to specify the maximum data-segment size for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitDataSize environment setting parameter to limit the maximum data-segment size.

Format

"LimitDataSize" = dword:maximum-data-segment-size-for-each-process

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

To Page Top

(47) IsLimitFileSize

Use this parameter to specify whether to limit the permanent-file size for each process of a job that is executed from JP1/AJS3.

Format

"IsLimitFileSize" = dword:limit-flag-for-the-maximum-permanent-file-size-for-each-process

Specifiable values

0

The permanent-file size for each process of a job is not limited.

1

The permanent-file size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(48) LimitFileSize

Use this parameter to specify the maximum permanent-file size for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitFileSize environment setting parameter to limit the maximum permanent-file size.

Format

"LimitFileSize" = dword:maximum-permanent-file-size-for-each-process

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

To Page Top

(49) IsLimitMemorySize

Use this parameter to specify whether to limit the memory size (total amount of physical memory and swap area) for each process of a job that is executed from JP1/AJS3.

Format

"IsLimitMemorySize" = dword:limit-flag-for-the-maximum-memory-size-for-each-process

Specifiable values

0

The memory size for each process of a job is not limited.

1

The memory size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(50) LimitMemorySize

Use this parameter to specify the maximum memory size (total amount of physical memory and swap area) for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitMemorySize environment setting parameter to limit the maximum memory size.

Format

"LimitMemorySize" = dword:maximum-memory-size-for-each-process

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

To Page Top

(51) IsLimitStackSize

Use this parameter to specify whether to limit the stack segment size for each process of a job that is executed from JP1/AJS3.

Format

"IsLimitStackSize" = dword:maximum-stack-segment-size-for-each-process

Specifiable values

0

The stack segment size for each process of a job is not limited.

1

The stack segment size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(52) LimitStackSize

Use this parameter to specify the maximum stack segment size for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitStackSize environment setting parameter to limit the maximum stack segment size.

Format

"LimitStackSize" = dword:maximum-stack-segment-size-for-each-process

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

To Page Top

(53) IsLimitCpuTime

Use this parameter to specify whether to limit the CPU time for each process of a job that is executed from JP1/AJS3.

Format

"IsLimitCpuTime" = dword:limit-flag-for-the-maximum-CPU-time-for-each-process

Specifiable values

0

The CPU time for each process of a job is not limited.

1

The CPU time for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(54) LimitCpuTime

Use this parameter to specify the maximum CPU time for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitCpuTime environment setting parameter to limit the maximum CPU time.

Format

"LimitCpuTime" = dword:maximum-CPU-time-for-each-process

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

To Page Top

(55) IsLimitWorkSize

Use this parameter to specify whether to limit the working-set size (amount of physical memory used by a process) for each process of a job that is executed from JP1/AJS3.

Format

"IsLimitWorkSize" = dword:limit-flag-for-the-maximum-working-set-size-for-each-process

Specifiable values

0

The working-set size for each process of a job is not limited.

1

The working-set size for each process of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you use Solaris, do not specify this flag. If you specify this flag, JP1/AJS3 might not be able to start.

To Page Top

(56) LimitWorkSize

Use this parameter to specify the maximum working-set size (amount of physical memory used by process) for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitWorkSize environment setting parameter to limit the maximum working-set size.

Format

"LimitWorkSize" = dword:maximum-working-set-size-for-each-process

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

To Page Top

(57) IsLimitNoFile

Use this parameter to specify whether to limit the number of file descriptors for each process of a job that is executed from JP1/AJS3.

Format

"IsLimitNoFile" = dword:limit-flag-for-the-maximum-number-of-file-descriptors-for-each-process

Specifiable values

0

The number of file descriptors for each file of a job is not limited.

1

The number of file descriptors for each file of a job is limited.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(58) LimitNoFile

Use this parameter to specify the maximum number of file descriptors for each process of a job that is executed from JP1/AJS3.

The specified parameter value takes effect when 1 is specified for the IsLimitNoFile environment setting parameter to limit the maximum number of file descriptors.

Format

"LimitNoFile" = dword:maximum-number-of-file-descriptors-for-each-process

Specifiable values

A hexadecimal value from 0 to 7FFFFFFF (0 to 2,147,483,647 in decimal)

Default value

dword:7FFFFFFF (2,147,483,647 in decimal)

Recommended value

Depends on the user environment.

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

The valid range of 0 to 7FFFFFFF is the range of values that are logically available. The actual valid range depends on the range set in the setrlimit() OS system call.

If you specify dword:7FFFFFFF, the upper limit set for the system is used.

If you specify a number smaller than dword:7FFFFFFF, but larger than the upper limit of the system, the upper limit of the system is used.

If the setting fails, the system outputs a message and does not change the limit.

To Page Top

(59) PipeComTimeout

Use this parameter to specify the pipe communication timeout value.

For details, see 15.2.15 Changing the timeout value for pipe communication of the agent.

Format

"PipeComTimeout" = dword:pipe-communication-timeout-value-for-agents

Specifiable values

A hexadecimal value (in seconds) from 0000012C to 7FFFFFFF (300 to 2,147,483,647 in decimal)

Default value

dword:0000012C (300 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you specify a large value for the pipe communication timeout period, a job failure might not be detected quickly enough.

You can specify one second as the minimum value for the pipe communication timeout period. If you specify a value less than 300 seconds, however, the possibility that pipe communication times out increases, and a job might fail to start. For this reason, the minimum specifiable value is defined as 300 seconds or more. Note, however that if you specify a value that is less than 300 seconds, no error occurs and operation will continue.

To Page Top

(60) AfterForkPipeTimeout

Use this parameter to specify the timeout value for job process execution ready notification.

For details, see 15.2.16 Setting the timeout value for receiving notification from the job process that execution is ready.

Format

"AfterForkPipeTimeout" = dword:timeout-value-for-job-process-execution-ready-notification

Specifiable values

A hexadecimal value (in seconds) from 00000384 to 00015180 (900 to 86,400 in decimal)

The maximum value, which is 00015180 (86,400 seconds in decimal), is the number of seconds in one day.

Default value

dword:00000384 (900 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you specify a large value as the timeout value for reporting that preparations for job process execution have been completed, a job failure might not be detected quickly enough.

You can specify zero seconds as the minimum timeout value for reporting that preparations for job process execution have been completed. If you specify a value less than 900 seconds, however, the possibility a timeout error occurs increases, and a job might fail to start. For this reason, the minimum specifiable value is defined as 900 seconds or more. Note, however, that if you specify a value that is less than 900 seconds, no error occurs, and operation will continue.

To Page Top

(61) IsCacheCmdSearchPath

Use this parameter to specify whether to cache the value of the command-search path that is to be used when a job starts.

Caching the value improves performance when a job starts because the search path is obtained quickly. Note, however, that if you change the path when the value is cached, the change does not immediately take effect. Therefore, if you change the command-search path with caching enabled, wait at least 5 minutes before starting the job.

Format

"IsCacheCmdSearchPath" = dword:flag-for-specifying-whether-to-cache-the-command-search-path-value

Specifiable values

0

The value for the command-search path is not cached.

1

The value for the command-search path is cached.

If you specify any value other than 0 or 1, the specified value is changed to 1.

If you often change the value for the PATH environment variable of the execution OS user, and want the change applied immediately when a job is executed, change this parameter value to 0. Note, however, that specifying 0 degrades job execution performance.

If you want operation to be consistent with that of version 06-71 or earlier, specify dword:00000000.

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Supplementary note

The command-search path is a PATH environment variable set in the login script of the execution OS user.

To Page Top

(62) IsUseWorkPath

Use this parameter to specify whether to change the work path when a job is executed to the work directory of the JP1/AJS3 agent process.

Format

"IsUseWorkPath" = dword:flag-for-specifying-whether-to-change-the-work-path-for-job-execution

Specifiable values

0

The work path when a job is executed is not changed to the work directory used when the process is executed (the setting is disabled).

1

The work path when a job is executed is changed to the work directory used when the agent process is executed.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Supplementary notes

• When a job is executed, the system creates a temporary file whose name begins with JPQ_EXEC in the work path.

  You can specify 0 and omit work path name specification (work path name specification in the -w option of the jpqjobsub command). In that case, however, a temporary file whose name begins with JPQ_EXEC is created in the home directory of the job executing user. If the home directory is not defined, root (/) is assumed.

  To prevent a temporary file from being created in the home directory of the job executing user, specify 1 to change the work path for job execution to the work directory for the execution of JP1/AJS3 agent process.

• You can specify 1 and omit work path name specification (work path name specification in the -w option of the jpqjobsub command). In that case, however, a temporary file whose name begins with JPQ_EXEC is created in the work directory for the execution of JP1/AJS3 agent process.

• If a directory is explicitly specified for Working path in the job definition, a temporary file whose name begins with JPQ_EXEC is created in the directory specified for Working path regardless of the setting of this parameter.

• If a JP1/AJS3 process ends abnormally (because of OS shutdown, for example), a temporary file whose name begins with JPQ_EXEC might not be deleted but remain in the specified work path.

  You can delete the remaining temporary file without problems if the JP1/AJS3 service has been stopped.

To Page Top

(63) IsSigchldDefault

Use this parameter to specify whether to execute jobs with the default setting (SIG_DFL), whereby the SIGCHLD signal is received.

For details, see 15.2.17 Applying SIG_DFL (setting for receiving the SIGCHLD signal) to a child process started from JP1/AJS3.

Format

"IsSigchldDefault" = dword:definition-for-changing-setting-of-child-processes-started-by-JP1/AJS3-to-the-SIG_DFL-setting-whereby-the-SIGCHLD-signal-is-received

Specifiable values

0

Specify this value to execute the job with the setting (SIG_IGN) whereby the SIGCHLD signal is ignored.

1

Specify this value to execute the job with the setting (SIG_DFL) whereby the SIGCHLD signal is received.

Default value

dword:00000000 (0 in decimal)

During a new installation and setup of JP1/AJS3, 1 is set.

Recommended value

dword:00000001 (1 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(64) FileAccessPermissionMode

Use this parameter to specify the method to check access permissions for the files listed below when executing Unix jobs or executing HTTP connection jobs on a Linux host.

• Script file^#

• Environment variable file^#

• Standard input file^#

• Standard output file

• Standard error output file

• Destination file^#

#

This file cannot be specified for HTTP connection jobs.

For details, see 15.2.18 Enabling the file access permission check for the ACL and secondary group settings during job execution.

Format

"FileAccessPermissionMode" = dword:setting-of-the-method-to-check-file-access-permissions-when-executing-jobs-on-a-UNIX-host

Specifiable values

0

The access permission of each file is checked according to the file permission setting. Then, depending on the file, the behavior is as follows.

• For script files

  The access permission is checked according to the access control list and secondary group settings.

• For files other than script files

  Checks according to the access control list and secondary group settings are not performed.

1

The access permission of the script file is checked according to the file permission, access control list, and secondary group settings.

For the access permissions of files other than the script file, only the check according to the file permission is performed.

2

The access permission of each file is checked according to the file permission, access control list, and secondary group settings.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you change the parameter value to 2, a job that can start by default even if the access control list or secondary group for this job is set might fail to start. Before you specify a setting, consider the difference between the setting that uses only the file permission and the settings that also use the access control list or secondary group settings to prevent any effect on the starting of a job.

To Page Top

(65) NotfyJobStateInterval

Use this parameter to specify the interval for resending the job result file.

For details, see 6.2.5 Changing the interval and number of resend attempts for job result files (for Windows) or 15.2.5 Changing the interval and number of resend attempts for job result files (for UNIX).

Format

"NotfyJobStateInterval" = dword:interval-for-resending-the-job-result-file

Specifiable values

A hexadecimal value (in seconds) from 0 to 00015180 (0 to 86,400 in decimal).

The maximum value is 00015180 (86,400 seconds in decimal), which is the number of seconds in one day.

If you do not want to resend the result file, specify 0.

Default value

dword:0000012C (300 in decimal, which means 5 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you specify 0 for this parameter, the result file is not resent. Therefore, job completion will not be reported if transfer of the result file fails, and the state of job completion will be detected by job status monitoring on the manager host. Because monitoring of the job status is usually performed by polling at five-minutes intervals, detection of job end could be delayed.

In either of the following cases, the end information for a job on the agent host is deleted. As a result, the job will be killed, and the message KAVU4597-W (A missed job at the agent (agent-host-name) was forcibly terminated.) will be output to the integrated trace log on the manager host.

• When the resend operation is repeated until the upper limit of NotfyJobStateCount is reached, at which time transfer of the result file fails

• When the agent host's JP1/AJS3 service stops before the manager host starts checking the job status

To Page Top

(66) NotfyJobStateCount

Use this parameter to specify the number of times that the job result file is to be resent.

For details, see 6.2.5 Changing the interval and number of resend attempts for job result files (for Windows) or 15.2.5 Changing the interval and number of resend attempts for job result files (for UNIX).

Format

"NotfyJobStateCount" = dword:number-of-times-job-result-file-to-be-resent

Specifiable values

A hexadecimal value from 1 to 00000800 (1 to 2,048 in decimal)

Default value

dword:00000120 (288 in decimal)

During a new installation of JP1/AJS3, dword:00000002 (2 in decimal) is set.

Recommended value

dword:00000002 (2 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

Supplementary note

If you use the default values of this parameter and the NotfyJobStateInterval environment setting parameter, a resend operation is performed at five-minute intervals for 24 hours.

To Page Top

(67) ConnectTimeout (for job execution control agent)

Use this parameter to specify the TCP/IP connection timeout value.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"ConnectTimeout" = dword:definition-of-the-TCP/IP-connection-timeout-value-of-the-job-execution-control-agent

Specifiable values

A hexadecimal value (in milliseconds) from 00002710 to 000927C0 (10,000 to 600,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal, which is 90 seconds)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

• If you decrease the connection timeout value, a timeout might occur before the connection is completed, resulting in a TCP/IP communication connection error.

• Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this parameter is reached.

To Page Top

(68) CommunicateRetryCount (for job execution control agent)

Use this parameter to specify the number of retries for a TCP/IP connection error.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"CommunicateRetryCount" = dword:definition-of-the-number-of-retries-for-a-TCP/IP-connection-error-on-the-job-execution-control-agent

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you increase the value for number of retries too much, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

To Page Top

(69) CommunicateRetryInterval (for job execution control agent)

Use this parameter to specify the TCP/IP connection error retry interval.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"CommunicateRetryInterval" = dword:definition-of-the-TCP/IP-connection-error-retry-interval-on-the-job-execution-control-agent

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (1 to 300 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you decrease the value for the retry interval so that it is too small, the communication retry interval will be too short. As a result, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

To Page Top

(70) LogonUserRetryCount

Use this parameter to specify the number of retries for obtaining an access token when Standard is specified for Exec. service.

For details, see 6.2.19 Changing the settings for logon retries when a job is executed.

Format

"LogonUserRetryCount" = dword:number-of-retries-for-obtaining-an-access-token-when-"Standard"-is-specified-for-"Exc.service"

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000003 (3 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you specify 0, no retry attempts are made.

To Page Top

(71) LogonUserRetryInterval

Use this parameter to specify the retry interval for obtaining the access token when Standard is specified for Exec. service.

For details, see 6.2.19 Changing the settings for logon retries when a job is executed.

Format

"LogonUserRetryInterval" = dword:retry-interval-for-obtaining-an-access-token-when-"Standard"-is-specified-for-"Exec.service"

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (0 to 300 in decimal)

Default value

dword:00000001 (1 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(72) variable-name

This parameter is used to define a work path for job execution as a variable.

Format

"variable-name" = "value"

variable-name

Specify the character string for the variable name in the format $variable-name$. The specified variable name here can be used in the file path names and parameters.

value

Specify the installation path for the execution program indicated by variable-name on each applicable host.

Cautionary note

If you define environment setting parameters incorrectly, you can perform the recovery procedure described in B. Recovery Procedure Used When an Incorrect Environment Settings Parameter is Set.

For details, see 6.2.1 Defining variables for work paths used during job execution (for Windows) or 15.2.1 Defining variables for work paths used during job execution (for UNIX).

To Page Top

(73) All Users

Specify the search path name for all JP1 users.

Format

"All Users" = search-path-for-a-transfer-file

Supplementary note

You can specify a search path name for each JP1 user separately, and a search path name for all JP1 users in any sequence.

When you write multiple search path names in Windows, use two colons (::) to delimit them. Also enclose the entire path name after the equal sign (=) in double quotation marks (").

If the specifications are duplicated, the priority is as follows:

• The specification for a JP1 user has priority over the specification for all JP1 users. If a transfer file with a search path that was specified for a JP1 user is found, a search using the search path specified for all JP1 users is not performed.

• If a JP1 user name is duplicated, the most recent specification has priority.

For details, see 6.2.2 Defining search paths for a file to be transferred (for Windows) or 15.2.2 Defining search paths for a file to be transferred (for UNIX).

To Page Top

(74) JP1-user-name

Specify the search path name for each JP1 user who executes a job.

Format

"JP1-user-name" = search-path-for-a-transfer-file

Supplementary note

You can specify a search path name for each JP1 user separately, and a search path name for all JP1 users in any sequence.

When you write multiple search path names in Windows, use two colons (::) to delimit them. Also enclose the entire path name after the equal sign (=) in double quotation marks (").

If specifications are duplicated, the priority is as follows:

• The specification for a JP1 user has priority over the specification for all JP1 users. If a transfer file with a search path that was specified for a JP1 user is found, a search using the search path specified for all JP1 users is not performed.

• If a JP1 user name is duplicated, the most recent specification has priority.

For details, see 6.2.2 Defining search paths for a file to be transferred (for Windows) or 15.2.2 Defining search paths for a file to be transferred (for UNIX).

To Page Top

(75) ConnectTimeout (for the command and scheduler to be used for job execution)

Use this parameter to specify the TCP/IP connection timeout value.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"ConnectTimeout" = dword:definition-of-the-TCP/IP-connection-timeout-value-for-job-execution-and-schedulers-commands

Specifiable values

A hexadecimal value (in milliseconds) from 00002710 to 000927C0 (10,000 to 600,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal, which is 90 seconds)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

• If you decrease the connection timeout value, a timeout might occur before the connection is completed, resulting in a TCP/IP communication connection error.

• Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this parameter is reached.

To Page Top

(76) CommunicateRetryCount (for the command and scheduler to be used for job execution)

Use this parameter to specify the number of retries for a TCP/IP connection error.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"CommunicateRetryCount" = dword:definition-of-number-of-retries-for-an-TCP/IP-connection-error-for-job-execution-and-scheduler-commands

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you increase the value for number of retries too much, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

To Page Top

(77) CommunicateRetryInterval (for the command and scheduler to be used for job execution)

Use this parameter to specify the TCP/IP connection error retry interval.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"CommunicateRetryInterval" = dword:definition-of-the-TCP/IP-connection-error-retry-interval-for-job-execution-and-scheduler-commands

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (1 to 300 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you decrease the value for the retry interval to so that it is too small, the communication retry interval will be too short. As a result, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

To Page Top

(78) CommunicateTimeout

Use this parameter to specify the communication timeout period.

For details, see 6.2.14 Changing the timeout value for the job execution control manager process (for Windows) or 15.2.14 Changing the timeout value for the job execution control manager process (for UNIX).

Format

"CommunicateTimeout" = dword:setting-value

Specifiable values

A hexadecimal value (in milliseconds) from 000927c0 to 0036EE80 (600,000 to 3,600,000 in decimal)

Default value

dword:000927c0 (600,000 in decimal, which is 10 minutes)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(79) MacroOptionReplaceMode

When the passing information in a macro variable that has no characters before and after it is a NULL character string, use this parameter to specify whether to replace the macro variable name with a NULL character string.

For details, see 6.2.11 Setting the handling of a macro variable when the value is a NULL string (for Windows) or 15.2.11 Setting the handling of a macro variable when the value is a NULL string (for UNIX).

Format

"MacroOptionReplaceMode" = dword:whether-to-replace-the-passing-information-in-a-macro-variable-with-a-NULL-character-string

Specifiable values

0

The specified macro variable name is used as is as a character string. There is no replacement with a NULL string.

1

The macro variable name is replaced with a NULL string.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(80) IsHA (for the command and scheduler to be used for job execution)

Use this parameter to specify the definition for setting up a cluster environment for the commands and schedulers used for job execution. Specify this parameter only to stop cluster use.

Format

"IsHA" = dword:definition-for-the-cluster-environment-setup-for-the-commands-and-schedulers-used-for-job-execution

Specifiable values

0

Specifies to stop cluster use.

1

If you execute setup when operating a cluster system, this value is automatically set to the parameter for the physical and logical hosts.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(81) PassingInfoUsePreRc

Specify whether to enable or disable the return value of the preceding job in a passing information setting job.

For details, see 6.2.25 Settings for using the return value of the preceding job in the passing information setting jobs (for Windows) or 15.2.23 Settings for using the return value of the preceding job in the passing information setting jobs (for UNIX).

Format

"PassingInfoUsePreRc"=dword:settings-for-using-the-return-value-of-the-preceding-job-in-the-passing-information-setting-jobs

Specifiable values

0

Regardless of the return value of the preceding job, the return value of the passing information setting job itself is set.

1

If the return value of the preceding job is 0, the return value of the passing information setting job itself is set.

If the return value of the preceding job is a return value other than 0, the return value of the preceding job in set as the return value of the passing information setting job.

Default value

dword:00000001 (1 in decimal)

During a new installation of JP1/AJS3, dword:00000000 (0 in decimal) is set.

Recommended value

dword:00000000 (0 in decimal)

When the setting takes effect

Immediately (the next time a passing information setting job is executed)

To Page Top

(82) ConnectTimeout (for the status reporting process for job execution control)

Use this parameter to specify the TCP/IP connection timeout value.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"ConnectTimeout" = dword:definition-of-the-TCP/IP-connection-timeout-value-in-the-status-reporting-process-for-the-job-execution-control

Specifiable values

A hexadecimal value (in milliseconds) from 00002710 to 000927C0 (10,000 to 600,000 in decimal)

Default value

dword:00015F90 (90,000 in decimal, which is 90 seconds)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary notes

• If you decrease the connection timeout value, a timeout might occur before the connection is completed, resulting in a TCP/IP communication connection error.

• Depending on the connection timeout specifications and the settings for the OS, a connection timeout might occur before the value specified for this parameter is reached.

To Page Top

(83) CommunicateRetryCount (for the status reporting process for job execution control)

Use this parameter to specify the number of retries for a TCP/IP connection error.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"CommunicateRetryCount" = dword:definition-of-the-number-of-retries-for-a-TCP/IP-connection-error-in-the-status-reporting-process-for-job-execution-control

Specifiable values

A hexadecimal value from 00000000 to 00000064 (0 to 100 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you increase the value for number of retries too much, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

To Page Top

(84) CommunicateRetryInterval (for the status reporting process for job execution control)

Use this parameter to specify the TCP/IP connection error retry interval.

For details about the definition, see 6.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for Windows) or 15.2.8 Changing the timeout period, interval of retries, and number of retries for TCP/IP connections (for UNIX).

Format

"CommunicateRetryInterval" = dword:definition-of-the-TCP/IP-connection-error-retry-interval-in-the-status-reporting-process-for-job-execution-control

Specifiable values

A hexadecimal value (in seconds) from 00000001 to 0000012C (1 to 300 in decimal)

Default value

dword:00000014 (20 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

Cautionary note

If you decrease the value for the retry interval so that it is too small, the communication retry interval will be too short. As a result, unavoidable communication errors might cause the number of TCP/IP connection errors to increase.

To Page Top

(85) IsHA (for the status reporting process for job execution control)

Use this parameter to specify the definition for setting up a cluster environment for the status reporting process for job execution control. Specify this parameter only to stop cluster use.

Format

"IsHA" = dword:definition-for-cluster-environment-setup-for-the-status-reporting-process-for-job-execution-control

Specifiable values

0

Specifies to stop cluster use.

1

If you execute setup when operating a cluster system, this value is automatically set to the parameter for the physical and logical hosts.

Default value

dword:00000000 (0 in decimal)

Recommended value

None

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(86) MergeEnvMode

Use this parameter to specify whether an environment variable in a job definition is enabled when the name is the same as a system environment variable name.

For details, see 6.2.21 Settings for enabling an environment variable in a job definition when the name is the same as a system environment variable name.

Format

"MergeEnvMode" = dword:definition-for-whether-an-environment-variable-in-a-job-definition-is-enabled-when-the-name-is-the-same-as-a-system-environment-variable-name

Specifiable values

0

Specify this value to disable an environment variable in a job definition when the name is the same as a system environment variable name.

1

Specify this value to enable an environment variable in a job definition when the name is the same as a system environment variable name.

Default value

dword:00000000 (0 in decimal)

During a new installation of JP1/AJS3, dword:00000001 (1 in decimal) is set.

Recommended value

dword:00000001 (1 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(87) UACAdministratorsExec (for job)

Use this parameter to specify whether a user can execute jobs as a user with administrator permissions when Standard is specified for Exec. Service of the job and the UAC function is enabled.

For details, see 6.2.22 Settings for executing jobs as a user with administrator permissions when the UAC is enabled.

Format

"UACAdministratorsExec" = dword:setting-for-executing-jobs-as-a-user-with-administrator-permissions-when-UAC-is-enabled

Specifiable values

0

When the UAC function is enabled, all OS users who belong to the Administrators group execute jobs with the administrator permissions disabled. However, the built-in Administrator and an OS user whose account is the same as the JP1/AJS3 service account are excluded.

1

When the UAC function is enabled, an OS user who belongs to the Administrators group executes jobs as a user with administrator permissions.

When you specify 1, the Log on as a batch job permission must be set for all OS users (including standard users) who execute jobs.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(88) GetPasswd_RetryCount

Use this parameter to specify the number of retry attempts when an attempt to acquire user information from the OS password file has failed.

Usually, you do not need to change this value.

For details, see 15.2.20 Changing the settings for retries when user information is acquired.

Format

"GetPasswd_RetryCount" = dword:number-of-retry-attempts-when-an-attempt-to-acquire-user-information-from-the-OS-password-file-has-failed

Specifiable values

A hexadecimal value from 00000000 to 0000000A (0 to 10 in decimal)

If you specify dword:00000000, a retry is not performed.

Default value

dword:00000002 (2 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(89) GetPasswd_RetryInterval

Use this parameter to specify the retry interval when an attempt to acquire user information from the OS password file has failed.

Usually, you do not need to change this value.

For details, see 15.2.20 Changing the settings for retries when user information is acquired.

Format

"GetPasswd_RetryInterval" = dword:retry-interval-when-an-attempt-to-acquire-user-information-from-the-OS-password-file-has-failed

Specifiable values

A hexadecimal value (in milliseconds) from 00000000 to 00002710 (0 to 10,000 in decimal)

If you specify dword:00000000, a retry is performed immediately.

Default value

dword:000003E8 (1,000 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(90) IgnoreResultFileError (for job)

Use this parameter to specify the operation to be executed if an error occurs during the transfer processing of a job result file (standard output file or standard error output file) and if Standard is specified for Exec. Service.

For details, see 6.2.24 Operation settings when job result file transfer fails (Windows), or 15.2.22 Operation settings when job result file transfer fails (UNIX).

Format

"IgnoreResultFileError" = dword:operation-if-a-transfer-error-occurs-in-a-job-result-file

Specifiable values

0

If an error occurs during the transfer processing of a job result file, -1 is set as the job return code and the job status is set to Ended abnormally.

1

If an error occurs during the transfer processing of a job result file, the return code of the job process is set as the job return code and the job status is set to Ended normally, Ended with warning, or Ended abnormally according to how the end of processing is judged.

Default value

dword:00000000 (0 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(91) PreventResultFileLack

Use this parameter to specify whether all data generated by jobs is output to result files.

For details, see 6.2.26 Setting for ensuring that data generated by jobs is output to result files.

Format

"PreventResultFileLack" = dword:setting-for-ensuring-that-data-generated-by-jobs-is-output-to-result-files

Specifiable values

0

If 0 is specified, data generated by jobs might not be output to result files if disk access or restart of processing takes time. (For example, restart of processing takes time when the memory used by JP1/AJS3 is swapped out.)

1

If 1 is specified, data generated by jobs is output to result files even if disk access or restart of processing takes time. (For example, restart of processing takes time when the memory used by JP1/AJS3 is swapped out.)

Default value

dword:00000000 (0 in decimal)

Recommended value

Depends on the user environment.

Note that 1 is recommended if you use the passing information setting job.

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(92) SendFileSizeStatus

Use this parameter to specify the behavior when the size of transmitted files exceeds the upper limit.

For details, see 6.2.27 Placing restrictions on file transmission (for Windows) or 15.2.24 Placing restrictions on file transmission (for UNIX).

Format

"SendFileSizeStatus"=dword:behavior-when-file-size-reaches-the-upper-limit

Specifiable values

0

The size of transmitted files is checked, and the KAVU3507-I message is output when the size of transmitted files reaches the upper limit.

All data of result files is transmitted, and the status of job termination is inherited.

1

The size of transmitted files is checked, and the KAVU3508-I message is output when the size of transmitted files reaches the upper limit.

Result files are transmitted up to the total size as large as the upper-limit size (value specified in the LimitSendFileSize environment setting parameter), and the file data exceeding the upper-limit size is discarded. Then, the termination status of the job is set to Ended abnormally, and the KAVU3510-E message is output.

For details about the termination code and status, see 6.2.27(3) Behavior when the size of transmitted files exceeds the upper limit (for Windows) or 15.2.24(3) Behavior when the size of transmitted files exceeds the upper limit (for UNIX).

2

The size of transmitted files is checked, and the KAVU3508-I message is output when the size of transmitted files reaches the upper limit.

Result files are transmitted up to the total size as large as the upper-limit size (value specified in the LimitSendFileSize environment setting parameter), and the file data exceeding the upper-limit size is discarded. Then, the termination status of the job is set to Ended with warning, and the KAVU3509-W message is output. If the job status on the agent host was Ended abnormally, the status is inherited.

For details about the termination code and status, see 6.2.27(3) Behavior when the size of transmitted files exceeds the upper limit (for Windows) or 15.2.24(3) Behavior when the size of transmitted files exceeds the upper limit (for UNIX).

3

The size of transmitted files is checked, and the KAVU3508-I message is output when the size of transmitted files reaches the upper limit.

Result files are transmitted up to the total size as large as the upper-limit size (value specified in the LimitSendFileSize environment setting parameter), and the file data exceeding the upper-limit size is discarded. As the job termination status, the termination status on the agent host is inherited.

For details about the termination code and status, see 6.2.27(3) Behavior when the size of transmitted files exceeds the upper limit (for Windows) or 15.2.24(3) Behavior when the size of transmitted files exceeds the upper limit (for UNIX).

When this value is specified, the job status will be Ended normally even if the size of transmitted files exceeds the upper limit. However, because the result files are not complete yet, make sure that the incomplete result files will not cause any problems in cases such as when a succeeding job will reference the result files.

Default value

dword:00000000 (0 in decimal)

During a new installation of JP1/AJS3, dword:00000003 (3 in decimal) is set.

Recommended value

dword:00000003 (3 in decimal)

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(93) LimitSendFileSize

Use this parameter to specify the upper limit of the size of transmitted files.

If the size of the result files used during job execution exceeds a value estimated based on operation, the agent host limits the size of the files to be transmitted. We recommend that you set the upper limit of file size to a value (around 3 megabytes) that is appropriate to your operations.

The set upper limit is used to check the total size of result files (standard output and standard error output files).

Note that checking with the upper limit might have a margin of error of plus or minus several hundred bytes from the data transmitted to the manager.

The following shows how to estimate the file size (in units of bytes):

For details, see 6.2.27 Placing restrictions on file transmission (for Windows) or 15.2.24 Placing restrictions on file transmission (for UNIX).

Format

"LimitSendFileSize"=dword:upper-limit-of-the-size-of-transmitted-files

Specifiable values

A hexadecimal value (in bytes) from 00080000 to 08000000 (524,288 to 134,217,728 in decimal)

Default value

dword:00300000 (3,145,728 in decimal)

Recommended value

Default value

When the setting takes effect

After JP1/AJS3 is restarted

To Page Top

(94) JobHistoryLogFileSize

Use this parameter to specify the size of the job execution history log file that is output by JP1/AJS3 - Agent Minimal Edition.

This parameter applies to JP1/AJS3 - Agent Minimal Edition only. Even if a value is set for this parameter, the value will not apply to JP1/AJS3 - Agent or JP1/AJS3 - Manager.

Format

"JobHistoryLogFileSize"=dword:size-of-the-job-execution-history-log-file

Specifiable values

A hexadecimal value (in kilobytes) from 00000200 to 00001000 (512 to 4,096 in decimal)

Default value

dword:00000200 (512 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

Before changing the value of this parameter, you must delete existing job execution history log files and the management file for these files.

For details about how to change the parameter, see G.2(3) Estimating the job execution history log file in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

To Page Top

(95) JobHistoryLogFileCount

Use this parameter to specify the number of job execution history log files that are output by JP1/AJS3 - Agent Minimal Edition.

This parameter applies to JP1/AJS3 - Agent Minimal Edition only. Even if a value is set for this parameter, the value will not apply to JP1/AJS3 - Agent or JP1/AJS3 - Manager.

Format

"JobHistoryLogFileCount"=dword:number-of-the-job-execution-history-log-files

Specifiable values

A hexadecimal value from 00000002 to 00000010 (2 to 16 in decimal)

Default value

dword:00000002 (2 in decimal)

Recommended value

Set the value appropriate for the operating environment.

When the setting takes effect

The next time the JP1/AJS3 service is started

Cautionary note

Before changing the value of this parameter, you must delete existing job execution history log files and the management file for these files.

For details about how to change the parameter, see G.2(3) Estimating the job execution history log file in the JP1/Automatic Job Management System 3 System Design (Configuration) Guide.

To Page Top