CompuServe Thread

#TTX and SAS/C 6.1

6 messages in this thread
#30779From: Darron C. KnutsonDec 13, 1992 12:31 AM
I have a problem using TurboText with the SAS/C 6.1 compiler. Specifically, when I try to run the compiler/linker from TTX with Compile.ttx ARexx macro supplied by SAS, sc will run and compile my source files, but then the console window opened by the ARexx macro to take the output from the macro says "slink: unknown command; slink failed returncode 10". I'm using WShell 2.0, by the way. Yes, SC: and SC:C are in my search path. When I run sc from a shell, everything works as expected — sc compiles the source and slink gets called and finishes the job. What am I missing here? Darron
#30785From: Jim Nangano/SYSOPDec 13, 1992 12:57 PM
Darron, As a "guess", are you running TurboText in the background from your user startup? If so, are you starting it before you've added SC:C to your path? I suspect that the shell being spawned from within Turbotext, because it inherits the Path from the Turbotext process, doesn't have the added SC:C. Hope this helps…. – BobR (Motorola Inside!)
#30804From: Darron C. KnutsonDec 13, 1992 10:05 PM
Bob, Thanks for the suggestion. I'll take a look and see. What's really strange is that the ARexx macro can find the sc command but apparently sc, which calls slink, cannot find slink. Weird. Maybe it's time I got well enough acquainted with ARexx to write my own stuff that would work by opening a new WShell to handle the compile. Darron
#30805From: Darron C. KnutsonDec 13, 1992 10:32 PM
Bob, I gave it a shot and made sure that TurboText didn't get started before the necessary path command got executed and still got the same results. The ARexx script can find SC but SC apparently cannot find SLINK. Very strange, since SC and SLINK are in the same directory, SC:C, which is in the search path, which I put in s:user-startup, s:WShell-startup, and s:Shell-startup, just to make every possible process got the complete path needed. I'm still stumped. Thanks again for your interest and help. Darron
#30833From: Doug WalkerDec 15, 1992 8:37 PM
A couple of possibilities… There is a REXX script called "sc.rexx" that has confused many people… are you sure you are really running the SC compiler command and not that? If you're running the REXX script, perhaps it's not finding either SC or SLINK correctly. Second, are you making SC resident? Perhaps you're picking SC up from the resident list but SLINK is not resident. It's probably not a bad idea to make both of them resident if you have the memory. If neither of those fixes it, then I must admit to being stumped, but I can see that Ken Yarnall (the author of the macros) gets a copy of your message, and perhaps he can clear it up. (I would try it, but I don't have a copy of TTX.) –Doug
#30856From: Darron C. KnutsonDec 16, 1992 11:18 PM
Doug — Thanks for the suggestions. It appears you've solved my problem. I can't find a script called "sc.rexx" either in my rexx: directory or in sc:rexx. However, making both sc and slink resident did the trick! I still don't understand why the script didn't work before, as sc and slink are in the same directory and I hadn't made either of them resident before. If Ken Yarnall has any suggestions, I'd be glad to hear them. Oh well, all's well that ends well. Thanks again for the help! Darron