Introducing the New RPG Developer PDF Print E-mail
Written by Joe Pluta   
Tuesday, 31 July 2007

The new RPG language is not your father's RPG, and the industry needs a new publication devoted to this new language and to the new generation of programmers using it.

The title of the article is actually a bit of a pun. Not only does the phrase "New RPG Developer" highlight the name of our newly relaunched RPG Developer publication, but it also refers to that publication's readership, namely the "new RPG developer." So please allow me to introduce them both.

The New RPG Developer Publication

You can think of the new RPG Developer publication as an umbrella for all things RPG. At MC Press Online, we consider RPG to be essential to the future of the platform. However you slice it, if RPG is no longer the flagship language, then the System i loses its strategic advantage and becomes nothing more than an expensive Linux and Java machine. And while there are some black-helicopter conspiracy theorists who think that obsolescence is IBM's master plan, the investment in the hardware, in i5/OS, and in RPG itself argue against such a notion.

So, since we believe in the future of both the System i and the RPG language, we believe there is a need for a publication like RPG Developer. One of our ads even proclaims, "All RPG, All the Time," and that's a great five-word synopsis. However, the new publication is a bit more complex than its predecessor, because today's RPG itself is more complex. RPG has a unique dual nature of preserving legacy investments by still running code written decades ago, yet continually being upgraded to add the latest programming features. And the operating system has grown with it. IBM has evolved i5/OS to allow millions, perhaps billions, of lines of code to continue to run untouched while at the same time adding capabilities that most other operating systems can't even attempt, such as direct interoperability between all of its compiled languages and even support for interoperability with Java.

Few procedural languages provide the same level of programming sophistication, and none provides the performance that RPG achieves—performance due at least in part to its unparalleled level of integration with the database. Early versions of RPG enabled massive enterprise applications to run on the smaller, slower processors of the first IBM midranges. But the RPG compiler team is not content with that; as the hardware gets faster and the operating system more powerful, the language is continually enhanced to take advantage of this growth through features such as better access to the APIs of the system and native support for XML.

And so any publication devoted to RPG today needs to cater to both facets of the language: It needs the leading industry experts to provide you the very best in RPG development techniques, but it also must embrace the new generation of programmers. RPG Developer is the first publication designed to address both of those natures of the language. Back in June, Thomas M. Stockwell introduced our team of renowned RPG authorities from System i Developer. This month, I'm letting you in on the other side of the publication, what I like to refer to as "Extreme RPG."

Extreme RPG: The Other Half of the Publication

Extreme RPG includes not only new techniques in RPG development, but also new methods of delivering education for them. For example, take my new WDSC video tutorials. Even though I'm one of the old dogs in RPG development (with nearly 30 years in the field), I'm also the leading advocate of WDSC; I was one of the only non-IBM System i experts asked to speak at the Rational Software Developers Conference. And one of the first features of the new publication are monthly installments of my new video tutorials for WDSC.

But I'm hardly the only person you'll hear from. Instead, the new RPG Developer has begun a campaign of actively recruiting fresh, new faces from the industry, both young programmers and programmers who extend the boundaries of the language. We think we've put our best foot forward by getting Aaron Bartell to come on board as our first industry author, and other voices will include technological innovators such as Adam Glauser and of course the sometimes irreverent but always relevant Joel Klebanoff.

Speaking of Joel, you may have read his recent article on the IBM Academic Initiative for the System i. This program makes it even more clear just how relevant the System i is to IBM's strategic direction. This is IBM's version of extreme System i education. The folks at IBM are working with universities and community colleges around the country—indeed, even around the world—to invigorate their curriculums with as much System i knowledge as possible, thereby heading off the skills shortage that has become almost a self-fulfilling prophecy of the IT media.

IBM's recent reorganization of the divisions (see Thomas M. Stockwell's article "System i Division Split into Two Business Units") has predictably given more fodder to the black-helicopter folks, letting them proclaim ever more loudly the end of the platform. However, a recent conversation I had with IBMer Linda Grigoleit made it clear that nothing could be further from the truth and that the System i is one of the fundamental components of the IBM Academic Initiative. It's not easy, but IBM is making a concerted effort to get the education community and the business community together to provide employment opportunities for new programmers and thus to restore the appeal of IT as a career path—and the System i in particular as one of the premiere platforms for that career.

