Sending an Indirect Transfer from Unix, LINUX or Windows (Store & Forward)

Document ID : KB000055540
Last Modified Date : 14/02/2018
Show Technical Document Details

Indirect transfers are useful when the two partners do not support the same protocol - TCPIP on one side and SNA on the other. They are also useful if the final destination is not always available. The intermediate platform in such transfers is the mainframe. Performing a Send job, Send file and Send Report are all supported. Receive is not supported.

This example shows how to start the transfer on the Unix, LINUX or Windows side, going through the mainframe to a final destination that supports only SNA. For information about initiating an indirect transfer from the AS/400, please see TEC392737.

On the initiating side (Unix, LINUX or Windows),

The .cnf file must specify:

  • REMOTE_SYSTEM=xx where xx is the same name specified for the WRITER in the dest member below.

  • XIDEST= which must indicate the mainframe ipname or address

  • PORT = (if not the default)

On the mainframe you must create and enable a destination member for the final destination. The dest member must contain:

    • WRITER = xx

    • LU = actual luname at the final destination

    • PSOPASS = Password for the final destination

    • PSOUSER = Userid for the final destination


For more information about how indirect transfers work, please see TEC329967.