mainframe connectivity

12
ViaSQL Mainframe Connectivity

Upload: elvin-mckenzie

Post on 17-Jan-2018

256 views

Category:

Documents


0 download

DESCRIPTION

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

TRANSCRIPT

Page 1: Mainframe Connectivity

ViaSQL

Mainframe Connectivity

Page 2: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 2

Access to ViaSQL Access Server

ViaSQL Direct and ViaSQL Integrator TCP/IP

– easier to set up– less configurable

APPC (LU6.2 or SNA)– can be complicated– more performance potential

One ViaSQL Access Server transaction can accept both connection types

Page 3: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 3

TCP/IP Requirements

VSE – Connectivity Systems Inc. TCP/IP stack

ViaSQL Direct ODBC platform– Windows 95/98/NT/2000– native TCP/IP stack

ViaSQL Direct JDBC platform– any JAVA platform– native TCP/IP stack

ViaSQL Integrator (Gateway) platform– Windows NT/2000– native TCP/IP stack

Page 4: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 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 MDILDedicated Terminal ID TCP*Initialization String 00

--- Port Assignments -Listening ServicePort # Transid5501 MDI5502 MDI2000000000000000(and more -- up to 30 ports)

Page 5: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 5

ViaSQL Listener Transaction

Installed automatically with ViaSQL Access Server (if TCP/IP was specified)

Long-running CICS transaction Listens on assigned ports, initiates CICS service transaction,

passes connection on, returns to listening

Page 6: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 6

ViaSQL Listener Transaction

Typically started and stopped with ViaSQL Access Server start/stop transactions

Must be running for TCP/IP connectivity

Page 7: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 7

Dedicated Terminal ID

CICS terminals dedicated to ViaSQL– must be sequential– defined in TCT table– limits the number of concurrent connections

Page 8: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 8

Other TCP/IP Parameters

Initialization string– Relates listener to tcp/ip partition. Default is 00

Listener port #– port numbers assigned to ViaSQL listener

Service transid– CICS transaction(s) assigned to ViaSQL Access Server

Page 9: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 9

TCP/IP Setup — Other End

Standard Windows 95/98/NT/2000 setup– specify IP address of VSE platform– specify port number assigned to desired ViaSQL Access Server

transaction Same for:

– ViaSQL Direct ODBC Driver– ViaSQL Direct JDBC Driver– ViaSQL Gateway

Page 10: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 10

TCP/IP Resources

ViaSQL TCP/IP Guidelines– with TCP/IP Configuration Table

Should be able to ping

Page 11: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 11

APPC Requirements

VSE– many VTAM and CICS definitions

Windows 95/98/NT/2000– Microsoft SNA Server configured to match VSE setup– MS SNA Server client required on each machine if using ViaSQL Direct

ODBC Driver.

Page 12: Mainframe Connectivity

Viaserv, Inc. Mainframe Connectivity – 12

APPC Resources

ViaSQL APPC Guidelines– with APPC Configuration Table

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