MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » February 2014

Re: Printing cmddft's



fixed

On 24-Feb-2014 13:58 -0800, fbocch2595@xxxxxxx wrote:

<<SNIP>> Wouldn't DSPCMDDFT be a good thing to have so you know what
defaults have been changed... like WRKSYSVAL?


Easily accomplished. Whenever Change Command Default (CHGCMDDFT) is used to perform a system customization, record that customization. Then whenever a list of customizations needs to be viewed, present the list of customizations that was maintained as part of the System Change Management.

As I had suggested in a past discussion, if an indication of the default change from the original shipped-default is required [if for example one refuses to implement system change-management], then a DCR to request the capability be added to the Command Definition object support and the retrieve command API, because currently the ability seems not to exist per:
<http://pic.dhe.ibm.com/infocenter/iseries/v7r1m0/topic/apis/qcdrcmdd.htm>
_Retrieve Command Definition (QCDRCMDD) API_
"...
The Retrieve Command Definition (QCDRCMDD) API retrieves information from a CL command (*CMD) object and generates XML (Extensible Markup Language) source statements which describe the command. The generated command information XML source is called Command Definition Markup Language or CDML. The CDML source can be stored in either a receiver variable or a stream file, depending on the destination format name specified.
...
If the default value for an optional command parameter has been changed using the Change Command Default (CHGCMDDFT) command, the returned command information will reflect the default currently in effect rather than the default specified when the command was created.
..."

However given that customizations typically would be re-applied after any release upgrade or after applying maintenance that might have /lost/ those customizations, IMNSHO establishing proper system change management that allows one to easily view the customizations [e.g. as a script, which could be queried] seems the easiest means to effect that.

Otherwise... obtaining\retrieving that information from the *CMD objects of a freshly scratch-installed system to the same release [and updates obtained from the new or refreshed object with the delivery of a PTFed command], could be used as a basis for a comparison; e.g. a feature\utility such as diff or CMPPFM could be used to show what has changed from the same XML information retrieved for the current version of the /same/ command definition object.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact