Send File

Run the Send File program (XRSNDGO) to execute the Send File. The Send File program (XRSNDGO) registers the information of the file to be sent in the Send Control file (HULFT.QUEUE) and issues an order for the Send processing to the Send program (XRSND).

You can also execute the Send File interactively (on the HULFT Management Console). For details, refer to Execution of requests.

Send File Program (XRSNDGO)

Program Name

XRSNDGO

Execution parameters (for EXEC statement)

[ERR=CONT]

CONT

This parameter is defined to continue the processing.

Specifying this parameter when you define multiple XRCRD definition cards continues the processing of subsequent XRCRD definition cards even if an error occurs during the processing of an XRCRD definition card.

In addition, when you define 'SYNC' on each XRCRD definition card, the program continues processing even if an error occurs in the Send processing.

XRSYSIN Definition Card

This card defines the System Environment Settings of 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) 
RESENDDEL=Criteria to Delete Resend Queue 
PREFIX=First Modifier of Send Work Files 
CMPBLK=Work File Block Length for Compression 
RECLEN=Shiftcode Mode for Send Files 
JOBTIME=Job Timeout for Pre-send Job 
SCANMODE=Handling of Cancelation of Synchronous Transfer 
PSCHG=Pack Zone Conversion 
PSASCII=Sign for ASCII 
PSEBCDIC=Sign for EBCDIC 
GAIJIFILE=Use Custom Character Table Mode 
GAIJIERR=Process when Custom Character has not been Registered 
CLEARMODE=Post-send Clear Mode 
DYNAMIC-DIRECT=Direct Transfer Mode for Dynamic Specification 
INIT-UNIT=UNIT Name of Send Files and Receive Files 
UNIT=UNIT Name of Send Work Files 
WORKVOLMODE=Work Volume Mode 
JESC=JES Command Acronym 
JLIB1=Subsequent Job Addition Step STEPLIB Settings 1 
JLIB2=Subsequent Job Addition Step STEPLIB Settings 1 
JLIB3=Subsequent Job Addition Step STEPLIB Settings 1 
JELIB1=Subsequent Job Addition Step STEPLIB Settings 2 
JELIB2=Subsequent Job Addition Step STEPLIB Settings 2 
JELIB3=Subsequent Job Addition Step STEPLIB Settings 2 
SNDRETRY=Retry Count for Accessing Send Files 
SNDRTIME=Retry Interval for Accessing Send Files 
EUCSP=Space Code Mode During EUC Code Conversion 
MSGDYNPARM=Message Dynamic Parameter Specification 
DEFER=Deferred Mount 
JCLRETRY=JCL Library Retry Count 
JCLRTIME=JCL Library Retry Interval 
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 
RPREFIX=First Modifier of Receive Work Files 
INDOPTVAR=Indicator Options for Environment Variable 
CODE-CONVERSION-LOCATION=Storage for Code Conversion Table 
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.

Note

When you run the Send program (XRSND), make sure you define the same value for Post-send Clear Mode (CLEARMODE) as the value you defined for Post-send Clear Mode in the System Environment Settings.

XRCRD Definition Card

The following shows the format of the definition card for defining information necessary for the execution of the Send File.

Format of definition card

            a      b         c                 d             e        f 
FILE-ID=xxxxxxxx[,P=999][,DD=xxxxxxxx][,GRPID=xxxxxxxx|HOST=xx...xx][,SYNC] 
            g 
   [,MSG0=xxxx...xxxx][,MSG1=xxxx...xxxx][,MSG2=xxxx...xxxx] 

   [,MSG3=xxxx...xxxx][,MSG4=xxxx...xxxx][,MSG5=xxxx...xxxx] 
            h 
   [,MSGL0=xxxx...xxxx][,MSGL1=xxxx...xxxx]

= Remarks =

If the definition card spans two lines, use either of the following two methods to define the definition card:

Describe the first line up to column 71, and then insert a hyphen (-) in column 72. Describe the second line starting in column 1.
Describe a line up to a comma (,) that follows a parameter, insert a single byte space, and then insert a hyphen (-) in column 71 or before.

