List of Send Management Information fields

Basic Settings

Send File Name (FILENAME)

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

Specify the file name with a full path.

In HULFT8 Enterprise grade environments, you can specify a file that uses network resources. For details, refer to the explanation of networked files in UNIX/Linux 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 where the format or multi format of the Send file is registered

For details on format IDs, refer to List of Format Information fields.

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

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

Compression Preference (COMP)

Compression type that is used when a file is transferred

None (N):

None

Horizontal (1):

Compression within records

Vertical (2):

Compression across records

DEFLATE (3):

DEFLATE

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 (COMP) 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 (COMP).

• Compression Speed (S)

• Standard (D)

• Compression Ratio (C)

Omitting this field sets 'Default (D).'

Code Conversion (KJCHNGE)

Specify the option for code conversion of the send target file

Sending Side (S)

Sending side

Receiving Side (R):

Receiving side

No Conversion (N):

No 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.

This field is displayed when HULFT Manager connects to HULFT Ver.8.1 or higher.

• 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 when you specify sending-side conversion.

EBCDIC Code 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.

This field is displayed when HULFT Manager connects to HULFT lower than Ver.8.1.

• Kana (A)

• Lower Case (B)

• ASCII (C)

• ASPEN (D)

• Standard (E)

• Standard Extension (F)

• NEC Kana (G)

• Kana Extension (H)

• User Table 1 (V)

• User Table 2 (W)

• User Table 3 (X)

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

If you omit this setting, the default value varies depending on the setting of HULFT Operation Language (hullang) in the System Environment Settings on the destination host.

• When HULFT Operation Language is set to 'JPN' (Japanese)

  'Kana' (A) is set.

• When HULFT Operation Language is set to 'ENG' (English)

  'Standard' (E) is set.

For details on HULFT Operation Language, refer to UNIX/Linux Administration Manual.

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 and save the file after sending ends successfully

Clear (C):

Lock the file while sending is in progress and clear the file to 0 byte after the sending ends successfully

Delete (D):

Lock the file while sending is in progress and delete the file after the sending ends successfully

Lock (L):

Lock the file while sending is in progress and save 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 destinations of the Send file are registered

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

Pre-send Job ID (PREJOBID)

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

For details on job IDs, refer to List of Job Information fields.

If omitted, HULFT does not start the specified job.

Successful Job ID (JOBID)

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

For details on job IDs, refer to List of Job Information fields.

If omitted, HULFT does not start the specified job.

Unsuccessful Job ID (EJOBID)

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

For details on job IDs, refer to List of Job Information fields.

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, files will not be received in CSV format.

To establish interface, specify 'FORMAT (F)' or 'MULTIFORMAT (M)' for Transfer Type (TRANSTYPE).

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 when starting the file transfer

A smaller number means a higher priority.

Transfer Block Length (BLOCKLEN)

Length of data used to transfer one block

The product of the values for Transfer Block Length and Transfer Block Count cannot exceed 65520.

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).

For details, refer to UNIX/Linux Administration Manual.

Transfer Block Count (BLOCKCNT)

Number of blocks per transfer

The product of the values for Transfer Block Length and Transfer Block Count cannot exceed 65520.

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).

For details, refer to UNIX/Linux Administration Manual.

Shiftcode Mode (SHIFTTRANSACT)

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

Marked (Y):

Add shift codes

Unmarked (N):

Do not add shift codes

Omitting this field sets 'Marked (Y).'

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

Key used when data is encrypted in an encryption algorithm

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

If this field is omitted, the file is not encrypted.

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

Key used when data is encrypted in an encryption algorithm

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

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 HULFT on the receiving host is lower than Ver.8

• When 'Enabled (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 on 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, code conversion may switch to the receiving-side even if you specify "Sending Side" (S) for Code Conversion (KJCHNGE), or code conversion may switch to the sending-side even if you specify "Receiving Side" (R) for Code Conversion (KJCHNGE). For details, refer to the explanation about the sending-side conversion and the receiving-side conversion in Code Conversion Manual.

Send File Mode

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

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' for only one of either Transfer Block Length or Transfer Block Count, an error occurs.

For details, refer to UNIX/Linux 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

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 receiving side.

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

When HULFT sends Chinese language data to a Type MF-IBMi host

When HULFT Manager connects to HULFT Ver.8.1 or higher to send 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 HULFT Manager connects to HULFT Ver.8.1 or higher, you can specify 'Autoconfiguration (0)' 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) in which the code set of the destination host is registered in the System Environment Settings, refer to UNIX/Linux Administration Manual.

For details on Code Set for Transfer (KCODETYPE) in which the code set of the host on the receiving side is registered, refer to List of Host Information fields.