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.

Yeah, I was thinking of the matter of new parameters and all - if one didn't need them, it could work pretty seamlessly. Of course, one would depend on the defaults of new parameters, and that may or may not cause problems. Things like CPYFRMIMPF and CPYTOIMPF gave some of us lots of grief!!

Vern

Dennis Lovelady wrote:

I've heard of an approach of creating a command of the same name and
with the same parameters as an IBM command, and have a CPP that
basically runs the system command from there. This command and CPP
would
be placed above QSYS in the system portion of the library list.

Does that sound familiar? Or am I in desperate need of a vacation?

That is how I implemented my tape management system in another life. Works
great; the only issue being that as IBM adds parameters/options (which
happened a lot with the SAV* commands back then) there was rework to be
done. But this gave access to the before and after, visibility to the
command's success, and so on.

Still, the exit point is probably a better answer if only because of the
rework.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
You can't have everything. Where would you put it?

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.