Receive Management Information (i5OS)

The file information of files to be received is registered.

Field List

Table 6.42 List of Receive Management Information Fields

Field Name

Default Value

Setting Value

Optional

Remarks

File ID

 

Alphanumeric characters

-

Within 8 bytes starting with an alphabet

Comment

 

Characters

Within 60 bytes

File Name

 

Alphanumeric characters

-

In the range from 3 to 33 bytes

Record Length

 

From 1 to 32766

-

 

Registration Mode

New Creation

(*1)

-

 

Error Recovery

Delete

(*1)

-

 

Receive Mode

Single Receive

(*1)

-

 

Generation File

No

(*1)

-

 

Generation File Count

0

From 0,2 to 9999

-

 

EBCDIC Code Set

Standard

(*1)

-

 

Successful Job ID

 

Alphanumeric characters

Within 8 bytes starting with an alphabet

Unsuccessful Job ID

 

Alphanumeric characters

Within 8 bytes starting with an alphabet

Notification

Receive Completion

(*1)

-

 

Transfer Group ID

 

Alphanumeric characters

Within 8 bytes starting with an alphabet

Verify Data

No

(*1)

-

 

Encryption Key

 

Alphanumeric characters

In the range from 8 to 20 bytes

:

Optional

-

:

Mandatory

*1

:

On screen, select an option.

Explanation of Each Field

This section explains the fields that are to be set in Receive Management Information.

File ID

The ID to identify the Receive file

Comment

The comments related to the Receive file

File Name

File stored on i5/OS

For a physical data file, specify in '<library name>/<file name>(<member name>)' format.

For an archive file, specify in '<library name>/<file name>' format.

You cannot use reserved words such as '*FIRST' or '*FILE' and so forth for the Name of Receive file.

Specification of the file name with the reserved words may result in unexpected behavior of HULFT.

Record Length

Receive file record length

When Receive file does not exist, specify the length of the record in the newly created Receive file. When the Receive file already exists, specify the record length of that file.

Registration Mode

Registration method of file when receiving

New Creation:

New creation mode

Replace:

Replace mode

Append:

Append mode

Error Recovery

The Receive file processing when the Receive operation fails.

  • Delete

  • Keep

  • Restore

Receive Mode

Receiving mode of Receive file

Single Receive:

File is received from a single host.

Multiple Receive:

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

When 'Multiple Receive' is specified, specify 'Append' in Registration Mode and 'Keep' in Error Recovery.

Generation File

Setting of management of Receive file generation files

No:

Generation File Management is not available

Yes:

Generation File Management is available

When 'Yes' is selected, the Registration Mode must be set to 'New Creation' or 'Replace' and the Error Recovery to 'Delete.'

Generation File Count

Receive file generation file management count

When 'Yes' is specified in the Generation File, specify a number from '2' to '9999.'

If you specify 'No' for the Generation File, the value will become '0' and you cannot specify this field.

EBCDIC Code Set

EBCDIC code system used to convert single byte code

  • Kana

  • Lower Case

  • ASCII

  • ASPEN

  • Standard

  • Standard Extension

  • NEC Kana

  • Kana Extension

  • User Table 1

  • User Table 2

  • User Table 3

This setting becomes valid when the Code Conversion of the Send Management Information on the sending side is set to 'Receiving Side.'

= Remarks =

You can specify 'Kana Extension' if HULFT at the connection destination is Ver.7.3.0 or higher.

Successful Job ID

The ID of the job to be started when receiving file is completed successfully

For details on the Job ID, refer to Job Information (i5OS).

When omitted, the job is not started.

Unsuccessful Job ID

The ID of the job to be started when receiving file is completed unsuccessfully

For details on the Job ID, refer to Job Information (i5OS).

When omitted, the job is not started.

Notification

Receive completion notification to sending side host

Receive Completion:

Notify after the receive is complete

Successful Job Completion:

Notify after Post-receive Successful Job complete

Transfer Group ID

ID by which send destination of the Send file is registered

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

Verify Data

This field specifies whether to verify data of the file to receive.

No:

Does not verify data

