Page 2 of 2

Re: DB2 bind with different Versions.

PostPosted: Tue Feb 01, 2011 2:15 pm
by GuyC
fairly smple, in a "normal" setup:
- each time you precompile your source into a dbrm and a precompiled source, DB2 puts a string in it both. It looks like a timestamp but isn't. That is the version of the package.
- bind turns your dbrm into a package, compile turns your pre-compiled source into a load
- at run time this "version" out of the load module is used (together with the name,...) to find the corresponding package in DB2. The key of a package inside DB2 is location.collection.name.version . location and collection are found via the plan you specify at run time, name and version are found in the loadmodule.

Because version is part of the key, multiple versions can co-exist. run with one loadmodule => use one package, run with another => use another package.

Re: DB2 bind with different Versions.

PostPosted: Tue Feb 01, 2011 2:19 pm
by GuyC
And it's packageversion or dbrmversion. DB2 versions are something else.
Clear questions get clear answers.
Dubious questions get answers depending on the psychic powers available on that day.

Re: DB2 bind with different Versions.

PostPosted: Wed Feb 02, 2011 1:16 am
by dick scherrer
Hello,

But if you want one group of people to use one and other people to use another and they try to use the same program load module name in the same cics region, it will still not do what you want. . .