Joined: 26 May 2005 Posts: 178 Location: Copenhagen, Denmark
I'm not quite sure if this is the right place to post this question. It is about compilation and link edit in different regions.
I have seen some shops where they compile the source code only in DEV region and move only load lib and DBRM to next level. They only BIND in the next levels. In our shop we compile, link edit and BIND in all the regions.
say our PL1, DB2 program will be comipiled, link edit and BIND in DEV,TEST, USER TEST and PROD also. I was told that moving the LOADLIB and DBRM to next level is a good practice. Is this true.?
As per my knowledge Its good to compile in every region so that they will be compiled with the respective Language environment parameters.
Is there any significant reason to move LOADLIB and DBRM instead of compiling again.?
Joined: 23 Nov 2006 Posts: 19270 Location: Inside the Matrix
One of the drawbacks of compiling over again for each "step up" is that the resulting load modules are un-tested. If a production module abends or gives incorrect results, time is often lost determining if the problem is actually the code or simply the excecutable.
My personal preference is to compile/link one time and promote the executable.
As time goes by, there are more organizations (that i've been involved with) that are trying to change to where they compile at muiltiple levels and so far, most of them have found it more work than any value added. I've talked with other people who have done this for years with no problems. A lot depends on how the infrastructure is set up and how well the CM function is administered.