FUSSEND

You can use the FUSSEND exec to queue a request to send a file to a remote partner.

Required Parameters

The following table lists the required parameters of the FUSSCMD exec:

Parameter Description
LFILE | LF | DSN Defines the data set that the platform server updates with data received by the remote system.
RFILE | RF | REMOTE_FILE Defines the name of the file on the remote platform server system.

The remote system will read this file and send the data to the local platform server that will write the data to the LFILE file.

IPADDR or IPNAME or LIST or NODE IPADDR: defines the dotted decimal IP address of the remote platform server node.

IPNAME: defines the IP name of the remote platform server node. It can be up to 24 bytes.

LIST: defines the name of the distribution list.

NODE: defines the name of the destination node for a request. The LUname is used if NODE is not defined to the platform server.

Optional Parameters

The optional parameters of the FUSSEND exec are as follows: includes the following optional parameters:

Optional Parameters Description
ALLOC_TYPE Defines the allocation type for creating data sets.

The valid values are as follows:

  • C: cylinders
  • T: tracks
  • M: megabytes
  • K: kilobytes
ALLOC_DIR Defines the number of directory blocks that should be allocated when a data set is created.
ALLOC_PRI Defines the primary allocation quantity when creating a data set.
ALLOC_SEC Defines the secondary allocation quantity when creating a data set.
AVAIL Defines whether TAPE is supported.
  • IMMED: the remote file is available to users as soon as the file transfer is completed. This is the default and the best practice.
  • DEFER: the remote file availability is deferred. The platform server treats this as a TAPE.
BLOCKSIZE Defines the size of the block when creating a data set.
CKPT Defines whether to take checkpoints during this transfer.

The valid values are as follows:

  • nn: defines the time in minutes that each checkpoint takes. Allowable values are 1 - 9999 minutes.
  • YES: use a five minute checkpoint interval.
  • NO: do not use checkpoint. This is the default option.
COMPRESS Defines whether to use data compression, or defines the data compression algorithm to use.

The valid values are as follows:

  • NO: no compression is used. This is the default option.
  • YES: use RLE compression.
  • RLE: use RLE compression.
  • LZ: use LZ compression.
CONFIG | CFG Defines the configuration file used by the platform server exec.

If this parameter is not defined, the platform server uses the default configuration.

COPIES Defines the number of copies for a report.
Note: This parameter is used only when TRANS_TYPE=PRINT is specified.
CRCCHECK(CRC) Defines whether to perform CRC checking on the transfer.

The valid values are as follows:

  • YES: CRC checking is used.
  • NO: no CRC checking is used.
CRLF Defines whether records are delimited by CRLF (Carriage Return/Line Feed).

The valid values are as follows:

  • YES: records are delimited by CRLF.
  • NO: records are not delimited by CRLF. This is the default option.
DATACLASS Defines the SMS data class when creating a data set.
DATASET_TYPE Defines the type of data set to be created.

The valid values are as follows:

  • PDS: create z/OS PDS.
  • LIBRARY: create z/OS PDS/E.
  • DSN: create z/OS sequential files.
  • VSAM: create z/OS VSAM files.
DESCRIPTION Defines the user data for the transfer in 25 bytes.
DESTINATION Defines the destination for a report.
DISP Defines the type of allocation that the platform server performs for the request.

The valid values are as follows:

  • SHR: allocates as DISP=SHR.
  • OLD: allocates as DISP=OLD.
EFFECT Defines how the platform server open a data set when writing to the data set.

The valid values are as follows:

  • C: create.
  • R: replace.
  • A: append a file.
  • CR: create or replace. This is the default option.
  • CA: create or append.
EMAIL_FAIL Defines the email address to which to send an email notification when a request is completed unsuccessfully.
EMAIL_GOOD Defines the email address to which to send an email notification when a request is completed successfully.
ENCRYPT Defines the level of encryption that is used by the transfer.

If specified, this parameter overrides the ENCRYPT parameter specified in the GLOBAL or NODE definitions for this transfer.