Input contents of definition card

a. File ID

This parameter defines the file ID in the Send Management Information that is registered in the Send and Receive Management file (HULFT.FILE). (Mandatory)

Specify a string of alphanumeric characters (and "_" if desired) that is within 50 bytes.

b. Transfer priority

This parameter defines the priority of the relevant transfer in the Send Queue. (Optional)

Set a value from '1' to '256' for this parameter.

The lower the value, the higher the priority. When you default this parameter, HULFT uses the value that you specified for the Transfer Priority in the Send Management Information.

c. Send file DD Name

This parameter is defined to dynamically specify a file name instead of the Send file name in the Send Management Information that you registered in the Send and Receive Management file (HULFT.FILE). (Optional)

Specify the name of the data set that you want to send in the JCL and specify the relevant DD name.

Specify alphanumeric characters within 8 bytes for this parameter.

d. Transfer group ID

This parameter is defined to specify a transfer group ID instead of the transfer group ID in the Send Management Information that you registered in the Send and Receive Management file (HULFT.FILE). (Optional)

Define the transfer group ID that is already registered in the Send and Receive Management file (HULFT.FILE).

Specify a string of alphanumeric characters (and "_" if desired) that is within 50 bytes.

e. Host name

This parameter replaces the host names that are defined for the transfer group ID in the Send Management Information on HULFT that is registered in the Send and Receive Management file (HULFT.FILE). (Optional)

Define a host name that is already registered in the Host Information file (HULFT.HOST).

Specify alphanumeric characters within 50 bytes for this parameter.

f. Synchronous Transfer

This parameter is defined to stop job steps of the Send File program (XRSNDGO) until the Send processing ends. (Optional)

g. Message0 to message5

These parameters define messages that are sent to the host on the receiving side. (Optional)

Define a string within 50 bytes for each message.

If you default these parameters, messages are not sent to the host on the receiving side.

You can define up to six messages.

h. Long message0 to long message1

These parameters define long messages that are sent to the host on the receiving side. (Optional)

Define a string within 200 bytes for each message.

If you default these parameters, long messages are not sent to the host on the receiving side.

You can define up to two long messages.

Note

When you perform the Direct Transfer by specifying the Send file dynamically, define the following in the DD statement:

Define only one dataset name for each DD name.

If you define two or more dataset names for one DD name, only the first defined dataset is transferred.
Define 'SHR' for the DISP parameter.

= Remarks =

When you define a variable from 'MSG0' to 'MSG5' or from 'MSGL0' to 'MSGL1' on the XRCRD definition card and carry out replacement with message, you must define a value from '1' to '3' for the Message Dynamic Parameter Specification (MSGDYNPARM) in the System Environment Settings.
When you define a variable from 'MSG0' to 'MSG5' or from 'MSGL0' to 'MSGL1' on the XRCRD definition card, replacement with message may end unsuccessfully and the transmission may fail, due to the language setting of the remote host.

For points to be noted on message transmission, refer to the following:

