Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# FUSWAIT

You can use the FUSWAIT exec to wait for 1 - 40 transfers that are queued with the MWAIT parameter to complete.

## Required Parameter

No parameter is required by the FUSWAIT exec.

## Optional Parameters

The following table lists the optional parameters of the FUSWAIT exec:

Parameter | Description
--- | ---
CONFIG | CFG | Defines the configuration file used by the FUSWAIT exec. If this parameter is not defined, the Platform Server REXX uses the default configuration.
INTERVAL | Defines the number of seconds between the status scans of a request. Default = 10 seconds. For more information, see Waiting for Transfer Requests to Complete.
PURGE | Defines the Platform Server to purge all requests that are not completed when the TIMEOUT expires. For more information, see Waiting for Transfer Requests to Complete.
SAY | Displays the updated status after each time the request status is checked. Note: The Platform Server only scans uncompleted transfers for status checks; if the transfers are completed, the Platform Server does not scan them for status checks. For more information, see Waiting for Transfer Requests to Complete.
TIMEOUT | Defines the number of seconds that the Platform Server continues to scan requests that are not completed. Default = 300 seconds. For more information, see Waiting for Transfer Requests to Complete.

## Example

The following example shows how to use the FUSWAIT exec to wait for more than one transfers to complete.

    FUSSEND IPADDR=190.190.190.100 LF=local.file RF=remote.file1 MWAIT
    FUSSEND IPADDR=190.190.190.101 LF=local.file RF=remote.file2 MWAIT
    FUSSEND IPADDR=190.190.190.102 LF=local.file RF=remote.file3 MWAIT

In this example, three transfers are queued and are ready to be waited on. The following command defines the Platform Server to wait on the three transfers to complete, scan the status in every five seconds, write status updates, stop scanning the requests after 300 seconds, and then purges the uncompleted requests.

    FUSWAIT INTERVAL=5 SAY TIMEOUT=300 PURGE

The output of this example is as follows:

    TRANSACTION=IA21500005 STATUS=ACTIVE   RECORD=000023072 BYTES=001868639
    TRANSACTION=IA21500006 STATUS=ACTIVE   RECORD=000012242 BYTES=000991439
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500005 STATUS=COMPLETE RECORD=000025603 BYTES=002073701
    TRANSACTION=IA21500006 STATUS=ACTIVE   RECORD=000025087 BYTES=002031839
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500006 STATUS=COMPLETE RECORD=000025603 BYTES=002073701
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TRANSACTION=IA21500007 STATUS=INACTIVE RECORD=000000000 BYTES=000000000
    TIMEOUT EXPIRED WAITING FOR TRANSACTION TO COMPLETE
    TRANSACTION IA21500007  PURGED FROM QUEUE DUE TO PURGE PARAMETER
    ***Fusion retcode.......=  4
    ***Total Transfers......=  03
    ***Completed transfers..=  02
    ***Successful transfers.=  02
    ***Failed transfers.....=  00
    ***Purged transfers.....=  01
    FUSWAIT RC==>  4 Partial success of MFT Platform Server MWAIT

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.