× 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.



I have always really liked having user-written commands to do utility-type
functions.  The ability to run them from a command line and also from
within a CL program was always very handy and understandable.  Especially
since AS/400 programmers use the OS/400 commands all the time.

However I am finding that commands are becoming a bit limited as one writes
more and more ILE functions.  Because a command always runs a CPP (the
operative word being the last "P" for Program), you are getting the
performance issues inherent in CALLing programs rather than using a
subprocedure (or a module) as you would if the command was a subprocedure
instead.  And since most commands are designed and written for one-pass
use, they (usually) open and close their files every time they're run.

All of this seems to be a performance penalty when a command is used over
and over.  Any comments or opinions?

Bill


--

NOTICE:  The information contained in this electronic mail transmission is
intended by Convergys Corporation for the use of the named individual or
entity to which it is directed and may contain information that is
privileged or otherwise confidential.  If you have received this electronic
mail transmission in error, please delete it from your system without
copying or forwarding it, and notify the sender of the error by reply email
or by telephone (collect), so that the sender's address records can be
corrected.




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.