List of Receive Management Information fields

You can register file information about the file to be received (called Receive file or receive target file). For the registration method, refer to Using the Receive Management Information.

Field List

Table 4.71 List of Receive Management Information Fields
Field Name		Default Value	Setting Value	Optional	Remarks
File ID			Alphanumeric characters and "_"	-	Within 50 bytes starting with an alphabetic character
Comment			Characters	✓	Within 60 bytes (*1)
Basic Settings
	File Name		Alphanumeric characters	-	3–33 bytes
	Record Length	128	1–32766	-
	Registration Mode	New Creation	(*2)	-
	Error Handling	Delete	(*2)	-
	Receive Mode	Single Receive	(*2)	-
	Generational Management	No	(*2)	-
	No. of Generations	0	0, 2–9999	-
	EBCDIC Set	Autoconfiguration	(*2)	-
	Successful Job ID		Alphanumeric characters and "_"	✓	Within 50 bytes starting with an alphabetic character
	Unsuccessful Job ID		Alphanumeric characters and "_"	✓	Within 50 bytes starting with an alphabetic character
Extension Settings
	Notification	Receive Completion	(*2)	-
	Transfer Group ID		Alphanumeric characters and "_"	✓	Within 50 bytes starting with an alphabetic character
	Verify Data	No	(*2)	-
	Cipher Key (when Forced Strong Key mode is disabled) (*3)		Alphanumeric characters	✓	8–20 bytes
	Cipher Key (when Forced Strong Key mode is enabled) (*4)		Hexadecimal character string	-	64 digits

✓	:	Optional
-	:	Mandatory

*1	:	On the HULFT Manager Management Console, you can enter a string of up to 60 characters. When the destination host is HULFT Ver.8.1 or higher, the size of the string that you entered will be checked based on the code set that is set in HULFT at the connection destination. When HULFT checks and confirms that the size of the string meets the condition that is given in the remarks, the characters that you entered will be saved in HULFT.
*2	:	For the HULFT Manager Management Console, click a setting value on the pulldown list.
*3	:	This type of cipher key can be set in either of the following cases: HULFT of a version lower than Ver.8.4.0 is installed on the remote host HULFT Ver.8.4.0 or higher is installed and Forced Strong Key Mode (STRONGKEYMODE) is set to "0 (Disabled)" on the remote host
*4	:	This type of cipher key must be set in either of the following cases: HULFT Ver.8.4.0 or higher is installed and Forced Strong Key Mode (STRONGKEYMODE) is set to "1 (Enabled)" on the remote host

Explanation of each field

This section explains the fields to be specified in the Receive Management Information.

File ID

ID that identifies the Receive file

You cannot specify "_INSTANT_TRANSFER_" for the file ID, because this is the ID for instant transfer.

Comment

Comment for the Receive file

Basic Settings

File Name

File to be received that is stored on IBM i operating system

For a physical data file, specify the name in the format of 'library name/file name(member name).'

For an archive file, specify the name in the format of 'library name/file name.'

You cannot use reserved words such as '*FIRST' or '*FILE' and so forth for the name of Receive file. Specification of the file name with the reserved words may result in unexpected behavior of HULFT.

Record Length

Receive file record length

When the Receive file does not exist, specify the length of the record in the newly created Receive file. When the Receive file already exists, specify the record length of the existing file.

Registration Mode

Registration mode for the Receive file

New Creation:: New creation mode
Replace:: Replace mode
Append:: Append mode

Error Handling

Handling of the Receive file when the Receive processing fails

Delete:

Delete the Receive file.

Keep:

Keep the Receive file as it is when the Receive processing fails.

Restore:

Back up the Receive file before the Receive processing starts and restore the Receive file from the backup if the Receive processing fails.

If the Receive file does not exist before the Receive processing starts, HULFT operates in the same way as when you specify 'Delete.'

Receive Mode

Specify how the Receive file or Receive files are received

Single Receive:: File is received from a single host.
Multiple Receive:: File is received from multiple hosts and one file is created.

When 'Multiple Receive' is specified, specify 'Append' in Registration Mode and 'Keep' in Error Handling.

Generational Management

Select whether to apply a generational management to the Receive file

Yes:: Generational management is enabled.
No:: Generational management is disabled.

