CompuServe Thread

#SAS/C 6.0

4 messages in this thread
#29066From: Vic WagnerOct 9, 1992 7:29 PM
Doug (or anyone else): We just installed SAS 6.0 and have encountered the following anomaly. Any clues as to what is causing this error would be appreciated so maybe we can get our compile environment set up correctly. 3.HEARTOFGOLD.ARTHUR:> sc optimize test60 SAS/C Amiga Compiler 6.00 Copyright (c) 1988-1992 SAS Institute Inc. CXWRN: Can't create intermediate file QName: test60.q ERROR: 0 ***Can't open optimizer intermediate file The manuals don't mention this error ("0") Also, how come we can no longer direct to where the 'quad' files go? We would rather they go in RAM: on our machine. BTW, look at this: 3.HEARTOFGOLD.ARTHUR:> sc optimize objname=ram: test60 SAS/C Amiga Compiler 6.00 Copyright (c) 1988-1992 SAS Institute Inc. of course, we DON'T want our object file in RAM: <sigh>
#29084From: Michael McCormickOct 10, 1992 8:53 AM
Vic, I believe SAS 6.0 does not use quad anymore. As for the other question I'll take a look in the docs and see if you missed anything. MikeM:) "Amiga means never having to say your sorry!"
#29163From: Oxxi Tech SupportOct 12, 1992 2:25 PM
Wrongo Mike, SAS/C 6.0 does use quad files. It creates them in the objectcode directory. Mike Uman []xxi, Inc. >>> running under AutoPilot
#29592From: Doug WalkerOct 25, 1992 9:01 AM
SAS/C does open a quad file, but it only uses it if it runs out of memory while compiling. Most of the time, it should remain empty. Since it only uses it when you run out of RAM, putting the quad file in RAM: would be less than effective 8^) RE: your CXWRN message, this is very strange; I haven't heard of any similar problems. Is the directory you're in writable? I.E. would an Open() of the file in that directory succeed? It's possible that an open failure might cause that problem. If that's not it, make sure the disk is not full. AHA! I just recreated your CXWRN message by attempting to compile on a 100% full floppy. I first got a "Disk full" requester, then hit RETRY without freeing up any space and got the funny message. Looks like a case that calls for a better message. Thanks for the report. –Doug