Hi Andy

Try the process again using a user that is a SYSADM on the MVS DB2. I
have had distributed applications attempt to do a bind on the MVS system
and if the user was not a SYSADM the binds usually don't work. In my
case I am one of the Install SYSADMs so YMMV.


William B. Gannon
- IBM Certified Solutions Expert
- IBM Certified Database Administrator
DB2 Universal Database V8.1 for zOS

-----Original Message-----
From: Andy Liggins
[mailto:db2udbdba-ezmlmshield-x58854066.[Email address protected]
Sent: Thursday, January 31, 2008 10:49 AM
To: LazyDBA Discussion
Subject: bind issue using db2 UDB ver9.1.3 LUW to db2 os390 8.1.5


Hello DB2 DBA's

We are getting the following error when running an export utility
against a
DB2 database on OS/390.
This works fine from our old server running DB2 ver.8.2

SQL2019N An error occurred while binding the utilities to the database.

The select statement works fine by it self. it fails on the export.

We believe there is a bind command to run on the OS/390 side but not
sure
of the command.

Anyone with information for the proper bind commands on the OS/390 side?
Or, is there something we should do on our side?
We beleive the problem is on the OS/390 side because we also pull data
from
another OS/390 system in Canada without this issue.

Thanks very much!


---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
To post a dba job: http://jobs.lazydba.com
To Subscribe : http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html



-----------------------------------------
Under Florida law, e-mail addresses are public records. If you do
not want your e-mail address released in response to a public
records request, do not send electronic mail to this entity.
Instead, contact this office by phone or in writing.

DB2 & UDB email list listserv db2-l LazyDBA home page