Instant transfer

This section describes instant transfer.

Note

  • You can use instant transfer only when the versions of HULFT on the sending-side host and the receiving-side host are both Ver.8.4 or higher.

  • When Forced Strong Key mode is enabled, instant transfer cannot be performed.

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 entries.

Figure 2.28 Outline of instant transfer

= Remarks =

Because HULFT does not obtain the port number of the receiving-side host from the Host Information, if the port number that is set for the receiving-side host is different from the default port number, you must also specify the port number for instant transfer.

For details on how to execute instant transfer, refer to the following:

HULFT10 for zOS Operation Manual : Send File request for instant transfer

 

To perform an instant transfer, the following needs to be performed in advance on the receiving-side host:

  • Specify whether to accept requests for instant transfer in the Host Information (if the sending-side host is registered), or in the System Environment Settings (if not registered)

  • Specify the volume name which is allowed to accept instant transfer with a file and register the name of the file in the System Environment Settings

  • Specify the first modifier which is allowed to accept instant transfer with a file and register the name of the file in the System Environment Settings

For details, refer to the description in the following sections.

Available functions

Instant transfer is a simple transfer method that does not require management information. However, some functions cannot be used with instant transfer.

The following table provides important information about the availability of functions.

Table 2.8 Available functions for instant transfer

Function

Availability with instant transfer

Resending

Auto Resend

✓

Synchronous Transfer and Asynchronous Transfer

✓

Multicasting

Compressed Transfer

✓ (*1)

Generational Management

Code Conversion

✓ (*2)

Message Transmission

Job Start-up

Data Verification function

✓ (*3)

Transfer Group Check

Operation Log Output

✓

Encryption

✓ (*4)

✓

:

Available

Blank

:

Not available

*1

:

HULFT compresses files in the same way as the way it compresses files when you specify Vertical compression.

*2

:

For details, refer to Code conversion.

*3

:

HULFT always verifies data for instant transfer.

*4

:

In instant transfer, the cipher key is generated automatically.

Executing instant transfer

To execute instant transfer, the following methods are available on the sending-side host.

  • Instant Transfer Send File Issuance command

  • Instant Transfer Send File API

= Remarks =

Behavior of operations in sending-side transferring

For sending-side transferring of instant transfer, HULFT always uses the same settings without referring to the management information.

HULFT behaves in the same way as the way it behaves when the following values are set in the Send Management Information and the Host Information. Note that for some fields, HULFT uses the settings that you specify in the parameters when you issue a Send File request for instant transfer.

= Remarks =

Refer to the following for details on the Send Management Information and Host Information:

HULFT10 for zOS Operation Manual : Settings of management information

Table 2.9 Send Management Information

Field Name

Setting Value

File ID

_INSTANT_TRANSFER_

Mainframe DSN

Specified in a parameter

Volume Serial

(Omitted) (*1)

Transfer Mode

Direct

Work Volume Serial

(Omitted)

Capacity

(Omitted)

1ST Extent

(Omitted)

Secondary

(Omitted)

UNIT Quantity

(Omitted)

Transfer Type

Specified in a parameter (*2)

Multi/Format ID

(Omitted)

Compression Preference

Vertical

Code Conversion

(*3)

EBCDIC Set

(*3)

Send File Mode

Keep

Transfer Group ID

(Omitted)

Pre-send Job ID

(Omitted)

Successful Job ID

(Omitted)

Unsuccessful Job ID

(Omitted)

Interface DBID

(Omitted)

Transfer Interval

0

Transfer Priority

Specified in a parameter

Transfer Block Length

0

Transfer Block Count

0

Shiftcode Mode

Cut-Off

Subsequent Character

No Cut-off

UNIT

(Omitted)

Sequence Number

(Omitted)

Sending with RDW

No

Cipher Key

Generated automatically

*1

:

This field can be set only for cataloged files.

*2

:

You can specify only text transfer or binary transfer.

*3

:

For details, refer to Code conversion.

Table 2.10 Host Information

Field Name

Setting Value

Host Type

Host type of the receiving-side host

Code Set for Transfer

(*1)

Standard for Japanese

83JIS

Receive Port No.

Specified in a parameter

Observe Port No.

(*2)

Connection Type

LAN

Send Process Multiplex Level by Host

(Omitted)

Use HULFT7 Comm. Mode

No

Proxy Server Name

(Omitted)

Proxy Port No.

(Omitted)

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 Code conversion.

*2

:

These fields are not related to sending-side transferring.

Behavior of operations in receiving-side transferring

For receiving-side transferring of instant transfer, HULFT always uses the same settings without referring to the management information.

HULFT behaves in the same way as when the following values are set in the Receive Management Information and Host Information. Note that for some fields, HULFT uses the settings that you specify in the parameters of the Instant Transfer Send File Issuance command.

