×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 16/04/2009, at 5:53 AM, Sharon Cannon wrote:
Yes, I did. From what I had read in the FAQ at the RPG World web
site, it didn't look like that wouldn't work with CALLP like it does
with CALL. I guess I just need to come up with a test to see if it
will.
The only status codes the ILE RPG manual mentions that you can check
for with CALLP using the E extender are 00202, 00211, and 00231.
That's what led me to believe that you can't check for 00001.
You can't check that status with %ERROR because it's NOT an error for
a program to return with LR on--it's a normal and expected state.
You can use %STATUS to check ANY status. Simply code a %STATUS check
after the CALLP.
Your reference to the ILE RPG Manual states:
"To handle CALLP exceptions (program status codes 202, 211, or 231),
the operation code extender ’E’ can be specified. For more information
on error handling, see “Program Exception/Errors” on page 82."
Note that you can't use %ERROR to check those status values either.
ALl that %ERROR indicates is a problem of some sort occurred. To know
which problem you have to use %STATUS.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.