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.36 List of Receive Management Information Fields

Field name			Default Value	Setting Value	Optional	Remarks
Screen		File
File ID		RCVFILE		Uppercase alphanumeric characters and "_"	-	Within 50 bytes
Comment		COMMENT		Characters	✓	Within 60 bytes (*1)
Basic Settings
	Receive File Name	FILENAME		Characters	-	Within 200 bytes
	Owner Name	OWNER		Alphanumeric characters	✓	Within 14 bytes (*2)
	Group Name	GROUP		Alphanumeric characters	✓	Within 14 bytes (*2)
	Permission	PERM	Marked	(*3)	✓
	Registration Mode	TRANSMODE	New Creation (N)	(*4)	-
	Error Handling	ABNORMAL	Delete (D)	(*4)	-
	Receive Mode	RCVTYPE	Single Receive (S)	(*4)	-
	Generational Management	GENCTL	No (N)	(*4)	-
	No. of Generations	GENMNGNO		0, 2–9999	✓
	EBCDIC Set	CODESET	Autoconfiguration	(*4)	✓	(*5)
	EBCDIC Code Set	CODESET	(*6)	(*4)	✓	(*7)
	Successful Job ID	JOBID		Alphanumeric characters and "_"	✓	Within 50 bytes
	Unsuccessful Job ID	EJOBID		Alphanumeric characters and "_"	✓	Within 50 bytes
Extension Settings
	Notification	JOBWAIT	Receive Completion (T)	(*4)	✓
	Transfer Group ID	GRPID		Alphanumeric characters and "_"	✓	Within 50 bytes
	Verify Data	DATAVERIFY	No (0)	(*4)	✓
	Cipher Key (when Forced Strong Key mode is disabled) (*8)	PASSWORD		Alphanumeric characters	✓	8–20 bytes
	Cipher Key (when Forced Strong Key mode is enabled) (*9)			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	:	You cannot omit only Owner Name (OWNER) or only Group Name (GROUP).
*3	:	For the HULFT Manager Management Console, select the check box.
*4	:	For the HULFT Manager Management Console, click a setting value on the pulldown list.
*5	:	This field is displayed when HULFT Manager connects to HULFT Ver.8.1 or higher.
*6	:	The default value varies depending on the setting of HULFT Operation Language (hullang) in the System Environment Settings on the destination host. When HULFT Operation Language is set to 'JPN' (Japanese) 'Kana' (A) is set. When HULFT Operation Language is set to 'ENG' (English) 'Standard' (E) is set.
*7	:	This field is displayed when HULFT Manager connects to HULFT lower than Ver.8.1.
*8	:	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
*9	:	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. 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

= Remarks =

For HULFT for NSK, you can specify a Pre-receive Job and the extent.

• To specify a Pre-receive Job that you want to start, put '@' at the first byte, followed by a character string as the Job ID of the Pre-receive Job. Specify the Job ID within 50 bytes. For details on job IDs, refer to List of Job Information fields. For details on Pre-receive Jobs, refer to NSK Administration Manual.

• You can specify the capacity of the Guardian file by putting the second '@' followed by a 13-byte character string as the capacity. For details on how to specify the capacity of the Guardian file, refer to NSK Administration Manual.

• If you specify a Pre-receive Job or the extent, the third '@' indicates the beginning of a comment. If you do not specify either a Pre-receive Job or the capacity of the Guardian file, put the first or the second '@' without specifying a character string for it and then put the subsequent '@' immediately after the preceding '@.'

Basic Settings

Receive 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 on networked files, refer to Linux/AIX Administration Manual.

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 (OWNER), 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.

Unmarked (0):

Not Permitted

Marked (1):

Permitted

Omitting this field sets the following:

Table 4.37 Default Values of Access Permissions by User Type

	Read	Write	Execute
Owner	Permitted	Permitted	Not Permitted
Group Name	Permitted	Permitted	Not Permitted
Other	Permitted	Permitted	Not Permitted

Registration Mode (TRANSMODE)

Registration mode for the Receive file

New Creation (N):

Create new Receive files.

When you use an existing file name, an error occurs.

Replace (R):

Replace the content of an existing file with received data.

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

Append (M):

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

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

When Receive Mode is set to 'Single Receive (S)' and Registration Mode is set to 'Append (M)' and an error occurs during receiving, Receive data obtained before the occurrence of the error will be appended.

Error Handling (ABNORMAL)

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

Specify how the Receive file or Receive files are received

Single Receive (S):

File is received from a single host.

Multiple Receive (M):

File is received from multiple hosts and one file is created.

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

Generational Management (GENCTL)

Select whether to apply a generational management to the Receive file

No (N):

Generational management is disabled.

Yes (Y):

Generational management is enabled.

When you specify 'Yes (Y),' specify the following settings:

• 'New Creation (N)' or 'Replace (R)' for Registration Mode

• 'Delete (D)' for Error Handling

No. of Generations (GENMNGNO)

Number of generations used for managing the Receive file

The setting value is valid only when Generational Management (GENCTL) is set to 'Yes (Y).'

EBCDIC Set (CODESET)

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

Specify the EBCDIC Set for the sending-side host.

This field is displayed when HULFT Manager connects to HULFT Ver.8.1 or higher.

• 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 sending side is a Type MF-IBMi host and when you specify receiving-side conversion.

EBCDIC Code Set (CODESET)

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

Specify the EBCDIC Set for the sending-side host.

This field is displayed when HULFT Manager connects to HULFT lower than Ver.8.1.

• Kana (A)

• Lower Case (B)

• ASCII (C)

• ASPEN (D)

• Standard (E)

• Standard Extension (F)

• NEC Kana (G)

• Kana Extension (H)

• User Table 1 (V)

• User Table 2 (W)

• User Table 3 (X)

This setting is valid when the host on the sending side uses the Type-EBCDIC Code Set and you specify receiving-side conversion.

If you omit this setting, the default value varies depending on the setting of HULFT Operation Language (hullang) in the System Environment Settings on the destination host.

• When HULFT Operation Language is set to 'JPN' (Japanese)

  'Kana' (A) is set.

• When HULFT Operation Language is set to 'ENG' (English)

  'Standard' (E) is set.

For details on HULFT Operation Language, refer to Linux/AIX Administration Manual.

Successful Job ID (JOBID)

ID of the job to be started when the Receive processing of the file ends successfully

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

If omitted, HULFT does not start the specified job.

Unsuccessful Job ID (EJOBID)

ID of the job to be started when the Receive processing of the file ends unsuccessfully

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

If omitted, HULFT does not start the specified job.

Extension Settings

Notification (JOBWAIT)

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

Receive Completion (T):

Notify after completion of the Receive processing

Successful Job Completion (J):

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

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

Transfer Group ID (GRPID)

Transfer group ID of the Receive file

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

Verify Data (DATAVERIFY)

Specify whether to verify the data of the file to be received.

No (0):

Do not verify data

Yes (1):

Verify data

Omitting this field sets 'No (0).'

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.

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

Specify the same cipher key as is specified in the Send Management Information on the remote host.

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

Points to be noted when configuring settings