= Remarks =

Refer to the following for details on the Receive Management Information and Host Information:

HULFT10 for zOS Operation Manual : Settings of management information

Table 2.11 Receive Management Information

Field Name

Setting Value

File ID

_INSTANT_TRANSFER_

Mainframe DSN

(*1)

Volume Serial

(*1)

Catalog Operation

Catalog

Multivolume

Autoconfiguration

Handling of Inter-Mainframe Receiving

(*1)

Record Format

(*1)

Capacity

(*1)

1ST Extent

(*1)

Secondary

(*1)

Unused Area

(*1)

Record Length

(*1)

Block Size

(*1)

Registration Mode

Replace

Error Handling

Keep

Receive Mode

Single

EBCDIC Set

(*2)

Successful Job ID

(Omitted)

Unsuccessful Job ID

(Omitted)

Notification

Receive Completion

Transfer Group ID

(Omitted)

Verify Data

Yes

Storage Class

(Omitted)

Management Class

(Omitted)

Data Class

(Omitted)

UNIT

(*1)

Print Character

(*1)

Work Volume Serial

(Omitted)

Sequence Number

(Omitted)

Receiving with RDW

No

Cipher Key

Generated automatically

*1

:

Refer to Receive file.

*2

:

For details, refer to Code conversion.

Table 2.12 Host Information

Field Name

Setting Value

Host Type

Host type of the sending-side host

Code Set for Transfer

(*1)

Standard for Japanese

83JIS

Receive Port No.

(Not used)

Observe Port No.

(Not used)

Connection Type

(*2)

Send Process Multiplex Level by Host

(*2)

Use HULFT7 Comm. 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 Code conversion.

*2

:

These fields are not related to receiving-side transferring.

*3

:

If the relevant host is registered in the Host Information, HULFT uses the setting value of this field.

If the relevant host is not registered in the Host Information, HULFT uses the setting value of Allow Instant Transfer from Unregistered Host in the System Environment Settings.

Receive file

For instant transfer, the information related to the receive file can be specified in the System Environment Settings on the receiving-side host or specified for the parameters when a Send File request for instant transfer is issued on the sending-side host.

For details on the parameters to be set when you issue a Send File request for instant transfer, refer to the following:

HULFT10 for zOS Operation Manual : Send File request for instant transfer

Receive File Name

When the receive file name is specified on the sending-side host, HULFT behaves in the same way as the way it behaves when the receive file name is specified for Mainframe DSN (DSNAME) in the Receive Management Information.

When the receive file name is omitted on the sending-side host, HULFT behaves in the same way as the way it behaves when "&SNDFILE" is specified for Mainframe DSN (DSNAME) in the Receive Management Information.

Note

The receiving-side transferring can be performed only when the first modifier of the receive file matches one of the names registered in the instant transfer receive file naming file.

For details on the instant transfer receive file naming file, refer to Specifying receivable file names and volume names.

Save Destination of Receive File

To receive data in an existing file

When the save destination of the receive file is specified on the sending-side host, HULFT behaves in the same way as the way it behaves when the save destination is specified for Volume Serial (VOLUME) in the Receive Management Information.

When the save destination of the receive file is omitted on the sending-side host, HULFT behaves in the same way as the way it behaves when the specification of Volume Serial (VOLUME) in the Receive Management Information is omitted.

To receive data in a new file

The behavior is the same as when the fields in the Receive Management Information are set as in the table below.

Table 2.13 Behavior when receiving data in a new file

Fields in the Receive Management Information

Fields in the System Environment Settings

Volume Serial

Default volume name (*1)

Handling of Inter-Mainframe Receiving

Inter-MF Instant Transfer Receive Attribute Value Source (INSTTRANSMFRCVORG)
in the System Environment Settings

Capacity

Instant Transfer Receive File Capacity (INSTTRANSRCVSPACE)
in the System Environment Settings

1ST Extent

Secondary

Unused Area

Record Format

Instant Transfer Receive File DCB (INSTTRANSRCVDCB)
in the System Environment Settings

Print Character

Record Length

Block Size

UNIT

Instant Transfer Receive File Unit (INSTTRANSRCVUNIT)
in the System Environment Settings

*1

:

The default volume name is specified in the instant transfer receive volumes file.

For details on the instant transfer receive volumes file, refer to Specifying receivable file names and volume names.

 

For details on the fields in the System Environment Settings, refer to Explanation of each field.

= Remarks =

When creating a new receive file, the same file attributes are always used for the file regardless of the corresponding send file content. It is recommended that you create a receive file as appropriate for the send file in advance.

Note

The receiving-side transferring can be performed only when the receive volume of the receive file matches one of the volume names registered in the instant transfer receive volumes file.

For details on the instant transfer receive volumes file, refer to Specifying receivable file names and volume names.

