List of Send Management Information fields
You can register file information of files that you send. For the registration method, refer to Using the Send Management Information.
Field List
Field Name |
Default Value |
Setting Value |
Optional |
Remarks |
|
---|---|---|---|---|---|
|
Alphanumeric characters and "_" |
- |
Within 50 bytes starting with an alphabetic character |
||
|
Characters |
✓ |
Within 60 bytes (*1) |
||
Basic Settings |
|||||
|
|
Alphanumeric characters |
- |
3–33 bytes |
|
|
(*2) |
- |
|
||
|
Alphanumeric characters and "_" |
✓ |
Within 50 bytes starting with an alphabetic character |
||
None |
(*2) |
- |
|
||
Default |
(*2) |
- |
|
||
Sending Side |
(*2) |
- |
|
||
Autoconfiguration |
(*2) |
- |
|
||
Keep |
(*2) |
- |
|
||
|
Alphanumeric characters and "_" |
- |
Within 50 bytes starting with an alphabetic character |
||
|
Alphanumeric characters and "_" |
✓ |
Within 50 bytes starting with an alphabetic character |
||
|
Alphanumeric characters and "_" |
✓ |
Within 50 bytes starting with an alphabetic character |
||
|
Alphanumeric characters and "_" |
✓ |
Within 50 bytes starting with an alphabetic character |
||
Extension Settings |
|||||
|
|
(*2) |
✓ |
Only the string 'CSV' (*3) |
|
0 |
0–32767 |
- |
Unit: milliseconds |
||
50 |
1–256 |
- |
|
||
0 |
0, 128–65520 |
- |
|
||
0 |
0, 1–99 |
- |
|
||
Cut |
(*2) |
- |
|
||
No Cut-off |
(*2) |
- |
|
||
|
Alphanumeric characters |
✓ |
8–20 bytes |
||
Hexadecimal character string |
- |
64 digits |
✓ |
: |
Optional |
- |
: |
Mandatory |
*1 |
: |
On the HULFT Manager Management Console, you can enter a string of up to 60 characters. When the destination host is HULFT Ver.8.1 or higher, the size of the string that you entered will be checked based on the code set that is set in HULFT at the connection destination. When HULFT checks and confirms that the size of the string meets the condition that is given in the remarks, the characters that you entered will be saved in HULFT. |
*2 |
: |
For the HULFT Manager Management Console, click a setting value on the pulldown list. |
*3 |
: |
Available only when Transfer Type is set to 'FORMAT' or 'MULTIFORMAT.' |
*4 |
: |
This type of cipher key can be set in either of the following cases:
|
*5 |
: |
This type of cipher key must be set in either of the following cases:
|
Explanation of each field
This section explains the fields to be specified in the Send Management Information.
- File ID
-
ID that identifies the Send file
You cannot specify "_INSTANT_TRANSFER_" for the file ID, because this is the ID for instant transfer.
- Comment
-
Comment for the file to send
Basic Settings
- File Name
-
Specify a file to send (called Send file, or send target file) that is stored on an IBM i
For a physical data file, specify the name in the format of 'library name/file name(member name).'
For an archive file, specify the name in the format of 'library name/file name.'
You cannot use reserved words such as '*FIRST' or '*FILE' and so forth for the name of Send file. Specification of the file name with the reserved words may result in unexpected behavior of HULFT.
- Transfer Type
-
Data type of the file to send
- FORMAT:
-
Format data
- BINARY:
-
Binary data
- TEXT:
-
Text data
- MULTIFORMAT:
-
Multi Format data
- Format/Multi Format ID
-
ID where the format or multi format of the Send file is registered
For details on format IDs, refer to List of Format Information fields.
For details on multi format IDs, refer to List of Multi Format Information fields.
Format ID is mandatory when 'FORMAT' is specified for Transfer Type. Multi format ID is mandatory when 'MULTIFORMAT' is specified for Transfer Type.
- Compression Preference
-
Compression type that is used when a file is transferred
- None:
-
None
- Horizontal:
-
Compression within records
- Vertical:
-
Compression across records
- DEFLATE:
-
DEFLATE
- DEFLATE Level
-
Specify the level when 'DEFLATE' is set for Compression Preference
-
Compression Speed
-
Default
-
Compression Ratio
-
- Code Conversion
-
Specify the option for code conversion of the send target file
- Sending Side:
-
Sending side
- Receiving Side:
-
Receiving side
- No Conversion:
-
No conversion
- EBCDIC Set
-
Specify Type-EBCDIC Code Set that is used for the conversion of single-byte codes
When Type-EBCDIC Code Set is set for Code Set for Transfer on the destination host, specify the EBCDIC set of the destination host (sending-side host).
When UTF-8 is set for Code Set for Transfer on the destination host, specify the EBCDIC set of the receiving-side host.
-
Autoconfiguration
-
Katakana
-
Lower Case
-
ASCII
-
ASPEN
-
Japan (Latin) for IBM
-
Japan (Latin) Extended for IBM
-
NEC Katakana
-
Japan (Katakana) Extended for IBM
-
Simplified Chinese Extended
-
User Table 1
-
User Table 2
-
User Table 3
Omitting this field sets 'Autoconfiguration.'
-
- Send File Mode
-
Specify the mode for exclusive control of the Send file applied during the sending, and the handling of the file in the case where the sending ends successfully.
- Keep:
-
Do not lock the file while sending is in progress and save the file after sending ends successfully
- Clear:
-
Lock the file while sending is in progress and clear the file to 0 byte after the sending ends successfully
- Delete:
-
Lock the file while sending is in progress and delete the file after the sending ends successfully
- Lock:
-
Lock the file while sending is in progress and save the file after the sending ends successfully
- Transfer Group ID
-
ID of the record in which the send destinations of the Send file are registered
For details on transfer group IDs, refer to List of Transfer Group Information fields.
- Pre-send Job ID
-
ID of the job to be executed before the Send processing starts
For details on job IDs, refer to List of Job Information fields.
When this field is omitted, the job is not started.
- Successful Job ID
-
ID of the job to be started when the Send processing 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 Send processing 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
- Interface DBID
-
This is the interface at the receiving host of the sent data
- CSV:
-
Convert the Receive file into CSV format on the host on the receiving side
When the Receive file is converted and received on the host on the receiving side (for UNIX, Linux, NonStop, or Windows) in CSV format, specify 'CSV.'
When you omit this field, files will not be received in CSV format.
When you use the Interface function, specify 'FORMAT' or 'MULTIFORMAT' for Transfer Type.
- Transfer Interval
-
Interval per transfer unit (Transfer Block Length x Transfer Block Count)
Omitting this field sets '0.'
- Transfer Priority
-
Priority in queue when starting the file transfer
A smaller number means a higher priority.
- Transfer Block Length
-
Length of data used to transfer one block
The product of the values for Transfer Block Length and Transfer Block Count cannot exceed 65520.
- Transfer Block Count
-
Number of blocks per transfer
The product of the values for Transfer Block Length and Transfer Block Count cannot exceed 65520.
- Shiftcode Mode
-
Shift code mode at the time of code conversion to a Type Win-UX host
- Cut:
-
Convert to the shortened data by removing shift codes
- Space:
-
Convert shift codes into space codes
When 'UTF-8' is specified for Code Set for Transfer (CS4TRNSFR) in the System Environment Settings on the destination host, one of the following settings is displayed:
- Add:
-
Add shift codes
- Do not add:
-
Do not add shift codes
- Subsequent Character
-
Mode of handling subsequent characters
- No Cut-off:
-
Do not remove trailing spaces
- Cut Off Spaces:
-
Remove trailing spaces
- Cipher Key (when Forced Strong Key mode is disabled)
-
Key used when data is encrypted in an encryption algorithm
You can apply security to the file to be sent. Specify the same cipher key as is specified in the Receive Management Information on the remote host.
If this field is omitted, the file is not encrypted.
- Cipher Key (when Forced Strong Key mode is enabled)
-
Key used when data is encrypted in an encryption algorithm
You can apply security to the file to be sent. Specify the same cipher key as is specified in the Receive Management Information on the remote host.
Points to be noted when configuring settings
Compression Preference
In the following cases, even if 'DEFLATE' is specified for Compression Preference, the file is transferred without being compressed:
-
When HULFT on the receiving host is lower than Ver.8
-
When Use HULFT7 Comm. Mode in the Host Information List is set to 'Enabled'
DEFLATE Level
This field cannot be specified if one of the following values for Compression Preference is selected:
-
None
-
Horizontal
-
Vertical
Code Conversion
-
When the receiving-side host runs a version of HULFT for Mainframe that is lower than Ver.8.4 and "8" (UTF-8) is specified for Code Set for Transfer in the System Environment Settings on the receiving-side host, you cannot specify "Receiving Side".
-
When both the sending-side host and the receiving-side host are Ver.8.4 or higher, code conversion may switch to the receiving-side even if you specify "Sending Side" for Code Conversion, or code conversion may switch to the sending-side even if you specify "Receiving Side" for Code Conversion. For details, refer to the explanation about the sending-side conversion and the receiving-side conversion in Code Conversion Manual.
Send File Mode
To carry out multicasting, set Send File Mode to 'Keep.'
Where the Send file is a physical data file, HULFT carries out 'Clear' or 'Delete' against the member of the physical data file, when you specify 'Clear' or 'Delete' for Send File Mode.
Transfer Block Length and Transfer Block Count
If you specify '0' for both Transfer Block Length and Transfer Block Count, HULFT automatically optimizes the size of the transfer unit (Transfer Block Length x Transfer Block Count).
However, if you specify '0' for only one of either Transfer Block Length or Transfer Block Count, an error occurs.
For details, refer to IBMi Administration Manual.
Replacement Message
-
You can replace variables with messages in the fields that are listed below.
Specify '&MSG0' to '&MSG5' or '&MSGL0' to '&MSGL1' in the following fields to replace the variables with messages that you specify when you issue the Send File or when you issue the Send Request on the host on the receiving side:
-
Send File Name
-
Transfer Group ID
-
Pre-send Job ID
-
Successful Job ID
-
Format ID
-
Multi Format ID
-
-
The message is converted with the type of the code set that is specified for HULFT Character Set (HULCHARSET) in the System Environment Settings.
-
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 receiving side.
For points to be noted on message transmission, refer to IBMi Administration Manual.
When HULFT sends Chinese language data to a Type MF-IBMi host
Specify 'Simplified Chinese Extended' for EBCDIC Set.
Check that 'C' (IBM Simplified Chinese) 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" for EBCDIC Set, 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 Transfer (KCODETYPE) for Host on Sending Side |
Code Set for Transfer (KCODETYPE) for Host on Receiving Side |
|||||
---|---|---|---|---|---|---|
SHIFT-JIS |
EUC-JP |
GB18030 |
IBM Kanji |
JEF |
IBM |
|
IBM Kanji |
F |
F |
|
F |
F |
|
IBM Simplified Chinese |
|
|
I |
|
|
I |
Blank |
: |
For these combinations, code conversion cannot be executed during file transfer. |
F |
: |
Japan (Latin) Extended for IBM |
I |
: |
Simplified Chinese Extended |
For details on Code Set for Transfer (CS4TRNSFR) in which the code set of the destination host is registered in the System Environment Settings, refer to IBMi Administration Manual.
For details on Code Set for Transfer (KCODETYPE) in which the code set of the host on the receiving side is registered, refer to List of Host Information fields.
Comment
Even if full-width characters that are registered in Comment can be displayed on the HULFT Manager Management Console, the characters may not be displayed correctly on the HULFT Management Console for HULFT10 for IBMi.