QCAPCMD has several important advantages over QCMDEXC. For the purposes of this tip, I am going to focus on the error handling abilities of QCAPCMD. However, it would be worth your time to check out the IBM documentation on the QCAPCMD and find out what the other differences are.
To understand the difference between the way QCMDEXC handles errors and the way QCAPCMD handles errors it is necessary to understand the way most system APIs handle exceptions. Most system APIs use an error structure called QUSEC (or Qus_EC_t if you are using C) to return information regarding exception conditions and error data. You can find the layout of this structure in the QSYSINC library (QUSEC in QRPGLESRC). This structure is what nearly all APIs use to provide exception data back to the calling program. It is interesting to note that QCMDEXC is somewhat of an exception (no pun intended) in the way it handles exception conditions because it does not use the QUSEC structure.
What you gain by using the QUSEC structure is that if an exception condition occurs when the QCAPCMD command is executed, then the information regarding the exception is returned via the QUSEC structure. More importantly, the exception condition is "trapped" and not passed up the stack to the RPG program that ran it (i.e., a program exception condition will not be triggered and no *PSSR). This gives you much more flexibility in the way that you handle these types of conditions.
On a separate note, if you are going to be using system APIs and have access to C, then I would highly recommend creating simple C "wrappers" for commonly used APIs. By using "wrappers," regardless of language, you can usually reduce the number of parameters that you need to pass and create a simpler interface to the API. Also, when you can use C, the program code is simpler (and usually shorter) and you have access to structure field names that makes sense. Maybe it's just me, but "Err->Exception_Id" is much clearer than "QUSEI." In the downloadable code, I have included both a C wrapper and an RPG wrapper for the QCAPCMD so you can be the judge as to which is simpler to read and use.
Use CRTRPGMOD to create both the TESTCMD module and the RPG version of the RUNCMD module. Use CRTCMOD to create the RUNCMD module from the C source. The TESTCMD program will function the same regardless of which RUNCMD module you bind it to.
Jeff Olen is a member of the AS/400 development team at Gauss Interprise, a content management software company located in Irvine, California. He can be reached by email at
Jeff Olen is a super-spy now but keeps his cover identity intact by working for video game studios on the East Coast. So when he’s not out killing members of ISIS or rescuing refugees, you can find him playing Wolfenstein II or testing the new Fallout 76 releases at his beach house in Costa Rica. In any case, he can’t be reached. You can email his cat at
MC Press books written by Jeff Olen available now on the MC Press Bookstore.
 |
||
 |
|
The IBM i Programmer’s Guide to PHP Get the scoop on how PHP can—and should—be deployed on IBM systems. List Price $79.95 Now On Sale
|
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