Send Management Information

Basic Settings

File Name (FILENAME)

Specify a file to send (called Send file, or send target file) that is stored on a Windows operating system.

Specify the file name with a full path.

In HULFT8 Server grade environments, you can specify a file that uses network resources. For details, refer to the explanation of networked files in Administration Manual.

Transfer Type (TRANSTYPE)

Data type of the file to send

FORMAT (F):

Format data

BINARY (B):

Binary data

TEXT (T):

Text data

MULTIFORMAT (M):

Multi format data

Format/Multi Format ID (FMTID)

ID of the record in which the format or formats of the Send file is registered

For details on format IDs, refer to Format Information.

For details on multi format IDs, refer to Multi Format Information.

When Transfer Type is specified as 'FORMAT' (F), the format ID is mandatory, and when Transfer Type is specified as 'MULTIFORMAT' (M), the multi format ID is mandatory.

Compression Preference (COMP)

Compression type that is used when a file is transferred

None (N):

No compression

Horizontal (1):

Compression within records

Vertical (2):

Compression across records

DEFLATE (3):

DEFLATE compression

Compression Unit (COMPSIZE)

Processing unit of records when compressing binary files

The higher the value, the faster the processing speed (however, if you set a higher value, compression will require more memory).

You cannot omit this field in the following cases:

• When Transfer Type is set to "BINARY" (B) and Compression Preference is set to "Horizontal" (1)

• When Transfer Type is set to "BINARY" (B) and Compression Preference is set to "Vertical" (2)

DEFLATE Level (DEFLATELEVEL)

Compression level for DEFLATE compression

This field can be set only if 'DEFLATE' (3) is specified for Compression Preference.

• Compression Speed (S)

• Standard (D)

• Compression Ratio (C)

Omitting this field sets 'Standard' (D).

Code Conversion (KJCHNGE)

Specify the option for code conversion of the send target file

Sending Side (S):

Carry out code conversion on the host on the sending side

Receiving Side (R):

Carry out code conversion on the host on the receiving side

No Conversion (N):

Send the file without carrying out code conversion

EBCDIC Set (CODESET)

Specify Type-EBCDIC Code Set that is used for the conversion of single-byte codes

Specify the EBCDIC Set for the receiving-side host (remote host).

• Autoconfiguration (0)

• Katakana (A)

• Lower Case (B)

• ASCII (C)

• ASPEN (D)

• Japan (Latin) for IBM (E)

• Japan (Latin) Extended for IBM (F)

• NEC Katakana (G)

• Japan (Katakana) Extended for IBM (H)

• Simplified Chinese Extended (I)

• User Table 1 (V)

• User Table 2 (W)

• User Table 3 (X)

Omitting this field sets 'Autoconfiguration' (0).

This setting is valid when the host on the receiving side is a Type MF-IBMi host and you specify sending-side conversion.

Send File Mode (CLEAR)

Specify the mode for exclusive control of the Send file applied during the sending, and the handling of the file in the case where the sending ends successfully.

Keep (K):

Do not lock the file while sending is in progress. HULFT saves the file after the sending ends successfully.

Clear (C):

Lock the file while sending is in progress. After the sending ends successfully, HULFT clears the file and the size of the file becomes 0 bytes.

Delete (D):

Lock the file while sending is in progress. HULFT deletes the file after the sending ends successfully.

Lock (L):

Lock the file while sending is in progress. HULFT saves the file after the sending ends successfully.

Omitting this field sets 'Keep' (K).

Transfer Group ID (GRPID)

ID of the record in which the send destination of the Send file is registered

For details on transfer group IDs, refer to Transfer Group Information.

Pre-send Job ID (PREJOBID)

ID of the job to be executed before HULFT starts the Send processing

For details on job IDs, refer to Job Information.

If omitted, HULFT does not start the specified job.

Successful Job ID (JOBID)

ID of the job to be executed when the Send processing ends successfully

For details on job IDs, refer to Job Information.

If omitted, HULFT does not start the specified job.

Unsuccessful Job ID (EJOBID)

ID of the job to be executed when the Send processing ends unsuccessfully

For details on job IDs, refer to Job Information.

If omitted, HULFT does not start the specified job.

Extension Settings

Interface DBID (DBID)

Format of sent data used as interface on the receiving side

CSV:

Convert the Receive file into CSV format on the host on the receiving side

To receive the receive file in CSV format on the receiving-side host (for UNIX, Linux, NonStop, or Windows), specify "CSV".

When you omit this field, HULFT does not carry out receiving in CSV format.

When you use the Interface function, specify 'FORMAT' (F) or 'MULTIFORMAT' (M) for Transfer Type.

Transfer Interval (INTERVAL)

Interval per transfer unit (Transfer Block Length x Transfer Block Count)

Omitting this field sets '0.'

Transfer Priority (TRANSPRTY)

Priority in queue used when starting the file transfer

