|
I'll try to be to be constructive, so let me offer a suggestion: Change your main driver source to C or RPG (or other HLL). Compile all your CL sources into ILE modules. Compile your C or RPG driver source into a module. Bind them all into a single program. You get all the benefits of CL (LOGCLPGM, ease of command calls, error handling via MONMSG etc.) and all the benefits of HLL having subroutines that do special tasks, use of embedded SQL to your heart's content (yes, you can call SQL stored procedures via "exec sql CALL MYSTOREDPROC"), etc. Opinion: Even though CL is compiled into an object, I still think of it as scripting language. If I need to do something "complex", I use an HLL (in my case C). Just one way I keep myself out of troubles you're faced with today, not that I don't get myself into other pickles :) Elvis -----Original Message----- Subject: Re: iSeries 25% Growth 3rd Quarter On 10/19/05, michael@xxxxxxxxxxxxxxxxxx <michael@xxxxxxxxxxxxxxxxxx> wrote: > I would have written that in RPG and made calls to QCMDEXC if needed. bad choice Michael! because, then I lose the LOGCLPGM feature of CL. We were working on a problem with one of the vendor feeds yesterday. This is a large sysytem and I dont have access to the production partition. operations emailed me the 50 page joblog and I was able to track down the problem. If I had used RPG as you suggest that would not have been possible. -Steve
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.