4.3.6 Options related to job execution

(1) Defining the work path for job execution as a variable

If a different installation path is used for JP1/AJS3 at each agent host, or if the JP1/AJS3 installation path at an agent host is not defined in the environment variable PATH, by defining the installation path at the agent hosts as a variable, you can enable jobs to be executed regardless of where JP1/AJS3 is installed on the agent.

We recommend that you define the work path for job execution as a variable when JP1/AJS3 runs in different environments; for example, when the executable files for job execution reside on the C drive in one agent host, and on the D drive in another agent host.

For details about setting the work path as a variable, see 6.2.1 Defining variables for work paths used during job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows systems) or 15.2.1 Defining variables for work paths used during job execution in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX systems).

To Page Top

(2) Executing jobs with long file names (Windows only)

When a job is executed, the name of the executable file is converted to a short file name recognized by NTFS (NT file system) volumes and FAT (file allocation table) volumes. We recommend that you enable this option if you want to run job executable files with long file names without converting them to short file names.

For details about this option, see 6.2.15 Executing a job by using a long file name in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

To Page Top

(3) Defining the search path for transfer files

In JP1/AJS3, you can transfer the text files required for job execution from the manager host to an execution agent host. For example, you can transfer a settings file (.ini file) in which the environment (path and so on) of the executable file is defined.

You can pre-define a search path. When you specify the files to transfer from the manager host to the agent host, JP1/AJS3 will look for the files in that search path, and forward those found.

We recommend that you enable this option if you want to define the files to be transferred without specifying their paths.

For details about this option, see 6.2.2 Defining search paths for a file to be transferred in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for Windows systems) or 15.2.2 Defining search paths for a file to be transferred in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1 (for UNIX systems).

To Page Top

(4) Setting the pipe communication timeout value for an agent (UNIX only)

A timeout might occur during pipe communication between agent processes of the job execution control. Possible causes of this timeout are:

• A large number of jobs were executed at one time.

• The CPU has a high load.

• Due to insufficient real memory, the agent process of the job execution control was swapped out and not executed for 300 seconds or longer.

If these problems remain unresolved and pipe communication timeout errors are likely to recur, we recommend that you increase the timeout for pipe communication at the host on which the agent processes run.

Important note

If the setting for pipe communication timeout is too long, job errors might take longer to be detected.

For details about setting the pipe communication timeout, see 15.2.15 Changing the timeout value for pipe communication of the agent in the Job Management Partner 1/Automatic Job Management System 3 Configuration Guide 1.

To Page Top