× 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.



There's an example of the QCDRCMDD part of the equation to be found here:
http://iprodeveloper.com/rpg-programming/apis-example-command-definition-api-and-api-xml-output-processing

Cheers,
Carsten

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Vernon Hamberg
Sent: 25. februar 2014 00:23
To: Midrange Systems Technical Discussion
Subject: Re: Printing cmddft's

As Chuck mentions, there is the QCDRCMDD - Retrieve Command Description
- API. This can give you either an XML file or a variable with XML of the various "elements" in the source used to create the command.

And it does give the default as it is - not as delivered or not as the source may specify.

Now if you are talking about IBM commands, you COULD use a roundabout way to get to the default of the original - get the help text, which always shows the original default as an underlined value.

I dug around, and there is an API - Retrieve Help Text (QUHRHLPT) API - this puts out an XML with what the help looks like - it might give you whether something is a default and would not be affected by CHGCMDDFT.

I also see there is a Java class (CommandHelpRetriever) that can be called in QShell - it uses these 2 APIs, apparently - and it's from IBM.

HTH
Vern

On 2/24/2014 3:58 PM, fbocch2595@xxxxxxx wrote:
How is that done? Wouldn't dspcmddft be a good thing to have so you know what dft's have been changed...like wrksysval?




-----Original Message-----
From: rob <rob@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Mon, Feb 24, 2014 4:55 pm
Subject: Re: Printing cmddft's


It is possible to list all IBM commands that have had CHGCMDDFT ran on
them.


Rob Berendt

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.

This communication is intended only for use by the addressee.It may contain confidential or privilegedinformation.
If you receive this communication unintentionally, please inform us immediately and delete this e-mail and any attachments.
Warning: Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept
responsibility for any loss or damage arising from the use of this email or attachments.

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.