Receive Management Information

Receive Management Information Update Screen

Receive File Name (FILENAME)

Name of the Receive file

Specify the file name with a full path.

In HULFT8 Enterprise grade environments, you can specify a file that uses network resources. For details, refer to the explanation of networked files in 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, 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 is a Type MF-IBMi host and when you specify receiving-side conversion.

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

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

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.

File ID

You cannot specify "_INSTANT_TRANSFER_" for File ID (RCVFILE).

Specification of Registration Mode, Receive Mode, and Generational Management

The combinations that can be specified in the Receive Management Information are as follows:

Receive Mode

• Point to be noted when specifying 'M' (Multiple)

  You must be careful when carrying out the operation, because during the Receive processing, the data is stored in a temporary file and is copied to the Receive file after the Receive processing is complete.

Error Handling

• Point to be noted when specifying 'D' (Delete)

  When 'N' (New Creation) is selected for Registration Mode, if an error occurs because the Receive file already exists, the existing file is not deleted.

• Points to be noted when specifying 'K' (Keep)

  When 'M' (Multiple) is selected for Receive Mode, if an error occurs during receiving of data in a temp file, the data received up to the point when the error occurred 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 duplicate data.

Notification

When 'J' (Successful Job Completion) is specified for Notification (JOBWAIT), a time-out may occur on the remote host, because the remote host does not receive the completion notification from the remote host until the Post-receive Job ends. Be sure to take this into account when you set the time-out period.

Replacement Message

If you use the environment variables from $MSG0 to $MSG5 and from $MSGL0 to $MSGL1 inside the fields below, the variables are replaced with messages when the receiving is carried out. The messages may be assigned by the Send Request command on the receiving side or by the Send File command on the sending side.

• Receive File Name

• Transfer Group ID

• Successful Job ID

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 remote host.

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

Receive File Name

• When specifying any of the following, specify 'S' (Single) as Receive Mode:

  • $SNDFILE

  • '$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.

• If you specify '$SNDFILE,' the name of the Send file on the host on the sending side is set as the Receive file name.

• When the host on the sending side is HULFT for UNIX/Linux, if you specify '$SNDPATH,' the path of the host on the sending side is set for the path of the Receive file.

• When the host on the sending side is not HULFT for UNIX/Linux, replacement of '$SNDPATH' will not be carried out.

• 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 on the host on the sending side depending on the language settings on the remote host.

  For details, refer to Administration Manual.

• When using $SNDPATH, specify $SNDFILE at the same time. You cannot specify only $SNDPATH.

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

  Table 2.6 File Naming Conventions

  Host Type		Receive File Name (UNIX or Linux)
  Send File Name		$SNDPATH$SNDFILE	$SNDFILE	/usr/$SNDFILE
  Mainframe
  	Sequential Organization file HULFT.DAT.SND.F01	HULFT.DAT.SND.F01	HULFT.DAT.SND.F01	/usr/HULFT.DAT.SND.F01
  	Partitioned Organization file HULFT.DAT.F02(SND)	HULFT.DAT.SND.F02	HULFT.DAT.SND.F02	/usr/HULFT.DAT.SND.F02
  UNIX or Linux
  	/hulft/dat/snd.f03	/hulft/dat/snd.f03	snd.f03	/usr/snd.f03
  Windows
  	c:\hulft\dat\snd.f04	snd.f04	snd.f04	/usr/snd.f04
  IBMi
  	hulft/f05(snd)	snd.f05	snd.f05	/usr/snd.f05

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

Specify 'I' (Simplified Chinese Extended) for EBCDIC Set.

Make sure that 'G' (GB18030) or '8' (UTF-8) is specified for Code Set for Transfer in the System Environment Settings.

Behavior of the operation when "Autoconfiguration" is specified for EBCDIC Set

When you specify "0" (Autoconfiguration) for EBCDIC Set (CODESET), the setting value for the EBCDIC Set that is actually used in the single byte code conversion during file transfer is determined as follows.

For details on Code Set for Transfer (cs4trnsfr) in the System Environment Settings for which the code set of the local host is registered, refer to Administration Manual.

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