By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
437,586 Members | 2,347 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 437,586 IT Pros & Developers. It's quick & easy.

Bind Needed for remote remote PC Access to DB2 for OS/390

P: n/a
I am running DB2 V8.1 ESE client running on Windows XP Professional
configured to connect directly to DB2 V6.1.2 on OS/390. I can connect
to the OS/390 DB2 database (DB2 subsystem). But when I try to issue a
select, I get an error message saying:

"DB21034E The command was processed as an SQL statement because it
was not a valid Command Line Processor command. During SQL
processing it returned: SQL0805N Package
"DBD1DDF.NULLID.SQLC2E03.41414141414A4852" was not found.
SQLSTATE=51002."

When I try to bind the packages with the Client Configuration
Assistant, it says I do not have "Create In" authority (to create
packages on the remote OS/390 host):

"... does not have the privilege to perform operation "CREATE IN *" on
object "DBD1DDF.NULLID.SQLUBE00". SQLSTATE=42501."

My mainframe DBA says that if CREATE IN authority is given for the
bind, then the packages will overlay the existing packages on DB2 for
OS/390 which have been created for version 7 clients, and would cause
problems for everyone else. Anyone know is this is true and is there a
solution?
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Check the DB2 Connect User's Guide. Chapter 9 explains the requirements
for binding clients to a host database. It also specifies that multiple
service levels of a client product can be bound to the same database.

Perhaps your mainframe DBA needs to have a look at the manual(s).

Phil Sherman

Mark wrote:
I am running DB2 V8.1 ESE client running on Windows XP Professional
configured to connect directly to DB2 V6.1.2 on OS/390. I can connect
to the OS/390 DB2 database (DB2 subsystem). But when I try to issue a
select, I get an error message saying:

"DB21034E The command was processed as an SQL statement because it
was not a valid Command Line Processor command. During SQL
processing it returned: SQL0805N Package
"DBD1DDF.NULLID.SQLC2E03.41414141414A4852" was not found.
SQLSTATE=51002."

When I try to bind the packages with the Client Configuration
Assistant, it says I do not have "Create In" authority (to create
packages on the remote OS/390 host):

"... does not have the privilege to perform operation "CREATE IN *" on
object "DBD1DDF.NULLID.SQLUBE00". SQLSTATE=42501."

My mainframe DBA says that if CREATE IN authority is given for the
bind, then the packages will overlay the existing packages on DB2 for
OS/390 which have been created for version 7 clients, and would cause
problems for everyone else. Anyone know is this is true and is there a
solution?


Nov 12 '05 #2

P: n/a
Philip Sherman <ps******@ameritech.net> wrote in message news:<mU*****************@newssvr17.news.prodigy.c om>...
Check the DB2 Connect User's Guide. Chapter 9 explains the requirements
for binding clients to a host database. It also specifies that multiple
service levels of a client product can be bound to the same database.

Perhaps your mainframe DBA needs to have a look at the manual(s).

Phil Sherman

OK, I got the bind problem solved and I can connect and do certain
funtions (select, etc). But when I try an export (of an DB2 OS/390
table) from the version 7.2 or version 8.1 DB2 client, I get an error
message saying that the function (export) is not supported with a down
level server (DB2 for OS/390 version 6.2).

Has anyone exported in IXF format from DB2 for OS/390 6.2 to a DB2
Windows client (version 7 or 8)?
Nov 12 '05 #3

P: n/a
Ian
Mark wrote:
Philip Sherman <ps******@ameritech.net> wrote in message news:<mU*****************@newssvr17.news.prodigy.c om>...
Check the DB2 Connect User's Guide. Chapter 9 explains the requirements
for binding clients to a host database. It also specifies that multiple
service levels of a client product can be bound to the same database.

Perhaps your mainframe DBA needs to have a look at the manual(s).

Phil Sherman


OK, I got the bind problem solved and I can connect and do certain
funtions (select, etc). But when I try an export (of an DB2 OS/390
table) from the version 7.2 or version 8.1 DB2 client, I get an error
message saying that the function (export) is not supported with a down
level server (DB2 for OS/390 version 6.2).

Has anyone exported in IXF format from DB2 for OS/390 6.2 to a DB2
Windows client (version 7 or 8)?


You need to configure DB2 Connect properly (i.e. set up the DCS
directory properly). It sounds like you've defined the connection as
though it's running on DB2 UDB for LUW, not DB2 for z/OS.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----
Nov 12 '05 #4

P: n/a
Ian <ia*****@mobileaudio.com> wrote in message

You need to configure DB2 Connect properly (i.e. set up the DCS
directory properly). It sounds like you've defined the connection as
though it's running on DB2 UDB for LUW, not DB2 for z/OS.


The configuration is specifically set up with the host being OS/390. I
can do selects and some ohter functions just fine, but not exports. I
did check the Configure DCS box in the Configuration Assistant, but
none of the details where specified since they don't seem applicable
to this case. If you know which DCS settings to use, please let me
know.
Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.