I had an interesting conversation at RPG World earlier this month. The discussion was about shop standards, which led to questions about the benefit of the use of "template programming." This technique is widely used in most AS/400 and iSeries shops. It involves the use of pre-written programs of various categories, such as work-with panels, subfield searches, and file maintenance.
Programmers copy these templates to create new applications, thus easily following the shop standards for screen layout and program structure. The other and perhaps more beneficial aspect of copying program templates is that programmers can get programs running more quickly if some of the code is already written for them.
I refer to program templates as "starter code," program source code that is used to get you started writing a program. A lot of commercial applications use starter code, including those that take advantage of wizards to generate customized starter code for an application. These wizards prompt the developer for a few variables and then copy the starter code--with a few modifications--to a destination library.
But what was interesting about this conversation is that it seems that no one updates their templates. They use program templates to help set shop standards, but they haven't updated those templates for (in some cases) years. One programmer admitted to using templates that had originally been created at least seven years ago.
While it is good to have shop standards--and it is a great idea to use program templates as starter code--it is my opinion that those templates should be reviewed annually. Programmers don't write applications the same way they did five years ago, so why should they have to use five-year-old templates to get them started?
Program templates that are not reviewed and updated periodically can contain code that is just as obsolete as those legacy applications we all love to hate. Here's a check list that you can use to verify whether or not a program template needs to be reviewed and brought into the 21st century.
-
Is it written in RPG III (aka RPG/400)? Then rewrite it.
- Is there an IFEQ, WHENxx, DOWxx, or DOUxx in the code? Then rewrite it, because it was simply ported from RPG III.
- Does it avoid RPG IV subprocedures? Then rewrite it.
- Does it take advantage of the INDDS? If not, review it to see if you can reduce the use of indicators throughout the code.
- Does it use function key response indicators to condition code? If so, review it and consider avoiding command key response indicators. Instead, use position 369 of the WSDS and named constants to respond to the function keys that are pressed.
- Does it use hard-coded literal values? If so, review it and move all the hard-coded values to named constants.
- Does it have standard values hard-coded in the Definition specifications? If so, review it and consider moving fixed values that are shared between all programs or all program templates into their own /COPY source member. Then, embed them back into the programs using a /COPY or /INCLUDE directive.
- Does it need to be compiled on multiple releases of OS/400? If so, review it and consider leveraging the conditional compiler directives. These are directives that allow you to include and omit source code based on the release of OS/400 that is being used to compile the program. The benefit here is that you can embed code that will do a particular task easily under a later release and retrofit it so it will work on older releases.
These are just a few of the things to take into consideration when reviewing or rewriting your shop's standard programming templates. If you don't have standard templates, you should consider creating some type of starter code library soon. It will help your developers leverage the skills of others. One thing to consider might be to have your best developer build the starter code/program templates and allow the others to review the code.
Bob Cozzi has been programming in RPG since 1978. Since then, he has written many articles and several books, including The Modern RPG Language --the most widely used RPG reference manual in the world. Bob is also a very popular speaker at industry events such as COMMON and RPG World and is the author of his own Web site, rpgiv.com.
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