|
Rob, I agree, it may seem trivial to know the intricacies of every opcode, but it can pay off when you need to do something and you don't have to waste time finding the best way to accomplish the task. For example, why waste time creating a sub-procedure when a new bif accomplishes the same task. We have used the certification to push our new programmers. Not knowing what will be on the test forces them to study all aspects of programming. As far as some rules of thumb on using procedures, I would set some standards first. To establish those standards I would recommend reading the ILE concepts manual, as well as the ILE RPG manuals. News/400 also has an RPGIV style forum that is pretty good. The standards that I have found most useful are: Exported procedures or values are unique across our entire system. Procedures are used in only one program or service program. (One exception, our initial sign on program) Binding source is used for all service programs. Like procedures are grouped in a single module. Prototypes are used on all calls. Each module has a corresponding prototype member with the same name in QPROTOSRC. Wherever a default can be established the procedure should use *OMIT and/or *NOPASS. An error flag is returned from each procedure unless the value returned can be used to determine whether an error occurred. CONST is used for all parameters that cannot be modified. The parameters for a procedure are completely described in a heading for each prototype. Everything but our menu interface program uses *CALLER. (One exception, our trigger and DB modules). Service programs are grouped as universal, universal system functions, universal application functions, database, and application specific (Order entry, A/R, etc.). I would be interested to hear other peoples recommendations. David Morris >>> Rob Berendt <rob@dekko.com> 09/03 8:24 AM >>> There is some arguement for knowing some of this stuff instead of just looking it up. Many of use read the new manuals right away. Jumping to the sections 'what is new for this release'. It's when I have to show someone with a few years experience in RPG what the SETLL operation code is that I think certification would provide a higher level of confidence in the programmer. Does the RPG certification require renewal like the CCP does, (unless you were grandfathered)? I work with some sharp people but there is always someone that would not do something new if you pointed a gun to their head. I am starting to do all my new stuff in ILERPG but have yet to figure out how to do a procedure. God knows I want to. Purchased the ATS courses but they stop short of procedures. I mention this for two reasons. One, maybe the RPG certification is the challenge I need to get up to snuff. Two, any recomendations as to how to learn procedures, activation groups and what not? The new op codes, eval, record layouts, 'D' specs, etc were pretty simple to figure out. peteh@inwave.com on 09/02/98 10:36:52 PM Please respond to MIDRANGE-L@MIDRANGE.COM@Internet To: MIDRANGE-L@MIDRANGE.COM@Internet cc: Subject: Re: AS/400 RPG Certification Test At 08:56 09/02/98 -0500, Richard Baird wrote: >Ken, > >I took the test, got a 92. (woohoo) I suppose at some level these tests are fine, but I really question their value for anything but the lowest skill level. I write several different languages, and currently two different dialects of RPG. It' just not possible to keep it all 100% straight. For the more esoteric things (which indicators do what for TESTN? How do you find the system name for an SQL table? What the ~@!# is the op code for rollback this week?), I look it up in the manual. Life's too short to worry about this crap. You'd have to be an idiot savant. I think it's much more important to know how to quickly find that obscure bit of info than it is to be able to recite it on command. A good programmer can quickly shift gears and adapt to whatever environment is at hand. I'll always prefer someone who can think over someone who can only recite. Pete Hall peteh@inwave.com http://www.inwave.com/~peteh/ +--- | 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.