Receive Management Information (UNIX/Linux)
The file information of files to be received is registered.
(1) Field List
Field Name |
Default Value |
Setting Value |
Optional |
Remarks |
---|---|---|---|---|
File ID |
|
Upper case alphanumeric characters |
- |
Within 8 bytes |
Comment |
|
Characters |
✓ |
Within 60 bytes |
Receive File Name |
|
Alphanumeric characters |
- |
Within 200 bytes |
Owner Name |
|
Alphanumeric characters |
- |
Within 14 bytes |
Group Name |
|
Alphanumeric characters |
- |
Within 14 bytes |
Permission |
Marked |
(*1) |
✓ |
|
Registration Mode |
New Creation |
(*1) |
- |
|
Error Recovery |
Delete |
(*1) |
- |
|
Receive Mode |
Single Receive |
(*1) |
- |
|
Generation File |
No |
(*1) |
- |
|
Generation File Count |
|
From 0,2 to 9999 |
✓ |
|
EBCDIC Code Set |
Standard |
(*1) |
- |
|
Successful Job ID |
|
Alphanumeric characters |
✓ |
Within 8 bytes |
Unsuccessful Job ID |
|
Alphanumeric characters |
✓ |
Within 8 bytes |
Notification |
Receive Completion |
(*1) |
- |
|
Transfer Group ID |
|
Alphanumeric characters |
✓ |
Within 8 bytes |
Verify Data |
No |
(*1) |
✓ |
|
Interfacing with Exchanger |
N |
Y,N |
✓ |
|
Encryption Key |
|
Alphanumeric characters |
✓ |
8 to 20 bytes |
✓ |
: |
Optional |
- |
: |
Mandatory |
*1 |
: |
On screen, select an option. |
(2) 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
- Receive File Name
-
The name of the Receive file.
Specify the name using the full path.
In the environment that installed HULFT7 for UNIX/Linux-EX, you can specify a file that utilizes network resource. For details, refer to the explanation of networked files in UNIX/Linux Administration Manual for the destination host.
- Owner Name
-
The owner of the Receive file
Set the owner name registered in the system.
- Group Name
-
The Receive file group name
Set the group name registered in the system.
- Permission
-
The permission mode to read, write or execute the file.
- Marked:
-
Not permitted
- Unmark:
-
Permitted
- 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 to be specified, enter 'Append' in the Registration Mode and 'Keep' in Error Recovery.
- Generation File
-
The Receive file generation file management
- 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
-
The generation file management count of the Receive file.
Specify this value when 'Yes' is specified in Generation File. If you specify 'No' for the Generation File, the value will become '0' and you cannot specify this field.
- EBCDIC Code Set
-
The EBCDIC code system to be used when converting EBCDIC code to ASCII 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 (UNIX/Linux).
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 (UNIX/Linux).
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
-
The Transfer Group ID of the Receive file.
For details on the Transfer Group ID, refer to Transfer Group Information (UNIX/Linux).
- Verify Data
-
This field specifies whether to verify data of the file to receive.
- No:
-
Does not verify data
- Yes:
-
Verify data
- Interfacing with Exchanger
-
Interface between the Receive system and HULFT Exchanger Option.
- Y:
-
Interface with Exchanger
- N:
-
Do not Interface with Exchanger
For details on interfacing with HULFT Exchanger, refer to the manuals of HULFT Exchanger.
- 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 the Encryption Key is not specified in Send Management Information on the sending side, Encryption Key is disregarded even if it is specified on the receiving side.
When you default this field, decryption of the data is not carried out.
(3) Points to be Noted When Setting
Specification of Registration Mode, Receive Mode, and Generation File
The combinations that can be specified in Receive Management Information are as follows.
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 |
Receive Mode
Specification of 'Multiple Receive' file.
It is necessary to take enough care because during receive, the data is stored in a temporary file and is copied to the Receive file after the Receive operation is completed.
Error Recovery
Points to be noted when specifying 'Delete.'
When 'New Creation' is selected as the Registration Mode, if the Receive file already exists resulting in an error, the existing files are not deleted.
Points to be noted when specifying 'Keep.'
When 'Multiple Receive' is selected as the Receive Mode, if error occurs while receiving in a temporary file, the data received prior to the occurrence of the error is not written to the Receive file. In addition, if any error occurs when the temporary file is being copied to the Receive file, the receive data up to that point is added. Therefore there should be a function embedded in your application program to check duplicate data.
Replacement Message
The fields that can be used for message replacement are given below.
By specifying '$MSG0' to '$MSG5' to the following fields, field values are replaced with the messages that are specified at the time of the Send Request or the those sent from the sending side.
-
Receive File Name
-
Transfer Group ID
-
Successful Job ID
Receive File Name
-
By specifying '$SNDFILE,' the Send file name of the sending side is set to the Receive file name. When the sending side is UNIX or Linux, the path name of the sending side is set to the path name of the Receive file by specifying '$SNDPATH.' The naming conventions for using the Send File Name as the Receive File Name are as follows.
-
Specify 'Single Receive' in the Receive Mode when specifying '$SNDFILE.'
-
If Send File Name contains double byte code, it is treated as an error.
Host Type |
Receive File Name |
|||
---|---|---|---|---|
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 |
Partition Organization File HULFT.DAT.F02(SND) |
HULFT.DAT.SND.F02 |
HULFT.DAT.SND.F02 |
/usr/HULFT.DAT.SND.F02 |
|
UNIX/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 |
i5OS |
||||
|
hulft/f05(snd) |
snd.f05 |
snd.f05 |
/usr/snd.f05 |
While using '$SNDPATH,' use it in combination only with '$SNDFILE' (as '$SNDPATH$SNDFILE'). You cannot add any characters before or after it.