List of Receive Management Information fields

Basic Settings

Mainframe DSN

Data set name (DSN) of the Receive file

Specify according to the data set naming conventions for Mainframe.

Volume Serial

Serial number of the volume that stores the Receive file

Specify according to the volume serial number naming conventions for Mainframe.

Catalog Operation

Catalog management method for the Receive file

No:

Do not catalog the file

Generational Management:

Manage generations of the file

Catalog:

Catalog the file

Omitting this field sets 'No.'

Multivolume

Method for allocating the Receive file to a volume

Single:

Single volume

Multi:

Multiple volumes

Autoconfiguration

Automatically select Single volume or Multiple volumes

Omitting this field sets 'Single.'

Inter-MF Receiving Applies Settings From

Selection of the Receive file attributes

SND:

Use the attribute of the Send file

RCV:

Use the attribute of the Receive Management Information

Omitting this field sets 'RCV.'

Record Format

Record format of the Receive file

• Fix

• Var

• Omission

When you specify Data Class, 'Omission' is displayed.

Capacity

Capacity unit for the Receive file

CYL:

Cylinder

TRK:

Track

OMIT

 

When you specify Data Class, 'OMIT' is displayed.

Omitting this field sets 'CYL.' However, if Data Class is specified, the value of the specified data class is set.

1ST Extent

First extent for the Receive file

Omitting this field sets '5.' However, if Data Class is specified, the value of the specified data class is set.

Secondary

Secondary extent for the Receive file

Omitting this field sets '3.' However, if Data Class is specified, the value of the specified data class is set.

Unused Area

Handling of the unused space of the Receive file

• Release

• Do not release

Record Length

Record length of the Receive file

When Data Class is specified, the value of the specified Data Class is set.

Block Size

Block size of the Receive file

Storage Class

Named list that specifies the performance and the availability requirements of dataset storage service attributes

SMS controls the data placement by using this attribute.

Management Class

The list of migration, backup, and retention period attributes of a dataset that the system uses for storage management on the dataset level

Data Class

The list of allotment attributes that the system uses for the creation of a dataset

= Remarks =

• Storage Class, Management Class, and Data Class are displayed only when connecting to HULFT for zOS.

• If the Storage Class, the Management Class, or the Data Class is set, HULFT operates similar to when 'SMS' is set in the execution parameter of the Receive program (XRRCV).

Registration Mode

Registration method of the file to be received

New Creation:

Create new Receive file

An error occurs if a file of the same name already exists

Replace:

Replace the content of an existing file with received data

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

Append:

Append the received data to the end of the existing file

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

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

Even if an error occurs during the period after file transfer terminates but before the Receive processing ends, this field is ignored because the file transfer has already terminated.

Receive Mode

Receive mode for the Receive file

Single Receive:

File is received from a single host.

Multiple Receive:

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

EBCDIC Set

Type-EBCDIC Code Set of the host on the receiving side that is used for the conversion of single-byte codes

• Autoconfiguration

• Katakana

• Lower Case

• ASCII

• ASPEN

• Japan (Latin) for IBM

• Japan (Latin) Extended for IBM

• NEC Katakana

• Japan (Katakana) Extended for IBM

• User Table 1

• User Table 2

• User Table 3

Omitting this field sets '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

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.

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

Unsuccessful Job ID

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.

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

Omitting this field sets 'Receive Completion.'

Transfer Group ID

Transfer group ID of the Receive file

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

Verify Data

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

No:

Do not verify data

Yes:

Verify data

Omitting this field sets 'No.'

UNIT

Unit name of the unit that stores the Receive file

Print Character

Selection for the standard format file

• Disabled

• ANSI

• Machine

Work Volume Serial

Serial number of the volume that stores Receive work files for the Multiple Receive

Defaulting this field creates Receive work files in the same volume as the Receive file.

Sequence Number

Sequence number on the tape volume that stores the Receive file

Receiving with RDW

Specify whether to receive data with the Record Descriptor Word (RDW) added

Yes:

Receive with RDW

No:

Receive without RDW

Omitting this field sets 'No.'

When you receive files with RDW, you need to either specify 'Var' or 'Omission' for Record Format. If you specify 'Omission,' Record Format is set to 'Fix.'

For details, refer to Administration Manual for the destination host.

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. Set the same cipher key as the one set in the Send Management Information of the remote host.

Be sure to specify the cipher key. Note that if the sending-side host is not in Forced Strong Key mode, a transfer error always occurs.

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

File ID

You cannot specify "_INSTANT_TRANSFER_" for File ID.

Receive File Name

