Changing from SNA to TCPIP with CA XCOM for AS/400

Products

• XCOM Data Transport

Issue/Introduction

How to Change from SNA to TCPIP with CA XCOM for AS/400 

Environment

Release:
Component: XCAS4R

Resolution

Overview of Migrating to TCPIP

1. Make sure that the TCPIP LOCAL host name is defined on the AS/400.
   Use CFGTCP - Option 12 - The fully qualified hostname is required such as 141.202.187.20 USPRGP9D.CA.COM.
   The actual OPTION number may differ according to different versions of the operating system.
   
   
2. Find out the TCPIP hostname or address of any partners. Find out whether they are using the default port of 8044 for XCOM or another port.
   
   
3. Create new remote system profiles or modify the ones you have. You can run both SNA and TCPIP transfers, so you may want to create new remote system profiles if you are going to be running both for a while.
   
   For TCPIP, fill in the following fields:
   TCP/IP Remote host identifier - hostname or ip address
   TCP/IP remote port - defaults to 8044 - the default is usually OK
   You can leave the other TCPIP parameters at the default values.
   NOTE: Set REMOTE location name to *BLANK
   
   
4. Modify any CL's
   Remove RMTLOC and RMTNETID - SNA parameters
   Add TCPRMTHOST which can be set to either the TCPIP hostname or address.
   Add TCPRMTPORT and set it to the port name - needed only if the remote XCOM partner is NOT using the default 8044 - The person responsible for support for the partner will need to tell you this.
   
   
5. If you will be receiving remotely initiated TCPIP transfers, you will need to bring up XCOM TCPIP Principal and Agent(s). Review the parameters in the manual that you can specify when issuing this command if you will be running concurrent transfers with TCPIP.
   

   STRXCOMTCP/STRXCTCP (stop it with STPXCOMTCP/STPXCTCP)

   The user issuing the STRXCOMTCP command should be given authority to the IBM programs QWTSETP, QSYGETPH and QSYRLSPH and must also have *ALLOBJ special authority.
   
   
   

Additional Information

1. For additional information, also refer to this technical document:
   
   Increasing the Number of Simultaneous Incoming TCPIP Transfers