Send Management Information

You can register the information about the files to send. There are two ways to register the information.

• Registration using the HULFT Management Console

  => Refer to Using the Send Management Information

• Registration by running commands with parameter files

  => Refer to Management Information Batch Registration command

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 and "_"	-	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 and "_"	✓	Within 50 bytes
	Compression Preference	COMP	N	N, 1, 2, 3, 4	-
	Compression Unit	COMPSIZE	0	0, 1–32760	✓	Unit: bytes
	Compression Mode	COMPMODE		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 and "_"	✓	Within 50 bytes
	Pre-send Job ID	PREJOBID		Alphanumeric characters and "_"	✓	Within 50 bytes
	Successful Job ID	JOBID		Alphanumeric characters and "_"	✓	Within 50 bytes
	Unsuccessful Job ID	EJOBID		Alphanumeric characters and "_"	✓	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.

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 Linux operating system.

Specify the file name with a full path.

In HULFT10 Enterprise grade environments, you can specify a file that uses network resources. For details, refer to the following:

HULFT10 for Linux/AIX Administration Manual : Networked files

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

4:

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

Compression Mode (COMPMODE)

Compression mode for DEFLATE compression or Zstandard compression

This field can be set only if "3" (DEFLATE) or "4" (Zstandard) 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 uses the Type-EBCDIC Code Set and you specify sending-side conversion.

= Remarks =

"D" (ASPEN) and "G" (NEC Katakana) are not recommended.

If you specify "D" (ASPEN) and "G" (NEC Katakana), the files may not be converted.

Use a different code set.

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)

How to handle shift codes when carrying out code conversions with Type-EBCDIC Code Set

Y:

Add shift codes

N:

Do not add shift codes

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

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

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 (when Forced Strong Key mode is enabled) (PASSWORD)

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.

Points to be noted when setting