Showing posts with label toa. Show all posts
Showing posts with label toa. Show all posts

Wednesday, March 7, 2012

Connecting to a Datacom DB data source

I recently installed SQL Server 2000 Reporting Services and connect to
a number of disparate data sources -- except a CA Datacom/DB
(mainframe) data source.
Any ideas on how to connect to the mainframe data so that it has the
look and feel of an ODBC database? And if so, what are the products
involved?
Thanks,
RBollinger
I'm using CA-Visual Express to hit Datacom through the Client ODBC Driver. It's a bit tricky with the authorities. You have to make sure they're set at the ODBC level if you want more than read-only access. We've not quite worked out the details on this yet. However, you can import any datacom table through the same ODBC driver using MS Access and perform all queries through there. (Not graceful, granted, but it does work!)
Good Luck,
rrowe.

Connecting to a Datacom DB data source

I recently installed SQL Server 2000 Reporting Services and connect to
a number of disparate data sources -- except a CA Datacom/DB
(mainframe) data source.
Any ideas on how to connect to the mainframe data so that it has the
look and feel of an ODBC database? And if so, what are the products
involved?
Thanks,
RBollingerI'm using CA-Visual Express to hit Datacom through the Client ODBC
Driver. It's a bit tricky with the authorities. You have to make sure
they're set at the ODBC level if you want more than read-only access.
We've not quite worked out the details on this yet. However, you can
import any datacom table through the same ODBC driver using MS Access
and perform all queries through there. (Not graceful, granted, but it
does work!)
Good Luck,
rrowe.
rrowe
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message535356.html

Friday, February 10, 2012

Connect to SQL 6.5 from Win XP Pro

I need to create a system DSN SQL connection (Data Source) on my machine to
a server that is a domain controller in a different domain in preparation
for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5 SP6.
I have an account on that domain but I can't get authenticated even though I
have administrative privileges and we have a trusted connection between the
two domains. What am I doing wrong?
thanks
chuck
Charles,
Check the SQL 6.5 Servers authentication mode. In 6.5 it can be set to
Standard, Integrated, or Mixed. Authentication using trusted connections
will fail if it's set to Standard.
Jon Jahren
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.co m...
> I need to create a system DSN SQL connection (Data Source) on my machine
to
> a server that is a domain controller in a different domain in preparation
> for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5
SP6.
> I have an account on that domain but I can't get authenticated even though
I
> have administrative privileges and we have a trusted connection between
the
> two domains. What am I doing wrong?
> thanks
> chuck
>
|||If by C# program, you mean a managed program using datasets, datareaders and
the like; I doubt that you will be able to do so for SQL Server 6.5; as the
..NET environment doesn't offer support for ODBC or OLEDB drivers version 2.5
and less. (I'm not sure about the exact number version, however SQL 6.5 is
quite probably older than the minimum requirement for an SQL-Server OLEDB
driver.)
However, if you intention is to use ADO and interoperability, then of course
you will have no problem.
S. L.
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.co m...
>I need to create a system DSN SQL connection (Data Source) on my machine to
>a server that is a domain controller in a different domain in preparation
>for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5 SP6.
>I have an account on that domain but I can't get authenticated even though
>I have administrative privileges and we have a trusted connection between
>the two domains. What am I doing wrong?
> thanks
> chuck
>
|||Oups!
After verification, I'm wrong. The framework 1.1 now allows connection to
ODBC and SQL-Server 6.5. See:
http://www.able-consulting.com/dotne...anagedProvider
S. L.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:ejszvxayEHA.2540@.TK2MSFTNGP09.phx.gbl...
> If by C# program, you mean a managed program using datasets, datareaders
> and the like; I doubt that you will be able to do so for SQL Server 6.5;
> as the .NET environment doesn't offer support for ODBC or OLEDB drivers
> version 2.5 and less. (I'm not sure about the exact number version,
> however SQL 6.5 is quite probably older than the minimum requirement for
> an SQL-Server OLEDB driver.)
> However, if you intention is to use ADO and interoperability, then of
> course you will have no problem.
> S. L.
> "Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
> news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.co m...
>

Connect to SQL 6.5 from Win XP Pro

I need to create a system DSN SQL connection (Data Source) on my machine to
a server that is a domain controller in a different domain in preparation
for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5 SP6.
I have an account on that domain but I can't get authenticated even though I
have administrative privileges and we have a trusted connection between the
two domains. What am I doing wrong?
thanks
chuckCharles,
Check the SQL 6.5 Servers authentication mode. In 6.5 it can be set to
Standard, Integrated, or Mixed. Authentication using trusted connections
will fail if it's set to Standard.
Jon Jahren
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.com...
> I need to create a system DSN SQL connection (Data Source) on my machine
to
> a server that is a domain controller in a different domain in preparation
> for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5
SP6.
> I have an account on that domain but I can't get authenticated even though
I
> have administrative privileges and we have a trusted connection between
the
> two domains. What am I doing wrong?
> thanks
> chuck
>|||If by C# program, you mean a managed program using datasets, datareaders and
the like; I doubt that you will be able to do so for SQL Server 6.5; as the
.NET environment doesn't offer support for ODBC or OLEDB drivers version 2.
5
and less. (I'm not sure about the exact number version, however SQL 6.5 is
quite probably older than the minimum requirement for an SQL-Server OLEDB
driver.)
However, if you intention is to use ADO and interoperability, then of course
you will have no problem.
S. L.
"Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.com...
>I need to create a system DSN SQL connection (Data Source) on my machine to
>a server that is a domain controller in a different domain in preparation
>for a C# program I'm writing. It is running NT 4.0 server with SQL 6.5 SP6.
>I have an account on that domain but I can't get authenticated even though
>I have administrative privileges and we have a trusted connection between
>the two domains. What am I doing wrong?
> thanks
> chuck
>|||Oups!
After verification, I'm wrong. The framework 1.1 now allows connection to
ODBC and SQL-Server 6.5. See:
r" target="_blank">http://www.able-consulting.com/dotn...rovide
r
S. L.
"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:ejszvxayEHA.2540@.TK2MSFTNGP09.phx.gbl...
> If by C# program, you mean a managed program using datasets, datareaders
> and the like; I doubt that you will be able to do so for SQL Server 6.5;
> as the .NET environment doesn't offer support for ODBC or OLEDB drivers
> version 2.5 and less. (I'm not sure about the exact number version,
> however SQL 6.5 is quite probably older than the minimum requirement for
> an SQL-Server OLEDB driver.)
> However, if you intention is to use ADO and interoperability, then of
> course you will have no problem.
> S. L.
> "Charles MacLean" <charlesmaclean@.sbcglobal.net> wrote in message
> news:HjQkd.7644$L92.1112@.newssvr16.news.prodigy.com...
>