Re: Command Defaults... Are they stored anywhere?

Or maybe just look on another system for those commands that have been
changed?

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On Thu, Jun 23, 2022 at 6:09 AM Vern Hamberg via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I believe I've seen a way to get the original defaults, but it's not a
lot of fun - look at the help for the command. Seems I've seen it
present the defaults as originally specified, because CHGCMDDFT does
nothing for related help, especially UIM-defined help.

Isn't there another API for retrieving UIM help code? And one for
command information? Not sure it's exactly useful in this context, however.

Cheers
Vern

On 6/22/2022 11:05 PM, x y wrote:

Aren't they part of the command object? CHGCMDDFT changes the defaults

for

everybody, not just the current user. CHGCMDDFT changes the object's
change/time; that suggests the (changed) defaults are buried in the

object.

There's code (RTVCMDDFN?) floating around that does a semi-good version

of

extracting the command source from a command object; QCDRCMDD is the API.
But I can't think of a way of getting the original defaults--other than
looking at the source code, of course.

On Wed, Jun 22, 2022 at 2:36 PM Brad Stone <bvstone@xxxxxxxxx> wrote:

Something I've been wondering for a long time.. are command defaults

stored

anywhere in a table... or are they actually part of the command itself?

Even if it's just if a user uses CHGCMDDFT to change it and it's only
stored then, that may be useful.

If they are stored in the command object.. I suppose there's no way to

get

the defaults without processing the command with a CL... maybe dumping

the

object? Man, I haven't done that forever. :)

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any

Cloud

Provider!
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

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

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com