We are running under Windows using Nat 6.1.1.17. I recently discovered that we had 2 Bufferpools running on the same machine - 1 as the result of a runtime version install and the other as a result of a developer version install.
My question - what if any, are the likely problems with this setup.
We were running without problems for quite a while and then I was noticing some strange phenomena like programs Stowed appeared to be picking up a wrong version of a DDM (a DDM of a same name but residing in another library).
We have since deleted one of the bufferpools but I was just curious as to what might be the impact of this setup.
There’s no impact because the 2 bufferpools sure enough had different bufferpool keys, otherwise you wouldn’t have been able to start 2 of them in the first place.
I was noticing some strange phenomena like programs Stowed appeared to be picking up a
wrong version of a DDM (a DDM of a same name but residing in another library).
This is not a problem of two different buffer-pools. We have this strange behavior sometimes with ANY object, because we have up to 8 Steplibs and objects with the same name in different libraries. We have also GDA named COMMON in some of this steplibs.
The search/find-logic of the bufferpool does not care about a library-name, it is looking only for the object-name. Sometimes this leads into the situation, that you call an object from the current library, but this object with the same name (from another library) is already in bufferpool. In this case, natural takes the bufferpool-object, and not from the current library. If this happens with a GDA, your application will immediate terminate with error 933.
I opened in Feb/March this year a support request (#606283). SAG-Support was able to reproduce this and agreed that this is an error, but they changed this request to an Enhancement Proposal (#4404), due to the complexity of such a correction in bufferpool (they said).
To avoid this problem, you have to make sure, that there are no duplicate object-names in the steplib-sequence.
The other opportunity is to set BPSFI=OFF, but this is not acceptable for a production environment.