Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / January 2005

Tip: Looking for answers? Try searching our database.

What authority level should user have to access z/OS tables from Windows

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Vladimir Khvostov - 29 Sep 2003 16:06 GMT
I am trying to access mainframe tables from Windows.
Using Configuration Assistant I successfully added mainframe database.
Test connection dialog showed that connection tested sucessfully for
all connection types(CLI, ODBC, etc.).
After that I opened Control Center and got next message:

[IBM][CLI Driver][DB2] SQL0805N  Package
"S390LOC.NULLID.SYSSH200.5359534C564C3031" was not found.  
SQLSTATE=51002

I also tried to do very simple selects from Command Window and got
Package not found errror.

Error message said that DB2 programs may need to be rebound to the
database.
So, I went ahead and ran:
DB2 bind @db2ubind.lst blocking all grant public

And got a lot of errors:
LINE    MESSAGES FOR db2ubind.lst
------  --------------------------------------------------------------------
       SQL0061W  The binder is in progress.

LINE    MESSAGES FOR db2ajgrt.bnd
------  --------------------------------------------------------------------
       SQL0038W  The bind option SQLERROR CONTINUE has been
                 activated since it is required when binding this
DB2-supplied
                 list file to DB2/MVS, SQL/DS, or OS/400.
       SQL0551N  "VLADK" does not have the privilege to perform
                 operation "CREATE IN" on object
"S390LOC.NULLID.SQLABE00".
                 SQLSTATE=42501

LINE    MESSAGES FOR db2ueiwi.bnd
------  --------------------------------------------------------------------
       SQL0038W  The bind option SQLERROR CONTINUE has been
                 activated since it is required when binding this
DB2-supplied
                 list file to DB2/MVS, SQL/DS, or OS/400.
       SQL0551N  "VLADK" does not have the privilege to perform
                 operation "CREATE IN" on object
"S390LOC.NULLID.SQLUAE05".
                 SQLSTATE=42501

Any ideas?

Thanks,
-- Vladimir Khvostov
Larry Edelstein - 22 Jan 2005 22:51 GMT
The authority level to "access" is not the same as the authority level to bind.
You need either BINDADD or SYSADM to bind. Then you can access using the
standard access authorities.

Larry Edelstein

> I am trying to access mainframe tables from Windows.
> Using Configuration Assistant I successfully added mainframe database.
[quoted text clipped - 45 lines]
> Thanks,
> -- Vladimir Khvostov
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.