#1050 RXOFNC/RXEXF exits do not honor set flags

[Rony G. Flatscher]

If an RXOFNC/RXEXF exit handler sets the flags rxfferr ("invalid call to routine") or rxffnfnd ("function not found") and returning with RXEXIT_HANDLED the respective Rexx conditions do not get raised.

Returning instead RXEXIT_RAISE_ERROR will raise error 48, "Failure in system service", which is not the same as what the flags indicate.

[Rick McGuire]

Based on your comment in the mailing list, I suspect you have an error in your code. In order to raise those errors, you must return the RXEXIT_HANDLED return code, not RXEXIT_RAISE_ERROR. Our test buckets have variations for these conditions and the tests are clearly working. If this is not the case, then you'll need to provide a sample that will recreate the problem.

[Rony G. Flatscher]

A testcase can be found (due to its size) at http://wi.wu.ac.at/rgf/rexx/tmp/debug/, named
"tmp20120222.zip", which demonstrates this behaviour:

    - download and unzip this archive, change into


    - open a command line window and change into the subdirectory "tmp20120222"


    - follow the few instructions given in the "readme.txt" file

RXOFNC-exit: The test demonstrating this behaviour is in the subdirectory "test_no_condition_raised" and can be started by entering "java JavaRunRexxWith_RXOFNC_Exit" which will load the Rexx interpreter and execute the Rexx program stored in "testRexxWith_RXOFNC_Exit.rxj".

RXEXF-exit: The test demonstrating this behaviour is in the subdirectory test_no_condition_raised" and can be started by entering "java JavaRunRexxWith_RXEXF_Exit" which will load the Rexx interpreter and execute the Rexx program stored in "testRexxWith_RXEXF_Exit.rxj".

[Rick McGuire]

I can't figure out from your code where you think those flags are getting set, but when the exit returns, neither of those flags are ever set. This appears to be a bug in your code.

[Rony G. Flatscher]

Was programming error of reporter, ooRexx is fine.