| Author |
Message |
Ahmed Ezz
Guest
|
 Posted:
Sun Aug 28, 2005 4:51 pm Post subject:
DB2 Access for VSE/ESA |
|
|
ok am trying to connect to DB2/VSE 7.2.0 on a client mainframe the problem
that we don't have an option on the data source wizard for DB2/VSE just
DB2/6000 and DB2/VMS is there a patch or something am missing here
--
--
Regards
Ahmed Ezz |
|
| Back to top |
|
 |
Neil Pike
Guest
|
| Posted:
Mon Aug 29, 2005 8:53 am Post subject:
Re: DB2 Access for VSE/ESA |
|
|
Ahmed - I'd just try choosing DB2/MVS
| Quote: | ok am trying to connect to DB2/VSE 7.2.0 on a client mainframe the problem
that we don't have an option on the data source wizard for DB2/VSE just
DB2/6000 and DB2/VMS is there a patch or something am missing here
|
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP |
|
| Back to top |
|
|
Ahmed Ezz
Guest
|
| Posted:
Mon Aug 29, 2005 12:52 pm Post subject:
Re: DB2 Access for VSE/ESA |
|
|
i tried the DB2/MVS but it keep giving me error saying that the database
didn't understand a paramter or value that was pased with DB2 error
sqlstate: HY000 SQLCODE: -385
--
--
Regards
Ahmed Ezz
"Neil Pike" wrote:
| Quote: | Ahmed - I'd just try choosing DB2/MVS
ok am trying to connect to DB2/VSE 7.2.0 on a client mainframe the problem
that we don't have an option on the data source wizard for DB2/VSE just
DB2/6000 and DB2/VMS is there a patch or something am missing here
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
|
|
|
| Back to top |
|
|
Neil Pike
Guest
|
| Posted:
Mon Aug 29, 2005 4:52 pm Post subject:
Re: DB2 Access for VSE/ESA |
|
|
Ahmed,
That means the packages required for the HIS driver to work are not installed
on the DB2 instance on the mainframe you're connecting to. See below for some
details and how to install it - extracted from the supplied doco.
----------------
Creating Packages for Use With DB2
The OLE DB Provider for DB2 and the ODBC Driver for DB2 are implemented as IBM
Distributed Relational Database Architecture (DRDA) Application Requesters.
Both the OLE DB Provider for DB2 and the ODBC Driver for DB2 use packages to
issue SQL statements and call DB2 stored procedures. There is a
provider-specific property that the OLE DB Provider for DB2 and the ODBC Driver
for DB2 use to identify a location in which to create and store DB2 packages.
Both the OLE DB Provider for DB2 and the ODBC Driver for DB2 will create
packages dynamically in the location to which the user points using the Package
Collection property or configuration parameter. For OLE DB, this location may
be configured using the Connection and Advanced tabs using Microsoft Data Link
or can be passed as part of the connection string as an attribute keyword and
argument. For the ODBC Driver for DB2, this Package Collection field can be
configured on the Target Database tab of the ODBC Data Source Administrator.
There are two package creation options:
The OLE DB Provider for DB2 and the ODBC Driver for DB2 will auto-create one
package for the currently used isolation level at run-time if no package
already exists. This auto-create process may fail if the user account does not
have authority to create packages.
An administrator or user can manually creates all four packages (five packages
on DB2/400) for use with all isolation levels and for use by all users
(PUBLIC). Host Integration Server 2000 includes a utility program for use by
users with appropriate administrative privilege for this purpose.
However, some users may not have the security level when manually creating
packages to GRANT authority to the packages to other users (PUBLIC, for
example). This can be a problem if two or more users with different user IDs
try to access a single collection of packages. The first user that created the
packages will have access to the packages, but the second user likely will not.
The Host Integration Server 2000 CD-ROM includes a program for use by an
administrator to create packages. This tool can be run using a privileged User
ID to create packages in collections accessed by multiple users. The Create
Packages for DB2 utility, CrtPkg.exe, is a GUI-based tool included with Host
Integration Server 2000 for creating packages for use with DB2. This tool is
installed in the System folder below the subdirectory where the Microsoft Host
Integration Server 2000 has been installed. The default location where this
tool is installed is the following:
Program Files\Microsoft HI Server\system\CrtPkg.exe
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP |
|
| Back to top |
|
|
Aaron Grady [MSFT]
Guest
|
| Posted:
Wed Aug 31, 2005 12:52 am Post subject:
Re: DB2 Access for VSE/ESA |
|
|
Actually....the -385 error means that the target host is telling us that a
parameter that we sent was not supported.
In fact, I hate to be the bearer of bad news, but the Ole DB Provider for
DB2, ODBC Driver for DB2, and Managed Provider for DB2 do not support
DB2/VSE (sometimes referred to as SQL/DS). While DB2/VSE supports the DRDA
protocol, apparently it is a back level version, and not current enough to
work with our provider. I do not believe this has changed, although I could
be wrong. Either way we do not test against DB2/VSE here and we do not
support it. At the moment there are no plans to add this support in the next
version of HIS. I'll be sure and pass along the feedback to the appropriate
people so that they know someone was asking about this suppport.
NOTE: Other features of HIS like Transaction Integrator do work against VSE.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server
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
"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.0000630d.1348163a@compuserve.com...
| Quote: | Ahmed,
That means the packages required for the HIS driver to work are not
installed
on the DB2 instance on the mainframe you're connecting to. See below for
some
details and how to install it - extracted from the supplied doco.
----------------
Creating Packages for Use With DB2
The OLE DB Provider for DB2 and the ODBC Driver for DB2 are implemented as
IBM
Distributed Relational Database Architecture (DRDA) Application
Requesters.
Both the OLE DB Provider for DB2 and the ODBC Driver for DB2 use packages
to
issue SQL statements and call DB2 stored procedures. There is a
provider-specific property that the OLE DB Provider for DB2 and the ODBC
Driver
for DB2 use to identify a location in which to create and store DB2
packages.
Both the OLE DB Provider for DB2 and the ODBC Driver for DB2 will create
packages dynamically in the location to which the user points using the
Package
Collection property or configuration parameter. For OLE DB, this location
may
be configured using the Connection and Advanced tabs using Microsoft Data
Link
or can be passed as part of the connection string as an attribute keyword
and
argument. For the ODBC Driver for DB2, this Package Collection field can
be
configured on the Target Database tab of the ODBC Data Source
Administrator.
There are two package creation options:
The OLE DB Provider for DB2 and the ODBC Driver for DB2 will auto-create
one
package for the currently used isolation level at run-time if no package
already exists. This auto-create process may fail if the user account does
not
have authority to create packages.
An administrator or user can manually creates all four packages (five
packages
on DB2/400) for use with all isolation levels and for use by all users
(PUBLIC). Host Integration Server 2000 includes a utility program for use
by
users with appropriate administrative privilege for this purpose.
However, some users may not have the security level when manually creating
packages to GRANT authority to the packages to other users (PUBLIC, for
example). This can be a problem if two or more users with different user
IDs
try to access a single collection of packages. The first user that created
the
packages will have access to the packages, but the second user likely will
not.
The Host Integration Server 2000 CD-ROM includes a program for use by an
administrator to create packages. This tool can be run using a privileged
User
ID to create packages in collections accessed by multiple users. The
Create
Packages for DB2 utility, CrtPkg.exe, is a GUI-based tool included with
Host
Integration Server 2000 for creating packages for use with DB2. This tool
is
installed in the System folder below the subdirectory where the Microsoft
Host
Integration Server 2000 has been installed. The default location where
this
tool is installed is the following:
Program Files\Microsoft HI Server\system\CrtPkg.exe
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
|
|
|
| Back to top |
|
|
Neil Pike
Guest
|
| Posted:
Wed Aug 31, 2005 8:53 am Post subject:
Re: DB2 Access for VSE/ESA |
|
|
Thanks Aaron.
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP |
|
| Back to top |
|
|
Bob
Guest
|
| Posted:
Mon Sep 05, 2005 12:52 pm Post subject:
Re: DB2 Access for VSE/ESA |
|
|
Another alternative is StarQuest's StarSQL, which does work with DB2/VSE.
http://www.starquest.com/Productfolder/starsql.html
Bob
"Aaron Grady [MSFT]" <aagrady@online.microsoft.com> a écrit dans le messaoge
de news:OrFwW6brFHA.2228@TK2MSFTNGP10.phx.gbl...
| Quote: | Actually....the -385 error means that the target host is telling us that a
parameter that we sent was not supported.
In fact, I hate to be the bearer of bad news, but the Ole DB Provider for
DB2, ODBC Driver for DB2, and Managed Provider for DB2 do not support
DB2/VSE (sometimes referred to as SQL/DS). While DB2/VSE supports the DRDA
protocol, apparently it is a back level version, and not current enough to
work with our provider. I do not believe this has changed, although I
could
be wrong. Either way we do not test against DB2/VSE here and we do not
support it. At the moment there are no plans to add this support in the
next
version of HIS. I'll be sure and pass along the feedback to the
appropriate
people so that they know someone was asking about this suppport.
NOTE: Other features of HIS like Transaction Integrator do work against
VSE.
HTH,
--
Aaron Grady
MCSE + Internet, MCDBA, MCSD, MCAD.NET
SNA Server/Host Integration Server
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
"Neil Pike" <neilpike@compuserve.com> wrote in message
news:VA.0000630d.1348163a@compuserve.com...
Ahmed,
That means the packages required for the HIS driver to work are not
installed
on the DB2 instance on the mainframe you're connecting to. See below
for
some
details and how to install it - extracted from the supplied doco.
----------------
Creating Packages for Use With DB2
The OLE DB Provider for DB2 and the ODBC Driver for DB2 are implemented
as
IBM
Distributed Relational Database Architecture (DRDA) Application
Requesters.
Both the OLE DB Provider for DB2 and the ODBC Driver for DB2 use
packages
to
issue SQL statements and call DB2 stored procedures. There is a
provider-specific property that the OLE DB Provider for DB2 and the ODBC
Driver
for DB2 use to identify a location in which to create and store DB2
packages.
Both the OLE DB Provider for DB2 and the ODBC Driver for DB2 will create
packages dynamically in the location to which the user points using the
Package
Collection property or configuration parameter. For OLE DB, this
location
may
be configured using the Connection and Advanced tabs using Microsoft
Data
Link
or can be passed as part of the connection string as an attribute
keyword
and
argument. For the ODBC Driver for DB2, this Package Collection field can
be
configured on the Target Database tab of the ODBC Data Source
Administrator.
There are two package creation options:
The OLE DB Provider for DB2 and the ODBC Driver for DB2 will auto-create
one
package for the currently used isolation level at run-time if no package
already exists. This auto-create process may fail if the user account
does
not
have authority to create packages.
An administrator or user can manually creates all four packages (five
packages
on DB2/400) for use with all isolation levels and for use by all users
(PUBLIC). Host Integration Server 2000 includes a utility program for
use
by
users with appropriate administrative privilege for this purpose.
However, some users may not have the security level when manually
creating
packages to GRANT authority to the packages to other users (PUBLIC, for
example). This can be a problem if two or more users with different user
IDs
try to access a single collection of packages. The first user that
created
the
packages will have access to the packages, but the second user likely
will
not.
The Host Integration Server 2000 CD-ROM includes a program for use by an
administrator to create packages. This tool can be run using a
privileged
User
ID to create packages in collections accessed by multiple users. The
Create
Packages for DB2 utility, CrtPkg.exe, is a GUI-based tool included with
Host
Integration Server 2000 for creating packages for use with DB2. This
tool
is
installed in the System folder below the subdirectory where the
Microsoft
Host
Integration Server 2000 has been installed. The default location where
this
tool is installed is the following:
Program Files\Microsoft HI Server\system\CrtPkg.exe
Neil Pike. Protech Computing Ltd
Microsoft SNA/HIS MVP
|
|
|
| Back to top |
|
|
Walter
Guest
|
| Posted:
Wed Oct 05, 2005 4:51 pm Post subject:
RE: DB2 Access for VSE/ESA |
|
|
There is a partner solution from GT Software that will allow you to connect
to any datasource on a VSE platform.
http://www.gtsoftware.com/products/tcaccess.php
Hope this helps...
"Ahmed Ezz" wrote:
| Quote: | ok am trying to connect to DB2/VSE 7.2.0 on a client mainframe the problem
that we don't have an option on the data source wizard for DB2/VSE just
DB2/6000 and DB2/VMS is there a patch or something am missing here
--
--
Regards
Ahmed Ezz
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in