Receive Management Information

Receive Management Information Update (Basic) screen

Volume Serial (VOL)

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

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

Catalog Operation (CATALOG)

This field specifies the catalog management method for the Receive file.

N (No):

Do not catalog the file

Y (GDG):

Use the generation file

C (Catalog):

Catalog the file

Defaulting this field sets 'N' (No).

Note

• If 'V' (Search the volume) is set for Search Scope for Receive File (RCV-FILE-SEARCH) in the System Environment Settings and both of the following conditions are met, the file will be received but not cataloged even if you specify 'C' (Catalog) for Catalog Operation (CATALOG):

  • A file with the same name as the Receive file is cataloged.

  • A new Receive file will be created on another volume with the same name as the cataloged file.

• If 'C' (Search the catalog) is set for Search Scope for Receive File (RCV-FILE-SEARCH) in the System Environment Settings, the file is cataloged even if you specify 'N' (No) for Catalog Operation (CATALOG).

Multivolume (VOL-TYPE)

This field specifies the method for allocating the Receive file to a volume.

S (Single):

Single volume

M (Multi):

Multiple volumes

A (Autoconfiguration):

Select Single volume or Multiple volumes automatically

Defaulting this field sets 'S' (Single).

MF-to-MF File Attrib (MFRCVORG)

This field specifies the selection of the attribute of the Receive file.

R (RCV):

Use the attribute of the Receive Management Information

S (SND):

Use the attribute of the Send file

Defaulting this field sets 'R' (RCV).

Record Format (RECFM)

This field specifies the record format of the Receive file.

F (Fix):

Fixed length

V (Var):

Variable length

Capacity (CYL|TRK)

This field specifies the space capacity unit for the Receive file.

C:

Cylinder

T:

Track

Defaulting this field sets 'C' (Cylinder). However, if you specify the Data Class (DATACLAS), the value of the specified data class is set.

1ST Extent (CYL|TRK)

This field specifies the first extent for the Receive file.

Defaulting this field sets '5.' However, if you specify the Data Class (DATACLAS), the value of the specified data class is set.

Secondary (CYL|TRK)

This field specifies the secondary extent for the Receive file.

Defaulting this field sets '3.' However, if you specify the Data Class (DATACLAS), the value of the specified data class is set.

Unused Area (CYL|TRK)

This field specifies the handling of the unused area of the Receive file.

RLSE:

Release

When defaulted:

Do not release

Record Length (LRECL)

This field specifies the record length of the Receive file.

Block Size (BLOCKLEN)

This field specifies the block size of the Receive file.

If you default this field when you have specified 'F' (Fix) for the Record Format (RECFM), the value of the Record Length (LRECL) is set. If you default this field when you have specified 'V' (Var) for the Record Format (RECFM), the value of the Record Length (LRECL) plus 4 is set.

Registration Mode (TRANSMODE)

This field specifies the registration mode of the file to be received.

N (New Creation):

Create new Receive file

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

R (Replace):

Replace the contents of the file with the received data

If the file does not exist, a new file is created

M (Append):

Append the received data to the end of the existing file

If the file does not exist, a new file is created

Error Handling (ABNORMAL)

This field specifies how HULFT handles the Receive file when the Receive processing fails.

D (Delete):

Delete the Receive file

K (Keep):

Keep the Receive file as it is when the Receive processing fails

