MVSFORUMS.com

[misi01]

I hope I can explain this well enough so everyone can understand.

We have a client/system that used VB6 and Cobol/DL/1. Recently, we had to convert the VB6 code to .net. At the same time, it was important that any errors in the .net code didn't screw up the "real" DL/1 test database. What we did was to create copies of the database and then change the PSB with it's PCB's and AIB names so that the code could "choose" to which database it should write based on variations of the client userid. All well and good.

Now we're going to convert from DL/1 to DB2 and I'm wondering if there is some "simple" method of being able to switch between DB2 databases ? I'm not sure if it's standard, but at work, all our cobol/DB2 code is written along the lines of

[dbzTHEdinosauer]

two schema's in the same task? or just potentially a different schema for each transaction?

and you are on a y/OS mainframe?????
_________________
Dick Brenholtz
American living in Varel, Germany

[CZerfas]

If you are relative new to DB2, look at the concept of packages and collections. What you want to achieve, switching between test databases, is done best with binding the dbrms into multiple collections, while one collection uses one table creator-id.

If you now create different plans, each using one of the collections, you switch between your test databases by using different plans during the start of your application.

This concept is very powerful, but you need some reading to feel comfortable with it.

regards
Christian