| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | REXX errors |
On Tuesday, 96/01/02, Ruud Senden wrote to All about "REXX errors" as follows: RS> Does anybody know how to do this? Is there a single command for RS> this, or do I have to create this error-message myself, by using RS> the CONDITION-function and the RC and SIGL-variables (together with RS> errortext and sourceline-functions)? Hi Ruud, You have just posted the solution yourself. The CONDITION() built-in function and the SIGL variable will tell you what happened and where, respectively. The RC variable will not usually be meaningful. Regards Dave * KWQ/2 1.2i * PL/I: Understatement is the purest form of eloquence. --- Maximus/2 3.01* Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4) SEEN-BY: 270/101 620/243 711/401 409 410 413 430 808 809 934 955 712/407 515 SEEN-BY: 712/517 628 713/888 800/1 7877/2809 @PATH: 440/4 141/209 270/101 712/515 711/808 809 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.