R (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 'D' (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 (RCVTYPE)

This field specifies the receive mode for the Receive file.

S (Single Receive):

Receive the file from a single host

M (Multiple Receive):

Receive the file from multiple hosts and create one file

EBCDIC Set (CODESET)

This field specifies the Type-EBCDIC Code Set on the local host that HULFT uses to convert single byte codes

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

V:

User Table 1

W:

User Table 2

X:

User Table 3

Defaulting this field sets '0' (Autoconfiguration).

This setting is valid when the host on the sending side is a Type MF-IBMi host and you specify receiving-side conversion.

Successful Job ID (JOBID)

This field specifies the Job ID of the job that HULFT executes when the Receive processing of the file ends successfully.

For details on the Job ID, refer to Job Information.

If you default this field, the job is not executed.

Unsuccessful Job ID (AB-JOBID)

This field specifies the Job ID of the job that HULFT executes when the Receive processing of the file ends unsuccessfully.

For details on the Job ID, refer to Job Information.

If you default this field, the job is not executed.

Receive Management Information Update (Extension) screen

Notification (RCVEND-NOTICE)

This field specifies the 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 successful job completion following the Receive processing

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

Transfer Group ID (GRPID)

This field specifies the Transfer Group ID of the Receive file.

For details on the Transfer Group ID, refer to Transfer Group Information.

Verify Data (DATAVERIFY)

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

0 (No):

Do not verify data

1 (Yes):

Verify data

Defaulting this field sets '0.'

Storage Class (STORCLAS)

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

SMS uses these attributes to control the data arrangement.

Management Class (MGMTCLAS)

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.

Data Class (DATACLAS)

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

= Remarks =

If you specify Storage Class (STORCLAS), Management Class (MGMTCLAS), or Data Class (DATACLAS), HULFT behaves in the same way as when you specify "C" (Catalog Search) for Search Scope for Receive File (RCV-FILE-SEARCH).

UNIT (UNIT)

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

Print Character (PRINT-CNTL)

This field specifies the selection for the standard format file.

A (ANSI):

ANSI control character

M (Machine):

Machine control character

Work Volume Serial (WORK-VOL)

This field specifies the 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 (VSEQNO)

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

Receiving with RDW (RCV-RDW)

This field specifies whether or not to receive data with the Record Descriptor Word (RDW) added.

N (No):

Receiving without RDW

Y (Yes):

Receiving with RDW

Defaulting this field sets 'N' (No).

To receive the file with RDW, specify 'V' (Var) for the Record Format (RECFM). For details, refer to Administration Manual.

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

This field specifies the key for decryption of the data.

Specify this field to carry out decryption of encrypted data. Specify the same cipher key as the Cipher Key specified in the Send Management Information on the remote host.

If the cipher keys differ, data is not decrypted correctly.

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

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

This field specifies the key for decryption of the data.

Specify this field to carry out decryption of encrypted data. Specify the same cipher key as the Cipher Key specified in the Send Management Information on 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).

The name of the Receive file

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

• When you specify one of the following environment variables for the file name, specify 'S' (Single Receive) for the Receive Mode (RCVTYPE):

  • &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 the Mainframe DSN (DSNAME), you must specify either of the following values for the Message Dynamic Parameter Specification (MSGDYNPARM) in the System Environment Settings:

  • 1 (Replace with message for all the management information)

  • 3 (Replace with message for all the management information and the JCL for the Job Information)

• If you specify '&SNDFILE' for the Mainframe DSN (DSNAME), you cannot specify the suffix for '&SNDFILE' in characters.

• You can specify '&SNDFILE' to use the Send file name of the host on the sending side as the Receive file name.

• The following table shows the naming conventions that apply when you use the Send file name of the host on the sending side as the Receive file name:

  Table 2.4 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

  When the value sent from the host on the sending side replaces the value of one of the following fields, if the field name after replacement does not comply with the naming conventions of the operating system, a transfer error will occur:

  • Mainframe DSN (DSNAME)

  • Volume Serial (VOL)

  • UNIT (UNIT)

Volume Serial

If you default the Volume Serial (VOL), HULFT searches the catalog and allocates the Receive file.

When you carry out the Receive processing on an SMS-managed volume, the operating system automatically allocates the volumes that belong to the storage group. Therefore, HULFT does not use the value specified for the Volume Serial (VOL).

Catalog Operation

The Catalog Operation (CATALOG) is enabled only when you create a new Receive file.

When you create a new Receive file on an SMS-managed volume, the Receive file is cataloged regardless of the specification for Catalog Operation (CATALOG).

For details on generational management, refer to Administration Manual.

Multivolume

• When you specify 'S' (Single) for the Multivolume (VOL-TYPE), if you carry out the Receive processing for a multi-volume file, a transfer error occurs.

  In addition, when you specify 'S' (Single) for the Multivolume (VOL-TYPE) 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

  • The Receive file experiences data overflow during the Receive processing

  In such cases, it is recommended that you specify 'A' (Autoconfiguration) for the Multivolume (VOL-TYPE).

• When you specify 'M' (Multi) for the Multivolume, note the following points:

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

    A cataloged multi-volume file must already 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 the following conditions are fulfilled, a portion of the existing data will remain in any volumes that were not used:

    • The number of volumes used during the Receive processing is lower than the number of volumes being used prior to the Receive processing

    • The Receive file is a multi-volume file

    • 'R' (Replace) is specified for the Registration Mode (TRANSMODE)

  • You cannot specify 'M' (Multiple Receive) for the Receive Mode (RCVTYPE).

  • You cannot specify 'R' (Restore) for the Error Handling (ABNORMAL).

  • You cannot specify the Volume Serial (VOL).

  • The value specified for the UNIT (UNIT) is not used.

  • When you carry out the Receive processing for a multi-volume file, if you specify 'Y' (GDG) for the Catalog Operation (CATALOG), a transfer error occurs.

  • When you carry out the Receive processing for a multi-volume file, HULFT does not output the UNIT or the Volume Serial in the Receive Log.

• When you specify 'A' (Autoconfiguration) for the Multivolume, note the following points:

  • 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, when HULFT obtains the number of volumes of the Receive file from the catalog and finds that the file is a multi-volume file, HULFT operates as follows:

    • If 'R' (Restore) is specified for the Error Handling (ABNORMAL), an error occurs.

    • If 'M' (Multiple Receive) is specified for the Receive Mode (RCVTYPE), an error occurs.

MF-to-MF File Attrib

• Specification of 'S' (SND) for the MF-to-MF File Attrib (MFRCVORG) is effective when both of the following are true:

  • The host on the sending side is Mainframe

  • 'S' (Single Receive) is specified for the Receive Mode (RCVTYPE)

• If the host on the sending side is a type other than Mainframe, HULFT uses the file attributes that you registered in the Receive Management Information. Therefore, if you defaulted the file attributes in the Receive Management Information, a transfer error occurs.

• Even if you specify 'S' (SND) for the MF-to-MF File Attrib (MFRCVORG) and the type of the host on the sending side is Mainframe, the following restrictions apply according to the attributes of the Send file:

  • If the Send file is one of the following files, HULFT uses the file attributes that you registered in the Receive Management Information;

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

    • File that is stored on a tape volume

    • File that is managed by SMS

  • Even if you create the Send file in a non-blocked format, HULFT creates the Receive file in a blocked format.

  • If you create the Send file in a unit of capacity other than tracks or cylinders, HULFT uses the value that you registered in the Receive Management Information.

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

  • HULFT applies the capacity of 1ST Extent and the Secondary of the Send file to the 1ST Extent and the Secondary of the Receive file.

Block Size

If the Record Format (RECFM) is 'F' (Fix), specify an integral multiple of the Record Length (LRECL) for the value of the Block Size (BLOCKLEN).

If the Record Format is 'V' (Var), specify an integral above the value of the Record Length (LRECL) plus 4 for the Block Size (BLOCKLEN).

Registration Mode

When you specify 'S' (Single Receive) for the Receive Mode (RCVTYPE) and 'M' (Append) for the Registration Mode (TRANSMODE), if an error occurs during the Receive processing, the data received up to the point where the error occurred is appended to the Receive file.

When you specify 'M' (Multiple Receive) for the Receive Mode (RCVTYPE), the specification for the Registration Mode (TRANSMODE) becomes the Registration Mode not for the Receive file, but for the Receive work files. Therefore, regardless of the specification for the Registration Mode (TRANSMODE), the data will always be appended to the Receive file.

Error Handling

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

  When you select 'N' (New Creation) for the Registration Mode (TRANSMODE), if the Receive file already exists, an error occurs and HULFT does not delete the existing file.

• Points to be noted when specifying 'R' (Restore)

  When you specify 'R' (Restore) for the Error Handling (ABNORMAL), a backup file for restoration of the Receive file is created on the same volume and with the same capacity as the Receive file.

  Therefore, the same capacity as that required for the Receive file must be available on the same volume as the Receive file.

  The backup file for the restoration of the Receive file is created with the file name 'Receive File Name.BK.'

  Therefore, if a file with the same name already exists, or if a backup file cannot be created due to the SMS settings, a Receive file allocation error occurs.

  When you carry out the Receive processing on an SMS-managed volume, if you specify 'R' (Restore) for the Error Handling (ABNORMAL), specify the following fields with the same class of attribute as in the Receive Management Information:

  • Storage Class (STORCLAS)

  • Management Class (MGMTCLAS)

  • Data Class (DATACLAS)

Receive Mode

• When you specify 'M' (Multiple Receive) for the Receive Mode (RCVTYPE), you must specify the Successful Job ID (JOBID).

  In the Multiple Receive, HULFT receives data in Receive work files, and after the Receive processing is complete, when the successful job is executed, HULFT appends the data to the Receive file.

  If an error occurs during the Receive processing, HULFT does not append the data that HULFT received before the occurrence of the error to the Receive file, even if you have specified 'K' (Keep) for the Error Handling (ABNORMAL).

  If an error occurs while HULFT is appending the data of the Receive work files to the Receive file, even if you have specified 'D' (Delete) for the Error Handling (ABNORMAL), the data received up to the point when the error occurred is appended, and deletion from the Receive file does not occur.

  For details on Receive work files, refer to Administration Manual.

• When you use the Multiple Receive, specify as follows:

  • Specify 'S' (Single) for the Multivolume (VOL-TYPE) or default it

  • Specify 'R' (RCV) for the MF-to-MF File Attrib (MFRCVORG) or default it

• When you specify one of the following environment variables for the Mainframe DSN (DSNAME), specify 'S' (Single Receive) for the 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:

  • One of the following values for the Execute Post-receive Job (TTRCVJOB) in the System Environment Settings;

    • '0' (Do not execute the Post-receive Job)

    • '2' (Execute the Post-receive Job with TYPRUN=SCAN added)

  • '1' (Output) for the Output Receive File (TTRCVFILOUTPUT) in the System Environment Settings

  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.

EBCDIC Set

If you specify any of the following values, you must register the corresponding EBCDIC user table in advance:

• V (User Table 1)

• W (User Table 2)

• X (User Table 3)

In order to specify any of the above, there are conditions that must be met. Even when the conditions are met, an error may occur during receiving. For details, refer to Code Conversion Manual.

Notification

If you specify 'J' (Successful Job Completion) for the Notification (RCVEND-NOTICE), HULFT does not send a receive completion notification to the remote host until the Post-receive Job ends.

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

Data Class

If you specify the Data Class (DATACLAS), you can default the following fields:

• Record Format (RECFM)

• Record Length (LRECL)

• Block Size (BLOCKLEN)

• 1ST Extent (CYL|TRK)

• Secondary (CYL|TRK)

• Capacity (CYL|TRK)

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

UNIT

If you default the UNIT (UNIT), HULFT uses the value specified for the UNIT Name of Send Files and Receive Files (INIT-UNIT) in the System Environment Settings.

Print Character

The Print Character attribute for the Receive file may be changed depending on the specification of the Registration Mode (TRANSMODE), as follows:

Work Volume Serial

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

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

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

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

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

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

Sequence Number

If you default the Sequence Number (VSEQNO) and carry out the Receive processing of a file on a tape volume, HULFT regards the Sequence Number as 1 during the Receive processing.

Replacement Message

Listed below are the fields for which you can carry out replacement with message.

In the following fields, if you specify '&MSG0' to '&MSG5' or '&MSGL0' to '&MSGL1,' the strings are replaced with messages that you specified when you issued the Send Request, or messages sent from the host on the sending side:

• Mainframe DSN (DSNAME)

• Volume Serial (VOL)

• UNIT (UNIT)

• Transfer Group ID (GRPID)

• Successful Job ID (JOBID)

HULFT may not be able to carry out replacement with message 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.

Restrictions on use of tape volumes

There are several restrictions that apply when carrying out the Receive processing on a tape volume. For details on restrictions, refer to Restrictions on use of tape volumes.

Operation when 'Autoconfiguration' is specified for EBCDIC Set

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

Receiving files in SMS-managed environment

There are several points to be noted when you carry out the Receive processing in an SMS-managed environment.

For the operation of HULFT in an SMS-managed environment, refer to Administration Manual.