Re: Compiler Command Overrides

It's been years, but I seem to remember someone causing themselves A Big
Problem due to S being next to D on the keyboard.

Think SLTCMD vs DLTCMD. Both accept generic*.

No, it wasn't me, but I don't remember who. I never use SLTCMD, I just do
WRK* to see all the WRK commands.

On Wed, Feb 22, 2017 at 3:58 PM, DrFranken <midrange@xxxxxxxxxxxx> wrote:

Just don't EVER copy the QCMD object in there. Don't ask me how I know...


- Larry "DrFranken" Bolhuis

www.Frankeni.com
www.iDevCloud.com - Personal Development IBM i timeshare service.
www.iInTheCloud.com - Commercial IBM i Cloud Hosting.

On 2/22/2017 3:44 PM, Rob Berendt wrote:

IDK if my fears are rational or not but I have this issue with adding my
own 'system' library ahead of IBM's.

If I put a custom command in there and IBM adds a new parameter to both
the command and the program object then my custom one goes casters up.
Granted, that should stick out and not just slip through like a changed
default might.


Rob Berendt

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD