Re: Replaced Object still referenced

[tegger@xxxxxxxxxxx]

I'm used to this when the user is actively using the program when I recompile it. 
Once they returned to a main menu, they would get the recompiled version when they went back into the menu options. 




----- Original Message -----

From: "Vernon Hamberg" <vhamberg@xxxxxxxxxxxxxxx> 
To: "RPG programming on the IBM i (AS/400 and iSeries)" <rpg400-l@xxxxxxxxxxxx> 
Sent: Monday, September 28, 2015 9:27:18 AM 
Subject: Re: Replaced Object still referenced 

Hi Jay 

Basically, the users have to sign off and back on again, to release the 
resolution to the old program. 

I believe this is working as designed - if a program is in use at the 
time you compile it (and specify to replace it), that program is 
attached to library QRPLOBJ, and the user's job still knows where it is. 
This means that the job knows nothing about the new program. 

RCLRSC does nothing about this - it isn't supposed to. 

Sorry for the "bad" news - I suppose you could try to delete the old 
program before compiling - which would get you lots of calls to your 
help desk! 

Vern 

On 9/28/2015 7:53 AM, tegger@xxxxxxxxxxx wrote: 
> I have a chuck of code that uses DDS PF files to indicate the program name to call in specific situations. 
> The problem is that if one of these programs (named in the PF) is recompiled, the calling program gets the old replaced version of the program until the user signs off the system and back on. 
>
> I have RCLRSC on the controlling CLP, but that's not helping any. 
>
> Any ideas? 
>
>
> Jay 
> Marydel, DE