Send Management Information

You can register the information about the files to send. 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 the registration by running commands with parameter files, refer to Management Information Batch Registration command.

Table 2.1 List of Send Management Information Fields

Field Value

Default Value

Setting Value

Optional

Remarks

Screen

File

File ID

SNDFILE

 

Uppercase alphanumeric characters

-

Within 50 bytes

Comment

COMMENT

 

Characters

Within 60 bytes

Send Management Information Update Screen

 

Send File Name

FILENAME

 

Alphanumeric characters

-

Within 200 bytes

Transfer Type

TRANSTYPE

 

F, B, T, M

-

 

Format/Multi Format ID

FMTID

 

Alphanumeric characters

Within 50 bytes

Compression Preference

COMP

N

N, 1, 2, 3

-

 

Compression Unit

COMPSIZE

0

0, 1–32760

Unit: bytes

DEFLATE Level

DEFLATELEVEL

 

S, D, C

 

Code Conversion

KJCHNGE

 

S, R, N

-

 

EBCDIC Set

CODESET

0

0, A to I, V to X

 

Send File Mode

CLEAR

K

K, C, D, L

 

Transfer Group ID

GRPID

 

Alphanumeric characters

Within 50 bytes

Pre-send Job ID

PREJOBID

 

Alphanumeric characters

Within 50 bytes

Successful Job ID

JOBID

 

Alphanumeric characters

Within 50 bytes

Unsuccessful Job ID

EJOBID

 

Alphanumeric characters

Within 50 bytes

Send Management Information Update Screen (Extension)

 

Interface DBID

DBID

 

CSV

Only the string 'CSV' (*1)

Transfer Interval

INTERVAL

0

0–32760

Unit: milliseconds

Transfer Priority

TRANSPRTY

50

1–256

-

 

Transfer Block Length

BLOCKLEN

0

0, 128–65520

-

Unit: bytes

Transfer Block Count

BLOCKCNT

0

0–99

-

 

Shiftcode Mode

SHIFTTRANSACT

Y

Y, N

 

Cipher Key
(when Forced Strong Key mode is disabled) (*2)

PASSWORD

 

Alphanumeric characters

8–20 bytes

Cipher Key
(when Forced Strong Key mode is enabled) (*3)

Hexadecimal character string

-

64 digits

:

Optional

-

:

Mandatory

*1

:

You can set this field when you select 'F' (FORMAT) or 'M' (MULTI-FMT) for Transfer Type (TRANSTYPE).

*2

:

This type of cipher key can be set when Forced Strong Key Mode (strongkeymode) is set to "0 (Disabled)" in the System Environment Settings.

*3

:

This type of cipher key must be set when Forced Strong Key Mode (strongkeymode) is set to "1 (Enabled)" in the System Environment Settings.

(2) Explanation of each field

This section explains the fields to be specified in the Send Management 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.

File ID (SNDFILE)

ID that identifies the Send file

Comment (COMMENT)

Comment related to the file to send

Send Management Information Update Screen

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 Administration Manual.

Transfer Type (TRANSTYPE)

Data type of the file to send

F (FORMAT):

Format data

B (BINARY):

Binary data

T (TEXT):

Text data

M (MULTI FORMAT):

Multi format data

Format/Multi Format ID (FMTID)

ID of the record in which the format or multi format of the Send file are 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 'F' (FORMAT), the format ID is mandatory, and when Transfer Type is specified as 'M' (MULTI-FMT), the multi format ID is mandatory.

Compression Preference (COMP)

Compression type that is used when a file is transferred

N (NO):

None

1:

Horizontal (compression within records)

2:

Vertical (compression across records)

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 'B' (BINARY) and Compression Preference (COMP) is '1' (Horizontal (compression within records))

  • When Transfer Type is 'B' (BINARY) and Compression Preference is '2' (Vertical (compression across records))

DEFLATE Level (DEFLATELEVEL)

Compression level for DEFLATE compression

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

S:

Speed

D:

Standard

C:

Compression Ratio

Omitting this field sets 'D' (Standard).

Code Conversion (KJCHNGE)

Specify the option for code conversion of the send target file

S:

Sending-side

R:

Receiving-side

N:

No Conversion

EBCDIC Set (CODESET)

Specify the Type-EBCDIC code set that is used to convert single-byte codes.

Choose the same EBCDIC set as that used on the receiving-side host (remote host).

0:

Autoconfiguration

A:

EBCDIC Katakana

B:

EBCDIC Lowercase

C:

EBCDIC ASCII

D:

EBCDIC ASPEN

E:

Japan (Latin) for IBM

F:

Japan (Latin) Extended for IBM

G:

NEC Katakana

H:

Japan (Katakana) Extended for IBM

I:

Simplified Chinese Extended

V:

User Table 1

W:

User Table 2

X:

User Table 3

Omitting this field sets '0' (Autoconfiguration).

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.

K (KEEP):

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

C (CLEAR):

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.

D (DELETE):

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

L (LOCK):

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

Omitting this field sets 'K' (KEEP).

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.

Send Management Information Update Screen (Extension)

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 'F' (FORMAT) or 'M' (MULTI FORMAT) 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 data used to transfer one block

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

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.

Shiftcode Mode (SHIFTTRANSACT)

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

Y:

Add shift codes

N:

Do not add shift codes

Omitting this field sets 'Y' (Add shift codes).

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.

(3) Points to be noted when setting

File ID

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

Compression Preference

Even if '3' (DEFLATE) 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 'Y' (Yes) 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 '3' (DEFLATE) is specified for Compression Preference.

DEFLATE Level

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

  • N (None)

  • 1 (Horizontal)

  • 2 (Vertical)

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 "R" (Convert on the receiving-side host).

  • 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 "S" (Convert on the sending-side host) for Code Conversion (KJCHNGE), or switch to the sending-side even if you specify "R" (Convert on the receiving-side host) 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 'K' (KEEP) is selected for Send File Mode (FILENAME), 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' only for Transfer Block Length or only for Transfer Block Count, an error occurs.

For details, refer to Administration Manual.

Replacement Message

Listed below are the fields that you can replace variables in messages.

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 remote host.

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

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

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

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

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

When you specify "0" (Autoconfiguration) 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.

Table 2.2 Setting value that is automatically determined for the EBCDIC Set

Code Set for Transfer of Local Host

Code Set for Transfer of Remote Host

UTF-8

SHIFT-JIS

EUC-JP

GB18030

IBM
Kanji

JEF

KEIS

NEC
Kanji

IBM Simplified
Chinese

SHIFT-JIS

-

-

-

F

A

D

G

EUC-JP

-

-

-

F

A

D

G

UTF-8

-

-

-

-

F

A

D

G

I

GB18030

-

-

I

-

:

The setting value of the EBCDIC Set is not used in code conversion during file transfer.

Blank

:

For these combinations, code conversion cannot be executed during file transfer.

A

:

EBCDIC Katakana

D

:

EBCDIC-ASPEN

F

:

Japan (Latin) Extended for IBM

G

:

NEC Katakana

I

:

Simplified Chinese Extended

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

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