× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Sounds like the SP was already active from a previous run and perhaps you forgot to RCLACTGRP QILE?


Jon P.

On Apr 28, 2023, at 11:20 AM, 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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.