Steve,
Sign-off and sign-on again, or issue:
RRTJOB RTGDTA(QCMDI)
to reset your job as it was when you first signed on.
This will close all activation groups, thus purging any "activated" *PGMs and *SRVPGMs that may be loaded in those AGs.
The *LIBL only comes into play if the *SRVPGM (or *PGM) is not already "loaded" and activated within your job.
That is the essence of your "problem" or issue... the *SRVPGM was already activated in the QILE AG.
Hope that helps,
Mark S. Waterbury
On Friday, April 28, 2023 at 11:21:05 AM EDT, Stephen Coyle <stephenfcoyle@xxxxxxxxx> wrote:
Hi All,
I have a dev version and a prod version of the same service program.
They each live in their own library.
Both are activation group QILE.
I also have a CLP that determines which environment a request is being made from.
This CLP then sets the *LIBL accordingly.
The prod *LIBL does not include the library where the dev service program
exists.
The dev *LIBL does include the library of the prod service program, but it
is below the dev version library.
I had to debug some new changes to the service program the other day.
This was in the dev environment and I had set a breakpoint within the dev
version of the service program.
The breakpoint was never hit.
When I debugged the prod version, the breakpoint I set did stop.
The library list of the job was correct for the environment.
The files that were hit were also the correct files from dev....phew!
The issue only seemed to affect the version of the service program.
I was under the impression that the library list would control which
version of the service program is executed.
It appears that the first version of the service program activated is used
going forward.
Hope that made sense.
Can anyone confirm the behavior in this type of situation?
Any suggestions as to how the correct version can be executed?
Thanks in advance,
- Steve
midrange.com
