PatZ wrote:We had a situation where we performed a NEWCOPY, but the program didn't refresh.
As you say below, yes, it did refresh.
There are 2 TOR's under an AOR, so we used CRTE to get to the AOR. We did a NEWCOPY and it looked successful, there were no errors and usecount & rescount were both 0.
Did the byte count change too (assuming the new module was changed enough to be a different length)?
It appeared that the new version of code was executing fine in one of the TOR's, but not the second.
Either the executable code resides in the second TOR or that TOR is pointing to another AOR.
The abend generated by the tran in the second TOR showed a DB2 consistency token from the old version of the program, so it was still executing the old load module. After a CICS bounce the next day, everything was fine (as we expected).
That would be expected if the AOR/TOR that holds the other copy got restarted.
Next time this occurs, cedf the failing version and once into the non-refreshed version, CECI, load the module, get the load address, view that storaage for the compiler imbedded timestamp to confirm that it is still the old module.
Then try a CECI ASSIGN SYSID to see which system the CEDF on the unrefreshed module n(and hopefully the module itself) is running/residing in.