1 Mainframe Connectivity

2 Access to ViaSQL Access Server n ViaSQL Direct and ViaSQL Integrator n TCP/IP –easier to set up –less configurable n APPC (LU6.2 or SNA) –can be complicated –more performance potential n One ViaSQL Access Server transaction can accept both connection types

3 TCP/IP Requirements n OS/390 –IBM’s TCP/IP stack, v3r2 or later n ViaSQL Direct ODBC platform –Windows 95/98/NT/2000 –native TCP/IP stack n ViaSQL Direct JDBC platform –any Java platform –native TCP/IP stack n ViaSQL Integraotr –Windows NT/2000 –native TCP/IP stack

4 ViaSQL Access Server TCP/IP Configuration T C P / I P P A R A M E T E R S Listener Transaction ID MDIL Dedicated Terminal ID TCP* Initialization String TCPIP --- Port Assignments - Listening Service Port # Transid 5501 MDI 5502 MDI (and more -- up to 30 ports)

5 ViaSQL Listener Transaction n Installed automatically with ViaSQL Access Server (if TCP/IP was specified) –does not use IBM listener or the IBM listener configuration under CICS –can reside in same CICS region n Long-running CICS transaction n Listens on assigned ports, initiates CICS service transaction, passes connection on, returns to listening

6 ViaSQL Listener Transaction n Typically started and stopped with ViaSQL Access Server start/stop transactions n Must be running for ViaSQL Direct and Gateway clients to connect to Access Server

7 Dedicated Terminal ID n CICS terminals dedicated to ViaSQL –must be defined as “sequential” terminals –not shared by any other task / application –defined in TCT table (can’t use RDO) –limits the number of concurrent connections

8 Other TCP/IP Parameters n Initialization string –identifies TCP/IP address space –for IBM TCP/IP, must be TCPIP n Listener port # –port numbers assigned to ViaSQL listener n Service transid –CICS transaction(s) assigned to ViaSQL Access Server

9 TCP/IP Setup — Other End n ViaSQL LAN component opens a socket to ViaSQL Access Server listener transaction –specify IP address of OS/390 platform –specify port number assigned to desired ViaSQL Access Server listener transaction (MDIL) n Same for: –ViaSQL Direct ODBC Driver –ViaSQL Direct JDBC Driver –ViaSQL Gateway

10 TCP/IP Resources n ViaSQL TCP/IP Guidelines –with TCP/IP Configuration Table

11 APPC Requirements n OS/390 –many VTAM and CICS definitions n ViaSQL Gateway –Microsoft SNA Server configured to match OS/390 setup –Most installations that use SNA will use the Gateway. There is a version of the ViaSQL Direct ODBC Driver that supports SNA, but the Microsoft SNA Server client must be installed on each client machine to support this. n Only MS SNA Server supported –No support for IBM or Netware SNA connectivity n ViaSQL Direct JDBC Driver not supported in an SNA environment (requires TCP/IP)

12 APPC Resources n ViaSQL APPC Guidelines –with APPC Configuration Table n APPCTEST –tests APPC connectivity outside the ViaSQL software APPCTEST transaction in CICS supplied client program run from ViaSQL Gateway or ViaSQL Direct platform –helps isolate problems

13 Tech Support Recommendations n For each customer –get filled-out copy of APPC Configuration Table or TCP/IP Configuration Table –ensure APPCTEST is available on customer’s system n Get customer to document (print screens, etc.) all configuration –get copies n Read APPCTEST and troubleshooting sections of APPC Guidelines