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



Hi, James:

Take a look at the CRTPRXCMD command -- prompt it and press F1, etc.

Issue:
DSPCMD QSYS/CRTBNDRPG

And you should see something like this:

Display Command Information

Command . . . : CRTBNDRPG Library . . . : QSYS

Target command . . . . . . : CRTBNDRPG
Library . . . . . . . . : QDEVTOOLS
Text . . . . . . . . . . . : Create Bound RPG Program

Current proxy chain . . . : QSYS/CRTBNDRPG
QDEVTOOLS/CRTBNDRPG
...(snip)...


So, you can tell if you are looking at a "rpoxy" command by examining the "proxy chain"...

HTH,
'
Mark S. Waterbury

> On 10/16/2013 1:45 PM, James H. H. Lampert wrote:
Oh, now this is interesting:

The CRTBNDRPG in QSYS has an attribute of "PRX"; is that this "proxy"
that somebody mentioned? Could somebody point me to an explanation of
what this is?

And I see another one, in QDEVTOOLS, that DOES show the previously
mentioned signs of being changed.

Another customer's V7 box also shows the same, on QDEVTOOLS/CRTBNDRPG,
but in their case, the activation group/storage model defaults are as
advertised, and the default debugging view appears to have been changed
to *ALL (very convenient for me!).

And I see the same PRX thing on our V6 box, but we're still on factory
defaults.

At any rate, on the "problem" box, I simply added an H-spec (which SEU
didn't like, at first!) setting the STGMDL to *SNGLVL, in the problem
source member, and that solved the problem.

--
JHHL


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.