Sending an Indirect Transfer from XCOM for AS/400 (Store & Forward)

Products

• XCOM Data Transport
• XCOM Data Transport - Windows
• XCOM Data Transport - Linux PC
• XCOM Data Transport - z/OS

Issue/Introduction

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 SENDJOB, SENDFILE and SENDREPORT are all supported. RECEIVE is not supported.

 

Environment

Release:
Component: XCAS4

Resolution

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

On the AS/400,

Create a profile (ADDRMTSYS or CHGRMTSYS) with the following keywords and save it. Specify it when you want to do an indirect transfer:

• DEST should equal xx where xx is the same name specified for the WRITER in the dest member below.
  
  
• INTSYS 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 How XCOM Store and Forward Works.