My application uses object rexx for scripting tasks
and I am trying to move it to version 3.10. The
application is Win32-based and and links to rexx.dll
and rexxapi.dll at runtime. I have put all the
required runtime components into a private folder
which is referenced in the PATH variable as ..\oorexx.
Under 300, the dlls load and link and execute
perfectly (as they have under all previous versions),
Under 301, the dlls also load and link, but the very
first call to RexxStart fails. I provide additional
data in the attached file (since I don't have symbols
for the two dlls, the info may not shed much light on
the problem). I am not running the RexxApi service;
the rexx environment is strictly defined by the
contents of the oorexx folder and the PATH reference
I have switched between the 3.00 and 3.10 environments
(by renaming the 300 and 301 folders to "oorexx")
repeatedly to reproduce the problem without fail. I
have made no changes in my application, so I must
assume the problem is with 310.
At this point I am clueless as to how to get around
this problem (other than continue running with version
301). I would greatly appreciate any thoughts you
might have on this issue.