-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
REXX: SIGNAL ON FAILURE isn't working (Not recognized). #88
Comments
SIGNAL ON FAILURE was added to REXX in VM/SP Release 6, after REXX had been available on VM for about 5 years. |
It looks like SIGNAL ON ERROR doesn't work correctly either. It is not being signaled when a CMS command gets a non-zero RC. ======================== SIGNAL ON ERROR 'ACCESS 333 Z' ERROR: SAY 'ERROR SIGNALLED'Currently returns:
|
Down load a test fix from https://www.dropbox.com/s/xrbt2nlcv2958aj/brexxfix.aws?dl=0 This is an aws tape made with a TAPE DUMP BREXX TEXT command. |
I don't know how Bob Bolch intended to fix this, and his Dropbox link is now dead, but I've written a fix of my own and sent a pull request to the main source tree. |
Thank you for the fix. As a Rexx programmer, I appeciate having VMCE Rexx
(BRexx) woking properly.
Bertram Moshier
WB8ERT
…On Fri, Jun 7, 2024, 03:49 Ross Patterson ***@***.***> wrote:
I don't know how Bob Bolch intended to fix this, and his Dropbox link is
now dead, but I've written a fix of my own
<https://github.com/RossPatterson/CMS-370-BREXX/tree/feat-failure> and
sent a pull request to the main source tree
<adesutherland/CMS-370-BREXX#76>.
—
Reply to this email directly, view it on GitHub
<#88 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5BYKGMV2HLQJJBM2EH4T2LZGFX27AVCNFSM6AAAAABI6HXS76VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJUGM4DMMRTGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This is being tracked as bREXX Issue #75 and is fixed in bREXX 1.1.0 beta 01. |
My REXX program template (which I just uploaded) does:
/------------------------
| Enable trap processing |
*------------------------*/
SIGNAL ON ERROR
SIGNAL ON FAILURE
SIGNAL ON HALT
SIGNAL ON NOVALUE
SIGNAL ON SYNTAX
I found REXX on VM/CE isn't supporting SIGNAL ON FAILURE
When REXX hits the statement SIGNAL ON FAILURE the following appears as the error:
template exec
29 - SIGNAL ON FAILURE
Error 25.3 running template, line 29: SIGNAL ON must be followed by one of the keywords ERROR, HALT, NOVALUE, NOTREADY or SYNTAX;
found "FAILURE"
Ready(20025); T=0.16/0.20 11:17:41
The text was updated successfully, but these errors were encountered: