#RexxMast paths
3 messages in this thread
I am trying to launch arexx macros from a program by sending filenames to
the resident process. Everything works great, but when I try to access
macros using a relative path (i.e. :Programs/arexx/cg/macro.rexx), the
host looks for the file using the root that rexxmast started with for the
':' part of the path. Fair enough… if the macro is in rexx: AND has no
path, it works too. If it is in a subdirectory of rexx:, it doesn't work
'cause the host doesn't try its search paths if a path is included.
Still OK, cause I can assign rexx: to several subdirecto ries as well as
the original REXX: dir. Now the host doesn't want to find files with no
path that live in one of the multiple paths assigned to Rexx:, but if the
macro is specified as rexx:macro.rexx, then it will be found, presumably
because dos does the multi-assign support. The question:
Have I come across the best solution? Do you have any relevant tips?
Thanks,
Arnie
p.s. I assume the pragma for CD won't hold over several file messages..
Arnie,
I can offer a couple of comments, though I'm not sure I understand what problem
you're having. ARexx path searching doesn't work with DOS multi-assigns, as it
first obtains a lock on a search directory and then generates the names to look
for relative to that lock. If you have our PathHandler utility (from WShell),
you can build multi-apth REXX: directories. Otherwise, the directories ARexx
searches in will be the current directory of the client process and the REXX:
directory.
-Bill
It is as I assumed.. I would like the search path to include the CD of
the process which sent the filename/command to the 'AREXX' port. My
current solution is good enough.