| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Rexx`ercising |
I've have REXX support added to my app. I had it before, but I've done it
right this time... :-)
I have a thread that blocks on a semaphore until it is told to call
RexxStart() to launch a script. After RexxStart returns the thread blocks
on the semaphore again.
I have registered my Subcommand and Exit handler functions and they work
fine except for the exit handler.
The script runs fine until I try to abort it via RexxSetHalt() or if I try
to use use tracing via RexxSetTrace() (or 'trace a'in the rexx script).
Intercepting RXSIOSAY (Rexx's 'say' command) works fine, however, if I
receive RXSIOTRC (Rexx trace or error messages) I get a sys3175.
Anybody have any ideas?
Phil
Fido: 1:124/8014.1 | Internet: phil.crown{at}bluecafe.com
--- Blue Wave/Max v2.22b
* Origin: * MacSavvy OS/2 BBS * Dallas, Texas * 214-250-4479 * (1:124/1208)SEEN-BY: 50/99 270/101 620/243 711/401 409 410 413 430 808 809 934 955 SEEN-BY: 712/407 515 517 628 713/888 800/1 7877/2809 @PATH: 124/1208 1 396/1 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™.