Job Information

You can register commands to start a job before sending, after sending, after receiving, or after detection with the File Trigger function. A maximum of 13 jobs can be registered per Job ID. There are two ways to register the information.

(1) Field List

In the table below, the check marks in the Optional column indicate the fields considered optional during registration from the HULFT Management Console. Optional fields and mandatory fields for registration by running commands with parameter files may differ from those for registration using the HULFT Management Console.

For details on optional fields and mandatory fields for registration by running commands with parameter files, refer to Management Information Batch Registration command.

Table 2.8 List of Job Information Fields

Field Value

Default Value

Setting Value

Optional

Remarks

Screen

File

Job ID

JOB

 

Alphanumeric characters

-

Within 50 bytes

Comment

COMMENT

 

Characters

✓

Within 60 bytes

Job Name

JOB DEF to DEFEND

 

Alphanumeric characters

-

Within 200 bytes

✓

:

Optional

-

:

Mandatory

(2) Explanation of each field

This section explains the fields to be specified in the Job Information. The parenthesized strings are the names of each field and you can use them as field tags in a parameter file when registering the information.

Job ID (JOB)

ID that identifies the job to be started

This Job ID is related to Job ID in the Send Management Information, the Receive Management Information, or the File Trigger Information.

Comment (COMMENT)

Comment for the Startup Job

Job Name (JOB DEF to DEFEND)

Shell script names or program names

Specify the file name with a full path.

When parameters are specified, they are separated by spaces.

(3) Points to be noted when setting

If multiple jobs are specified

If multiple jobs are specified, they are executed in the order of registration. They are not executed concurrently. The subsequent jobs are not executed if a job ends unsuccessfully.

Replacement Message

Specify a variable from '$MSG0' to '$MSG5' or from '$MSGL0' to '$MSGL1' for Job Name to replace the string with the transmitted message.

HULFT may not be able to replace the variables with the messages correctly and the transfer may fail, depending on the language settings on the remote host.

For points to be noted on message transmission, refer to Administration Manual.

(4) Points to be noted when operating

Permissions at job execution

A job is executed with the permissions for the process in which the job is executed.

For example, a Post-send Job is executed with the permissions that are granted to the user account that started the Send daemon.

For details on permissions at job execution, refer to Administration Manual.