|
That API does not present any history - it shows only the current
defaults, if present. I seem to recall that a DMPOBJ might have the
value - yes, just ran a test.
If you DMPOBJ on a command, the default values are presented together
at an offset I didn't take time to work out. Then I ran CHGCMDDFT -
the original defaults are all in the same place, with a 2-byte length
before each value - the change is at another location.
I assume there's a template somewhere for this - could it be made
public? The MI list members may know.
On 2/11/2011 3:32 PM, CRPence wrote:
On 2/11/11 9:41 AM, Mike Wills wrote:
Like an idiot, I forgot to keep track of some key CHGCMDDFTI've not used the feature to extract a command definition as XML,
commands when I created them. How do I go back and look those up
so we can make sure they are there after we upgrade the system? I
know I have seen how to do this in the past. Google didn't turn
anything up for me. I'll add this to the Wiki when I get the
answer.
but that may provide information describing what specific
default(s) were changed; i.e. beyond knowing only that at least one
command parameter default was changed on the command according to
the 'CHGDFT' value in the ODAPAR field of the DSPOBJD output file
for that command object.?
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.