Specifying receivable file names and volume names

In instant transfer, because both save destination and 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 file and volume names under which files can be received on the receiving-side host in advance.

The request for receiving-side transferring is accepted only when both name and save destination of the receive file specified on the receiving-side host match ones of file and volume names registered in the file naming and volumes files for instant transfer.

The names of files which can be received in instant transfer is defined in a file called "instant transfer receive file naming file". The file name used as the instant transfer receive file naming file is specified as Instant Transfer Receive File Naming File (INSTTRANSDSNLST) in the System Environment Settings.

The volume names under which files can be received in instant transfer is defined in a file called "instant transfer receive volumes file". The file name used as the instant transfer receive file naming file is specified as Instant Transfer Receive Volume File (INSTTRANSVOLLST) in the System Environment Settings.

The default volume used when the save destination for the receive file is omitted on the sending-side host is also specified in the instant transfer receive volumes file.

If either of Instant Transfer Receive File Naming File or Instant Transfer Receive Volumes File is omitted, requests of instant transfer are rejected.

 

For details on the System Environment Settings, refer to System Environment Settings.

Specifying Instant Transfer Receive File Naming File

File name

The name of the instant transfer receive file naming file can be any arbitrary file name. Set Instant Transfer Receive File Naming File (INSTTRANSDSNLST) to the file name in the System Environment Settings.

The instant transfer receive file naming file must be cataloged.

File format

The instant transfer receive file naming file can be either a sequential or partitioned file. Use the record format below.

Table 2.14 Record format of the instant transfer receive file naming file

Record format

Fixed length dataset

Record size

80 bytes

Syntax of the file

In the instant transfer receive file naming file, list first modifiers of the receivable files. Specify one modifier per record in the file.

First modifier 1 
First modifier 2 
    :

Place an asterisk (*) at the end to match names beginning with the first modifier.

The instant transfer can be performed only when the first modifier of the receive file name specified on the sending-side host (or the send file name if the receive file name is omitted) matches one of the names registered in the instant transfer receive file naming file. The request for instant transfer is rejected when any first modifier in the file matches the receive (or send) file name.

Alternatively, if "ALLOW-ALL" is specified in the file, any receive file name is allowed and the request for instant transfer is accepted.

Description example

SISCO 
SAISON 
HUL*

If the content of the file is as above, HULFT behaves as follows:

  • The request for instant transfer is accepted when "SISCO.DAT.SND01" or "HUL001.DAT(SND)" is specified as the receive file name on the sending-side host.

  • The request for instant transfer is rejected when "SISCO123.DAT.SND04" or "ABC.DEF" is specified as the receive file name on the sending-side host.

Specifying the instant transfer receive volumes file

File name

The name of the instant transfer receive volumes file can be any arbitrary file name. Set Instant Transfer Receive Volumes File (INSTTRANSVOLLST) to the file name in the System Environment Settings.

The instant transfer receive volumes file must be cataloged.

File format

The instant transfer receive volumes file can be either a sequential or partitioned file. Use the record format below.

Table 2.15 Record format of the instant transfer receive volumes file

Record format

Fixed length dataset

Record size

80 bytes

Syntax of the file

In the instant transfer receive volumes file, list first modifiers of the receivable files. Specify one modifier per record in the file.

DEFAULT: Default volume name 
Volume name 1 
Volume name 2 
    :

Default volume name

Specify the name of the default volume after "DEFAULT:".

If the save destination for the receive file is omitted on the sending-side host, the receive file is stored in the default volume.

Alternatively, if "DEFAULT:STORAGE" is specified in the file, HULFT behaves as follows depending on the value for Search Scope for Receive File in the System Environment Settings:

Table 2.16 Behavior when "DEFAULT:STORAGE" is specified

Search Scope for Receive File

Behavior

Volume

Finds the volume with the storage attribute

Catalog

Invokes the ACS routine to find the volume
Volume name

List volume names under which files are allowed to be received. Specify one name per record in the file.

Place an asterisk (*) at the end to match volume names beginning with the substring.

The request for instant transfer is accepted only when the save destination for the receive file specified on the sending-side host matches ones of the volume names registered in the instant transfer receive volumes file. The request for instant transfer is rejected when any volume name in the file matches the receive file name.

You do not need to explicitly or redundantly specify the default volume name.

Alternatively, if "ALLOW-ALL" is specified in the file, any volume name is allowed and the request for instant transfer is accepted.

Description example 

DEFAULT:STORAGE 
HUL001 
WRK*

If the content of the file is as above, HULFT behaves as follows:

  • The request for instant transfer is accepted when "HUL001" or "WRK123" is specified as the save destination for the receive file name on the sending-side host.

  • The request for instant transfer is rejected when "SISCO" or "HULFT" is specified as the save destination for the receive file name on the sending-side host.

    If the save destination for the receive file is omitted on the sending-side host, the receive file is stored in the volume with the storage attribute.

