CompuServe Thread

#rx: unknown command

4 messages in this thread
#181482From: Kenneth P. OlsonJan 10, 1995 9:32 PM
Although I have Rexxc in my path, when I try to execute a certain script I get: rx: unknown command rx failed returncode 10 I know this is supposed to launch my arexx script, but it doesn't. Is there something I can do to get the computer to follow the path and find rx the way it is supposed to? I think the script which calls the second one containing the rx command simply changes directory to ram: and sets up a new shell. Even so why doesn' the path seem to be followed?
#181494From: Thomas HuntJan 10, 1995 10:42 PM
Kenneth: I had a similar problem when I installed VLT (Valiant Little Terminal). It required the ARPREXX.LIBRARY and gave me the same message when I tried to run scripts. Check documentation to see if a specific AREXX library is needed. I got the ARPREX.LIBRARY off of CIS and it works fine. Good luck. Tom
#181511From: Steve AhlstromJan 11, 1995 12:33 AM
Ken, You say that rexxc is in your path … you might double check by typing "Path" in the shell and see if it's REALLY there. I've had problems with paths depending on how I brought up the shell. If I used the icon from sys:system the paths were defined. If I started the shell from Toolmanager (either a dock or the menu) then the path wasn't set (only current directory and c:). I'm sure there's a reason why due when things run in the WBStartup — but I got tired of fighting it. I just copied the path line from the startup-sequence and pasted it into my shell-startup and now the path is always set.
#181601From: Steve MerzenaJan 11, 1995 7:42 PM
This might sound redundant, but have you checked to be certain that your Arexx program begins with: I once wrote a small Arexx program and went nuts trying to figure out why it wouldn't work, until, lo and behold! , I realized those two little symbols weren't there. If they aren't, it isn't recognized as an Arexx program, period. –Steve–