Send File request for instant transfer

To carry out instant transfer, issue the Send File request for instant transfer by using the following methods.

Execution of the Instant Transfer Send File Issuance command as a TSO command
Execution of the Instant Transfer Send File Issuance command as a batch TMP via JCL

This section explains these methods.

For details on the instant transfer function and restrictions, refer to the following:

HULFT10 for zOS Administration Manual : Instant transfer

Execution of the Instant Transfer Send File Issuance command as a TSO command

Enter the Instant Transfer Send File Issuance command as shown below and issue the Send File request for instant transfer.

HULSNDGO FILE('filename') HOST(hostname) PORT(port) RCVLOC('rcvloc') RCVFILE('filename') MODE(T) P(n) SYNC

Explanation of parameters

FILE('filename')

This parameter specifies the name of the send file. (Mandatory)

Specify alphanumeric characters within 44 bytes.

Enclose the send file name within single quotations (').

HOST(hostname)

This parameter specifies the host name of the receiving-side host. (Mandatory)

Specify alphanumeric characters within 50 bytes.

PORT(port)

This parameter specifies the port number of the receiving-side host. (Optional)

Omitting this field sets "30000".

RCVLOC('rcvloc')

This parameter specifies the save destination for the receive file. (Optional)

Specify alphanumeric characters within 200 bytes.

Enclose the save destination of the receive file within single quotations (').

For details on the save destination used when the field is omitted, refer to Points to be noted on parameters.

RCVFILE('filename')

This parameter specifies the file name of the receive file. (Optional)

Specify alphanumeric characters within 200 bytes.

Enclose the file name of the receive file within single quotations (').

If you omit this parameter, the receive file is created with the same name as the send file.

MODE(T)

This parameter specifies the transfer type. (Optional)

T:: Text data
B:: Binary data

Omitting this field sets "T" (text data).

P(n)

This parameter specifies the transfer priority. (Optional)

Omitting this field sets "50".

SYNC

Specify this parameter to carry out synchronous transfer. (Optional)

Note

If you have started a synchronous transfer by specifying SYNC, and when you want to terminate the TSO command for any reason, press the Attention key (Esc key).

= Remarks =

You can execute the Instant Transfer Send File Issuance command with "HULS" instead of "HULSNDGO".
Enter the following commands in TSO/E READY mode to display an explanation of the Instant Transfer Send File Issuance command.
```
 READY         
HELP HULS 
```
```
 READY         
HELP HULSNDGO
```
For errors displayed after executing the Instant Transfer Send File Issuance command, refer to the following:

HULFT10 for zOS Error Codes and Messages: Instant transfer messages

Execution of the Instant Transfer Send File Issuance command as a batch TMP via JCL

Issue the Send File request for Instant Transfer as a batch TMP via JCL.

XRSYSIN definition card

This card sets the System Environment Settings of the HULFT system. For details on the definitions, refer to the following:

HULFT10 for zOS Administration Manual : Explanation of each field

Format of definition card

START-TASK=Job Name of Send Program (Job name for XRSND) 
CMPBLK=Work File Block Length for Compression 
SCANMODE=Handling of Cancelation of Synchronous Transfer 
GAIJIFILE=Use Custom Character Table 
GAIJIERR=Process when Custom Character has not been Registered 
INIT-UNIT=UNIT Name of Send Files and Receive Files 
JESC=JES Command Acronym 
SNDRETRY=Retry Count for Accessing Send Files 
SNDRTIME=Retry Interval for Accessing Send Files 
EUCSP=Space Code Mode During EUC Code Conversion 
CNVLENCHK=Handling of Data Exceeded Max Length after Code Conversion 
OPLSELECT=Operation Log Output Option (*1) 
SND-SEQNO-THRESHOLD=Send SEQ No. Threshold 
HULCHARSET=HULFT Character Set 
INSTTRANSCODCNV=Instant Transfer Code Conversion Side 
INSTTRANSEBCDIC=Instant Transfer EBCDIC Set 
INSTTRANSCMDQUE=Send Control File to Issue Instant Transfer 
SYSFILEOUTPUTMODE=System File Output Mode

When you use the operation log output function, you must include definitions related to operation logs. For details, refer to Definitions for operation logs.

Example of JCL

//HULSNDGO JOB  CLASS=A,MSGCLASS=B
//**-----------------------------------------------------------------**
//*  FILE('SEND-FILE-NAME')  -
//*  HOST('HOSTNAME')  -
//*   PORT('VALUE')  -                 * PORT NO. (DEFAULT:30000)
//*   RCVLOC('RECEIVING-LOCATION')   - * MF:VOL,WIN/UX:PATH,IBMi:LIB
//*   RCVFILE('RECEIVING-FILE-NAME') -
//*   MODE('MODE')  -                  * T:TEXT(DEFAULT),B:BINARY
//*   P('VALUE')    -                  * TRANSFER PRIORITY
//*   SYNC                             * SYNCHRONOUS TRANSFER
//**-----------------------------------------------------------------**
//HULSNDGO EXEC PGM=IKJEFT01,REGION=4096K
//STEPLIB  DD   DSN=HULFT.LOAD,DISP=SHR
//XRHULINS DD   DSN=HULFT.PARMLIB(HULPRM),DISP=SHR
//SYSTSIN  DD   *
HULSNDGO FILE('HULFT.DATA')            -
         HOST(PC00001)                 -
         PORT(30000)                   -
         RCVLOC('C:\RECIEVE-FOLDER')   -
         RCVFILE('RECEIVE-FILE.TXT')   -
         MODE(T)                       -
         P(50)                         -
         SYNC
//SYSTSPRT DD   SYSOUT=*
//SYSPRINT DD   SYSOUT=*
//

DD Name	Value	Description
STEPLIB	HULFT.LOAD	HULFT load module library
XRHULINS	HULFT.PARMLIB(HULPRM)	System Environment Settings File

Points to be noted on parameters

Specification of send file

You can only specify cataloged files for the send file.

You cannot specify files that are not cataloged for the send file.
You cannot specify files on tape volume for the send file.

Specification of the receiving-side host

Specify a host that runs HULFT Ver.8.4 or higher as the receiving-side host.

Specification of receive file

Specify an existing location for the save destination of the receive file.
Specify both the save destination and the name for the receive file according to the operating system specifications of the receiving-side host.
If the save destination for the receive file is omitted, a particular location is used on the receiving-side host as the default destination for the receive file.

The save destination differs depending on the machine type.

For details on the default destination used when the save destination for the receive file is omitted, refer to the following for each host type:

HULFT10 for Windows Administration Manual : Instant transfer

HULFT10 for Linux/AIX Administration Manual : Instant transfer

HULFT10 for IBMi Administration Manual : Instant transfer

HULFT10 for zOS Administration Manual : Instant transfer
If the specified receive file does not exist, a new receive file is created.

Specification of the receive file when the receiving-side host is HULFT10 for zOS

You cannot specify tape volume as the save destination for the receive file.
If the file that is specified for the receive file does not exist, the receive file that is newly created is always cataloged.
In the case that a new receive file is created by issuing an instant transfer request, specify the settings and the attribute of the receive file in the System Environment Settings on the receiving-side host beforehand. For the fields that you must set, refer to the following for the receiving-side host:

HULFT10 for Windows Administration Manual : Security

HULFT10 for Linux/AIX Administration Manual : Security Settings

HULFT10 for IBMi Administration Manual : Instant Transfer Settings

HULFT10 for zOS Administration Manual : Explanation of each field
When the receiving-side host is HULFT8 for zOS and you specify an existing file as the receive file, whether the catalog or the volume is searched depends on the setting of Search Scope for Receive File (RCV-FILE-SEARCH) in the System Environment Settings of the receiving-side host.
If destination files are defined in the instant transfer receive file naming file, only those files that match the definition are accepted as the destination in receiving-side transferring.

If destination files are not defined (i.e. the definition is omitted) in the instant transfer receive file naming file, receiving-side transferring is not performed.
If destination volumes are defined in the instant transfer receive volumes file, only those volumes that match the definition are accepted as the destination in receiving-side transferring.

If destination volumes are not defined (i.e. the definition is omitted) in the instant transfer receive volumes file, receiving-side transferring is not performed.