How to encapsulate SNA over TCP

How to encapsulate SNA over TCP

The SAVRST* commands are an awesome tool for moving libraries and objects such as files and source. However, if you have moved from Token Ring to TCP/IP, you have lost the functionality of all of the SNA commands -- unless you configure your system to encapsulate SNA over TCP. What is really nice about this is you don't have to manage distribution queues or manage directory entries for all of the users. As always security concerns are relevant.

There are five main points that have to be configured in order to configure SNA over TCP/IP. These steps must be true/configured on both the host and the target system.

1. You must have 5722SS1 option 22 "ObjectConnect" on your system.

2. Your network attributes must have "Allow AnyNet support....*YES"

3. You must have a host entry on the host system, for the target system, that has a valid IP address and route to the target system with a host name of XXX.SNA.IBM.COM (XXXX =System name of the target system)

4. You must create an APPC controller on the host and target system. CRTCTLAPPC CTLD(XXXX) LINKTYPE(*ANYNW) RMTNETID(SYSTEMB) RMTCPNAME(ANYNET)TEXT('AnyNet connection to system SYSTEMB')
XXXX = the controller name
RMTNETID = the remote systems name
RMTCPNAME = the remote control point name

I named mine ANYNET. This will be used on both the target and host system.

5. You have to create or modify the Remote Configuration list for QAPPNRMT.

    Requires Free Membership to View

    Login

    Register today to access targeted resources from our editorial writers and independent industry experts including news, tips, and advice to help you do your job more efficiently and effectively. Stay informed on the hottest topics and biggest challenges faced by IT professionals working with iSeries products and services.

    By submitting your registration information to Search400.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of Search400.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

CRTCFGL TYPE(*APPNRMT) TEXT('AnyNet TCP Connection list') <<ENTER>>

REMOTE LOCATION = the remote systems name.

REMOTE NET ID: APPN

LOCAL LOCATION: The local systems name is found by issuing a DSPNETA.

REMOTE CONTROL POINT: Is the same control point that was used when creating the controller.

CONTROL POINT NET ID: APPN

Naturally, both the host and the target systems must be configured this way. If you e-mail me, I have a nice Word document that would walk you through these steps in better detail.

==================================
MORE INFORMATION ON THIS TOPIC
==================================

The Best Web Links: Tips, tutorials and more.

Visit the ITKnowledge Exchange and get answers to your systems management questions fast.

Read this Search400.com Featured Topic: Take control of your iSeries.

Ask the Experts yourself: Our systems management gurus are waiting to answer your technical questions.


This was first published in February 2005

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

Back to top