Re: Compiler Command Overrides -- MIDRANGE-L

× 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, everyone:

"No one respects the flame quite like the fool who's badly burned"-- lyrics from a song by Pete Townshend

You need to be careful about issuing CHGCMDDFT against "proxy" commands -- as of V5R4 and above, many LPPs install a "proxy" command in QSYS,that points to the "real" command in the "base" LPP library. For example, if you issue:

DSPCMD CRTBNDRPG

you will likely 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

If you just issue:
CHGCMDDFT CMD(CRTBNDRPG) NEWDFT('OPTION(*SRCSTMT)')

it does not change the "proxy" command, but "follows the chain" and alters the "real" CRTBNDRPG *CMD object in library QDEVTOOLS.

(See the help text for the CRTPRXCMD command for some details.)

Hope that helps,

Mark S. Waterbury

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.