Job Information

The Job Information stores the information about the commands that you run as a job before sending, after sending, or after receiving. A maximum of five jobs can be registered per Job ID. There are two ways to register records in the information.

Registration using the Management Console

->Refer to Creating and editing a record of the Job Information.
Registration using parameter file and command

->Refer to Management Information Batch Registration command.

Fields

The table below carries the values and optional statuses for the registration using the Management Console. The optional statuses for the registration using parameter file and command may differ from those for the registration using the Management Console. For the detail on optional statuses for the registration using parameter file and command, refer to Management Information Batch Registration command.

Table 2.7 Fields of the Job Information
Field Name		Default Value	Valid Values	Optional	Remarks
Screen	File	Default Value	Valid Values	Optional	Remarks
Job ID	JOB		Alphanumeric characters and "_"		Within 50 bytes starting with an alphabetic letter
Job Description	JOBDESC		Alphanumeric characters		In the range of 3 to 21 bytes
Job Name	JOB DEF to DEFEND		Alphanumeric characters		Within 210 bytes per job (*1)
Comment	COMMENT		Characters	✔	Within 60 bytes

✔	:	Optional
Blank	:	Mandatory
*1	:	You can register a string "DEFEND" as a value for the Job Name on HULFT Management Console. However, you cannot register a string "DEFEND" as a value for the Job Name when you use the Management Information Batch Registration command (UTLIUPDT), because the string is a reserved word in the command.

Explanations of each field

This section explains the fields to be specified in a record of the Job Information. A string within brackets () is the tag of a field name to be specified when you use a parameter file to register the information.

Job ID (JOB)

ID to identify the user job that is to be started

This ID is used as a job ID in the Send Management Information and in the Receive Management Information.

Job Description (JOBDESC)

Job description name

Specify the name in the format of Library name/Job description name.

Job Name (JOB DEF to DEFEND)

CL commands

Specify the CL command to run.

Comment (COMMENT)

Comment on the user job to run

Points to be noted on the settings

Specifying multiple jobs

After you submit the job that you specified for the Job Name as a program of HULFT, execute the REXX procedure. When a number of jobs are specified, the jobs are executed in a sequence. They are not executed in parallel.

Pre-send job error

When the Pre-send Job ends with an error, the Send File is terminated with an error.

Unsuccessful end of job

If a post-send or post-receive job ended with an error, execution of subsequent jobs is suppressed when a severity level higher than Job Interrupt Severity specified in the System Environment Settings is detected. When the job is not a CL command, the job may not be able to be run.

Entry of single quotes

When you use single quotation (') in a Job Name, specify two single quotations ('') consecutively.

Replacement of messages

By describing a variable substitution from "$MSG0" to "$MSG5" or from "$MSGL0" to "$MSGL1" in a parameter value of a job, you can assign a transmitted replacement message to the variable (except for the Job Name).

Depending on the language setting of the host that you communicate, the messages may not be assigned properly and the replacement messages may cause transfer to end with an error in some cases. For notes on message transmissions, refer to the following:

HULFT10 for IBMi Administration Manual : Message Transmission

Message on job execution

If the Post-send Job or the Post-receive Job fails to start due to wrong specification, HULFT outputs a message to the output queue (OUTQ) for star of the Send system and the Receive system when attempting to execute the job. Check that the output queue is not connected to a printer. Also, delete the messages from the output queue regularly.

For the details of output queue, refer to the relevant document of IBM i.

Exceptional cases for the Job Description in the Job Information

Regarding jobs given in the following table, script of the Job Description in the Job Information is ignored, even though it is specified.

Table 2.8 Exceptional cases for job description
Job	Execution Environment Used
Pre-send job	User who issued UTLSEND
Post-receive successful job (when Notification is set to "J" (Successful Job Completion) in the Receive Management Information )	Receive job
Job to be executed according to the request by the Remote Job Execution program	Request job

Relation between the job description and job execution

HULFT uses the Job Description specified in the Job Information when the application internally submits (by using the SBMJOB command) the specified job as a subsequent job.

The relation between the default values of each parameter in the SBMJOB (Submit Job) command of IBM i and the values actually used on HULFT is shown in table below:

Table 2.9 Default value for the parameter and the value used when the job is executed
Default Value	Value Used
*JOBD	Value of the job description specified in the Job Information
Other than "*JOBD"	Value specified as the default value