Point and click queries.

            Any data source.

                        Any computer.

                                    Data server.

                                                Free.


      Mainframe Data Sources
                ( Please scroll down. )

Disclaimer

Brand names are addressed only as a service to CoreReader users. See the source specifics page for details.

To add to these notes or to add your favorite data source, see instructions on the source specifics page.

Source

See below.

Running With Mainframes

Although IBM refused to cooperate with the CoreReader project, CoreReader has been successfully connected to IBM mainframes.

The mainframe example that you find in CoreReader's connection screen is a minimal generic connection. The example provides required information, but much more can be used when connecting and much more may be required for a particular connection. The easiest way would be to use a DSN if one is handy.

The data socket determines how well a mainframe can be made to behave like a database server. In some cases, such as when accessing VSAM data sets, contextual mapping makes SQL problematic, so be prepared for surprises.

Behind the scenes, mainframe connections are extremely complex. For example, the connection must use APPC and LU6.2 in addition to the standard TCP/IP. If a native data socket is not on your machine, then try the Ms. SNA provider. Don't bother with MSDASQL because it does not speak all of the required protocols.

Since CoreReader is so forgiving, feel free to experiment. Mainframe connections are not easy.

A word of caution: Take care that you do not ask CoreReader to bring a mainframe-sized data table to your PC because he will do it and you may spend the following week cleaning up the mess.

CoreReader's ability to abstract may be particularly useful in mainframe work. Refer to the Database Abstraction section of the documentation for details.

This web site is maintained with Notepad.

Copyright 2001 - 2010 John Ragan.