× 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.



On 8/14/2015 10:00 AM, Michael Smith wrote:
I am a new user to RDi.

My version is RDi 9.1.

After opening SQLRPGLE member(from my development environment) for PGMA, and making changes I complied PGMA.

In the list of errors that is a RNF5054, I clicked this error.

RDi opens /COPY member(from a production environment) where this error occur.

Is this normal behavior, if so, it appears that I would be able to modify the production environment source, without that change being promoted via our change management software...

At first blush it seems as though RDi is opening a /COPY member that you
don't expect, but how could it do that?
1) The /COPY has a hard-coded library
2) The library list for the connexion has PROD before DEV

You can see the library list several ways:
1) Right click the connexion, then Properties, then Subsystems. This
will show any additions to the library list being used by the user
profile you've connected with. If this is empty, the connexion is using
the library list in the *JOBD of the user profile.
2) Open a Commands Log View (Window > Show View > Commands Log). At the
bottom is a box where you can type commands. I use DSPLIBL
OUTPUT(*PRINT) and then look at a green screen to see the spooled file.
That is the definitive library list being used by that connexion.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.