Re: CHGCMDDFT for TGTRLS from *CURRENT to V7R1M0 -- MIDRANGE-L

Subject: Re: CHGCMDDFT for TGTRLS from *CURRENT to V7R1M0
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 18 Jan 2018 12:26:54 -0600
List-archive: <https://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: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

On 1/18/2018 12:15 PM, Rob Berendt wrote:

Then perhaps one shouldn't code expecting IBM supplied defaults? If
you need CRTCLPGM to say TGTRLS(*CURRENT) then use CRTCLPGM TGTRLS(*CURRENT), and so on.

Hard to do when new parameters get added every release and you have to target the lowest supported release.

I wouldn't go so far as to supply EVERY parameter. That way if the customer does do a CHGCMDDFT, and it has no adverse effects on your software, then let the customer's change percolate through. If,
however, that parameter just has to be a particular value, then
supply that value.

You would be surprised at the modified defaults that we have encountered.

david

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