|
My usage of items like QCMDEXC, etc has depreciated. I rather like the API's instead of the commands, at least from HLL's. The error return code is a lot more flexible on the API's then trying to figure out what went wrong on a QCMDEXC call. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin Scott Mildenberger <scottmildenberger@xxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 10/24/2003 12:55 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> cc Subject Re: Starting out with sub-procedures Making the procedure only have one parm and doing the dirty work inside the procedure is exactly the way to do it. Whenever possible hide the dirty stuff inside procedures so the only one who has to know about it is the person who wrote the procedure. My procedure to execute commands (I use the C function system but could have used QCMDEXC just as easily) even has optional parameters that work a little like MONMSG in CL - allowing the call to indicate it worked successfully even if a certain message id is received. Scott Mildenberger --- Booth Martin <Booth@xxxxxxxxxxxx> wrote: > Why does my new procedure that will run QCMDEXC need two parms > in? Why can > t I just send the command and let the new procedure determine > the command's > length? __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com _______________________________________________ This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.