• Do not enclose file names within single quotations (').

• When specifying any of the following environment variables, specify 'Single Receive' for Receive Mode:

  • &SNDFILE

  • &MSG0 to &MSG5

  • &MSGL0 to &MSGL1

• Files with '&' at the beginning of their name are created as temporary files, and are deleted after the Receive processing ends.

  Therefore, if you specify '&MSG0' to '&MSG5' or '&MSGL0' to '&MSGL1' for Mainframe DSN, you must set one of the following values for Message Dynamic Parameter Specification (MSGDYNPARM) in the System Environment Settings:

  • 1 (Replace all messages in the management information)

  • 3 (Replace all messages in JCL specified in the Job Information and in the management information)

• If you specify '&SNDFILE' for Mainframe DSN, you cannot set a character string after '&SNDFILE.'

• By specifying '&SNDFILE,' the Send file name of the sending host is set to the Receive file name.

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

  Table 4.26 File Naming Conventions

  Host Type	Send File Name	Receive File Name (Mainframe)
  Mainframe	Sequential Organization file HULFT.DAT.SND.F01	HULFT.DAT.SND.F01
  	Partitioned data set (PDS) HULFT.DAT.F02(SND)	HULFT.DAT.SND.F02
  UNIX or Linux	/hulft/dat/snd.f03	SND.F03
  Windows	c:\hulft\dat\snd.f04	SND.F04
  IBMi	HULFT/F05(SND)	SND.F05

  Note

  If you replace the value sent from the sending host with one of the following fields, a transfer error will occur if any replaced field names do not match the naming conventions of the operating system:

  • Mainframe DSN

  • Volume Serial

  • UNIT

Volume Serial

If you omit Volume Serial, the system will search the catalog and allocate a Receive file.

If the Receive file is on an SMS-managed volume, the value for Volume Serial is ignored because the operating system automatically allocates the volume of the storage group.

UNIT

If you omit UNIT, the value set for UNIT Name of Send Files and Receive Files (INIT-UNIT) in the System Environment Settings is used.

Catalog Operation

Catalog Operation is enabled only when you create a new Receive file.

If you create a new Receive file on an SMS-managed volume, it is cataloged regardless of Catalog Operation setting.

For details about generational management, refer to Administration Manual for the destination host.

Multivolume

• If you specify 'Single' for Multivolume and then receive a multi-volume file, a transfer error occurs.

  In addition, if you specify 'Single' for Multivolume and both of the following are fulfilled, the Receive file is automatically created as a multi-volume file:

  • A new Receive file is created on the tape volume

  • Data overflow occurs when receiving files

• If you specify 'Multi' for Multivolume, be sure to note the following:

  • You cannot create a new Receive file as a multi-volume file on non-SMS-managed volumes.

    Cataloged multi-volume files must be created.

    However, if you use a tape volume for the Receive processing, even if a cataloged multi-volume file is already created, you cannot carry out the Receive processing.

  • If all of the following conditions are met, a portion of the existing data will remain in unused volumes;

    • The number of volumes used for receiving is smaller than the number of volumes used before receiving.

    • The Receive file is a multi-volume file.

    • 'Replace' is set for Registration Mode.

  • 'Multiple Receive' cannot be specified for Receive Mode.

  • 'Restore' cannot be specified for Error Handling.

  • You cannot specify Volume Serial.

  • The value specified for UNIT is not used.

  • When receiving multi-volume files, a transfer error occurs if you specify 'Generational Management' for Catalog Operation.

  • When receiving multi-volume files, UNIT name and Volume Serial Number information will not be output to the Receive Log.

• If you specify 'Autoconfiguration' for Multivolume, be sure to note the following:

  • Make sure to catalog the Receive file so that HULFT can obtain the number of volumes from the catalog.

    If you do not catalog the Receive file, HULFT regards the Receive file as a single-volume file.

  • During Receive processing, after HULFT obtains the number of volumes from the catalog, when HULFT regards the Receive file as a multi-volume file, HULFT operates as follows:

    • If 'Restore' is specified for Error Recovery, an error occurs.

    • If 'Multiple Receive' is specified for Receive Mode, an error occurs.

Inter-MF Receiving Applies Settings From

• The "SND" setting for Inter-MF Receiving Applies Settings From is effective when both of the following conditions are met:

  • The host on the sending side is Mainframe.

  • 'Single Receive' is set for Receive Mode.

• If the host on the sending side is a type other than Mainframe, HULFT uses the file attributes registered in the Receive Management Information.

  Therefore, if you omit the file attributes for the Receive Management Information, a transfer error occurs.

• If "SND" is set for Inter-MF Receiving Applies Settings From, and even if the host on the sending side is Mainframe, the following restrictions are applicable for the Send file attributes.

  • If the Send file is one of the following files, the file attributes registered in the Receive Management Information will be used:

    • VSAM organization file (ESDS, KSDS, or RRDS)

    • File that is stored on a tape volume

    • File that is managed by SMS

  • Print Character in the Receive Management Information is set even when the Send file is set in Print character format.

  • The Receive file will be converted into blocked format even if the Send file is created in a format other than blocked format.

  • If the Send file is allocated in a unit of capacity other than tracks or cylinders, the value registered in the Receive Management Information is used.

  • If the Send file is an SMS-managed file, the class attribute of the Send file is not used for Receive file.

  • 1ST Extent and Secondary specified during allocation of the Send file are used for the Receive file. The Receive file is not created with the capacity used for the Send file.

Block Size

When Record Format is set to 'Fix,' Block Size is specified as an integral multiple of the value of Record Length.

When Record Format is set to 'Var,' Block Size is specified as an integer equal to or greater than the value of Record Length plus 4.

Work Volume Serial

Receive work files for Multiple Receive is named according to First Modifier of Receive Work Files (RPREFIX) in the System Environment Settings.

If Work Volume Serial is not specified in the Receive Management Information, the Receive work file is created in the same volume as the Receive file.

When you create Receive work files for the Multiple Receive in an SMS-managed volume, do not specify Work Volume Serial because that specification is disabled.

When the Receive file is managed by SMS and you want to create Multiple Receive work files in a non-SMS-managed volume, specify settings so that the following conditions are fulfilled:

• A non-SMS-managed volume is specified for Work Volume Serial in the Receive Management Information

• First Modifier of Receive Work Files (RPREFIX) is not managed by SMS

Registration Mode

If 'Append' is specified for Registration Mode when 'Single Receive' is set to Receive Mode, and if a problem occurs while receiving, the received data will be appended to the Receive file before the error occurs.

If you specify 'Multiple Receive' for Receive Mode, the specification for Registration Mode is applied to the Receive work file rather than the Receive file. Therefore, the Receive file is always appended, regardless of the Registration Mode setting.

Error Handling

• Points to be noted when specifying 'Delete'

Delete is not executed if the Receive file already exists and error occurs when 'New Creation' is selected as the Registration Mode.

• Points to be noted when specifying 'Restore'

If you specify 'Restore' for Error Handling, the backup files for restoring the Receive file are created in the same volume and with the same capacity as the Receive file.

Therefore, the volume where the Receive file is located must have available capacity equal to the size of the Receive file.

The backup file for restoring the Receive file is created with the name: 'Receive file name.BK.'

Therefore, if a file with the same name already exists or if a backup file cannot be created because of the SMS settings, an allocation error occurs for the Receive file.

When receiving on an SMS-managed volume, if you specify 'Restore' for Error Handling specify the class of the same attribute for Receive files in the following fields in the Receive Management Information:

• Storage Class

• Management Class

• Data Class

Receive Mode

• If you specify 'Multiple Receive' for Receive Mode, you must specify Successful Job ID.

  For Multiple Receive, Receive work files are used, and after receiving is complete a successful job is executed and the receive data is written into the Receive file.

  If any error occurs during receive operation the receive data is not written into the Receive file even if 'Keep' is set for Error Handling.

  Further, if an error occurs while appending the Receive work file to the Receive file, the data received before the error occurs will be written into the Receive file and the Receive file is not deleted, even if 'Delete' is set for Error Handling.

  For details about Receive work files, refer to Administration Manual on the destination host.

• For Multiple Receive, specify as follows:

  • Specify 'Single' for Multivolume, or omit this field.

  • Specify "RCV" for Inter-Mainframe Receiving Attributes, or omit this field.

• If you specified any of the following environment variables for Mainframe DSN, specify 'Single Receive' for Receive Mode:

  • &SNDFILE

  • &MSG0 to &MSG5

  • &MSGL0 to &MSGL1

• When you carry out the Multiple Receive in test mode, if both of the following values are set, the Receive file is not updated:

  • The Execute Post-receive Job in the System Environment Settings is 'Disabled'

  • The Output Receive File in the System Environment Settings is 'Output'

  In the above case, Receive work files are not deleted. Delete the work files manually. For details on the names of Receive work files, refer to Work Volume Serial in this section.

Print Character

The attributes for Print Character format might vary depending on the setting for Registration Mode, as shown below.

Notification

If 'Successful Job Completion' is specified for Notification, the completion notification will not be sent to the host until the Post-receive Job ends.

Therefore, a time-out may occur on the remote host.

Sequence Number

If you omit Sequence Number and receive files to the tape volume, the files are received as sequential number '1.'

Replacement Message

Listed below are the fields in which you can replace the variables with the messages.

Specify '&MSG0' to '&MSG5' or '&MSGL0' to '&MSGL1' in the following fields to replace the strings with the messages that are specified at the time of the Send Request or with messages sent from the sending side:

• Mainframe DSN

• Volume Serial

• UNIT

• 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 host on the sending side.

For points to be noted on message transmission, refer to Administration Manual for the destination host.

Data Class

If you specify Data Class, the following fields are optional:

• Record Format

• Record Length

• Block Size

• 1ST Extent

• Secondary

• Capacity

When you create a new Receive file, specify Data Class as a data class whose attribute is Sequential Organization.

Restrictions on using tape volumes

There are restrictions with respect to receiving in tape volumes. For details on these restrictions, refer to Operation Manual for the destination host.

EBCDIC Set

If you specify any of the following values, you must register an EBCDIC user table:

• User Table 1

• User Table 2

• User Table 3

For details on the registration of EBCDIC user tables, refer to Administration Manual for the destination host.

Note that certain conditions must be met when you specify any of the above values. In addition, even if the conditions for specification are met, an error may occur during receiving. For details, refer to Code Conversion Manual for the destination host.

Operation when 'Autoconfiguration' is specified for EBCDIC Set

When you specify '0' (Autoconfiguration) for EBCDIC Set, the value of the EBCDIC Set that is actually used in single-byte code conversion is determined for each transfer as follows: