15.2.24 Placing restrictions on file transmission

When a job^# has been executed in JP1/AJS3, result files (standard output and standard error output files) are transferred between the manager and agent hosts. If the size of these files exceeds a few megabytes, file data analysis and file data transfer impose a load on the manager host. As a result, CPU and memory usages increase, and job execution is delayed, which might degrade overall system performance.

#:: The description in this subsection applies to only PC jobs, Unix jobs, custom jobs, QUEUE jobs executed by JP1/AJS3, and submit jobs. The description does not apply to event jobs, custom event jobs, passing information setting jobs, HTTP connection jobs, flexible jobs, and queueless jobs.

Placing restrictions on file transmission enables you to set an upper limit on the total size of the results files (standard output and standard error output files) that are transmitted by the agent host when a job is executed.

You can also specify the behavior (that is, the status of job termination) and the message to be output when the size of the transmitted files exceeds the upper limit.

The following table describes the behavior and how file data is handled when the size of transmitted files exceeds the upper limit.

Table 15‒46: Behavior and how file data is handled when the size of transmitted files exceeds the upper limit
File type	Category	Value of the SendFileSizeStatus environment setting parameter
File type	Category	0	1	2	3
Result file	Job status	Actual termination status of the job	Ended abnormally	Ended with warning^#	Actual termination status of the job
	Type of message to be output	Information	Information Error	Information Warning	Information
	Handling of file data	Sending all file data	Discards the file data that exceeds the upper limit for a file size	Discards the file data that exceeds the upper limit for a file size	Discards the file data that exceeds the upper limit for a file size

#:: If the job status on the agent host is Ended abnormally, that status is inherited.

Organization of this subsection

(1) Definition procedure
(2) Environment setting parameter
(3) Behavior when the size of transmitted files exceeds the upper limit
(4) Note

(1) Definition procedure

Execute the following command to set the environment setting parameter described in (2) below:
```
jajs_config -k "definition-key" "parameter-name-1"=value-1 ["parameter-name-2"=value-2]
```
Restart JP1/AJS3.

The new settings are applied to the configuration definition.

To Page Top

(2) Environment setting parameter

Table 15‒47: Environment setting parameters to place restrictions on file transmission
Definition key	Environment setting parameter	Explanation
`[{JP1_DEFAULT\|logical-host}\JP1NBQAGENT\Job]`^#	`"SendFileSizeStatus"=`	Specifies the behavior when the file size reaches the upper limit.
`[{JP1_DEFAULT\|logical-host}\JP1NBQAGENT\Job]`^#	`"LimitSendFileSize"=`	Specifies the upper limit for a file size.

#:: The specification of the {JP1_DEFAULT|logical-host} part depends on whether the host is a physical host or a logical host. For a physical host, specify JP1_DEFAULT. For a logical host, specify the logical host name.

For details about the definition of these environment setting parameters, see the following:

To Page Top

(3) Behavior when the size of transmitted files exceeds the upper limit

The following describes the behavior when the size of transmitted files exceeds the upper limit:

Result files

Assume that the size of transmitted files reaches the upper limit when the value of the SendFileSizeStatus environment setting parameter is 1, 2, or 3. Then, the standard output and standard error output files up to the total size as large as the upper-limit size are transmitted to the agent host. Because the result files are not complete, 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.

The following table describes the return codes and end status of a job in the case when the size of its result files exceeds the upper limit.

Table 15‒48: End status and return codes when the size of result files exceeds the upper limit
Actual job status	Category	Value of SendFileSizeStatus environment setting parameter
Actual job status	Category	1	2	0 or 3
Ended normally (Including cases when Always normal is specified)	Status	Ended abnormally	Ended with warning	Ended normally
	Return code	Return value of the job^#	Return value of the job^#	Return value of the job^#
Ended with warning	Status	Ended abnormally	Ended with warning	Ended with warning
Ended with warning	Return code	Return value of the job^#	Return value of the job^#	Return value of the job^#
Ended abnormally	Status	Ended abnormally	Ended abnormally	Ended abnormally
Ended abnormally	Return code	Return value of the job^#	Return value of the job^#	Return value of the job^#
Killed	Status	Killed	Killed	Killed
Killed	Return code	PC job (`-1`), Unix job (`255`)	PC job (`-1`), Unix job (`255`)	PC job (`-1`), Unix job (`255`)
Failed to start	Status	Failed to start	Failed to start	Failed to start

#:: Return code of the job process executed as a job

To Page Top

(4) Note

When executing a passing information setting job, set an appropriate value for the LimitSendFileSize environment setting parameter. If the preceding job outputs a standard output file whose file size is larger than the value of the LimitSendFileSize environment setting parameter, the passing information setting job might fail in retrieving information from the standard output file.

To Page Top