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 dataset 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 datasets.
Valid values are:
|
| ALLOC_DIR | Defines the number of directory blocks that should be allocated when a dataset is created. |
| ALLOC_PRI | Defines the primary allocation quantity when creating a dataset. |
| ALLOC_SEC | Defines the secondary allocation quantity when creating a dataset. |
| AVAIL | Defines whether TAPE is supported.
|
| BLOCKSIZE | Defines the size of the block when creating a dataset. |
| CKPT | Defines whether to take checkpoints during this transfer.
Valid values are:
|
| COMPRESS | Defines whether to use data compression, or defines the data compression algorithm to use.
Valid values are:
|
| 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.
Valid values are:
|
| CRLF | Defines whether records are delimited by CRLF (Carriage Return/Line Feed).
Valid values are:
|
| DATACLASS | Defines the SMS data class when creating a dataset. |
| DATASET_TYPE | Defines the type of dataset to be created.
Valid values are:
|
| 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.
Valid values are:
|
| EFFECT | Defines how the Platform Server open a dataset when writing to the dataset.
Valid values are:
|
| 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. Valid values are:
For more information on this parameter, see Data Encryption. |
| EVERY | Defines the interval at which the request will be executed. |
| EVERY_COUNT | Defines the number of times that an EVERY request can be executed. |
| EVERY_EXDAYS | Defines the expiration interval in days for a transfer scheduled by an EVERY request. |
| EVERY_EXTIME | Defines the expiration interval in hours and minutes for a transfer scheduled by an EVERY request. |
| EVERY_MISSED | Defines whether a request is scheduled when the interval defined by the EVERY request has passed. |
| 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.
Valid values are:
|
| 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 dataset processing by the Platform Server.
When this parameter is specified, the catalog is not used to allocate the dataset. |
| 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 dataset. |
| LOCALLABEL |
Defines the label used on the initiating Platform Server when sending or receiving a tape file. The input format is (nn, |
| LOGON_DOMAIN | Defines the name of the Windows domain to which to log on. |
| MGTCLASS | Defines the SMS management class when creating a dataset. |
| 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
|
| OVOLUME | Defines the volume that is used for that is used for the output dataset for a transfer.
When this parameter is specified, the catalog is not used to allocate the dataset. |
| PERMIT_ACTNS | Defines the permitted actions for Windows.
Valid values are:
|
| PPA | Defines the preprocessing or postprocessing actions that are performed for the file transfer. The format of the PPA command is:
Where Status is:
Where Source is:
Where Action is: Where Data is: The data to be processed |
| PROCESS | Defines the process name that is associated with the request. |
| PRIORITY | Defines the priority for file transfers.
The allowable values are
|
| 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 dataset.
Valid values are:
|
| 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
|
| RETRY | Defines the number of times that the Platform Server tries a request when a network error occurred.
The default value of
|
| RETRYINT | Defines the retry interval of the file transfer.
This parameter can be specified in terms of hours, for example,
|
| 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.
Valid values are:
|
| 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
|
| 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 dataset. |
| 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. See TIMEOUT parameter in
Waiting for Transfer Requests to Complete.
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.
Valid values are:
|
| TRANS_TYPE | Defines the type of transfer being sent or received.
Valid values are:
|
| TRUNCATE(TRUNC) | This parameter is only used when receiving a file from Windows, UNIX, IBM i, or MFT Internet Server when record delimiters are defined. This parameter is ignored for a SEND or when communicating to another z/OS system.
Valid values are:
|
| TYPE | Defines the type of data in a file, and whether ASCII - EBCDIC conversion occurs.
Valid values are:
|
| 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.
Valid values are:
|
| VOLUME | Defines the volumes where the dataset 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.
Valid values are:
|
| 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