The valid values are as follows:

  • NONE: no encryption is used for this transfer.
  • DES: DES encryption is used.
  • 3DES: Triple DES encryption is used.
  • BF: Blowfish 56-bit encryption is used.
  • BLOWFISH: Blowfish 56-bit encryption is used.
  • BFL: Blowfish 448-bit encryption is used.
  • BLOWFISH_LONG: Blowfish 448-bit encryption is used.
  • AES: AES 256-bit encryption is used.

For more information on this parameter, see Data Encryption.

EVERY Defines the interval at which the request will be executed.

For more information on the description of the platform server Batch interface EVERY parameterin section in the Batch Interface section, see SYSIN Coding Parameters in SYSIN DD Statement. .

EVERY_COUNT Defines the number of times that an EVERY request can be executed.

For more information on the description of the platform server Batch interface EVERY_COUNT parameterin section in the Batch Interface section, see SYSIN Coding Parameters in SYSIN DD Statement.

EVERY_EXDAYS Defines the expiration interval in days for a transfer scheduled by an EVERY request.

For more information on the description of the platform server Batch interface EVERY_EXDAYS parameter in section in the Batch Interface section, see SYSIN Coding Parameters in SYSIN DD Statement.

EVERY_EXTIME Defines the expiration interval in hours and minutes for a transfer scheduled by an EVERY request.

For more information on the description of the platform server Batch interface EVERY_EXTIME parameterin section in the Batch Interface section, see SYSIN Coding Parameters in SYSIN DD Statement.

EVERY_MISSED Defines whether a request is scheduled when the interval defined by the EVERY request has passed.

For more information on the description of the platform server Batch interface EVERY_MISSED parameterin section in the Batch Interface section, see SYSIN Coding Parameters in SYSIN DD Statement.

EXPDT Defines the expiration date of a file transfer request, in Julian format, CCYYDDD.

The default value is 30 days from now.

EXPTM Defines the expiration time for a file transfer request.
FCB Defines a form control buffer for a report.
Note: This parameter is used only when TRANS_TYPE=PRINT is specified.
FORM Defines the name of the form for a report.
Note: This parameter is used only when TRANS_TYPE=PRINT is specified.
HOLD Defines whether a request is put on hold when it is queued.

The valid values are as follows:

  • Yes: puts the transfer on hold when it is queued.
  • No: does not put the transfer on hold when it is queued. This is the default option.
INTERVAL Defines the status scan interval.
Note: This parameter is ignored unless the WAIT parameter is specified.
IVOLUME Defines the volume that is used for input data set processing by the platform server.

When this parameter is specified, the catalog is not used to allocate the data set.

LDISP Defines local status, normal disposition, and error disposition.

The values of the LDISP parameter must be delimited by a colon instead of a comma.

LENGTH The record length of a file when creating a data set.
LOCALLABEL

Defines the label used on the initiating Platform Server when sending or receiving a tape file. The input format is (nn,SL) where nn defines the file label number andSL is the only label type currently supported. For sending a tape file, if the label information is in the catalog, this parameter is not required. This parameter is ignored for disk files.

LOGON_DOMAIN Defines the name of the Windows domain to which to log on.
MGTCLASS Defines the SMS management class when creating a data set.
MQ_GOOD Defines the MQ (Message Queue) to which the platform server writes a record when a request is completed successfully.
MQ_FAIL Defines the MQ (Message Queue) to which platform server writes a record when a request fails.
MWAIT Puts a request on a queue, and returns to the caller before the request is completed.
NODE Defines the name of the destination node for a request.

The LUname is used if the NODE parameter is not defined to the platform server.

NOTIFY Defines the TSO user to notify when the request is completed.
NOTIFY_TYPE Defines a type of user to notify when the request is completed.

Currently, the only option supported is TSO.

OVOLUME Defines the volume that is used for that is used for the output data set for a transfer.

