| View previous topic :: View next topic |
| Author |
Message |
djf
Beginner
Joined: 06 Feb 2007
Posts: 68
Topics: 27
|
 Posted: Fri Jan 22, 2010 2:07 pm Post subject: Test DB2 |
 |
|
We are preparing to test some applications under a new DB2, which is a freshly installed version of our current DB2.
But we do not want to recompile the programs - we just want to have DB2 be able to use the same application loadlibs and DBRMLIBs
So does anyone know which of the internal DB2 tables (probably one of the DSNDB06 tables) that holds the info about all the binds, etc, so that we don't get the program failures due to date/timestamp mismatches when we fire up the applications? |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12380
Topics: 75
Location: San Jose
|
|
| Back to top |
|
|
CZerfas
Intermediate
Joined: 31 Jan 2003
Posts: 211
Topics: 8
|
| Posted: Mon Jan 25, 2010 7:14 am Post subject: |
|
|
Using the same loadlibs and DBRM-libs is no problem, but you have to BIND all of your packes to the new tables.
The access paths created during a BIND are stored in the sceleton package table in DSNDB01, which you can't copy between DB2 subsystems.
regards
Christian |
|
| Back to top |
|
|
djf
Beginner
Joined: 06 Feb 2007
Posts: 68
Topics: 27
|
| Posted: Tue Jan 26, 2010 6:30 pm Post subject: |
|
|
Thanks to both you guys. We kind of reasoned that out this morning when I bumped across a website that said the ONLY input into a bind was the DBRM.
Since we save and archive our DBRMs, and can check SYSIBM.SYSDBRM for the program name and the library that held the DBRM, we were able to bind and then execute and existing program without a recompile.
I knew there had to be a way to do it, but I'm a bit hampered because I'm an OS guy, not a DB2 guru!! |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