When you specify 'Yes,' you must specify 'New Creation' or 'Replace' for Registration Mode and 'Delete' for Error Handling.

No. of Generations

Number of generations used for managing the Receive file

When you specify 'Yes' for Generational Management, specify a number from '2' to '9999.' If you specify 'No' for Generational Management, you must specify '0.'

EBCDIC Set

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

When Type-EBCDIC Code Set is set for Code Set for Transfer on the destination host, specify the EBCDIC set of the destination host (receiving-side host).

When UTF-8 is set for Code Set for Transfer on the destination host, specify the EBCDIC set of the sending-side host.

Autoconfiguration
Katakana
Lower Case
ASCII
ASPEN
Japan (Latin) for IBM
Japan (Latin) Extended for IBM
NEC Katakana
Japan (Katakana) Extended for IBM
Simplified Chinese Extended
User Table 1
User Table 2
User Table 3

Omitting this field sets 'Autoconfiguration.'

Successful Job ID

ID of the Job Information record in which the job to be started when the Receive processing of the file ends successfully is registered

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

When this field is omitted, the job is not started.

Unsuccessful Job ID

ID of the Job Information record in which the job to be started when the Receive processing of the file ends unsuccessfully is registered

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

When this field is omitted, the job is not started.

Extension Settings

Notification

Receive completion notification to be sent to the host on the sending side

Receive Completion:: Notify after completion of the Receive processing
Successful Job Completion:: Notify upon completion of the successful job (job to be executed in normal situation) after the Receive processing

Transfer Group ID

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

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

Verify Data

Specify whether to verify data of the file to receive

No:: Do not verify data
Yes:: Verify data

Cipher Key (when Forced Strong Key mode is disabled)

Key that HULFT uses when decrypting the data

Specify this field to decrypt encrypted data. Set the same cipher key as the one set in the Send Management Information of the remote host.

If no cipher key is set in the Send Management Information on the sending-side host, the cipher key is not used even when it is set on the receiving-side host.

If the cipher keys are not identical, data is not decrypted correctly.

Cipher Key (when Forced Strong Key mode is enabled)

Key that HULFT uses when decrypting the data

Specify this field to decrypt encrypted data.

If the cipher keys are not identical, data is not decrypted correctly.

Points to be noted when configuring settings

Specification of Registration Mode, Receive Mode, and Generational Management

When Receive Mode is set to 'Single Receive' and Registration Mode is set to 'Append' and an error occurs during receiving, Receive data obtained before the occurrence of the error will be overwritten. When Error Handling is set to 'Restore,' the Receive file before the start of the Receive process is saved as a separate member in the restored Receive file.

Table 4.72 Combinations of Settings in Receive Management Information
Registration Mode	Error Handling	Receive Mode
		Single Receive		Multiple Receive
		Generational Management	Generational Management	Generational Management	Generational Management
		Enabled	Disabled	Enabled	Disabled
New Creation	Delete	✓	✓
	Keep		✓
	Restore		✓
Replace	Delete	✓	✓
	Keep		✓
	Restore		✓
Append	Delete		✓
	Keep		✓		✓
	Restore		✓

✓	:	Combination that can be specified
Blank	:	Combination that cannot be specified

Archive File

For archive files, you cannot execute the Checkpoint Resend File or the Checkpoint Resend Request. Therefore, if you execute the Checkpoint Resend File or the Checkpoint Resend Request, HULFT resends the file from the top. If you specify 'New Creation' for Registration Mode in the Receive Management Information and then execute either the Checkpoint Resend File or the Checkpoint Resend Request, an error occurs.

Error Handling

Points to be noted when specifying 'Delete'

Delete is not executed if the Receive file already exists and an error occurs when 'New Creation' is specified as the Registration Mode.
Points to be noted when specifying 'Keep'

When 'Multiple Receive' is specified for Receive Mode, if an error occurs during receiving in a temporary file, the data received prior to the occurrence of the error is not written to the Receive file. However, if there is an error while copying the temp file into the Receive file, the received data up to that point is added. Therefore, there should be a function embedded in your application program to check for duplicate data.

Replacement Message

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