When this parameter is specified, the catalog is not used to allocate the data set.

PERMIT_ACTNS Defines the permitted actions for Windows.

The valid values are as follows:

  • S: system.
  • H: hidden file.
  • A: archive file.
  • R: read only.
  • C: NTFS compression.
  • Z: EOF CRLF. Add CRLF or CTRL-/Z to file end.
  • E: EOF. Add CTRL-Z to file end.
PROCESS Defines the process name that is associated with the request.
PRIORITY Defines the priority for file transfers.

The allowable values are 0 - 9. The default value is 3.

PRINTER_NAME Defines the name of a remote printer.
PURGE Defines whether to purge uncompleted transfers when the TIMEOUT interval expires.
Note: This parameter is ignored unless the WAIT parameter is specified.
RDISP Defines the remote status, normal disposition, and error disposition.

The values of the RDISP parameter must be delimited by a colon instead of a comma.

RECFM Defines the platform record format when creating a data set.

The valid values are as follows:

  • F: fixed
  • FB: fixed block
  • V: variable
  • VB: variable block
  • FS: fixed standard
  • VS: variable spanned
  • VBS: variable blocked spanned
REMOTELABEL Defines the label used on the target Platform Server when sending or receiving a tape file. The input format is (nn,SL) where nn defines the file label number and SL is the only label type currently supported. For sending a tape file, if the label information is in the catalog, this parameter is not required. This parameter is ignored for disk files.
RETENTIONPRD Defines the number of days that the platform server leaves a request on an active queue before purging the request.

The allowable values are 1 - 9999. The default value is 30 days.

RETRY Defines the number of times that the platform server tries a request when a network error occurred.

The default value of 1 means that the platform server purges the transfer when the first network error occurs. For best results set this parameter to 1 if you specify the WAIT parameter.

RETRYINT Defines the retry interval of the file transfer.

This parameter can be specified in terms of hours, for example, RETRYINT=2H or minutes, for example, RETRYINT=0M.

REXX_EXEC Defines a REXX exec that will be executed when the platform server request is completed, either successfully or unsuccessfully.
Note: This exec will only be executed when the platform server request is purged from the active queue.
RMTRAIL Defines whether to remove the trailing blanks and spaces when sending a TEXT file to the platform server for UNIX or Windows.

The valid values are as follows:

  • YES: remove trailing spaces and nulls.
  • NO: do not remove trailing spaces and nulls. This is the default option.
RPASS Defines the password for the user on a remote computer.
Note: This parameter can only be defined when the RUSER parameter is also defined.
RUSER Defines the name of the user on the remote computer.

If this parameter is not defined, the default value *PROFILE is used.

SAY Writes a status record on each status scan.
Note: This parameter is ignored unless the WAIT parameter is also specified.
STORCLASS Defines the SMS storage class when creating the data set.
SYSOUT Defines the SYSOUT class for a report.
Note: This parameter is used only when TRANS_TYPE=PRINT is specified.
TEMPLATE Defines the Windows template for a file transfer.
TIME Defines the start time of the request in 24-hour clock format, hhmm.
TIMEOUT Defines the timeout interval.
Note: This parameter is ignored unless the WAIT parameter is specified.
TLS Defines whether TLS (SSL) can be used for this request. This definition overrides the GLOBAL or NODE definitions.

The valid values are as follows:

  • YES: TLS is used for this transfer.
  • NO: TLS is not used for this transfer.
  • TUNNEL: All data transmitted is sent over an encrypted TLS Tunnel connection.
TRANS_TYPE Defines the type of transfer being sent or received.

The valid values are as follows:

  • FILE: data is written to a file. This is the default option.
  • PRINT: data is sent to a printing queue.
  • JOB: data is run as a job.
  • COMMAND: data is executed as a command.