You'll hear more about the initiative; we feel it's one of the most important and exciting programs IBM has for our platform. Linda's primary message to customers and partners is to talk to the folks at the Academic Initiative and "help us help you." You can visit the System i page noted above, or their home page, or contact them via email at This e-mail address is being protected from spam bots, you need JavaScript enabled to view it . Raise your hand: Get in touch with IBM or nudge your business partners to do so. Get involved! One of my favorite concepts is internships: If you have a new technology project that you just can't find the time for but that might appeal to your local community college as a real-world pilot project, then contact the Academic Initiative to see if it might work as an internship for their programmers. Nothing works to build new talent like hands-on work, and of course you get the benefit of seeing the technology without having to invest a ton of your own time.

I can't think of a better way to attract and educate the new generation of "Extreme RPG" programmers.

The XRPG Programmer

So who is the XRPG programmer? It's the programmer who uses RPG to process XML. It's the RPG programmer who calls an API or who prototypes a Java method. It's the programmer who is as comfortable in PHP as in RPG. It's the programmer who pushes the envelope of PASE or QShell or sets up virtual Linux partitions in the i5/OS machine. It's the programmer who wants to understand every built-in function, who uses free-form RPG and ILE. It's the programmer who uses RPG as a stored procedure or as the business logic for a JSP Model 2 Web application. It's the programmer who relies on modern tools like WDSC to build the next generation of applications.

But like the language itself, the XRPG programmer has another side: The XRPG programmer isn't just concerned with gigahertz and gigabytes; the XRPG programmer understands the real application of software to business needs. XRPG programmers see the computer as the mission-critical tool for making users more productive and thus making businesses more profitable. And they know that RPG is the best tool in world for doing just that.

The XRPG programmer is you. Welcome to your new publication.

Joe Pluta is the founder and chief architect of Pluta Brothers Design, Inc. and has been applying Extreme RPG tactics to business solutions for decades. Joe uses RPG for everything from client/server architectures to web enabling green screen applications. He has written several books, including E-Deployment: The Fastest Path to the Web, Eclipse: Step by Step, and WDSC: Step by Step. Joe performs onsite mentoring and speaks at user groups around the country. You can reach him at This e-mail address is being protected from spam bots, you need JavaScript enabled to view it .


Last Updated ( Thursday, 04 October 2007 )
 
Discuss (7 posts)
J.Pluta
Introducing the New RPG Developer
Aug 14 2007 13:15:00
As gently as I can, Jacobus, I must completely disagree with the phrase "most projects with any real complexity cannot be overseen." I've overseen quite substantial projects, with over a dozen programmers writing code for multiple platforms and delivering over a million lines of code with full NLS support in a dozen languages, all delivered on time and on budget. The systems were thick client Windows/iSeries applications written in C and RPG, and while we didn't use any OO languages, we used plenty of good programming techniques (data hiding, encapsulation, you name it). <p>Is it easy? No. Do requirements change during development? Certainly. But here is the reality: <p>Programming projects do not require object orientation. They simply require good architecture and proper project management. I've seen agile development projects go off the rails just like any other programming project. <p>It's not the tool, it's the people. <p>Anyway, if you insist on your opinion that OO is required to write code, even in the face of the fact that I have managed large production projects quite well using procedural languages, then we no longer have a common point of discussion. To insist that your opinion is correct in the face of contrary evidence is simply to argue for argument's sake, sort of like quibbling over naming conventions or bracket indentation. It's ultimately irrelevant to the real task of delivering code. <p>Joe
#114840
Guest.Visitor
Introducing the New RPG Developer
Aug 14 2007 10:29:00
One big problem I see with Agile Programming is that technical documentation is sparse until the project is complete. And, with any project, the requirements grow as the project progresses, but the deadline does not change. So management believes they can throw *MORE* resources (programmers) at the project and still meet the deadline. <BR>
Additionally, how do you agree on the deliverables if they are not documented? How will you know when all the undocumented deliverables have been delivered? <p>So, how will those new programmers (maybe offsite, maybe in another country) get up to speed on the project requirements with sparse documentation? The current programmers on the project have to *STOP* programming and *VERBALLY* give them the requirements. Programming comes to a screeching halt. And giving technical requirements verbally allows for misinterpretations and confusion, further delaying the project as programming work has to be redone/retested. <p>I believe that documentation must be done up front, even if not in a formal format, so additional resources can easily be added to the project. They just need to know how to read, and can ask any unanswered questions. Then documentation is updated just prior to the project going live. <p>But I am certainly a big fan of time boxed interations. <p>Chris
#114839
jacobus
Introducing the New RPG Developer
Aug 14 2007 06:12:00
is a well-known exponent of the "agile" development movement, which contrasts with the traditional waterfall method. It adopts the real-world view that software development is a chaotic process, although in a controllable manner. It's based on the fact that most projects, with any real complexity can not be overseen (a user knows what he wants when he sees it). So, an application is "molded", constantly refactured with constant interaction with the user. There is no strict seperation between the roles of analyst and developer. The roots of XP are in the language called "smalltalk", which gives a very dynamic and adaptable programming environment. However, RPG is not a good language to use for XP-style programming, because it doesn't have the necessary concepts (like OO) to provide for the abstractions to be made when architecting an application along the way. An OO language maybe is not mandatory for XP, but it's certainly very much needed if one adopts this style of programming. With objects, one can encapsulate and abstract out common logic (or behavior) during the refacturing process. Parts of the problem domain which are good understood can be abtracted out and generalized. Parts which are not yet understood can be completely separated and molded later as soon as requirements are more detailed. <p>gr. jacobus
#114838
jeff_olen@hotmail.com
Introducing the New RPG Developer
Aug 02 2007 16:45:00
As always Joe, you put it all so eloquently. I have been one of the voices predicting the "end" of RPG for quite a while. I have moderated my stance on that to a degree. However, I still maintain that the developer that only knows RPG is not a very hot commodity and is not likely to be sought after by companies.<br><br>

