Instant transfer
This section explains the instant transfer function.
-
The instant transfer function can be used only when both sending-side and receiving-side hosts run HULFT Ver.8.4 or higher.
-
Instant transfer cannot be used in Forced Strong Key mode.
(1) What is instant transfer?
Instant transfer is the function that allows you to send a file only by specifying the names of the target file and the receiving-side host without using pre-registered management information.
In instant transfer, if a port number different from the default value is set on the receiving-side host, the port number needs to be explicitly specified when starting the transferring because the number is not acquired from the Host Information
For details on how to perform an instant transfer, refer to Operation Manual.
To perform an instant transfer, the following needs to be performed in advance on the receiving-side host:
-
Specify the request acceptance setting for instant transfer in the Host Information (if the sending-side host is registered) or in the System Environment Settings (if not registered).
-
Specify, in a file, names of libraries under which instant transfer requests are accepted.
For details, refer to the description in the following sections.
(2) Functionality available in instant transfer
With instant transfer, the operation of transferring a file is very simple because it does not use management information settings. As a compromise, it requires some restrictions on the functionality. The table below describes the points to note about which part of the functionality is limited in instant transfer.
Functionality |
Can be used in instant transfer |
---|---|
Resend |
|
Auto Resend |
✔ |
Synchronous Transfer and Asynchronous Transfer |
✔ |
Multicasting |
|
Transfer with Compression |
✔ (*1) |
Generational Management |
|
Code Conversion |
✔ (*2) |
Message Transmission |
|
Job Startup |
|
Data Verification |
✔ (*3) |
Transfer Group Check |
|
Operation Log Output |
✔ |
Encryption |
✔ (*4) |
✔ |
: |
Available |
Blank |
: |
Not available |
*1 |
: |
HULFT behaves the same as when DEFLATE compression is selected. |
*2 |
: |
For details, refer to (8) Code Conversion. |
*3 |
: |
In instant transfer, data verification is always performed. |
*4 |
: |
In instant transfer, the cipher key is generated automatically. |
(3) How to execute instant transfer
To perform an instant transfer, execute the Instant Transfer Send File Issuance command on the sending-side host.
For details on the Instant Transfer Send File Issuance command, refer to Operation Manual.
(4) Behavior when sending-side transferring is performed
In sending-side transferring for instant transfer, because HULFT does not reference to management information, it always operates with the same settings.
Except for those parameters modified when issuing the Instant Transfer Send File request, the behavior of an instant transfer is the same as that obtained when the following values are specified in the Send Management Information and the Host Information:
For details on the Send Management Information and the Host Information, refer to Operation Manual.
Field Name |
Valid Values |
---|---|
File ID |
_INSTANT_TRANSFER_ |
Send File Name |
Specify by the parameter. |
Transfer Type |
Specify by the parameter (*1). |
Multi/Format ID |
(Optional) |
Compression Preference |
DEFLATE |
DEFLATE Level |
Default |
Code Conversion |
(*2) |
EBCDIC Set |
(*2) |
Send File Mode |
Keep |
Transfer Group ID |
(Optional) |
Pre-send Job ID |
(Optional) |
Successful Job ID |
(Optional) |
Unsuccessful Job ID |
(Optional) |
Interface DBID |
(Optional) |
Transfer Interval |
0 |
Transfer Priority |
Specify by the parameter. |
Transfer Block Length |
0 |
Transfer Block Count |
0 |
Shiftcode Mode |
(*3) |
Subsequent Character |
No Cut-Off |
Cipher Key |
Auto generation |
*1 |
: |
Note that only text transfer or binary transfer can be specified. |
*2 |
: |
For details, refer to (8) Code Conversion. |
*3 |
: |
Choose "Cut-Off" when Code Set for Transfer is set to "IBM Kanji" or "IBM Simplified Chinese", and "Add" when it is set to "UTF-8". |
Field Name |
Valid Values |
---|---|
Host Type |
Host type on the receiving side |
Code Set for Transfer |
(*1) |
Standard for Japanese |
83JIS |
Receive Port No. |
Specify by the parameter. |
Observe Port No. |
(*2) |
Send Process Multiplex Level by Host |
(Optional) |
HULFT7 Communication Mode |
Disabled |
Proxy Server Name |
(Optional) |
Proxy Port No. |
(Optional) |
Allow Send Request/Resend Request |
(*2) |
Allow to View Post-receive Job Result |
(*2) |
Allow to Notify Job Result |
(*2) |
Allow to Execute Remote Job |
(*2) |
Allow Instant Transfer |
(*2) |
Notify User Details |
No |
*1 |
: |
For details, refer to (8) Code Conversion. |
*2 |
: |
The field is not related to sending-side transferring. |
(5) Behavior when receiving-side transferring is performed
In receiving-side transferring for instant transfer, because HULFT does not reference to management information, it always operates with the same settings.
Except for those parameters modified when issuing the Instant Transfer Send File request, the behavior of an instant transfer is the same as that obtained when the following values are specified in the Send Management Information and the Host Information:
For details on the Receive Management Information and the Host Information, refer to Operation Manual.
Field Name |
Valid Values |
---|---|
File ID |
_INSTANT_TRANSFER_ |
Receive file name |
(*1) |
Record Length |
(*1) |
Registration Mode |
Replace |
Error Handling |
Keep |
Receive Mode |
Single Receive |
Generational Management |
No |
No. of Generations |
0 |
EBCDIC Set |
(*2) |
Successful Job ID |
(Optional) |
Unsuccessful Job ID |
(Optional) |
Receive Completion Notification |
Receiving File Completion |
Transfer Group ID |
(Optional) |
Verify Data |
Yes |
Cipher Key |
Auto generation |
*1 |
: |
For details, refer to (6) Receive file. |
*2 |
: |
For details, refer to (8) Code Conversion. |
Field Name |
Valid Values |
---|---|
Host Type |
Host type on the sending side |
Code Set for Transfer |
(*1) |
Standard for Japanese |
83JIS |
Receive Port No. |
(*2) |
Observe Port No. |
(*2) |
Send Process Multiplex Level by Host |
(*2) |
HULFT7 Communication Mode |
(*2) |
Proxy Server Name |
(*2) |
Proxy Port No. |
(*2) |
Allow Send Request/Resend Request |
(*2) |
Allow to View Post-receive Job Result |
(*2) |
Allow to Notify Job Result |
(*2) |
Allow to Execute Remote Job |
(*2) |
Allow Instant Transfer |
(*3) |
Notify User Details |
(*2) |
*1 |
: |
For details, refer to (8) Code Conversion. |
*2 |
: |
The field is not related to receiving-side transferring. |
*3 |
: |
If a record is registered for the host in the Host Information, the value depends on the setting. If no record is registered for the host in the Host Information, the value depends on Allow Instant Transfer from Unregistered Host specified in the System Environment Settings. |
In instant transfer, you can specify information about the receive file in the System Environment Settings or as parameters specified when the Instant Transfer Send File request is issued.
For details on parameters specified when issuing the Instant Transfer Send File request, refer to Operation Manual.
If the receive file name and the save destination for the receive file are specified or omitted on the sending-side host, the behavior is the same as that obtained when the following value is specified for Receive File Name in the Receive Management Information in each case:
Save destination for the receive file |
Receive file name |
File Name in the Receive Management Information (FILENAME) |
---|---|---|
Specified |
Specified |
Save destination for receive file/Receive File Name |
Omitted |
Save destination for receive file/&SNDFILE |
|
Omitted |
Specified |
Default library (*1)/Receive File Name |
Omitted |
Default library (*1)/&SNDFILE |
*1 |
: |
The default library is specified in the instant transfer receive libraries file. |
The receiving-side transferring is performed only when the receive library for the receive file matches one of the library names registered in the instant transfer receive libraries file.
For details on the instant transfer receive libraries file, refer to (7) Specifying library names under which file can be received.
Record length of the receive file
When an existing file is targeted for receiving-side transferring, the record length of the file is used.
When a new file is created as the receive file, the value for Instant Transfer Receive File Record Size (INSTTRANSRCDLEN) in the System Environment Settings is used.
For details on the field, refer to Instant Transfer Settings.
When it is specified that a new receive file is created, the same record length is always used no matter what the content of the send file is. We recommend you to create the receive file that corresponds and is consistent with the send file in advance.
(7) Specifying library names under which file can be received
In instant transfer, because both the save destination and the name of the receive file can be specified, the following possibilities exist.
-
Important files might be overwritten on the receiving-side host.
-
The specified save destination or name of the receive file might deviate from operational rules used in the business.
To avoid such a situation when you perform instant transfer, specify lists of library names under which files can be received on the receiving-side host in advance.
The request for receiving-side transferring is accepted only when the save destination for the receive file specified on the sending-side host matches one of the library names registered in the list stored in the libraries file.
The library names under which files can be received in instant transfer is defined in a file called "instant transfer receive libraries file".
The default library used when the save destination for the receive file is omitted on the sending-side host is also specified in the instant transfer receive libraries file.
If the instant transfer receive libraries file does not exist or reading the file fails, requests for receiving-side transferring in instant transfer are rejected.
Specifying the instant transfer receive libraries file
File Name
The name of the instant transfer receive libraries file is "INSTALWLIB". The file name cannot be changed.
The instant transfer receive libraries file must be placed in the library where HULFT is installed.
Syntax of the file
The syntax of the instant transfer receive libraries file is as follows:
*
* INSTANT TRANSFER ALLOW LIBRARY
*
* DEFAULT LIBRARY
DEFAULTLIB=default library name
* ALLOW LIBRARY
_LIST_START_
library name1 library name2
:
_LIST_END_
- Comment
-
If the first character of a line is an asterisk (*), the line is considered as a comment.
- Default library name
-
Specify the name of the default library after "DEFAULTLIB=".
If the save destination for the receive file is omitted on the sending-side host, the receive file is stored in the default library.
Specify a library name which is already created. If the save destination for the receive file is omitted on the sending-side host, a file transfer error occurs when the library with the name does not exist at the time when the request for receiving-side transferring is received.
If more than one "DEFAULTLIB=" lines are specified in the file, only the first line is applied and the rest of the lines are ignored.
The default value is "QGPL".
Even if the default library name is omitted, the Receive Acknowledge job starts successfully. However, in such a case, requests for instant transfer is rejected when the save destination for the receive file is omitted on the sending-side host.
- Library name
-
List librarys under which files are allowed to be received. Specify one name per record from "_LIST_START_" to "_LIST_END_" in the file. Up to 1000 library names, including the default library name, can be specified in the file.
Placing an asterisk (*) at the beginning or end of the record matches library names ending or beginning with the character string, respectively. Placing only an asterisk (*) in a record matches any arbitrary library name.
The request for instant transfer is accepted only when the save destination for the receive file specified on the sending-side host matches one of the library names registered in the libraries file. The request for instant transfer is rejected when any library name in the file matches the save destination for the receive file.
Even if no library name is specified, the Receive Acknowledge job starts successfully. However, in such a case, requests for instant transfer are rejected when the save destination for the receive file is specified on the sending-side host.
-
Lines between "_LIST_START_" and "_LIST_END_" in the file are not considered as comment lines even when they begin with "*". An asterisk at the beginning of a line is considered as a wildcard character for a match from the end of the string or an arbitrary search.
-
Library names of 11 bytes or longer are ignored.
-
Any record that violates the above syntax is ignored.
Description example
*
* INSTANT TRANSFER ALLOW LIBRARY
*
* DEFAULT LIBRARY
DEFAULTLIB=INSTTRANS
* ALLOW LIBRARY
_LIST_START_
ABC
DEF*
*OPQ
_LIST_END_
If the content of the file is as above, HULFT behaves as follows:
-
If the save destination for the receive file is omitted on the sending-side host, the receive file is stored in the INSTTRANS library.
-
The request for instant transfer is accepted when "ABC", "DEF001", or "LMNOPQ" is specified as the save destination for the receive file name on the sending-side host.
-
The request for instant transfer is rejected when "ABCD" or "ZZZ" is specified as the save destination for the receive file name on the sending-side host.
-
The request for instant transfer is accepted when "123OPQ" is specified as the save destination for the receive file name on the sending-side host, because it matches the record of "*QPQ". However, because "123OPQ" is an invalid library name, a transfer error occurs.
In instant transfer, information about code conversion is specified in the following fields in the System Environment Settings.
Code Set for Transfer (CS4TRNSFR)
In the same way as in regular transfer using management information, you can specify a code set that you want to use on the local host.
Instant Transfer EBCDIC Set (INSTTRANSEBCDIC)
Specify an EBCDIC set used in instant transfer on the local host.
If Code Set for Transfer is set to "UTF-8" on the local host, this value is not used.
Instant Transfer Code Conv Side (INSTTRANSCODCNV)
Specify whether code conversion in instant transfer is performed on the sending side or on the receiving side.
The value notified by the destination host is used as information about the code set specified on the destination host.
For notes on code conversion and details on how it behaves, refer to Code Conversion Manual.
(9) Observe Setting function in instant transfer
In instant transfer, you can attempt to send a file only by specifying the host name and the port number of the receiving-side host.
On the other hand, you can enable the receiving-side host to refuse to receive unexpected files on the receiving-side host.
By default, all requests for instant transfer are rejected regardless of whether or not the sending-side host is registered in the Host Information.
When the sending-side host is registered in the Host Information
To specify whether to accept instant transfer requests by host, specify Allow Instant Transfer (ALLOWINSTTRANS) in the Host Information.
Refer to Operation Manual for details about the Host Information.
Only Allow Instant Transfer is referenced even when the sending-side host is registered in the Host Information.
No other fields are referenced.
When the sending host is not registered in the Host Information
To specify whether to accept instant transfer requests from all unregistered hosts at once, specify Allow Instant Transfer from Unregistered Host (ALLOWINSTTRANS) in the System Environment Settings.
For details on Allow Instant Transfer from Unregistered Host, refer to Security Settings.
(10) Points to be noted on instant transfer
The following are the points to be noted when using instant transfer:
-
For file transfers executed by issuing Instant Transfer Send File, HULFT automatically assign the file ID "_INSTANT_TRANSFER_".
You can execute neither of the following by specifying this file ID:-
Issuing Send File
-
Issuing Resend File
-
Issuing Send Request
-
Issuing Resend Request
-
Registering records to the Send Management Information
-
Registering records to the Receive Management Information
On the other hand, for transfer status or log for which the file ID "_INSTANT_TRANSFER_" is assigned, you can perform any of the following operations in the same way as in regular transfer:
-
Inquiring and deleting records from the Send Log
-
Inquiring and deleting records from the Receive Log
-
Canceling sending-side transferring instances
-
Canceling receiving-side transferring instances
-
Modifying the Unsent Status Queue
-
-
Even when Dynamic Parameter Specification (DYNPARAM) is set to "0" (Cannot change dynamically) in the System Environment Settings, the send file name and the receiving-side host name can be specified as parameters for the Instant Transfer Send File Issuance command.
-
For details on errors from the Instant Transfer Send File Issuance command, and status codes and detail codes in the transfer status or log of instant transfers, refer to Error Codes and Messages.
-
The level of security differs as follows between regular transfer, which uses management information, and instant transfer:
Table 2.11 Security on the sending-side host
Regular transfer using management information
Instant transfer
File ID
Sending-side transferring is performed only when the same ID is registered on the receiving-side host
Sending-side transferring is performed regardless of whether the ID is registered in the Send Management Information
Host name
Sending-side transferring is performed only when the destination host is registered in the Host Information
Sending-side transferring is performed against any arbitrary destination host
Multiplicity by host
The value set in the Host Information is applied and multiple sending-side transferring instances can run up to the multiplicity of the value
No limit on multiplicity of transferring instances can be set
Multiplicity in the entire system
The value set in the System Environment Settings is applied and multiple sending-side transferring instances can run up to the multiplicity of the value
The value set in the System Environment Settings is applied and multiple sending-side transferring instances can run up to the multiplicity of the value
Table 2.12 Security on the receiving-side host
Regular transfer using management information
Instant transfer
File ID
Receiving-side transferring is performed only when the same ID is registered on the sending-side host
Receiving-side transferring is performed regardless of whether the ID is registered in the Send Management Information
Host name
Receiving-side transferring is performed only when the sending-side host is registered in the Host Information
Receiving-side transferring is performed only when the sending-side host is allowed to send files in the Host Information (or against any arbitrary host if set so) (*1)
Save destination for the receive file
Receive files can be stored only in the file name specified in the Receive Management Information
Receive files can be stored only to libraries specified in the instant transfer receive libraries file
Receive file name
Receiving-side transferring is performed in any arbitrary destination file name
Multiplicity in the entire system
The value set in the System Environment Settings is applied and multiple sending-side transferring instances can run up to the multiplicity of the value
The value set in the System Environment Settings is applied and multiple sending-side transferring instances can run up to the multiplicity of the value
*1
:
By default, an arbitrary host is not allowed.
When you use the instant transfer function, please take note of the above and specify appropriate settings in the Host Information and in the instant transfer receive libraries file.