Rick McGuire wrote:
> The other possibility is you've called RexxCreateInterpreter() on a
> thread that was already owned by Rexx. In that case, the
> RexxThreadContext returned with the instance pushes down the active
> one and can create the same symptoms if you return without destroying
> the
The other possibility is you've called RexxCreateInterpreter() on a
thread that was already owned by Rexx. In that case, the
RexxThreadContext returned with the instance pushes down the active
one and can create the same symptoms if you return without destroying
the instance. In that situation, y
Rick,
when invoking that program via Java, then it works without a problem!
If invoked via Java then in the native layer an AttachThread() is
invoked, a Routine object is created and invoked with CallRoutine(),
followed by a matching DetachThread().
---rony
Rony G. Flatscher wrote:
> Rick McG
