If you want to get a bunch of programmers cooking, say something like this: “Anyone who uses GOTOs ought to be fired,” or “The RPG cycle should be banned.” I’m going to throw in another condiment of the same flavor and say, “Subroutines should be consigned to history.” Let me first say that I plan to stand well clear of the discussions that will no doubt ensue—I like to leave myself room to backtrack. The only absolute I adhere to is “Keep the customer satisfied.” But, just for the record, I haven’t used a GOTO in many years, I’ve almost forgotten how the cycle works, and the last time I coded a BEGSR was over two years ago when V3R6 first delivered the prototyped subprocedure.
Now, allow me to divulge some thoughts on what kinds of programs keep customers happy. They’re the programs you said would be ready with that new mod by Monday, and they are. They go right to work from the day you ship them and don’t come back for rework. When you assign the job of maintaining them to a programmer, there is no hint of fear on his face. They are programs that offer some little improvement the customer didn’t ask for but got anyhow.
In my view, none of these positive elements are possible with programs that are difficult to read, difficult to understand, difficult to test. With most programmers working directly off of screens, certain conditions should be met: Blocks of logic should span no more than a few screen loads. Logic should be structured (and names given) in such a way that it is understood with the least necessary effort. If anything goes wrong, the malfunctioning code should be easy to isolate and correct. And, most important, as a program’s task becomes more complex, its internal structure must become more simple (you can get away with all sorts of poor structure and ill-conceived assumptions when your task is minor).
Compare subroutines to subprocedures with these requirements in mind, and there’s no contest. Subprocedures have local variables; defined physically near to where they are used; and no matter what you call them, they are unique to that specific subprocedure. Subroutines can use only global variables. Subprocedures have formal interfaces; subroutines don’t. Subprocedures can call themselves recursively; subroutines
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