Re: CHGOBJAUD of *CMD never gets logged; who did CHGWTR -- 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.

Hi Dennis

Not sure which VCP trick you refer to, but I would say that if one wanted to do something like log use of a command, it should be in the command exit, not in a VCP. Just as an example of a trick in the VCP. Not to say it hasn't crossed my mind once, but you can get bit badly when editing CL if you do that kind of thing.

Vern

Dennis Lovelady wrote:

But isn't the point of a VCP is to allow us do do stuff like this? If
not,
why publicize it at all?

No, the purpose of a VCP is to allow validity checking to be done before
invoking the CPP to actually execute.

This thread has apparently drifted (perhaps significantly) from the OP
observation that CHGWTR does not log an "Object Used" entry, and I don't
remember how we got here from there. (And since the thread spans so many
messages I did not track it down.) But what I'm fairly certain of, is that
this VCP trick is a hack to make the system take some action unrelated to
editing the parameters. Wouldn't you agree?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
REALITY.SYS corrupted. Reboot universe <Y/N>?

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.