Re: DB2 Connect and DB2 V7.5
Hello Ewald, I think the missing OBJECTs with CREATOR of NULLID are from running a BIND from UDB DB2/Connect against a DB2/VM server using DB2??LST. Please check your UDB DB2/Connect PD. However, you also have to run the following 'GRANT's before running the UDB DB2/Connect BIND: CONNECT SQLDBA IDENTIFIED BY SQLDBAPW; SET ERRORMODE CONTINUE; GRANT SELECT ON SYSTEM.SYSCATALOG TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSCOLUMNS TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSINDEXES TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSTABAUTH TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSKEYCOLS TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSINDEXES TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSTABAUTH TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSKEYCOLS TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSSYNONYMS TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSKEYS TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSVIEWS TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSCOLAUTH TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSTEM.SYSPROGAUTH TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSCAT.ROUTINES TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSCAT.INDEXES TO NULLID WITH GRANT OPTION; GRANT SELECT ON SYSCAT.INDEXCOLUSE TO NULLID WITH GRANT OPTION; COMMIT WORK RELEASE; ...Roland --- On Fri, 3/25/11, E. Roller ewald.rol...@rolf-benz.com wrote: From: E. Roller ewald.rol...@rolf-benz.com Subject: DB2 Connect and DB2 V7.5 To: IBMVM@LISTSERV.UARK.EDU Date: Friday, March 25, 2011, 10:54 AM Hi, struggling on with implementing DB2 V7.5, on VM I got some DRDA Problems with DB2 Connect. Environment: Database P1 is on Level 7.3 Database T1 is on Level 7.5 DB2 Connect V7.2 connects to P1 and T1 with no problems DB2 Connect V8.1 connects to P1 with no problems DB2 Connect V8.1 connecting to T1 ends up with errors: Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.php on line 292 Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.php on line 325 The difference of the databases P1 and T1 are in SYSTEM.SYSACCESS table: the old V7.3 fatabase contains the following entries (and some more), I don't know, where they come from: TNAME CREATOR -- --- SYSLN100 NULLID SYSLN101 NULLID SYSLN102 NULLID SYSLN200 NULLID SYSLN201 NULLID SYSLN202 NULLID SYSLN300 NULLID SYSLN301 NULLID SYSLN302 NULLID SYSLN400 NULLID SYSLN401 NULLID SYSLN402 NULLID SYSSN100 NULLID SYSSN101 NULLID SYSSN102 NULLID SYSSN200 NULLID SYSSN201 NULLID SYSSN202 NULLID SYSSN300 NULLID SYSSN301 NULLID In the V7.5 database these entries are missing. Reading the Database Administration Guide, I found out, that I have to set up a Stored Procedure Server for DB2 UDB V8.x connections. This is new with DB2 V7.3, the old database on this level works well without a Stored Proc Server. What do I miss ?? TIA Ewald Roller
Re: DB2 Connect and DB2 V7.5
The Database Administration Guide explains the Stored Procedure servers. It's Chapter 11 in the 7.5 manual. The SQL Reference can tell you how to create a stored procedure server for your database. See the CREATE PSERVER statement. I hope this helps, Nora Graves nora.e.gra...@irs.gov Main IRS, Room 6531 (202) 622-6735 Fax (202) 622-3123 SE:W:CAR:MP:D:KS:BRSI -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@ ILISTSERV.UARK.EDU] On Behalf Of E. Roller Sent: Friday, March 25, 2011 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: DB2 Connect and DB2 V7.5 Hi, struggling on with implementing DB2 V7.5, on VM I got some DRDA Problems with DB2 Connect. Environment: Database P1 is on Level 7.3 Database T1 is on Level 7.5 DB2 Connect V7.2 connects to P1 and T1 with no problems DB2 Connect V8.1 connects to P1 with no problems DB2 Connect V8.1 connecting to T1 ends up with errors: Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.php on line 292 Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.php on line 325 The difference of the databases P1 and T1 are in SYSTEM.SYSACCESS table: the old V7.3 fatabase contains the following entries (and some more), I don't know, where they come from: TNAME CREATOR -- --- SYSLN100NULLID SYSLN101NULLID SYSLN102NULLID SYSLN200NULLID SYSLN201NULLID SYSLN202NULLID SYSLN300NULLID SYSLN301NULLID SYSLN302NULLID SYSLN400NULLID SYSLN401NULLID SYSLN402NULLID SYSSN100NULLID SYSSN101NULLID SYSSN102NULLID SYSSN200NULLID SYSSN201NULLID SYSSN202NULLID SYSSN300NULLID SYSSN301NULLID In the V7.5 database these entries are missing. Reading the Database Administration Guide, I found out, that I have to set up a Stored Procedure Server for DB2 UDB V8.x connections. This is new with DB2 V7.3, the old database on this level works well without a Stored Proc Server. What do I miss ?? TIA Ewald Roller
Re: DB2 Connect and DB2 V7.5
BTW, on the subject of stored procedures... We have DB2/VSE 7.3 running on multiple VSE systems. We have been running DB2/UDB 7.x client on Windows going thru a DB2 Connect 7.x single user edition. Right...this setup doesn't require a stored procedure server. However, when we added a DB2 Connect 9.5 Server, and 9.5 clients, any use of the DB2 Command Center on the PC, requires a DB2 Stored Procedure Server running on the mainframe. Now, I don't know if it was the DB2 Connect version change that required the stored procedure server or that the DB2 client version change that required the stored procedure server, but now, anytime a DB2 9.x client starts using the DB2 Command Center, the stored procedure server DFLT0001 fires up to handle the request. Tom Duerbusch THD Consulting E. Roller ewald.rol...@rolf-benz.com 3/25/2011 9:54 AM Hi, struggling on with implementing DB2 V7.5, on VM I got some DRDA Problems with DB2 Connect. Environment: Database P1 is on Level 7.3 Database T1 is on Level 7.5 DB2 Connect V7.2 connects to P1 and T1 with no problems DB2 Connect V8.1 connects to P1 with no problems DB2 Connect V8.1 connecting to T1 ends up with errors: Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.php on line 292 Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.php on line 325 The difference of the databases P1 and T1 are in SYSTEM.SYSACCESS table: the old V7.3 fatabase contains the following entries (and some more), I don't know, where they come from: TNAME CREATOR -- --- SYSLN100NULLID SYSLN101NULLID SYSLN102NULLID SYSLN200NULLID SYSLN201NULLID SYSLN202NULLID SYSLN300NULLID SYSLN301NULLID SYSLN302NULLID SYSLN400NULLID SYSLN401NULLID SYSLN402NULLID SYSSN100NULLID SYSSN101NULLID SYSSN102NULLID SYSSN200NULLID SYSSN201NULLID SYSSN202NULLID SYSSN300NULLID SYSSN301NULLID In the V7.5 database these entries are missing. Reading the Database Administration Guide, I found out, that I have to set up a Stored Procedure Server for DB2 UDB V8.x connections. This is new with DB2 V7.3, the old database on this level works well without a Stored Proc Server. What do I miss ?? TIA Ewald Roller
Re: DB2 Connect and DB2 V7.5
Those modules get created by prepping DB2 connect into the DB2 databases on the VM side. How you get DB2 Connect to work without those modules is more perplexing to me to tell you the truth, but maybe that was possible in older releases of DB2 Connect. Anyway, there is a bind process that our DB2 Connect users follow to create those missing modules. I don't know what that process is since I am just a VM Db2 guy, but we typically have to give the DB2 Connect folks temporary DBA authority in order to do the preps, then your VM DBA needs to grant run on those new objects to public by connecting as NULLID. Tony Pignataro From: E. Roller ewald.rol...@rolf-benz.com To: IBMVM@LISTSERV.UARK.EDU Date: 03/25/2011 10:55 AM Subject:DB2 Connect and DB2 V7.5 Sent by:The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU Hi, struggling on with implementing DB2 V7.5, on VM I got some DRDA Problems with DB2 Connect. Environment: Database P1 is on Level 7.3 Database T1 is on Level 7.5 DB2 Connect V7.2 connects to P1 and T1 with no problems DB2 Connect V8.1 connects to P1 with no problems DB2 Connect V8.1 connecting to T1 ends up with errors: Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.ph p on line 292 Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.ph p on line 325 The difference of the databases P1 and T1 are in SYSTEM.SYSACCESS table: the old V7.3 fatabase contains the following entries (and some more), I don't know, where they come from: TNAME CREATOR -- --- SYSLN100NULLID SYSLN101NULLID SYSLN102NULLID SYSLN200NULLID SYSLN201NULLID SYSLN202NULLID SYSLN300NULLID SYSLN301NULLID SYSLN302NULLID SYSLN400NULLID SYSLN401NULLID SYSLN402NULLID SYSSN100NULLID SYSSN101NULLID SYSSN102NULLID SYSSN200NULLID SYSSN201NULLID SYSSN202NULLID SYSSN300NULLID SYSSN301NULLID In the V7.5 database these entries are missing. Reading the Database Administration Guide, I found out, that I have to se t up a Stored Procedure Server for DB2 UDB V8.x connections. This is new with DB2 V7.3, the old database on this level works well without a Stored Proc Server. What do I miss ?? TIA Ewald Roller
Re: DB2 Connect and DB2 V7.5
You have to rebind packages. You didn't say if you have the DB2 Connect Server version(s) or the standalone client. From each DB2 Connect Server, you have to rebind to each release of DB2 VM/VSE in which that Connect Server will access. Then, from each type of client (Win/.XP, Win/7 32 bit, Win/7 64 bit, etc), you have to rebind from that windows client to each release of DB2 Connect Server you are running. I don't know if you have to, but I did, bind from each type of Windows client to each release of DB2 you are running. Tom Duerbusch THD Consulting E. Roller ewald.rol...@rolf-benz.com 3/25/2011 9:54 AM Hi, struggling on with implementing DB2 V7.5, on VM I got some DRDA Problems with DB2 Connect. Environment: Database P1 is on Level 7.3 Database T1 is on Level 7.5 DB2 Connect V7.2 connects to P1 and T1 with no problems DB2 Connect V8.1 connects to P1 with no problems DB2 Connect V8.1 connecting to T1 ends up with errors: Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.php on line 292 Warning: SQL error: [IBM][CLI Driver][SQLDS/VM] SQL0805N Package .NULLID.SYSSN200 was not found. SQLSTATE=51002 , SQL state 51002 in SQLExecDirect in /web/intern/htdocs/archivts/TA0010.php on line 325 The difference of the databases P1 and T1 are in SYSTEM.SYSACCESS table: the old V7.3 fatabase contains the following entries (and some more), I don't know, where they come from: TNAME CREATOR -- --- SYSLN100NULLID SYSLN101NULLID SYSLN102NULLID SYSLN200NULLID SYSLN201NULLID SYSLN202NULLID SYSLN300NULLID SYSLN301NULLID SYSLN302NULLID SYSLN400NULLID SYSLN401NULLID SYSLN402NULLID SYSSN100NULLID SYSSN101NULLID SYSSN102NULLID SYSSN200NULLID SYSSN201NULLID SYSSN202NULLID SYSSN300NULLID SYSSN301NULLID In the V7.5 database these entries are missing. Reading the Database Administration Guide, I found out, that I have to set up a Stored Procedure Server for DB2 UDB V8.x connections. This is new with DB2 V7.3, the old database on this level works well without a Stored Proc Server. What do I miss ?? TIA Ewald Roller
