Often, when I'm debugging an RPG IV program, I run across some built-in functions whose values have been set by an opcode or perhaps even the %PARMS built-in function. As we all know, for some reason, IBM seems to have decided that we don't need to see the value represented by these built-in functions. So we are left to step through our code, watch our logic unfold, and guess what the built-in function's value is.
One way to circumvent this shortcoming in the debugger is to copy the value of those built-in functions to a work field. Then, using debug, you can view the content of those fields to see what the built-in function was set to.
The problem with this technique is that it puts variables and logic into the program that have nothing to do with the program itself. While it is fine for development/debug mode applications, production mode applications certainly should not have that extra stuff planted in them.
This is where compiler directives can help. While they don't completely resolve the issue at hand, they do provide a workaround for those annoying debugging issues related to built-in functions.
The basic idea is that you use the /IF DEFINED directive along with some descriptive word, such as "DEBUG," and condition the inclusion of certain lines of code based on that word being defined at compile time. You then include declarative statements and logic that define some work fields and then copy the value of the built-in functions into those work fields. Then, while you're in debug mode, you can view the content of the built-in function as it was when it was copied into the work fields.
The example in Figure 1 declares three works fields and then copies the value represented by %FOUND and %PARMS into two of those work fields.
|
Figure 1: Use compiler directives to simplify debugging.
The good thing about this technique is that, unless you also include a /DEFINE DEBUG statement in your source code or specify DEFINE(DEBUG) when you compile, the source code between these /IF DEFINED(DEBUG) and /ENDIF statements is not included in the compiled object.
If you are not a fan of the /IF and /ENDIF compiler directives and simply want to test for "debug mode" at runtime, you can use the DEBUGMODE() procedure from the RPG ToolKit. It provides you with a way to check for debug mode at runtime and then do whatever is necessary, based on the mode the program is in.
Here's an example of using the DEBUGMODE built-in function. Note that you can test for debug mode or not debug mode by optionally specifying *ON or *OFF for the first parameter.
|
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 RPG World and is the author of his own Web site and of the RPG ToolKit, an add-on library for RPG IV programmers.
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