Re: command defaults -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: command defaults
From: mlazarus <mlazarus@xxxxxxxxxxxx>
Date: Thu, 04 Oct 2018 13:18:41 -0400
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>

Mike,

One way is:

DSPOBJD OBJ(*IBM) OBJTYPE(*CMD) DETAIL(*SERVICE) OUTPUT(*OUTFILE) OUTFILE(QTEMP/DSPOBJD)
Then use your favorite query tool to view the list. Field ODAPAR will contain CHGDFT. Note that this works for the actual command, not the proxy.

-mark

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

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

Mike

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: command defaults , Smith, Mike

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.