This is what happens when the vendor decides to indiscriminately
change the names, bring multiple client versions to do the same
thing. Everything in DB2 connect world is nothing but unnecessary
confusion. But once you configure one server, it may look friendly
until you find another variation.
The Data server driver for ODBC / CLI cannot connect to DB2 zOS
on the host directly without using a DB2 Connect or a valid
license. It can however connect to a LUW host.
Do you have a valid license for a DB2 Connect server, unlimited
edition. If so try and locate the db2connectactivate script
and push the license to the DB2 z/OS host.
You can add the license with db2licm -a
Then you need to catalog the data sources. The following assumes
direct connection to zOS host from the desktop.
At the windows command prompt, type db2cmd (may require elevated
privilege on desktop). This should bring up another command
db2 catalog tcpip node zosubsysanode remote
zossubsysa.myorg.com server tcpipport_for_zossubsysa
(remote is the domain name or ip address for sbsystem and server
is the TCPIP listening port)
db2 catalog db zossubsysa_location as zossubsysa at node
zossubsysanode authentication SERVER
Use display ddf on the zOS host to validate the values.
Validate the connection to the host by signing to DB2.
db2 connect to zossusbsysa user myuserid
If the validation is successful,
db2 catalog system odbc data source zossubsysa
Thereafter odbac apps will see zossubsysa as a database.
If you decide to connect to a DB2 Connect, then the database
will need to be cataloged on DB2 connect server first. You will
then create a DCS entry. The DCS entry is created with the
db2 CATALOG DCS DATABASE zossubsysa_location AS zossubsysa parms
If you go DB2 connect server route your node should point at DB2
Connect server and db alias should point at the dcs you created for
db2 connect server.
If you find it hard, please post your display ddf o/p and
indicate whether you are using db2 connect gateway server approach
or direct connection.