|
On 03/15/99 11:46:31 AM Colin Williams wrote: >But the problem with QCMDEXC, is that you cannot do a MONMSG on any >commands you run, so if an error occurs in the command, the calling HLL >program falls over. In RPG400, put an indicator in the LO positions to detect an error. In the latest version of RPG IV, use CALLP(e) >The only problem with modules is that if you have to create an extra >module for every CL type task you want to perform, you could end up with >lots of modules/programs, when you only want to perform some very simple >function, and I prefer to use as few programs/modules as possible, to >keep object mangement simple! Simple management is certainly a benefit, but there are benefits to having a large library of granular functions, too. It's a matter of where you personally want to draw the line. IBM chose the "large library" approach - that's why there are so many CL commands. If you wanted to minimise program objects you could build a service program containing your most commonly used CL commands. A few parameters and a bit of parsing and you'd be all set. Buck Calabro Billing Concepts Inc (formerly CommSoft), Albany, NY mailto:mcalabro@commsoft.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.