Yes:

Verify data

Encryption Key

Key that decodes data.

Specify this parameter when you would like to decode encrypted data. Set the same encryption key as the one set in the Send Management Information of the remote host.

When you default this field, decryption of the data is not carried out.

Points to be Noted When Setting

Specification of Registration Mode, Receive Mode, and Generation File

When the Receive Mode is set to 'Single Receive' and 'Append' is specified for Registration Mode, Receive data obtained before the occurrence of an error will be overwritten if some kind of an error occur during receiving. When the Error Recovery is set to 'Restore,' The Receive file before the start of Receive process is saved as a separate member in the restored Receive file.

Table 6.43 Combination of Receive Management Information

Registration Mode

Error Recovery

Receive Mode

Single Receive

Multiple Receive

Generation File

Generation File

Generation File

Generation File

Enabled

Disabled

Enabled

Disabled

New Creation

Delete

 

 

Keep

 

 

 

Restore

 

 

 

Replace

Delete

 

 

Keep

 

 

 

Restore

 

 

 

Append

Delete

 

 

 

Keep

 

 

Restore

 

 

 

:

Combination that can be specified

Blank

:

Combination that cannot be specified

Archive File

When an archive file is specified in Receive File Name, specify 'Single Receive' in the Receive Mode. You cannot specify 'Append' in the Registration Mode.

Replacement Message

The fields for executing message replacement are as follows.

Specify "&MSG0" to "&MSG5" in the following fields to replace message sent from the sending side or the message specified at the time of Send Request.

  • Receive File Name

  • Transfer Group ID

  • Successful Job ID

Receive File Name

By specifying '&SNDFILE' (Physical data file) and '&SNDFILES' (Archive file), the Send file name of the sending side is set to the Receive file name. Also, when the sending side is i5OS, specify '&SNDLIB' to use Send File Library name as Receive File Library name. When the Send file name is set to the Receive file name, follow the naming conventions as shown below:

To specify '&SNDFILE,' '&SNDFILES' and '&SNDLIB,' specify 'Single Receive' in Receive Mode.

Table 6.44 File Naming Conventions

Send File Name

Receive File Name(i5OS)

Host Type

&SNDLIB&SNDFILE

MYLIB/&SNDFILE

&SNDLIB&SNDFILES

MYLIB/&SNDFILES

Mainframe

 

Sequential Organization File

HULFT.DAT.SND.F01

Conversion Error

MYLIB/F01(SND)

Conversion Error

MYLIB/SND

Partition Organization File

HULFT.DAT.F02(SND)

Conversion Error

MYLIB/F02(SND)

Conversion Error

MYLIB/SND

UNIX/Linux

 

with Extension

/HULFT/DAT/SND.F03

Conversion Error

MYLIB/F03(SND)

Conversion Error

MYLIB/SND

without Extension

/HULFT/DAT/SND

Conversion Error

MYLIB/SND(SND)

Conversion Error

MYLIB/SND

Windows

 

with Extension

C:\HULFT\DAT\SND.F04

Conversion Error

MYLIB/F04(SND)

Conversion Error

MYLIB/SND

without Extension

C:\HULFT\DAT\SND

Conversion Error

MYLIB/SND(SND)

Conversion Error

MYLIB/SND

i5OS

 

Physical File

HULFT/F05(SND)

HULFT/F05(SND)

MYLIB/F05(SND)

Conversion Error

Conversion Error

Archive File

HULFT/F06

Conversion Error

Conversion Error

HULFT/F06

MYLIB/F06

Record Length

When the Record Length specified in management information is not the same as that of the Receive file, the handling varies as per the Receive Mode. When 'Single Receive' is specified in the Receive Mode, the Record Length specified in the management information is ignored while executing the Receive process. When 'Multiple Receive' is specified in the Receive Mode, it is considered as a receive error.

Notification

When 'Receive Completion' is specified for the Notification, HULFT regards it as a different job from Receive Job. The application executes CL Command by using job description registered in the Job Information. When 'Successful Job Completion' is specified, the Receive Job directly executes the CL Command without using the job description.