From: Doug Payton To: All
Perhaps many RPG programmers already know of the following technique. I think it is worthwhile because it makes screen error checking and function key use very readable.
6 contains an example of a screen-handling program which must validate the month and year entered. For this example, the year must be the current year.
Figure 6 contains an example of a screen-handling program which must validate the month and year entered. For this example, the year must be the current year.
Before the ITER and LEAVE operation codes were introduced, I would use IF and ELSE. As a result, I would often end up with more than 10 ENDs at the bottom of the loop. Now the ITER and LEAVE allow me to put the ENDIF directly after the ITER. Control reverts to the end of the DO loop I am currently in. LEAVE exits me from the loop entirely. The LEAVE right before the ENDDO is optional. For instance, if you want to redisplay the screen after the submit, remove LEAVE.
If someone has a better approach, please share.
From: Ted Holt To: Doug Payton
First of all, I do not like the LEAVE and ITER operation codes. My understanding of structured programming is that every structure, which can be a loop or a subroutine, or just a related group of calculations, should have only one entry point and one exit point. LEAVE and ITER violate this concept.
Besides that, trying to figure out which loop will be affected by the LEAVE or ITER gets awfully confusing. I realize that I'm asking for trouble, but I believe that GOTO and TAG, used in a structured way, are clearer than LEAVE and ITER.
7 illustrates how you would write the same procedure without LEAVE and ITER.
Figure 7 illustrates how you would write the same procedure without LEAVE and ITER.
I like to put the verification calculations in their own subroutine, since verifying the keyed data is a task of its own. The ERROR variable functions like a parameter passed back from the routine, since RPG subroutines can't accept parameters.
From: Doug Payton To: Ted Holt
I see your point about LEAVE and ITER. I just happen to like them and use them quite a lot. I hate GOTOs because you can GOTO practically anywhere in the program you'd like, which is nearly impossible to read after enough of them have been implemented. When I use ITER and LEAVE, I place a comment on the same line documenting which DO loop I'm in.
Structured Programming
Figure 6 Sample Interactive RPG Program
*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 C 1 DOWEQ1 C EXFMTFORMAT1 C *IN03 IFEQ *ON =F3 C LEAVE =Exit program C ENDIF * C IBMO IFLT 1 C IBMO ORGT 12 * Your error routine goes here C ITER =Re-send screen C ENDIF * C IBYR IFNE UYEAR * Your error routine goes here C ITER =Re-send screen C ENDIF * . * No errors, submit. * . C LEAVE =Exit, no errors, * and job was submitted C ENDDO =1DOWEQ1 C MOVE *ON *INLR *. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7
Structured Programming
Figure 7 Eliminating LEAVE and ITER with Structured Code
*. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7 C ERROR DOUEQ'0' C CANCEL OREQ '1' C EXFMTFORMAT1 C MOVE *IN03 CANCEL 1 C CANCEL IFEQ '0' C EXFMTVFY1 verify input C ERROR IFEQ '0' * . * No errors, submit. * . C ENDIF C ENDIF C ENDDO C MOVE '1' *INLR * C VFY1 BEGSR * C MOVE '0' ERROR 1 assume all OK C IBMO IFLT 1 C IBMO ORGT 12 C IBYR ORNE UYEAR C MOVE '1' ERROR C ENDIF * C ENDSR *. 1 ...+... 2 ...+... 3 ...+... 4 ...+... 5 ...+... 6 ...+... 7
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