TRUNCATE(TRUNC) This parameter is only used when receiving a file from Windows, UNIX, IBMi or MFT Internet Server when record delimiters are defined. This parameter is ignored for a SEND or when communicating to another zOS system.
The valid values are:
  • NO: If the record received from the partner is greater than the LRECL, a truncate error occurs and the transfer is terminated with an error.
  • YES: If the record received from the partner is greater than the LRECL, the record is truncated and any data after the LRECL is lost.
  • WRAP: If the record received from the partner is greater than the LRECL, the record is truncated and any data after the LRECL is written to the next record. If the record received has no delimiters within the first 32760 bytes, a truncate error occurs and the transfer is terminated with an error. In cases like this, you should turn off delimiter checking, so records will be written without any delimiter checking.
TYPE Defines the type of data in a file, and whether ASCII - EBCDIC conversion occurs.

The valid values are as follows:

  • TEXT: remove trailing blanks and nulls, and perform data conversion.
  • DATA: the same as TEXT except that trailing blanks and nulls are not removed.
  • BINARY: do not perform data conversion. This is the default option.
USERNAME Defines the user name associated with a report.
UTF8BOM Defines whether the UTF-8 BOM(0xefbbbf) is added at the start of the converted data or is removed from the start of the data before conversion. This parameter is used only when the LCT parameter defines that Unicode services are used to convert data. This parameter can be used for a z/OS Initiated Send or Receive transfers, although it is more commonly used when sending a file to a target system that requires a BOM.

The valid values are:

  • ADD: The UTF-8 BOM (0xEFBBBF) is added at the start of the converted data. This value is typically used when sending data to a target system (like Linux) that requires the UTF-8 BOM at the start of the file.
  • REMOVE: The UTF-8 BOM (0xEFBBBF) is removed from the start of the file before converting the data. If the start of the file does not include the BOM, no changes are made. This value is typically used when receiving data from a target system (like Linux) that contains the UTF-8 BOM at the start of the file.
  • BOTH: The UTF-8 BOM (0xEFBBBF) is added at the start of the converted data. The UTF-8 BOM (0xEFBBBF) is removed from the start of the file before converting the data.
  • NONE: No UTF-8 BOM processing is performed. The UTF-8 BOM is not inserted at the start of the converted data or removed before conversion.
VOLUME Defines the volumes where the data set can be written.

Up to 5 volumes can be defined. If more than one volume is defined, the volumes must be delimited by colons.

VSAM_RRSLOT Defines whether the RRDS slot number is included in a VSAM RRDS transfer.
VSAM_KEYPOS Defines the VSAM KSDS key position relative to 0.
VSAM_KEYLEN Defines the VSAM KSDS key length.
VSAM_TYPE Defines the type of VSAM file to be created.

The valid values are as follows:

  • ESDS
  • KSDS
  • RRDS
VSAM_LIKE Defines the model DSN for VSAM file creation.
VSAM_LRECL Defines the record length used for VSAM file creation.
VSAM__REUSE Defines whether to use the VSAM RESUSE option.
WAIT Waits for this request to be completed before returning to REXX.
WRITER Defines the name of the z/OS external writer for a report.
Note: This parameter is only when TRANS_TYPE=PRINT is specified.

Example

The following example shows how to use the FUSSEND exec to queue a request to send a file to a remote partner: 

FUSSEND NODE=SNANODE LF=LOCAL.FILE1 RF=C:\FUSSEND.TXT INTERVAL=3 
SAY WAIT TYPE=TEXT CRLF=YES

The output of this example is as follows: 

TRANSACTION=IA01500042 STATUS=ACTIVE   RECORD=000000000
BYTES=000000000 
TRANSACTION=IA01500042 STATUS=COMPLETE RECORD=000000052
BYTES=000004160
***Fusion retcode.......=  0
***Fusion TransNum......=  IA01500042
***Completed transfers..=  01
***Successful transfers.=  01
***Failed transfers.....=  00
***Purged transfers.....=  00
***Last Message.........=  PGTF3101I Activity IA01500042
successfully transferred 52 records with remote node SNANODE
Request Queued successfully with TRANSNUM= IA01500042