what else is in your staging lib that you need. if only this module,
why don't you remove your staging lib from the loadlib concatenation?
Yes i need staging lib for other modules.
Even if i do that .. the production load will not find the time stamp against my test region plan.
Ultimately i want the production version to be bound in the test region for regression test. Thats why i want to know if i can update the CMN loadlib without chcking out the base vreiosn (as i don't want to replace the staging version).
Normally to recompile from Baseline we use Recompile (1.8) option in CMN but in this case if try to do so, it finds the conflict as another version is already present in the staging lib.
Joined: 22 Apr 2006 Posts: 6258 Location: Mumbai, India
You're using a lots of site-specific jargon in your explanations. So from that, what I understood so far, first suggestion from Dick seems to be perfect for your situation, did you try that?
Ultimately i want the production version to be bound in the test region for regression test.
Usually there is (are) "base-line" libraries which you can use "as is" for such testings. Unless you "check-out/stage" the component in your personal packages there is no question about timestamp mismatch.