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 Name			Default Value	Setting Value	Optional	Remarks
Screen		File
File ID		SNDFILE		Uppercase alphanumeric characters and "_"	-	Within 50 bytes
Comment		COMMENT		Characters	✓	Within 60 bytes
Basic Settings
	File Name	FILENAME		Characters	-	Within 200 bytes
	Transfer Type	TRANSTYPE	TEXT (T)	F, B, T, M	-	(*1)
	Format/Multi Format ID	FMTID		Uppercase alphanumeric characters and "_"	✓	Within 50 bytes
	Compression Preference	COMP	None (N)	N, 1, 2, 3, 4	-	(*1)
	Compression Unit	COMPSIZE	0	0, 1–32760	✓	Unit: bytes
	Compression Mode	COMPMODE		S, D, C	✓	(*2)
	Code Conversion	KJCHNGE	Sending Side (S)	S, R, N	-	(*1)
	EBCDIC Set	CODESET	Autoconfiguration (0)	0, A to I, V to X	✓	(*2)
	Send File Mode	CLEAR	Keep (K)	K, C, D, L	✓	(*2)
	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
Extension Settings
	Interface DBID	DBID		CSV	✓	Only the string 'CSV' (*3)
	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	Add (Y)	Y, N	✓	(*2)
	Mail Interface ID	MAILID		Uppercase alphanumeric characters	✓	Within 50 bytes
	Cipher Key(*4)	PASSWORD		Alphanumeric characters	✓	8–20 bytes
	Cipher Key(*5)			Hexadecimal character string	-	64 digits

✓	:	Optional
-	:	Mandatory

*1	:	For the HULFT Management Console, click a setting value on the pulldown list.
*2	:	For the HULFT Management Console, click a setting value on the pulldown list. When you do not specify this field, the default value will be set.
*3	:	Available only when Transfer Type (TRANSTYPE) is set to 'FORMAT' (F) or 'MULTIFORMAT' (M).
*4	:	This type of cipher key can be set when Forced Strong Key Mode (strongkeymode) is set to "Disabled (0)" in the System Environment Settings.
*5	:	This type of cipher key must be set when Forced Strong Key Mode (strongkeymode) is set to "Enabled (1)" 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

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 HULFT10 Server grade environments, you can specify a file that uses network resources. For details, refer to the following:

HULFT10 for Windows Administration Manual : Networked files

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

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

Compression Mode (COMPMODE)

Compression mode for DEFLATE compression or Zstandard compression

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

= Remarks =

"ASPEN" (D) and "NEC Katakana" (G) are not recommended. If you specify ASPEN (D) and NEC Katakana (G), 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.

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 with the Type-EBCDIC Code Set

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.

Points to be noted when setting