Receive Management Information

This field specifies the ID to identify the file to be received.

This field specifies the data set name for the file to be received.

Specify this field according to the naming rules for data set names for Mainframe.

Do not enclose the file names within single quotation marks (').

By specifying '&SNDFILE,' you can use the Send file name on the host on the sending side as the Receive file name. For details, refer to <Table> File Naming Rules.

When specifying '&SNDFILE,' select 'Single Receive' for the Receive Mode.

HULFT creates a file whose name is prefixed by '&' as a temporary file, and then deletes it after the Receive processing. If you specify one of the variables from '&MSG0' to '&MSG5' or from '&MSGL0' to '&MSGL1' as the Receive file name and configure the setting so that replacement with message is not carried out, HULFT creates the Receive file and names it as the corresponding string from '&MSG0' to '&MSG5' or from '&MSGL0' to '&MSGL1.' After the Receive processing, HULFT assumes that the Receive file is a temporary file due to its name, and deletes it.

This field specifies the registration mode for the Receive file.

<Table> Setting Values for Registration Mode

When you select 'Single Receive' (S) for the Receive Mode and 'Append' (M) for the Registration Mode, if an error occurs while a file is being received the receiving data up until the error occurred will be appended.

If you select 'Multiple Receive' (M) for the Receive Mode, the Registration Mode that you selected is applied to the Receive temporary file rather than the Receive file, and HULFT appends data regardless of the setting for the Registration Mode.

This field specifies the receive mode for the Receive file.

<Table> Setting Values for Receive Mode

This field specifies how to treat the Receive file when receiving fails.

<Table> Setting Values for Error Recovery

However, during the period from the Receive processing completion until disconnection (including the Post-receive Job), error recovery is disabled.

If you select 'Restore' (R), you require disk capacity that allows HULFT to store the original Receive file on the same volume as the current Receive file.

This field specifies the catalog operation for the Receive file.

<Table> Setting Values for Catalog Operation

Catalog operation is required only when HULFT creates a new Receive file. If the Receive file already exists, whether or not HULFT creates a new file depends on the attributes of the existing file.

HULFT for ACOS cannot create a new generation file. To receive in an existing generation file, select 'No' (N) rather than 'Generation File.'

For details about generation management, refer to Administration Manual.

How to assign a volume type to the Receive file

<Table> Setting Values for Multivolume

If the value of ‘Multi (M)’ is set as the volume class:

• If you want to receive data on multiple volumes, you must register the Receive file as multiple volumes in the catalog in advance.

• If the client is less than Ver.8.2.0, Checkpoint resending is not possible. The Resend processing is carried out from the first record.

• When HULFT receives data in an existing multi-volume file with the Registration Mode set as 'Replace' (R), if the number of volumes on which HULFT saves receiving data is lower than the number of volumes that were used for the file before the Receive processing, the data on the volumes that are not used for the Receive processing is left there. However, EOF is correctly appended to the end of the receiving data to guarantee that the file can be used for subsequent processing. (HULFT will not refer to the pre-receive data in this case.)

• The following settings are not possible:

  -	Receive Mode: Multiple Receive
  -	Error Recovery: Restore
  -	Volume Serial specification

• If you configure the following settings, an error will occur:

  -	Catalog Operation: Generation File
  -	The number of volumes for the Receive file and the setting of the Multivolume in the Receive Management Information do not match.

• If you received data on multiple volumes, the unit name and volume serial number information are not output in the Receive Log record.

If the value of ‘Auto (A)’ is set as the volume class:

• HULFT-HUB Manager searches for the catalog to determine whether to assign the single volume type or the multi volume type. If the applicable Receive file is not registered on the catalog yet, HULFT-HUB Manager automatically assigns the single volume type.

• Upon the Receive operations, if, based on the number of volumes retrieved from the catalog, HULFT-HUB Manager determines to assign the multi volume type to the Receive file, it behaves in the following way:

  -	In case that the value of ‘R (Restore)’ is specified for Error Recovery (ABNORMAL), HULFT-HUB Manager returns the error.
  -	In case that the value of ‘M (Multiple volumes)’ is specified for Receive Mode (RCVTYPE), HULFT-HUB Manager returns the error.

This field specifies the record format for the file to be received.

<Table> Setting Values for Record Format

This field specifies the units of space capacity for files to be received.

<Table> Setting Values for Capacity

If this value is not described in the CSV file for Collecting and Distributing System Management Information, one of the following values is enabled according to the host type.

<Table> Selection when a value is not described

This field specifies the processing for unused areas of files to be received.

<Table> Setting Values for Unused Area

This field specifies the serial number of the volume that stores the Receive file.

Specify this field according to the naming rules for the volume serial number for Mainframe.

If you omit the Volume Serial, HULFT refers to the STEPCAT catalog that is described in the JCL for XRRCV. If the Volume Serial is not in the catalog, an error will occur while receiving data.

This field specifies the serial number of the volume that stores temporary files during the Multiple Receive.

If you omit the Work Volume Serial, HULFT creates temporary files on the same volume as the Receive file.

This field specifies the transfer group ID of the Receive file.

For details about the transfer group ID, refer to Transfer Group Information.

This field specifies the EBCDIC Set that is used for single byte code conversion for the Receive file.

<Table> Setting Values for EBCDIC Set

You can use this setting when the Code Conversion for the Send Management Information on the host on the sending side is 'Receiving Host' (R).

This field specifies the name of the unit that stores the Receive file.

If you omit this field, HULFT uses the unit name that you specified for the Unit Group Name of Send and Receive File (INIT-UNIT) in the System Environment Settings.

This field specifies the sequence number on the tape device volume that stores the Receive file.

If you omit the Sequence Number and receive data on a tape volume, HULFT sets sequence number 1 and outputs to the tape volume.

This field specifies the list with names of data set storage service attributes that specify performance and availability requirements.

SMS uses these attributes to control data arrangement.

This field specifies the list of the migration, backup, and retention attributes of data sets. The system uses these attributes to manage the storage in the data set level.

This field specifies the list of allocation attributes that the system uses to create the data set.

When you specify the Data Class, you can omit the Record Format, the Record Length, the Block Size, (the Capacity), the 1ST Extent, and the Secondary.

If you create a new file, specify data class attributes whose organization is Sequential Organization for the Data Class.

This field specifies the selection for the standard format file.

<Table> Setting Values for Print Character

If the Receive file already exists, the setting value may be ignored, depending on the Registration Mode. If you specify 'Replace' (R) for the Registration Mode, HULFT also replaces the attribute that you set for the Receive file with the setting of the Print Character. If you specify 'Append' (M) for the Registration Mode, HULFT ignores setting of the Print Character and uses the attribute that is set for the Receive file.

This field specifies whether to use the attributes for the Receive file.

<Table> Setting Values for Use Attribute

You can use the attributes of the Send file only if you have selected 'Single' (S) for the Receive Mode and the remote host is Mainframe.

If HULFT is sending data from a host that is other than Mainframe, it uses the attributes that are registered in the Receive Management Information. If you have not registered attributes for the file in the Receive Management Information, an unsuccessful termination occurs.

Further, the following limitations will apply to the attributes of the Send file, even if you have set 'SND' (S) for the Use Attribute and the remote host is Mainframe:

This field specifies the Receive Completion Notification to be sent to the host on the sending side.

<Table> Setting Values for Notification

This field specifies whether or not to verify data of the file to be received.

<Table> Setting Values for Verify Data

This field specifies whether to delete Record Descriptor Word (RDW) for variable-length records when data is received.

<Table> Setting Values for Receiving with RDW

This field shows the host name for the client for which the Receive Management Information is registered.

This field specifies the alias for the Receive file.

It is recommended that you assign a unique name in the Receive Management Information so that each file ID that is displayed on screens in HULFT-HUB Manager can be easily identified.

This field shows the Batch Distribution Information ID with which the Receive Management Information is registered as distribution data.

This field specifies the Business Group ID that uses this Receive Management Information.

You can replace variables with the messages that you specify when issuing the Send Request or with the received messages, by specifying variables from '&MSG0' to '&MSG5' or from '&MSGL0' to '&MSGL1' in the following fields (Message Transmission function):

The naming rules when you use the Send file name as the Receive file name (&SNDFILE specification) are shown below.

<Table> File Naming Rules

You cannot specify the following:

If you specify 'Autoconfiguration' (0) for the EBCDIC Set, the type of EBCDIC that is actually used depends on the combination of the Kanji Code Type that is set in the Registered Client Information on both the client on the sending side and the client on the receiving side, as shown below.