Re: Emulator Interface with Win2k

Now you're talking.  These and other technical issues will help me in
selecting from the usual suspect of Emulators. Not forgetting Win2k.

Dare

----- Original Message -----
From: "Vernon Hamberg" <vhamberg@attbi.com>
To: <midrange-l@midrange.com>
Sent: Wednesday, March 20, 2002 1:54 PM
Subject: Re: Emulator Interface with Win2k


> Every driver has differing capabilities. Seems to me that CA's OLE/DB
> driver can only return single result sets, where HiT's can handle multiple
> ones. It may have changed by now. So these will need to be determined. But
> then, MS's OLE/DB over ODBC could handle multiple sets. But it had more
> overhead.
>
> TMTOWTDI - there's more than one way to do it
>
> At 01:47 PM 3/20/02 -0500, you wrote:
> >Are there limitations or issues with VB programming, Operating system,
> >Specific Emulation package, ODBC drivers and OLE/dB drivers.  If I
remember
> >correctly CA had issues with OLE/dB drivers etc.
> >
> >Dare
> >
> >----- Original Message -----
> >From: "Vernon Hamberg" <vhamberg@attbi.com>
> >To: <midrange-l@midrange.com>
> >Sent: Wednesday, March 20, 2002 1:33 PM
> >Subject: Re: Emulator Interface with Win2k
> >
> >
> > > It's been awhile, but here goes.
> > >
> > > The ODBC driver you use should handle getting to the server. Are you
using
> > > TCP/IP now? The server names should be available, host tables, DNS,
etc.
> > >
> > > VB could care less about connection protocols, just things like
> >authentication.
> > >
> > > Take alook at you ODBC Admin control panel app. It should show you
some
> > > options like protocol, server name, etc., and these are what you will
need
> > > to set up. Then it's easy. <g>
> > >
> > > At 01:12 PM 3/20/02 -0500, you wrote:
> > > >Isn't there an issue in addressing and configuration when you using
ODBC
> >and
> > > >VB.
> > > >
> > > >Dare
> > > >
> > > >----- Original Message -----
> > > >From: "Vernon Hamberg" <vhamberg@attbi.com>
> > > >To: <midrange-l@midrange.com>
> > > >Sent: Wednesday, March 20, 2002 1:06 PM
> > > >Subject: RE: Emulator Interface with Win2k
> > > >
> > > >
> > > > > I agree. Go with native TCP/IP. You get more options, all the
usual
> > > > > suspects, like WRQ Reflection, Personal Communications, Synapse,
> >Client
> > > > > Access, NetManage Rumba, various ODBC and OLE/DB drivers, etc.
> > > > >
> > > > > What benefit is there with SNA Server, other than connectivity?
> > > > >
> > > > > At 10:01 AM 3/20/02 -0800, you wrote:
> > > > > >Dare,
> > > > > >
> > > > > >In this day and age, an SNA gateway represents a huge overhead
with
> > > > > >unnecessary complexity.  Scrub the hard disk and set it up as a
Linux
> > > > > >play pen!
> > > > > >
> > > > > >You'll find your network easier to manage if you remove the
gateway
> >and
> > > > > >go direct to the AS/400.
> > > > > >
> > > > > >IMHO
> > > > > >
> > > > > >Best Regards
> > > > > >
> > > > > >Fritz Hayes
> > > > > >Atwater Associates
> > > > > >
> > > > > ><snip>
> > > > > >|
> > > > > >| I forgot about my SNA Server.  All client pass through this
server
> >to
> > > > > >get
> > > > > >| to
> > > > > >| the AS/400
> > > > > >|
> > > > > >
> > > > > >_______________________________________________
> > > > > >This is the Midrange Systems Technical Discussion (MIDRANGE-L)
> >mailing
> > > >list
> > > > > >To post a message email: MIDRANGE-L@midrange.com
> > > > > >To subscribe, unsubscribe, or change list options,
> > > > > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > > > >or email: MIDRANGE-L-request@midrange.com
> > > > > >Before posting, please take a moment to review the archives
> > > > > >at http://archive.midrange.com/midrange-l.
> > > > >
> > > > > _______________________________________________
> > > > > This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
> > > >list
> > > > > To post a message email: MIDRANGE-L@midrange.com
> > > > > To subscribe, unsubscribe, or change list options,
> > > > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > > > or email: MIDRANGE-L-request@midrange.com
> > > > > Before posting, please take a moment to review the archives
> > > > > at http://archive.midrange.com/midrange-l.
> > > > >
> > > >
> > > >_______________________________________________
> > > >This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
> >list
> > > >To post a message email: MIDRANGE-L@midrange.com
> > > >To subscribe, unsubscribe, or change list options,
> > > >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > >or email: MIDRANGE-L-request@midrange.com
> > > >Before posting, please take a moment to review the archives
> > > >at http://archive.midrange.com/midrange-l.
> > >
> > > _______________________________________________
> > > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> >list
> > > To post a message email: MIDRANGE-L@midrange.com
> > > To subscribe, unsubscribe, or change list options,
> > > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > > or email: MIDRANGE-L-request@midrange.com
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> > >
> >
> >_______________________________________________
> >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> >To post a message email: MIDRANGE-L@midrange.com
> >To subscribe, unsubscribe, or change list options,
> >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> >or email: MIDRANGE-L-request@midrange.com
> >Before posting, please take a moment to review the archives
> >at http://archive.midrange.com/midrange-l.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>