Started by Snuffy on utilitybaseSnuffy
Posted: 2004-Dec-29 14:28:18
In OS3.9, the dir. 'rexxc' housed all the rx commands; they're in C: now. S-S assigns REXX: Sys:s/arexx. This is all OK, but I still get 5/1 rexx errors, even in correct dir with 's' flag set.
Where's Gutyahr when you need him?
Posted: 2004-Dec-30 02:30:46
Do you have an example/test case? How do you run the script?
Posted: 2004-Dec-30 04:25:52
It doesn't matter what, it's a path problem. From WB execute: rx opendrawer.rexx - works fine. If any other scripts are placed in the same directory - Sys:S/Arexx, are not found. All CED rexx scripts went here too, but aren't found. What's with the path problems in OS4? It appears to me that ASSIGN function has a linking problem.
Posted: 2004-Dec-30 05:08:49
Here is a test script to try. Put it in sys:s/arexx and try to execute by WB execute as: rx test.rexx
file name= Test.rexx
/* hello world script */
say "Hello world!"
This normally returns 5/1 no program found error. I can't determine the path problem? This rexx system doesn't is not conforming to OS3.9 layouts BTW.
Posted: 2004-Dec-30 05:46:36 · Edited by: nicomen
I'm sorry, but I simply don't understand what the error is ;/
The changed paths are to make things a bit more consistent and sensical. But I'm not sure if what you are experiencing is directly connected to slightly different path layout where system scripts or system commands are stored.
Ah ok, I think I get it now, you want the RX command to look for scripts given as an argument in a certain path?
Why don't you just do "RX S:ARexx/Test.arexx" ?
Posted: 2004-Dec-31 08:13:28
->"...Why don't you just do "RX S:ARexx/Test.arexx" ?"
Wow, was that sweet! Thanks! I don't know why I couldn't think of the full path, but that's IT! I hope this get mentioned in needed documentation to OS4 someday-'when it's done!'
A very Happy New Year to you, sir, and the UtilityBase!
just passing through
Posted: 2007-Jan-9 14:10:28
Just thought I'd toss in a bit more that might help you: the "S:ARexx/" path
is also given the old "REXX:" assignment in OS4, by default.
So you can think of and use that new directory just like you might have used
the old "SYS:REXX/" or "REXX:" directory - and access it's contents by the
same (OS3.9) assignment - "REXX:Test.arexx", etc.
Good luck and HNY to you too,
Posted: 2007-Jan-9 16:29:41
I don't see the problem either. I never got an error from rx. Rx looks in Rexx: by itself, no path needed. And I am quite sure that S:Arexx is contained in the default path as is S:Shell. You should check your startup scripts (startup-sequence and user-startup).
Anyway, what hinders you to add a simple path s:arexx add into s:user-startup ?