The times they are a changin’, and apparently they’re changing too rapidly for some. There’s a lot of uncertainty among the readers of this magazine. I read it in email and hear it at user group meetings. The uncertainty boils down to one question: Does RPG have a future?
Midrange programmers want to know because RPG is the only applications programming language many of them know. IT managers in iSeries-centric shops want to know because their companies have a lot of money invested in applications written in RPG.
The answer is that RPG does indeed have a future. First, I want to explain why there is so much uncertainty. Then I’ll tell you why RPG is not dead.
Things Ain’t What They Used to Be
Why are people so shaky? There are several reasons. First, user interfaces have come a long way since the AS/400 was introduced in 1988. Windows has become widely used, and the Internet has been opened up to the general public. Everybody’s used to GUIs now, and the native RPG compilers don’t support a GUI in the same way that they seamlessly bind to display files.
Second, PCs have become a lot more powerful since 1988. Many businesses that used to require small business computers like the iSeries and its predecessors can now run on PC LANs, and the programming language of choice in the PC world isn’t RPG.
Third, it’s not uncommon to see an article in the trade press that says RPG is headed toward extinction.
Why RPG Is Going to Be Around for Awhile?
If the third reason is bothering you, relax. Reporters and columnists can—and do—write anything they like, even when they have no evidence to back it up.
RPG is going to be around for a while for several reasons. The first reason is the enormous amount of RPG code that installations depend on. Who can afford to stop all development to spend years rewriting his applications in Java? Who can be assured that, once the rewrite is complete, some other new and exciting language will not have replaced Java?
The second reason is that IBM is still enhancing RPG. The last version of RPG that some computer vendors supported was RPG II, primarily because they chose to put all of their eggs into UNIX, and later, into Windows NT. IBM continues to spend money on
RPG IV and VisualAge RPG so that RPG programmers can use their existing skills to develop new types of applications. I expect that the free-format calculations I wrote about in the September 1999 issue (see “IBM Cares More than You May Think”) will soon become a reality.
The third reason is that RPG is good at file processing. More “modern” languages, like C and Java, accommodate files and databases but don’t excel at file-handling. C was designed for writing systems software, like operating systems and compilers, not for printing payroll checks. RPG, like COBOL (whose death was falsely predicted years ago), was designed for business computing.
Keep in mind that it is interactive programming that is changing. Batch processing—overnight file updates, report generation—is fine as it is. Interactive processing is often handled by a two- or three-tier client/server architecture, in which the user interface, the business logic, and sometimes the file I/O, are in different programs. There’s no reason why the business logic and the file I/O can’t continue to be written in iSeries RPG, while the user interface is handled by either the Web, Java, Visual Basic, or even a visual RPG.
What RPG Programmers Should Do
RPG isn’t going to become extinct anytime soon, but the one-language shop may. This will make it harder for programmers who know only RPG to get jobs. Here are a few suggestions for RPG programmers:
• Learn RPG IV and ILE. The syntax of RPG IV, especially when the free-format calcs are added, is more like other widely used languages that you will likely have to learn. Learning to use service programs and subprocedures will help you understand how applications are built on other platforms.
• Learn one of the visual RPGs—either ASNA Visual RPG or VisualAge RPG. Visual programming consists of dragging and dropping icons to build a display, then filling in the code to drive it. Once you get the hang of one visual product, you’ll have a head start at learning others. I have heard that Visual Basic is now the most widely used programming language in the world. Wouldn’t it be nice to add that to your résumé?
• Learn a C-like language. Many of the new languages—Java and C# (pronounced C sharp)—are like C in their “features” (as I euphemistically refer to the logical results of poor language design).
• Learn object-oriented programming (OOP). It will be a while before it becomes widely used in business programming, but OO is on its way. In the meantime, you can use OO languages in the development of interactive client programs.
A True Story
Let me end with a true story. The instructors of a systems analysis and design course at the university where I did my graduate work had always required students to write their program assignments in COBOL. A new professor, fresh with her Ph.D. from a prestigious university, was assigned the course, and the first thing she did was to throw out the language requirement. Students were allowed to do their programming in any language for which the departmental machine had a compiler. The students were overjoyed because they were all more familiar with Pascal. But, would it surprise you to know that, within a few weeks, all of them abandoned Pascal and began writing their programs in COBOL? They had learned that newer is not always better, and that what looks good on paper isn’t always best in practice.
More than ever, there is a demand for IT to deliver innovation. Your IBM i has been an essential part of your business operations for years. However, your organization may struggle to maintain the current system and implement new projects. The thousands of customers we've worked with and surveyed state that expectations regarding the digital footprint and vision of the company are not aligned with the current IT environment.
TRY the one package that solves all your document design and printing challenges on all your platforms. Produce bar code labels, electronic forms, ad hoc reports, and RFID tags – without programming! MarkMagic is the only document design and print solution that combines report writing, WYSIWYG label and forms design, and conditional printing in one integrated product. Make sure your data survives when catastrophe hits. Request your trial now! Request Now.
Forms of ransomware has been around for over 30 years, and with more and more organizations suffering attacks each year, it continues to endure. What has made ransomware such a durable threat and what is the best way to combat it? In order to prevent ransomware, organizations must first understand how it works.
Disaster protection is vital to every business. Yet, it often consists of patched together procedures that are prone to error. From automatic backups to data encryption to media management, Robot automates the routine (yet often complex) tasks of iSeries backup and recovery, saving you time and money and making the process safer and more reliable. Automate your backups with the Robot Backup and Recovery Solution. Key features include:
Business users want new applications now. Market and regulatory pressures require faster application updates and delivery into production. Your IBM i developers may be approaching retirement, and you see no sure way to fill their positions with experienced developers. In addition, you may be caught between maintaining your existing applications and the uncertainty of moving to something new.
IT managers hoping to find new IBM i talent are discovering that the pool of experienced RPG programmers and operators or administrators with intimate knowledge of the operating system and the applications that run on it is small. This begs the question: How will you manage the platform that supports such a big part of your business? This guide offers strategies and software suggestions to help you plan IT staffing and resources and smooth the transition after your AS/400 talent retires. Read on to learn:
LATEST COMMENTS
MC Press Online