HULFT10 for zOS Administration Manual : Message transmission
When you use the following characters in a message or a long message, enclose the entire message within single quotations ('):
- Space
- Equal sign (=)
- Comma (,)
- Multibyte characters
You cannot specify the following in a message:
- Single quotation marks (')

Example of JCL

Example of JCL 1

The following shows an example of the JCL for sending according to the Send Management Information:

//XRSNDGO  JOB  CLASS=A,MSGCLASS=B                                              
//XRSNDGO  EXEC PGM=XRSNDGO,REGION=4096K                                        
//STEPLIB  DD   DSN=HULFT.LOAD,DISP=SHR                                         
[//XREXTLIB DD  DSN=HULFT.LOAD,DISP=SHR]                                        
//XRFILE   DD   DSN=HULFT.FILE,DISP=SHR                                         
//XRHOST   DD   DSN=HULFT.HOST,DISP=SHR                                         
//XRQUE    DD   DSN=HULFT.QUEUE,DISP=SHR                                        
//XRSYSIN  DD   DSN=HULFT.PARMLIB(HULPRM),DISP=SHR                              
//SYSOUT   DD   SYSOUT=*                                                        
//XRCRD    DD   *                                                               
      FILE-ID=LOOPTEST                                                          
//*   FILE-ID=XXXXXXXX,DD=INDD,GRPID=XXXXXXXX,P=999,SYNC                        
//

DD Name	Value	Description
STEPLIB	HULFT.LOAD	HULFT load module library
XREXTLIB	HULFT.LOAD	HULFT load module library (*1)
XRFILE	HULFT.FILE	Send and Receive Management File
XRHOST	HULFT.HOST	Host Information File
XRQUE	HULFT.QUEUE	Send Control File
XRSYSIN	HULFT.PARMLIB(HULPRM)	System Environment Settings File

When you specify conversion of custom character codes using custom character tables on the host on the sending side, you must add a library to store HULFT load module. For details on custom character tables, refer to the following:

HULFT10 for zOS Administration Manual : Custom character table

Example of JCL 2

The following shows an example of the JCL for using a DD statement to dynamically specify a Send file:

//XRSNDGO  JOB  CLASS=A,MSGCLASS=B                                              
//XRSNDGO  EXEC PGM=XRSNDGO,REGION=4096K                                        
//STEPLIB  DD   DSN=HULFT.LOAD,DISP=SHR                                         
//SNDFILES DD   DSN=PAYROLL.FILE,DISP=SHR                                       
//XRFILE   DD   DSN=HULFT.FILE,DISP=SHR                                         
//XRHOST   DD   DSN=HULFT.HOST,DISP=SHR                                         
//XRQUE    DD   DSN=HULFT.QUEUE,DISP=SHR                                        
//XRSYSIN  DD   DSN=HULFT.PARMLIB(HULPRM),DISP=SHR                              
//SYSOUT   DD   SYSOUT=*                                                        
//XRCRD    DD   *                                                               
      FILE-ID=LOOPTEST,DD=SNDFILES,GRPID=HP1                                    
//

DD Name	Value	Description
STEPLIB	HULFT.LOAD	HULFT load module library
SNDFILES	PAYROLL.FILE	Send file
XRFILE	HULFT.FILE	Send and Receive Management File
XRHOST	HULFT.HOST	Host Information File
XRQUE	HULFT.QUEUE	Send Control File
XRSYSIN	HULFT.PARMLIB(HULPRM)	System Environment Settings File

Cancelation of Synchronous Transfer

When you define the Synchronous Transfer, if you want to cancel the synchronization of the Send File program (XRSNDGO) that is waiting for the termination of the transfer, submit the following command. The following command does not cancel the transfer. To terminate the transfer, carry out cancelation of the transfer.

F Job name of Send File program,CANCEL

Note

When a Pre-send Job is registered in the Send Management Information, the following restrictions apply:
- If the Pre-send Job ends unsuccessfully, the program ends unsuccessfully without executing the Send File.
- Even in the case of multicasting (sending a file to multiple hosts), the program executes the Pre-send Job only once.
- Even if there is an error in the contents of the Send Management Information (for example, a necessary transfer group ID or a necessary Host Information record is not registered), the program executes the Pre-send Job.
When you use a DD statement to dynamically specify a Send file, HULFT behaves as follows:
- HULFT behaves differently if the Send file is locked by another user application.
  
  For details, refer to the following:
  
  HULFT10 for zOS Administration Manual : Settings related to file open and lock
- Even if 'D' (Delete) or 'L' (Lock) is specified for Send File Mode (CLEAR) in the Send Management Information, HULFT behaves as though 'K' (Keep) is specified.
- Even if 'C' (Clear) is specified for Send File Mode (CLEAR) in the Send Management Information, HULFT behaves as though 'K' (Keep) is specified in either of the following cases:
  - Direct Transfer is used.
  - Work File Transfer is used and 'A' (Clear or delete data after the Send processing ends successfully) is specified for Post-send Clear Mode (CLEARMODE) in the System Environment Settings.
When you run the Send File command with the Synchronous Transfer, if auto resending is carried out due to a communication error, the Send File command does not end until auto resending ends.