A smaller number means a higher priority.

Transfer Block Length (BLOCKLEN)

Length of one block for transferring data

The product of the values for Transfer Block Length (BLOCKLEN) and Transfer Block Count (BLOCKCNT) cannot exceed 65520.

Transfer Block Count (BLOCKCNT)

The number of blocks per transfer

The product of the values for Transfer Block Length (BLOCKLEN) and Transfer Block Count (BLOCKCNT) cannot exceed 65520.

Shiftcode Mode (SHIFTTRANSACT)

Shift code mode at the time of code conversion to a Type MF-IBMi host

Add (Y):

Add shift codes

Do not add (N):

Do not add shift codes

Omitting this field sets 'Add' (Y).

Mail Interface ID (MAILID)

Mail interface ID for the email that is issued after the file is sent

When you omit this field, HULFT does not interface with email.

Cipher Key (PASSWORD) (when Forced Strong Key mode is disabled)

Key that HULFT uses when encrypting the data

You can apply security to the file to send. Specify the same cipher key as the one specified in the Receive Management Information of the remote host.

When you omit this field, HULFT does not encrypt the file.

Cipher Key (PASSWORD) (when Forced Strong Key mode is enabled)

Key that HULFT uses when encrypting the data

You can apply security to the file to send. Specify the same cipher key as the one specified in the Receive Management Information of the remote host.

Make sure that you specify Cipher Key. If the receiving-side host is not in Forced Strong Key mode, a transfer error occurs.

File ID

You cannot specify "_INSTANT_TRANSFER_" for File ID (SNDFILE).

Compression Preference

Even if 'DEFLATE' (3) is specified for Compression Preference, the file is transferred without being compressed in the following cases:

• When the HULFT on the host on the receiving side is lower than Ver.8

• When 'Yes' (Y) is specified for Use HULFT7 Comm. Mode (HUL7MODE) in the Host Information

Compression Unit

Even if '0' is specified for Compression Unit (COMPSIZE), compression is carried out in the following case:

• When 'DEFLATE' (3) is specified for Compression Preference

DEFLATE Level

This field cannot be specified if one of the following values for Compression Preference is selected:

• None (N)

• Horizontal (1)

• Vertical (2)

Code Conversion

• When the receiving-side host runs a version of HULFT for Mainframe that is lower than Ver.8.4 and "8" (UTF-8) is specified for Code Set for Transfer in the System Environment Settings of the receiving-side host, you cannot specify "Receiving Side" (R).

• When both the sending-side host and the receiving-side host are Ver.8.4 or higher, the code converting side may switch to the receiving-side even if you specify "Sending Side" (S) for Code Conversion (KJCHNGE), or switch to the sending-side even if you specify "Receiving Side" (R) for Code Conversion. For details, refer to the explanation about the sending-side conversion and receiving-side conversion in Code Conversion Manual.

Send File Mode

• When an option other than 'Keep' (K) is selected, multicasting cannot be executed.

• When the specified Send file is used by HULFT and other user applications simultaneously, and 'Delete' (D) is specified for Send File Mode, the file may be unlocked for a moment, because the deletion will be executed after HULFT closes the file after transfer is complete.

  For details on the exclusive lock across the user applications, refer to Administration Manual.

Transfer Block Length and Transfer Block Count

If you specify '0' for both Transfer Block Length and Transfer Block Count, HULFT automatically optimizes the size of the Transfer Unit (Transfer Block Length x Transfer Block Count).

However, if you specify '0' only for Transfer Block Length or only for Transfer Block Count, an error occurs.

For details, refer to Administration Manual.

Replacement Message

You can replace variables with messages in the fields that are listed below.

If you use the environment variables from $MSG0 to $MSG5 and from $MSGL0 to $MSGL1 inside the fields below, the variables are replaced with messages when the sending is carried out. The messages may be assigned by the Send File command on the sending side or by the Send Request command on the receiving side.

• Send File Name

• Transfer Group ID

• Pre-send Job ID

• Successful Job ID

• Format ID

• Multi Format ID

• Mail Interface ID

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.

Setting up the EBCDIC Set when HULFT sends Chinese language data to a Type MF-IBMi host

Specify 'Simplified Chinese Extended' (I) for EBCDIC Set (CODESET).

Make sure that 'GB18030' (G) or 'UTF-8' (8) is specified for Code Set for Transfer (cs4trnsfr) in the System Environment Settings.

Behavior of the operation when "Autoconfiguration" is specified for EBCDIC Set

When you specify "Autoconfiguration" (0) for EBCDIC Set (CODESET), the setting value for the EBCDIC Set that is actually used in the single byte code conversion during file transfer is determined as follows.

For details on Code Set for Transfer (cs4trnsfr) with which the code set of the local host is registered in the System Environment Settings, refer to Administration Manual.

For details on Code Set for Transfer (KCODETYPE) with which the code set of the remote host is registered, refer to Host Information.