|
On Wed, 24 October 2001, Jim Langston wrote: > I create command source. 14. Remember to prompt, now what is the > call I want to use? And going back having to recreate commands > months later, what program was this command supposed to call? > No idea. I hope they documented it in the command source > (yeah, right, like that'll ever happen). > > I think commands would be utilized a lot more if you could > actually specify the program to call inside the command source > itself, then just compile with 14. I view command definition objects pretty much as I do prototypes for ILE RPG and I think that's a good analogy to describe their use. As others mentioned, by naming the CPP the same as the command, or even using a naming standard that says "For command ABC, name the CPP as ABCx", there's little problem linking the command with the CPP. And for setting the attributes, I've long used my own RECRTCMD that is almost certainly the same as Craig Rutledge's since there aren't that many ways of doing it. I've also got a RSTCMDATR command that lets me select a previous CMD version from QRPLOBJ and apply its attributes to the new CMD in case I mess up. It's mostly just RECRTCMD with a front-end selection list and CHGCMD instead of CRTCMD. (Hey, we're programmers... if a tool doesn't exist, create one.) I agree that IBM support for command creation could be a little more advanced, but I believe that CMDs provide much more than what the small cost of creating them is. Tom Liotta -- Tom Liotta The PowerTech Group, Inc. 19426 68th Avenue South Kent, WA 98032 Phone 253-872-7788 Fax 253-872-7904 http://www.400Security.com ___________________________________________________ The ALL NEW CS2000 from CompuServe Better! Faster! More Powerful! 250 FREE hours! Sign-on Now! http://www.compuserve.com/trycsrv/cs2000/webmail/
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.