USING STARSQL WITH IBM APPC NETWORKING SERVICES FOR WINDOWS STARSQL 1.04 September 19, 1995 Copyright 1995, StarWare Connectivity Software, Inc IBM APPC Networking Services for Windows (NS/Windows) is a complete APPC implementation for a single Windows-based PC. It can be used on a variety of LAN and other interfaces, including ethernet, token ring, SDLC, and twinax. In addition, it can use MPTN (Multiprotocol Transport Networking) architecture to transport APPC program information (which StarSQL uses) to an IBM host computer via a TCP/IP link. To use this feature, IBM AnyNet APPC over TCP/IP for Windows and a supported TCP/IP stack must be installed on the PC. The host computer must also support AnyNet. AnyNet support is standard in OS/400 v3r1 and AIX SNA Server/6000 v2.1; it is an option available for mainframe & OS/2 computers. Procedure for setting up a NS/Windows: * If you will be using a LAN connection, install IBM LAN Support (Windows 3.1) or MSDLC (Windows for Workgroups). * Install NS/Windows. * Configure NS/Windows with the "Configure" application - you will need to specify: Step 1) Local LU (e.g. "NETID.PC1"). Be sure to use a fully qualified (netid.lu) name here if you are using "auto-create controller" on an AS/400; otherwise the created controller description on the AS/400 will have a non-intuitive name like "C00000". link (e.g. LAN) Step 2) Link Definitions - e.g. token ring address of the host Note that if you are using ethernet, you will need to perform a bit- reversal calculation on the address. Step 3) Networking Services Definitions Modes - create modes as necessary Side Information - create a Side Information record that will be used by StarSQL e.g. Symbolic Destination Name HOSTNAME Partner LU NETID.HOSTNAME Mode QPCSUPP TP 07C4C2F2 Step 4) DONE - make sure you select this button to save your changes. OPERATION: 1. Use AutoStart Networking Services or Advanced Operations/Initialize LU to start NS/Windows. 2) Verify APPC connection to the Symbolic Destination Name entered in step 3 above - e.g. with APING. Even if APINGD is not installed on your host computer, this is a good test for connectivity - if you get the error "TP Not Recognized" then you know that you have a connection to the host. 3) Configure a StarSQL datasource: a) select "IBM APPC NS/Windows" as the Network type. b) Select Setup... and enter the Symbolic Destination Name entered in the side information record in step 3 above. Note that in this beta version of StarSQL, selecting HELP at this screen will bring up help information for Novell NetWare for SAA rather than NS/Windows; this will be fixed. HINTS FOR AnyNet SETUP: The following hints show the process of configuring AnyNet between NS/Windows and OS/400. Similar procedures would be used for connecting to other host platforms. Documentation: AnyNet setup for OS/400 v3r1 is documented in Appendix A of the Communications Configuration reference (SC41-3401). AnyNet APPC over TCP/IP for Windows has a single manual ("IBM AnyNet Guide to APPC over TCP/IP Version 1.0 for Windows SV40-0215-00) in Softcopy format on the distribution disks. Domain Name Server: Add new host name entries on your TCP/IP Domain Name Server to represent the AnyNet nodes - these are likely to be alias entries (CNAME) for the existing hostnames for your host and PC. Domain Name Services typically run on a UNIX host; if you do not have a Domain Name Server, you will need to add entries in the Hosts tables on both the host and the PC. The TCP hostnames should be of the form "HOST.NETID" (e.g. as400.appn & pc.appn). AnyNet will look for nodes with names like "as400.appn.yourdomain.com" on the AS/400: DSPNETA - verify that "Use AnyNet" is enabled. Note that enabling AnyNet support may reduce performance on all socket applications on the AS/400. Verify that TCP/IP is configured & working (e.g. make sure that host name resolution is working) CRTCTLAPPC - create APPC controller to be used by all APPC over TCP AnyNet connections. e.g "ANYNETCTL" type *ANYNW CP name TCP1 (arbitrary name - only used by APPN remote location list) Edit APPN Remote Location List: add entry: Remote location = PC Remote CP = TCP1 ON the NS/WINDOWS CLIENT: We used Windows for Workgroups & the Microsoft 3.11a TCP/IP stack. Make sure that TCP/IP is working - e.g. ftp or telnet to "as400.appn.yourdomain.com" (or just "as400.appn") The only configuration information related to the AnyNet product itself is the SNA Domain name suffix, which is set in AUTOEXEC.BAT: SNASUFFIX in AUTOEXEC.BAT = yourdomain.com Also check that the path statement in AUTOEXEC.BAT added by the AnyNet install (for \ANYNET\BIN) is placed correctly in AUTOEXEC.BAT. NS/WINDOWS configuration: Start "Configure" application Step 1: Local LU = APPN.PC connection type = MPTN (automatically set by AnyNet install) Step 2: Link Name = Anylink (default) Step 3: create mode if necessary - e.g. mode QPCSUPP added Side Info record: Sym Dest AS400 Partner LU APPN.AS400 Mode QPCSUPP TP 07C4C2F2 Step 4: DONE - select this button to save your changes TO TEST: Start "Advanced Operations" application LU Control - Intialize Connections: LU Services Activate partner LU = APPN.AS400 mode = QPCSUPP should connect to the AS/400 in AS/400 QSYSOPR message queue: Communications device PC was allocated to subsystem QCMN. APING or ATELL- you can run these (use symbolic name "AS400" for destination) they will fail if the APINGD or ATELLD TP is not present on the AS/400, but it tests communications with the AS/400. in AS/400 QSYSOPR message queue: Program start request received on communications device PC was rejected with reason codes 605, 1502. Hint: the Message Log ("View Message Log" in the NS/Win program group) contains information useful for tracking down problems.