Rick McGuire wrote:
> The Rexx instances are independent entities, but the associate thread
> context is not so. You will get rather unpredictable effects with
> creating two on the same thread and trying to switch back and forth.
> The last one created will end up getting picked up in most legacy
You still haven't corrected the code that's incorrectly registering
the exits. RXSIOSAY, etc. are not individual exits that you ran
register call backs for. There's just the single exit RXSIO. Same
problem with RXINIEXT. What you're effectively doing is sending other
exit calls to the I/O exit,
Rick McGuire wrote:
You still haven't corrected the code that's incorrectly registering
the exits. RXSIOSAY, etc. are not individual exits that you ran
register call backs for. There's just the single exit RXSIO. Same
problem with RXINIEXT. What you're effectively doing is sending other
exit
David Ashley wrote:
> All -
>
> Unfortunately, the problem you are seeing with access to the build
> machine is not a problem I have direct control over. It turns out the
> the build machine is up and runiing just fine, but the ATT network is
> timing out when you try to access it. I have opene
Rony G. Flatscher wrote:
David Ashley wrote:
All -
Unfortunately, the problem you are seeing with access to the build
machine is not a problem I have direct control over. It turns out the
the build machine is up and runiing just fine, but the ATT network is
timing out when you try to access
David Ashley wrote:
> Rony G. Flatscher wrote:
>>
>> David Ashley wrote:
>>> All -
>>>
>>> Unfortunately, the problem you are seeing with access to the build
>>> machine is not a problem I have direct control over. It turns out the
>>> the build machine is up and runiing just fine, but the ATT
Rick -
Ok, my bad. User error. :-)
After fixing a problem I made for myself. I got my first page of output
from Mod_ooRexx. Not everything is working yet but the rest should just
be normal programming errors. Debugging all this will take a bit but I
should have everything working in a few days
Good to hear you found the problemI didn't spot anything obvious
in my quick glance at the code.
I notice you're still using RexxVariablePool to set variables in the
INI exit. You might want to use the SetContextVariable() API instead,
but an even better solution might be to use the NOVALUE e
Rick McGuire wrote:
> Good to hear you found the problemI didn't spot anything obvious
> in my quick glance at the code.
>
> I notice you're still using RexxVariablePool to set variables in the
> INI exit. You might want to use the SetContextVariable() API instead,
> but an even better solutio
Other than "debug it", no. A traceback on the call might be useful.
Rick
On Tue, Mar 24, 2009 at 5:39 PM, David Ashley
wrote:
> Rick McGuire wrote:
>> Good to hear you found the problemI didn't spot anything obvious
>> in my quick glance at the code.
>>
>> I notice you're still using RexxVa
10 matches
Mail list logo