Specify '&MSG0' to '&MSG5' or '&MSGL0' to '&MSGL1' in the following fields to replace the strings with messages that you specify when you issue the Send Request, or with messages sent from the host on the sending side:
- Receive File Name
- Transfer Group ID
- Successful Job ID
The message is converted with the type of the code set that is specified for HULFT Character Set (HULCHARSET) in the System Environment Settings.
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 sending side.

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

Receive File Name

When specifying any of the following strings, specify 'Single Receive' for Receive Mode:
- '&SNDFILE' (physical data file)
- '&SNDFILES' (archive file)
- '&MSG0' to '&MSG5'
- '&MSGL0' to '&MSGL1'
If the name of the Send file includes double-byte codes, HULFT returns an error.
You cannot specify any character after '&SNDFILE' or '&SNDFILES.'
If you specify '&SNDFILE' or '&SNDFILES,' the Send file name is set to the Receive file name. Also, when the sending host is HULFT for IBMi, specify '&SNDLIB' to use the sending host library name as the Receive file library name.
When you replace the Receive file name, the transfer may fail because the Receive file name may not be replaced correctly with the Send file name depending on the language settings on the host on the sending side. For details, refer to IBMi Administration Manual.

When the Send file name is set to the Receive file name, follow the naming conventions as shown below:

Table 4.73 File Naming Conventions
Host Type		Receive File Name (IBMi)
Send File Name		&SNDLIB&SNDFILE	MYLIB/&SNDFILE	&SNDLIB&SNDFILES	MYLIB/&SNDFILES
Mainframe
	Sequential Organization file HULFT.DAT.SND.F01	Conversion error	MYLIB/F01(SND)	Conversion error	MYLIB/SND
	Partitioned data sets (PDS) HULFT.DAT.F02(SND)	Conversion error	MYLIB/F02(SND)	Conversion error	MYLIB/SND
UNIX or Linux
	With extension /HULFT/DAT/SND.F03	Conversion error	MYLIB/F03(SND)	Conversion error	MYLIB/SND
	Without extension /HULFT/DAT/SND	Conversion error	MYLIB/SND(SND)	Conversion error	MYLIB/SND
Windows
	With extension C:\HULFT\DAT\SND.F04	Conversion error	MYLIB/F04(SND)	Conversion error	MYLIB/SND
	Without extension C:\HULFT\DAT\SND	Conversion error	MYLIB/SND(SND)	Conversion error	MYLIB/SND
IBMi
	Physical file HULFT/F05(SND)	HULFT/F05(SND)	MYLIB/F05(SND)	Conversion error	Conversion error
	Archive file HULFT/F06	Conversion error	Conversion error	HULFT/F06	MYLIB/F06

Note

When using '&SNDLIB,' also specify '&SNDFILE' or '&SNDFILES' at the same time.

You cannot specify only '&SNDLIB.'

Record Length

When the record length specified in the management information is not the same as that of the Receive file, the handling based on Receive Mode. When 'Single Receive' is specified for Receive Mode, the record length specified in the management information is ignored during the Receive processing. When 'Multiple Receive' is specified for Receive Mode, it is considered as a receive error.

Notification

When 'Receive Completion' is specified for Notification, a job description that is registered in the Job Information is executed as a job that is different from the Receive job. Therefore, the job that is different from the Receive job executes the CL command.

When 'Successful Job Completion' is specified for Notification, the Receive job executes the CL command.

When HULFT receives Chinese language data from a Type MF-IBMi host

Specify 'Simplified Chinese Extended' for EBCDIC Set.

Check that 'C' (IBM Simplified Chinese) 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" for EBCDIC Set, 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 4.74 Values for EBCDIC Set that are determined automatically
Code Set for Transfer (KCODETYPE) for Host on Receiving Side	Code Set for Transfer (KCODETYPE) for Host on Sending Side
	SHIFT-JIS	EUC-JP	GB18030	IBM Kanji	JEF	IBM Simplified Chinese
IBM Kanji	F	F		F	F
IBM Simplified Chinese			I			I

Blank	:	For these combinations, code conversion cannot be executed during file transfer.
F	:	Japan (Latin) Extended for IBM
I	:	Simplified Chinese Extended

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

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

Comment

Even if double-byte characters that are registered in Comment can be displayed on the HULFT Manager Management Console, the characters may not be displayed correctly on the HULFT Management Console for HULFT10 for IBMi.