Rob:

But, that should only ever happen across an IBM i version/release upgrade. AFAIK, IBM never adds new parameters to commands within a release.

And, of course, part of your "upgrade" procedure should include running a CL program that deletes any existing duplicates of IBM commands from your "custom commands" (QSYS1) library, then duplicates the new versions from QSYS, and then re-applies any changes to any defaults.

Mark

> 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



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.