List of Job Information fields

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. For the registration method, refer to Using the Job Information.

Field List

Table 4.41 List of Job Information Fields

Field Name

Default Value

Setting Value

Optional

Remarks

Screen

File

Job ID

JOB

 

Alphanumeric characters and "_"

-

Within 50 bytes

Comment

COMMENT

 

Characters

Within 60 bytes (*1)

Startup Job

JOB DEF to DEFEND

 

Alphanumeric characters

-

Within 200 bytes

:

Optional

-

:

Mandatory

*1

:

On the HULFT Manager Management Console, you can enter a string of up to 60 characters. When the destination host is HULFT Ver.8.1 or higher, the size of the string that you entered will be checked based on the code set that is set in HULFT at the connection destination. When HULFT checks and confirms that the size of the string meets the condition that is given in the remarks, the characters that you entered will be saved in HULFT.

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 associated with Job ID in the Send Management Information, the Receive Management Information, or the File Trigger Information.

Comment (COMMENT)

Comment for the Startup Job

Startup Job (JOB DEF to DEFEND)

Shell script names or program names

Specify the file name with a full path.

Use space as the delimiter when setting the parameters.

Points to be noted when configuring settings

If multiple jobs are specified

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

Replacement Message

Specify '$MSG0' to '$MSG5' or '$MSGL0' to '$MSGL1' in the startup job to replace the strings with received messages.

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 host on the sending side.

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

Points to be noted when operating

Permissions at job execution

A job is executed with the permissions that are granted to the user account that started 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 Linux/AIX Administration Manual.