Receive Management Information
You can register information about the file to be received (called Receive file or receive target file). There are two ways to register the information.
-
Registration using the HULFT Management Console
=> Refer to Using the Receive Management Information
-
Registration by running commands with parameter files
=> Refer to Management Information Batch Registration command
Field List
In the table below, the check marks in the Optional column indicate the fields considered optional during registration from the HULFT Management Console. Optional fields and mandatory fields for registration by running commands with parameter files may differ from those for registration using the HULFT Management Console.
For details on optional fields and mandatory fields for the registration by running commands with parameter files, refer to Management Information Batch Registration command.
|
Field Name |
Default Value |
Setting Value |
Optional |
Remarks |
||
|---|---|---|---|---|---|---|
|
Screen |
File |
|||||
|
RCVFILE |
|
Uppercase alphanumeric characters and "_" |
- |
Within 50 bytes |
||
|
COMMENT |
|
Characters |
✓ |
Within 60 bytes |
||
|
Basic Settings |
||||||
|
|
FILENAME |
|
Characters |
- |
Within 200 bytes |
|
|
TRANSMODE |
New Creation (N) |
N, R, M |
- |
(*1) |
||
|
ABNORMAL |
Delete (D) |
D, K, R |
- |
(*1) |
||
|
RCVTYPE |
Single Receive (S) |
S, M |
- |
(*1) |
||
|
GENCTL |
No (N) |
Y, N |
- |
(*1) |
||
|
GENMNGNO |
|
0, 2–9999 |
✓ |
|
||
|
CODESET |
Autoconfiguration (0) |
0, A to I, V to X |
✓ |
(*2) |
||
|
JOBID |
|
Alphanumeric characters and "_" |
✓ |
Within 50 bytes |
||
|
EJOBID |
|
Alphanumeric characters and "_" |
✓ |
Within 50 bytes |
||
|
Extension Settings |
||||||
|
|
JOBWAIT |
Receive Completion (T) |
J, T |
✓ |
(*2) |
|
|
GRPID |
|
Alphanumeric characters and "_" |
✓ |
Within 50 bytes |
||
|
DATAVERIFY |
No (0) |
0, 1 |
✓ |
(*2) |
||
|
MAILID |
|
Uppercase alphanumeric characters |
✓ |
Within 50 bytes |
||
|
Cipher Key(*3) |
PASSWORD |
|
Alphanumeric characters |
✓ |
8–20 bytes |
|
|
Cipher Key(*4) |
Hexadecimal character string |
- |
64 digits |
|||
|
✓ |
: |
Optional |
|
- |
: |
Mandatory |
|
*1 |
: |
For the HULFT Management Console, click a setting value on the pulldown list. |
|
*2 |
: |
For the HULFT Management Console, click a setting value on the pulldown list. When you do not specify this field, the default value will be set. |
|
*3 |
: |
This type of cipher key can be set when Forced Strong Key Mode (strongkeymode) is set to "Disabled (0)" in the System Environment Settings. |
|
*4 |
: |
This type of cipher key must be set when Forced Strong Key Mode (strongkeymode) is set to "Enabled (1)" in the System Environment Settings. |
Explanation of each field
This section explains the fields to be specified in the Receive Management Information. The parenthesized strings are the names of each field and you can use them as field tags in a parameter file when registering the information.
- File ID (RCVFILE)
-
ID that identifies the Receive file
- Comment (COMMENT)
-
Comment for the Receive file
Basic Settings
- File Name (FILENAME)
-
Name of the Receive file
Specify the file name with a full path.
In HULFT10 Server grade environments, you can specify a file that uses network resources.
For details on networked files, refer to the following:
HULFT10 for Windows Administration Manual : Networked files
- Registration Mode (TRANSMODE)
-
Registration mode for the Receive file
- New Creation (N):
-
Create new Receive files.
Using an existing file name displays an error.
- Replace (R):
-
Replace the content of an existing file with received data.
A new file is created if the file does not exist.
- Append (M):
-
Append the received data to the end of the existing file.
A new file is created if the file does not exist.
When 'Append' (M) is specified for Registration Mode (TRANSMODE) when 'Single Receive' (S) is set for Receive Mode (RCVTYPE), if a problem occurs during receiving, the receive data up to the point where the error occurred will be appended to the file.
- Error Handling (ABNORMAL)
-
Handling of the Receive file at the time when the Receive processing fails
- Delete (D):
-
Delete the receive file
- Keep (K):
-
Keep the receive file as it is when the receiving-side transferring fails
- Restore (R):
-
Back up the receive file before the receiving-side transferring starts and restore the backup file if the receiving-side transferring fails
If the receive file does not exist before the receiving-side transferring starts, HULFT operates in the same way as when you specify "Delete" (D).
- Receive Mode (RCVTYPE)
-
Specify how the Receive file or Receive files are received
- Single Receive (S):
-
File is received from a single host.
- Multiple Receive (M):
-
Files are received from multiple hosts and one file is created.
If you specify 'Multiple Receive' (M), you must specify 'Append' (M) for Registration Mode and 'Keep' (K) for Error Handling (ABNORMAL).
- Generational Management (GENCTL)
-
Select whether to apply a generational management to the Receive file
- No (N):
-
Generational management is disabled.
- Yes (Y):
-
Generational management is enabled.
When you specify 'Yes' (Y), specify the following settings as shown:
-
'New Creation' (N) or 'Replace' (R) for Registration Mode
-
'Delete' (D) for Error Handling
- No. of Generations (GENMNGNO)
-
Number of generations used for managing the Receive file
The setting value is valid only when Generational Management (GENCTL) is set as 'Yes' (Y).
- EBCDIC Set (CODESET)
-
Specify Type-EBCDIC Code Set that is used for the conversion of single-byte codes
Specify the EBCDIC Set for the sending-side host (remote host).
-
Autoconfiguration (0)
-
Katakana (A)
-
Lower Case (B)
-
ASCII (C)
-
ASPEN (D)
-
Japan (Latin) for IBM (E)
-
Japan (Latin) Extended for IBM (F)
-
NEC Katakana (G)
-
Japan (Katakana) Extended for IBM (H)
-
Simplified Chinese Extended (I)
-
User Table 1 (V)
-
User Table 2 (W)
-
User Table 3 (X)
Omitting this field sets 'Autoconfiguration' (0).
This setting is valid when the host on the sending side uses the Type-EBCDIC Code Set and you specify receiving-side conversion.
= Remarks ="ASPEN" (D) and "NEC Katakana" (G) are not recommended. If you specify ASPEN (D) and NEC Katakana (G), the files may not be converted. Use a different code set.
-
- Successful Job ID (JOBID)
-
Job ID of the job that HULFT starts when the Receive processing of the file ends successfully
For details on job IDs, refer to Job Information.
If omitted, HULFT does not start the specified job.
- Unsuccessful Job ID (EJOBID)
-
Job ID of the job that HULFT starts when the Receive processing of the file ends unsuccessfully
For details on job IDs, refer to Job Information.
If omitted, HULFT does not start the specified job.
Extension Settings
- Notification (JOBWAIT)
-
Receive completion notification to be sent to the host on the sending side
- Receive Completion (T):
-
Notify after completion of the Receive processing.
- Successful Job Completion (J):
-
Notify upon completion of the successful job (job to be executed in normal situation) after the Receive processing.
Omitting this field sets 'Receive Completion' (T).
- Transfer Group ID (GRPID)
-
Transfer Group ID of the Receive file
For details on the Transfer Group ID, refer to Transfer Group Information.
- Verify Data (DATAVERIFY)
-
Specify whether to verify the data of the file to be received.
- No (0):
-
Do not verify data
- Yes (1):
-
Verify data
Omitting this field sets 'No' (0).
- Mail Interface ID (MAILID)
-
Mail Interface ID when the email is issued after files are received
When you omit this field, HULFT does not interface with email.
- Cipher Key (PASSWORD) (when Forced Strong Key mode is disabled)
-
Key that HULFT uses when decrypting the data
Specify this field to decode encrypted data.
Specify the same key as the Cipher Key that is specified in the Send Management Information of the remote host. If the cipher keys differ, data is not decrypted correctly.
The setting of the Cipher Key on the host on the receiving side is ignored when the field is not specified in the Send Management Information of the host on the sending side, even if this field is specified on the host on the receiving side.
- Cipher Key (PASSWORD) (when Forced Strong Key mode is enabled)
-
Key that HULFT uses when decrypting the data
Specify this field to decode encrypted data.
Specify the same key as the Cipher Key that is specified in the Send Management Information of 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.
Points to be noted when setting
File ID
You cannot specify "_INSTANT_TRANSFER_" for File ID (RCVFILE).
Specification of Registration Mode, Receive Mode, and Generational Management
The combinations that can be specified in the Receive Management Information are as follows:
|
Registration Mode |
Error Handling |
Receive Mode |
|||
|---|---|---|---|---|---|
|
Single Receive |
Multiple Receive |
||||
|
Generational Management |
Generational Management |
Generational Management |
Generational Management |
||
|
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 |
Error Handling
-
Point to be noted when specifying 'Delete' (D)
-
When 'New Creation' (N) is selected for Registration Mode, if an error occurs because the Receive file already exists, the existing file is not deleted.
-
If "Unrecoverable Mode" (1) is specified for Transfer-Related File Deletion Mode (trnsfr_file_del) in the System Environment Settings, and you need to delete the receive data during the processing, you cannot recover the deleted data.
-
-
Points to be noted when specifying 'Keep' (K)
When 'Multiple' (M) is selected for Receive Mode, if an error occurs during the receiving of data in a temp file, the data received up to the point when the error occurred is not written to the Receive file. However, if there is an error while copying the temp file into the Receive file, the received data up to that point is added. Therefore there should be a function embedded in your application program to check duplicate data.
-
Points to be noted when specifying "R" (Restore)
If "Unrecoverable Mode" (1) is specified for Transfer-Related File Deletion Mode (trnsfr_file_del) in the System Environment Settings, you cannot recover a receive file that is deleted when a transfer fails. In addition, you cannot recover a backup file that is deleted when a transfer completes successfully.
Receive Mode
-
Point to be noted when specifying 'Multiple Receive' (M)
-
You must be careful when carrying out the operation, because during the Receive processing, the data is stored in a temporary file and is copied to the Receive file after the Receive processing is complete.
-
If "Unrecoverable Mode" (1) is specified for Transfer-Related File Deletion Mode (trnsfr_file_del) in the System Environment Settings, and you need to delete data that is received during the processing, you cannot recover the deleted data.
-
Generational Management
If "Unrecoverable Mode" (1) is specified for Transfer-Related File Deletion Mode (trnsfr_file_del) in the System Environment Settings, and you need to delete data that is received during the processing, you cannot recover the deleted data.
Notification
When 'Successful Job Completion' (J) is specified for Notification (JOBWAIT), a time-out may occur on the remote host, because the remote host does not receive the completion notification until the Post-receive Job ends. Be sure to take this into account when you set the time-out period.
Replacement Message
You can replace variables with messages in the fields that are listed below.
If you use the environment variables from $MSG0 to $MSG5 and from $MSGL0 to $MSGL1 inside the fields below, the variables are replaced with messages when the sending is carried out. The messages may be assigned by the Send File command on the sending side or by the Send Request command on the receiving side.
-
Receive File Name
-
Transfer Group ID
-
Successful Job ID
-
Mail Interface 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 remote host.
For points to be noted on message transmission, refer to the following:
HULFT10 for Windows Administration Manual : Message transmission
Receive File Name
-
When specifying any of the following, specify 'Single Receive' (S) as Receive Mode:
-
'$SNDFILE'
-
'$MSG0' to '$MSG5'
-
'$MSGL0' to '$MSGL1'
-
-
If specifying '$SNDFILE' or '$SNDPATH' causes the size of the Receive file name to exceed the size that can be specified in the management information, an error occurs before receiving.
-
You cannot specify any character after '$SNDFILE.'
-
If you specify '$SNDFILE,' the Send file name on the host on the sending side is set as the Receive file name.
-
When the host on the sending side is HULFT for Windows, if you specify '$SNDPATH,' the path name of the host on the sending side is set as the path name of the Receive file.
-
When the host on the sending side is not HULFT for Windows, replacement of '$SNDPATH' will not be carried out.
-
When you replace the Receive file name, the transfer may fail because the Receive file name may not be replaced correctly with the Send file name on the host on the sending side, depending on the language settings on the remote host.
For details, refer to the following:
HULFT10 for Windows Administration Manual : Send and Receive
-
When using '$SNDPATH,' also specify '$SNDFILE' at the same time. You cannot specify only '$SNDPATH.'
-
When the Send file name is set to the Receive file name, follow the naming conventions as shown below.
Table 2.5 File Naming Conventions
Host Type
Receive File Name (Windows)
Send File Name
$SNDPATH$SNDFILE
$SNDFILE
c:\usr\$SNDFILE
Mainframe
Sequential Organization file
HULFT.DAT.SND.F01
HULFT.DAT.SND.F01
HULFT.DAT.SND.F01
c:\usr\HULFT.DAT.SND.F01
Partitioned Organization file
HULFT.DAT.F02(SND)
HULFT.DAT.SND.F02
HULFT.DAT.SND.F02
c:\usr\HULFT.DAT.SND.F02
UNIX or Linux
/hulft/dat/snd.f03
snd.f03
snd.f03
c:\usr\snd.f03
Windows
c:\hulft\dat\snd.f04
c:\hulft\dat\snd.f04
snd.f04
c:\usr\snd.f04
IBMi
hulft/f05(snd)
snd.f05
snd.f05
c:\usr\snd.f05
Setting up the EBCDIC Set when HULFT receives Chinese language data from a Type MF-IBMi host
Specify 'Simplified Chinese Extended' (I) for EBCDIC Set (CODESET).
Make sure that 'GB18030' (G) or 'UTF-8' (8) is specified for Code Set for Transfer (cs4trnsfr) in the System Environment Settings.
Behavior of the operation when "Autoconfiguration" is specified for EBCDIC Set
When you specify "Autoconfiguration" (0) for EBCDIC Set (CODESET), the setting value for the EBCDIC Set that is actually used in the single byte code conversion during file transfer is determined as follows.
|
Code Set for |
Code Set for Transfer of Remote Host |
||||||
|---|---|---|---|---|---|---|---|
|
UTF-8 |
SHIFT-JIS |
EUC-JP |
GB18030 |
IBM Kanji |
JEF |
IBM |
|
|
SHIFT-JIS |
- |
- |
- |
|
F |
A |
- |
|
UTF-8 |
- |
- |
- |
- |
F |
A |
I |
|
GB18030 |
- |
|
|
- |
|
|
I |
|
- |
: |
The setting value of the EBCDIC Set is not used in code conversion during file transfer. |
|
Blank |
: |
For these combinations, code conversion cannot be executed during file transfer. |
|
A |
: |
EBCDIC Katakana |
|
F |
: |
Japan (Latin) Extended for IBM |
|
I |
: |
Simplified Chinese Extended |
For details on Code Set for Transfer (cs4trnsfr) with which the code set of the local host is registered in the System Environment Settings, refer to the following:
HULFT10 for Windows Administration Manual : Code Conversion
For details on Code Set for Transfer (KCODETYPE) with which the code set of the remote host is registered, refer to Host Information.