Receive Management Information

You can register information about the file to be received (called Receive file or receive target file). There are two ways to register the information.

• Registration using the HULFT Management Console

  => Refer to Using the Receive 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.3 List of Receive Management Information Fields

Field Value			Default Value	Setting Value	Optional	Remarks
Screen		File
File ID		RCVFILE		Uppercase alphanumeric characters and "_"	-	Within 50 bytes
Comment		COMMENT		Characters	✓	Within 60 bytes
Receive Management Information Update Screen
	File Name	FILENAME		Alphanumeric characters	-	Within 200 bytes
	Owner Name	OWNER		Alphanumeric characters	✓	Within 14 bytes (*1)
	Group Name	GROUP		Alphanumeric characters	✓	Within 14 bytes (*1)
	Permission	PERM	(*2)	0, 1	✓
	Registration Mode	TRANSMODE		N, R, M	-
	Error Handling	ABNORMAL		D, K, R	-
	Receive Mode	RCVTYPE		S, M	-
	Generational Management	GENCTL		Y, N	-
	No. of Generations	GENMNGNO		0, 2–9999	✓
	EBCDIC Set	CODESET	0	0, A to I, V to X	✓
	Successful Job ID	JOBID		Alphanumeric characters and "_"	✓	Within 50 bytes
	Unsuccessful Job ID	EJOBID		Alphanumeric characters and "_"	✓	Within 50 bytes
Receive Management Information Update Screen (Extension)
	Notification	JOBWAIT	T	J, T	✓
	Transfer Group ID	GRPID		Alphanumeric characters and "_"	✓	Within 50 bytes
	Verify Data	DATAVERIFY	0	0, 1	✓
	Cipher Key (when Forced Strong Key mode is disabled)(*3)	PASSWORD		Alphanumeric characters	✓	8–20 bytes
	Cipher Key (when Forced Strong Key mode is enabled)(*4)			Hexadecimal character string	-	64 digits

✓	:	Optional
-	:	Mandatory

*1	:	You cannot omit only Owner Name (OWNER) or only Group Name (GROUP).
*2	:	The default value is '1' for the permission to read and write the file, and '0' for the permission to execute the file.
*3	:	This type of cipher key can be set when Forced Strong Key Mode (strongkeymode) is set to "0 (Disabled)" in the System Environment Settings.
*4	:	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 Receive 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 (RCVFILE)

ID that identifies the Receive file

Comment (COMMENT)

Comment for the Receive file

Receive Management Information Update Screen

File Name (FILENAME)

Name of the Receive file

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

Owner Name (OWNER)

Owner of the Receive file

Set the owner name registered in the system.

Note

• When you operate HULFT as a general user, if you specify Owner Name, specify the user name of the user account that started the Receive daemon. If you specify another user name, creation of the Receive file may fail.

• You cannot omit only Owner Name or only Group Name.

• If you omit Owner Name, creation of the Receive file is carried out with the group name of the user account that started the Receive daemon.

Group Name (GROUP)

Group name of the Receive file

Set the group name registered in the system.

Note

• When you operate HULFT as a general user and specify Group Name, specify the group name of the group to which the user account that started the Receive daemon belongs. If you specify another group name, creation of the Receive file may fail.

• You cannot omit only Owner Name or only Group Name.

• If you omit Group Name, creation of the Receive file is carried out with the group name of the user account that started the Receive daemon.

Permission (PERM)

Permission mode to read, write, or execute the file

0:

Clear

1:

Set Permission

Omitting this field sets one of the following values:

Table 2.4 Default Values for Permission Mode of File

	Read	Write	Execute
Owner	1	1	0
Group	1	1	0
Others	1	1	0

Registration Mode (TRANSMODE)

Registration mode of the Receive file

N (New Creation):

Create new Receive files.

Using an existing file name displays an error.

R (Replace):

Replace the content of an existing file with received data.

A new file is created if the file does not exist.

M (Append):

Append the received data to the end of the existing file.

A new file is created if the file does not exist.

When 'M' (Append) is specified for Registration Mode (TRANSMODE) when 'S' (Single Receive) is set for Receive Mode (RCVTYPE), if a problem occurs during receiving, the receive data up to the point where the error occurred will be appended to the file.

Error Handling (ABNORMAL)

Handling of the Receive file at the time when the Receive processing fails

D (Delete):

Delete the receive file.

K (Keep):

Keep the receive file as it is when the receiving-side transferring fails.

R (Restore):

Back up the receive file before the receiving-side transferring starts and restore the backup file if the receiving-side transferring fails.

If the receive file does not exist before the receiving-side transferring starts, HULFT operates in the same way as when you specify "D" (Delete).

Receive Mode (RCVTYPE)

Specify how the Receive file or Receive files are received

S (Single Receive):

File is received from a single host.

M (Multiple Receive):

Files are received from multiple hosts and one file is created.

If you specify 'M' (Multiple Receive), you must specify 'M' (Append) for Registration Mode and 'K' (Keep) for Error Handling.

Generational Management (GENCTL)

Select whether to apply a generational management to the Receive file

N:

Generational management is disabled.

Y:

Generational management is enabled.

If you specify 'Y' (generational management is available), you must specify either 'N' (New Creation) or 'R' (Replace) for Registration Mode and 'D' (Delete) for Error Handling.

No. of Generations (GENMNGNO)

Number of generations used for managing the Receive file

Specify this field when you specify 'Y' (generational management is available) for Generational Management. Specify '0' when you specify 'N' (generational management is not available) for Generational Management.

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 sending-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 sending side uses the Type-EBCDIC Code Set and you specify receiving-side conversion.

= Remarks =

"D" (EBCDIC-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.

Successful Job ID (JOBID)

Job ID of the job that HULFT starts when the Receive processing of the file ends successfully

For details on job IDs, refer to Job Information.

If omitted, HULFT does not start the specified job.

Unsuccessful Job ID (EJOBID)

Job ID of the job that HULFT starts when the Receive processing of the file ends unsuccessfully

For details on job IDs, refer to Job Information.

If omitted, HULFT does not start the specified job.

Receive Management Information Update Screen (Extension)

Notification (JOBWAIT)

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

T (Receive Completion):

Notify after completion of the Receive processing.

J (Successful Job Completion):

Notify upon completion of the successful job (job to be executed in normal situation) after the Receive processing.

Omitting this field sets 'T' (Receive Completion).

Transfer Group ID (GRPID)

Transfer Group ID of the Receive file

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

Verify Data (DATAVERIFY)

Specify whether to verify data of the file to receive.

0:

Do not verify data

1:

Verify data

Omitting this field sets '0' (does not verify data).

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

Key that HULFT uses when decrypting the data

Specify this field to decrypt encrypted data.

Specify the same key as the Cipher Key that is specified in the Send Management Information of the remote host. If the cipher keys differ, data is not decrypted correctly.

The setting of the Cipher Key on the host on the receiving side is ignored when the field is not specified in the Send Management Information of the host on the sending side, even if this field is specified on the host on the receiving side.

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

Key that HULFT uses when decrypting the data

Specify this field to decrypt encrypted data.

Specify the same key as the Cipher Key that is specified in the Send Management Information of the remote host. If the cipher keys differ, data is not decrypted correctly.

Make sure that you specify Cipher Key. If the sending-side host is not in Forced Strong Key mode, a transfer error occurs.

Points to be noted when setting