Code conversion

For instant transfer, specify the information on code conversion for the following fields in the System Environment Settings.

Instant Transfer EBCDIC Set (INSTTRANSEBCDIC)

Specify the EBCDIC set of the local host used for instant transfer.

Instant Transfer Code Conversion Side (INSTTRANSCODCNV)

Specify whether HULFT executes the sending-side conversion or receiving-side conversion for the instant transfer.

 

HULFT uses the code set information of the remote host that HULFT receives from the remote host during transfer.

Refer to the following for details about the how code conversion works and other points to be noted:

For details on each field of the System Environment Settings, refer to Explanation of each field.

Observe setting functions for instant transfer

You can use instant transfer to send a file if you only know the host name and port number of the receiving-side host.

On the receiving-side host, you can refuse instant transfer from unintended sending-side hosts.

= Remarks =

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 sending-side hosts are registered in the Host Information

By setting Allow Instant Transfer (ALLOWINSTTRANS) in the Host Information, you can specify whether or not HULFT accepts instant transfer for each host.

For details on the Host Information, refer to the following:

HULFT10 for zOS Operation Manual : Host Information

= Remarks =

Even if a sending-side host is registered in the Host Information, HULFT uses only the setting of Allow Instant Transfer for the host.

HULFT does not use other fields in the Host Information.

When sending-side hosts are not registered in the Host Information

By setting Allow Instant Transfer from Unregistered Host (ALLOWINSTTRANS) in the System Environment Settings, you can specify whether or not HULFT accepts instant transfer from any unregistered hosts.

For details on Allow Instant Transfer from Unregistered Host, refer to Explanation of each field.

Figure 2.29 Observe setting functions for instant transfer

Notes on instant transfer

The following are points to be noted on instant transfer.

  • HULFT automatically assigns a file ID of "_INSTANT_TRANSFER_" to the transfer that you execute by issuing a Send File request for instant transfer.

    You cannot use this file ID to execute the following operations:

    • Issuance of a Send File request

    • Issuance of a Resend File request

    • Issuance of a Send Request request

    • Issuance of a Resend Request request

    • Registration of the Send Management Information

    • Registration of the Receive Management Information

    For records for transfer status and transfer logs with the file ID "_INSTANT_TRANSFER_", you can execute the following operations as in the case of the conventional file IDs:

    • Inquiry and deletion of Send Log records

    • Inquiry and deletion of Receive Log records

    • Cancelation of sending-side transferring

    • Cancelation of receiving-side transferring

    • Change of the Unsent Status Queue

  • When you issue the Instant Transfer Send File Issuance command with JCL, a send file name cannot be dynamically specified with a DD statement.

  • Sending operations from tape volumes and receiving operations on tape volumes are not available.

  • For details on errors related to the Instant Transfer Send File Issuance command, and the status codes and detail codes that are output to records for the transfer status and transfer logs for instant transfer, refer to the following:

    HULFT10 for zOS Error Codes and Messages : Error codes in log records

  • The level of security differs between a management information based transfer and an instant transfer as follows:

    Table 2.17 Security on the sending-side host

     

    Management information based transfer

    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 always 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

    Multiplex level by host

    The value set in the Host Information is applied and multiple sending-side transferring instances can run only up to the multiplicity

    No limit on transferring multiplicity can be set

    Multiplex level of
    the entire system

    The value set in the System Environment Settings is applied and multiple sending-side transferring instances can run only up to the multiplicity

    The value set in the System Environment Settings is applied and multiple sending-side transferring instances can run only up to the multiplicity

    Table 2.18 Security on the receiving-side host

     

    Management information based transfer

    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 always regardless of whether the ID is registered in the Receive 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 registered in the Host Information (or against any arbitrary host if set so) (*1)

    Save location for the receive file

    Receiving-side transferring is performed only when the destination volume is registered in the Receive Management Information

    Receiving-side transferring is performed only when the destination volume is registered in the instant transfer receive volumes file

    Receive file name

    Receiving-side transferring is performed only when the destination file name is registered in the Receive Management Information

    Receiving-side transferring is performed only when the destination file name is registered in the instant transfer receive file naming file

    Multiplex level of
    the entire system

    The value set in the System Environment Settings is applied and multiple receiving-side transferring instances can run only up to the multiplicity

    The value set in the System Environment Settings is applied and multiple receiving-side transferring instances can run only up to the multiplicity

    *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, the instant transfer receive volumes file, and the instant transfer receive file naming file.

  • When the sending-side host is for UNIX/Linux, Windows, or IBMi, and the receiving-side host is for Mainframe, the compression preference is "None".

TOP

Policies     (c) Saison Technology Co.,Ltd. 1992