Re: command defaults -- MIDRANGE-L

Subject: Re: command defaults
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 4 Oct 2018 12:20:16 -0500
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 10/4/2018 12:17 PM, David Gibbs wrote:

On 10/4/2018 12:03 PM, Smith, Mike wrote:

Anybody know of a way to identify commands that have had their defaults changed?

If you do a DSPOBJD OBJ(<cmd>) OBJTYPE(*CMD) DETAIL(*SERVICE) and
look at the APAR ID, it will show 'CHGDFT'.

FWIW: Because this has burned us numerous times in the past, I added a function to Implementer that analyzed commands in QSYS to identify which ones had parameter defaults changed and how those commands were used in the product.

We include this information in the standard diagnostic information that we collect from customers when helping them with issues.

david

As an Amazon Associate we earn from qualifying purchases.

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.