Re: Compiler Command Overrides -- MIDRANGE-L

Subject: Re: Compiler Command Overrides
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
Date: Wed, 22 Feb 2017 21:47:50 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hi, Barbara:

Thanks for that update. I suspected that, since IBM introduced "Technical Refreshes" (TRs) this might be the case.

Another strike against the old techniques for overriding command defaults.

Mark S. Waterbury

> On 2/22/2017 6:12 PM, Barbara Morris wrote:

On 2017-02-22 4:00 PM, Mark S Waterbury wrote:

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

That used to be true, but there was a change in the way commands are shipped a few releases ago that made it possible to add new parameters via PTFs.

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.