On Tue, 8 Feb 2011 13:38:23 -0800, John Walker <[email protected]> wrote:
>In regards to REXX's� signal command.� It works fine if when you suddenly >need to leave a loop, you enclose it in a do end construct.�� I've never >had > stack overflow issues from using it. The stack issue occurs with the subroutine stack. If you have called a subroutine, and the subroutine issues a SIGNAL, you terminate active loops and DO groups but you remain within the subroutine until a RETURN is executed. See the TSO/E REXX Reference and look closely at the example showing how to use SIGNAL to implement a multi-way call. It shows setting up a dynamic label, then CALLing a subroutine which issues a SIGNAL that derives the label name to invoke, with an eventual RETURN that gets you back to the CALL statement. -- Walt Farrell IBM STSM, z/OS Security Design