As I mentioned in a separate posting, its all about finding the right tool for the job. RPG is well suited for many functions and has grown to a point where it is easily integrated with other development tools (e.g. Java, PHP, C++, etc...). So there is no reason to remain focused exclusively on RPG as your development tool as I know some RPG developers still are.<br><br>

Great article Joe. I look forward to seeing where the new RPG developer goes.<br><br>

Jeff Olen<br>
Olen Business Consulting, Inc.<br>
Email: <a href="mailto:jmo@olen-inc.com">jmo@olen-inc.com</a><br>
Phone: 760.703.5149<br>
Web: <a href="http://www.olen-inc.com">www.olen-inc.com</a>
#114837
J.Pluta
Introducing the New RPG Developer
Aug 02 2007 09:52:00
<i>Joe, are you planning to cover XP-style development using RPG? Or is the 'X' more a... marketing device?</i>&#32;<p>That's a darned good question, Buck. And it illustrates why we're reaching out to the newcomers. Personally, I'm too old school to have much use for Extreme Programming, at least as a total concept. Pair programming and design through refactoring just don't make sense to me. I do like the idea of lots of unit testing, although we had unit tests back in the days of cave computers. But I digress. <p>The idea is to make this publication the voice of the next generation of RPG programmers, and if somebody out there really thinks that XP programming can be applied to RPG, then I'm certainly willing to listen. If they can boil one facet down to 1000 words or so that make a workable tip to share with someone, then I'm all for it. <p>And THAT is what the Extreme in XRPG means, Buck: somebody with an idea that pushes the envelope of traditional programming. It's more the original meaning of Extreme, as in the X-Games, which XP appropriated to mean something very specific. BTW, Paul Tuohy tells me that he has been using the term Extreme RPG for years now, so I might be in copyright infringement here <grin>. <p>Joe
#114836
buck.calabro@commsoft.net
Introducing the New RPG Developer
Aug 01 2007 15:11:00
Joe, are you planning to cover XP-style development using RPG? Or is the 'X' more a... marketing device? <BR>
&nbsp;&nbsp;--buck
#114835
MC Press Web Site Staff
Introducing the New RPG Developer
Aug 14 2007 13:15:00
This is a discussion about <B>Introducing the New RPG Developer</b>.<p align='center'><a href=http://www.mcpressonline.com/mc?1@232.1KNKfHX1eQT.17@.6b509e8d>Click here for the article</a>.</p>
#114834


Discuss...
User Rating: / 0
PoorBest 
Related Articles
< Prev   Next >

   MC-STORE.COM