USE and EC-FLOW-USE

As I understand it, EC-FLOW-USE is a sort of
indicator for possible recursive USE directives.
But what is supposed to happen in
this situation ?
And how to detect it ?

Roger

"Roger While" <simrw@sim-basis.de> wrote in message
news:e69kf1$g8i$00$1@news.t-online.com...
> As I understand it, EC-FLOW-USE is a sort of
> indicator for possible recursive USE directives.
> But what is supposed to happen in
> this situation ?
> And how to detect it ?

Using WD 1.6 as the reference:

Page 584, 14.8.45.3 USE statement, General rules,
"2) During the execution of a USE procedure, if a
statement raises an exception condition that would cause
the execution of a USE procedure that had previously
been activated and had not yet returned control to the
activating entity, the EC-FLOW-USE exception condition
is set to exist."

Page 421, 14.5.12.1.5 Exception-names and exception
conditions, Table 14, shows EC-FLOW-USE as fatal.

Page 418, 14.5.12.1.2 Fatal exception conditions,
describes the actions to be taken, generally. Translating
from the general case to the specific case of
EC-FLOW-USE, what happens will depend on whether
the EC-FLOW-USE, EC-FLOW, or EC-ALL exception
conditions have been enabled; whether a USE statement
has been specified for EC-FLOW-USE, EC-FLOW, or
EC-ALL; and whether the PROPAGATE ON directive
has been given. Ultimately, if the EC-FLOW-USE
exception condition is enabled, the program must be
terminated abnormally; but if the exception is not enabled,
what happens is implementor-defined.

I think that a semaphore for each USE statement might
be reasonable for detecting the exception condition.