| Author |
Message |
eb
Guest
|
 Posted:
Fri May 27, 2005 4:53 pm Post subject:
OLE DB access to VSAM data sets from SQL server DTS |
|
|
Our company is in the process of replacing mainframe system with AS400. Since
we are highly regulated, we have to make sure that we preserve data fo a long
time. For this reason we are going to move data from the mainframe into a
variety of databases, some of it will and in Microsoft SQL 2000.
I am currently exploring ways of moving data from VSAM files into SQL 2000.
Microsoft HIS 2004 Client looks promising since it installed the OLE DB
provider for AS400 and VSAM. Manly due to my inexperience I got stuck already
when trying to define a connection to the mainframe.
My first question is whether I need to install and configure HIS 2004 server
or I can take the shortcut and just use OLE DB provider for AS400 and VSAM
when creating a connection within DTS package? If I can go ahead and just
use OLE DB provider for AS400 and VSAM then I need to understand better how
to properly configure the connection itself.
I would appreciate if you could point me somewhere where I could find the
answers to the types of questions I listed before. Thank you very much for
your help in advance.
Regards,
EB |
|
| Back to top |
|
 |
Aaron Grady [MSFT]
Guest
|
| Posted:
Sat May 28, 2005 12:52 am Post subject:
Re: OLE DB access to VSAM data sets from SQL server DTS |
|
|
EB-
The Ole Db Provider for AS/400 and VSAM can only connect to a mainframe over
APPC/LU6.2 which means you are going to need to install the server portion
of HIS and configure a link service, connection, and LUs for your host
system. The Ole Db Provider for AS/400 and VSAM does support direct TCP/IP
connections, but only to AS/400 systems.
The following article is older, but still applies for most of the settings
in the provider:
219077 INF: Configuring Data Sources for the Microsoft OLE DB Provider for
http://support.microsoft.com/?id=219077
However, that article assumes you have already setup your connection to your
host system. What I would recommend is the following:
1. Install the SNA services portion of HIS
2. Start SNA Manager and define a new link service. A link service defines
your physical connection to the host. If your connection is over ethernet
you're going to need to use a DLC link service or our new IP-DLC link
service. If you're not sure, just define one for now anyway.
3. Once the link service is defined, run the Mainframe APPC/LU6.2 wizard and
go through to the point where you can print out some worksheets. You can use
those worksheets to talk with your Mainframe administrators to try and get
the right settings for the connection.
If you're not familiar with Mainframe connections and APPC applications
there will probably be a lot of unfamiliar terminology and information.
Hopefully your mainframe guys can guide you along, but they may also not be
familiar with the Windows terminology. If you run into problems, please post
back and we'll try and guide you along.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"eb" <eb@discussions.microsoft.com> wrote in message
news:931D5F78-2981-4498-944E-F41D968CE446@microsoft.com...
| Quote: | Our company is in the process of replacing mainframe system with AS400.
Since
we are highly regulated, we have to make sure that we preserve data fo a
long
time. For this reason we are going to move data from the mainframe into a
variety of databases, some of it will and in Microsoft SQL 2000.
I am currently exploring ways of moving data from VSAM files into SQL
2000.
Microsoft HIS 2004 Client looks promising since it installed the OLE DB
provider for AS400 and VSAM. Manly due to my inexperience I got stuck
already
when trying to define a connection to the mainframe.
My first question is whether I need to install and configure HIS 2004
server
or I can take the shortcut and just use OLE DB provider for AS400 and VSAM
when creating a connection within DTS package? If I can go ahead and just
use OLE DB provider for AS400 and VSAM then I need to understand better
how
to properly configure the connection itself.
I would appreciate if you could point me somewhere where I could find the
answers to the types of questions I listed before. Thank you very much
for
your help in advance.
Regards,
EB
|
|
|
| Back to top |
|
|
MjkFinder
Guest
|
| Posted:
Sat Jun 04, 2005 10:16 am Post subject:
Re: OLE DB access to VSAM data sets from SQL server DTS |
|
|
Dear Aaron Grady
Regarding to your reply, I am already installed and configured HIS2004 and
it works fine from VB.NET application program .
I have 1 Question, How can I use this connection thought DTS "MS SQL Server"
??
Your reply is highly appreciated
Thanks & Regards
MjkFinder
"Aaron Grady [MSFT]" wrote:
| Quote: | EB-
The Ole Db Provider for AS/400 and VSAM can only connect to a mainframe over
APPC/LU6.2 which means you are going to need to install the server portion
of HIS and configure a link service, connection, and LUs for your host
system. The Ole Db Provider for AS/400 and VSAM does support direct TCP/IP
connections, but only to AS/400 systems.
The following article is older, but still applies for most of the settings
in the provider:
219077 INF: Configuring Data Sources for the Microsoft OLE DB Provider for
http://support.microsoft.com/?id=219077
However, that article assumes you have already setup your connection to your
host system. What I would recommend is the following:
1. Install the SNA services portion of HIS
2. Start SNA Manager and define a new link service. A link service defines
your physical connection to the host. If your connection is over ethernet
you're going to need to use a DLC link service or our new IP-DLC link
service. If you're not sure, just define one for now anyway.
3. Once the link service is defined, run the Mainframe APPC/LU6.2 wizard and
go through to the point where you can print out some worksheets. You can use
those worksheets to talk with your Mainframe administrators to try and get
the right settings for the connection.
If you're not familiar with Mainframe connections and APPC applications
there will probably be a lot of unfamiliar terminology and information.
Hopefully your mainframe guys can guide you along, but they may also not be
familiar with the Windows terminology. If you run into problems, please post
back and we'll try and guide you along.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD
SNA Server/Host Integration Server 2000
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of any included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"eb" <eb@discussions.microsoft.com> wrote in message
news:931D5F78-2981-4498-944E-F41D968CE446@microsoft.com...
Our company is in the process of replacing mainframe system with AS400.
Since
we are highly regulated, we have to make sure that we preserve data fo a
long
time. For this reason we are going to move data from the mainframe into a
variety of databases, some of it will and in Microsoft SQL 2000.
I am currently exploring ways of moving data from VSAM files into SQL
2000.
Microsoft HIS 2004 Client looks promising since it installed the OLE DB
provider for AS400 and VSAM. Manly due to my inexperience I got stuck
already
when trying to define a connection to the mainframe.
My first question is whether I need to install and configure HIS 2004
server
or I can take the shortcut and just use OLE DB provider for AS400 and VSAM
when creating a connection within DTS package? If I can go ahead and just
use OLE DB provider for AS400 and VSAM then I need to understand better
how
to properly configure the connection itself.
I would appreciate if you could point me somewhere where I could find the
answers to the types of questions I listed before. Thank you very much
for
your help in advance.
Regards,
EB
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in