...by the way: did you even try to use slashes on PC? That works! SAS tries
to convert all to the right syntax. You could use always slashes in your
libname / filename's instead of backslashes and the code should run on both
machines. If you have a UNIX machine, just try to use a backslash and tell
me about your results!
On Wed, 6 Apr 2005 07:19:20 -0700, Terjeson, Mark (IM&R)
>If SAS is loaded onto the machine (or server),
>then running SAS itself will look and feel the
>same. Initially for the SAS stuff, the path
>names use forwardslashes in Unix while the PC
>environment uses backslashes. e.g. in the PC
>world you might have:
> libname token 'C:\MyDir\MySubDir';
>while on the Unix platform it would look like:
> libname token '/home/mydir/mysubdir';
>When I move files back and forth between PC
>and Unix, the libname paths are basically all
>that has to change to run on either platform.
>The other area is when you are using the X
>command or LIBNAME to invoke utilities or
>other programs outside of SAS. Of course you
>have to use utility and operating system names
>for which environment you are in. e.g. in PC
>you might do the following:
> X 'dir';
> X 'mkdir newfolder';
>and in Unix the corollary would be:
> X 'ls -CF';
> X 'mkdir newfolder';
>Sometimes you'll notice that the PC have some
>of the same names as Unix.
>As for writing scripts, in the PC you wrote
>myscript.bat with DOS commands. There is no
>magic here to convert, you just have to look
>up the utilities that will perform the similar
>task. In Unix you similarly create a text file
>that has the Unix o/s (Operating System) commands.
>The unix scripts can, but don't have to, have file
>extensions in the name. The text file of commands
>can be invoked with the shell name prior, e.g.
> sh myscript
>or ksh myscript
>but you can also set the executable flags with
> chmod +x myscript
>and then you can skip the shell name and just
>invoke the script itself:
>So other than converting the pathnames and using
>different external utility names and parameters
>there won't be much difference, until you get into
>environment specific features of SAS that only have
>to do with one o/s. But for the most part you can
>run SAS stuff on either platform and just change
>paths and external commands, and voila!
>For version 7 or later you can copy/paste datasets
>between platforms and off they run just fine. For
>version 6.12 or earlier you had to convert the
>datasets between platforms.
>Sorry to make it sound too simple, but for the first
>99% of the time that's all you'll need to worry about.
>Hope this is helpful.
>Senior Programmer Analyst, IM&R
>Russell Investment Group
>Global Leaders in Multi-Manager Investing
>From: SAS(r) Discussion [mailto:SAS-L@LISTSERV.UGA.EDU] On Behalf Of
>Sent: Tuesday, April 05, 2005 5:54 PM
>Subject: SAS on Unix 101
>I neaver used SAS on Unix or Mvs can anybody explain me or forward me
>the links which has useful links about sas on Unix and Mvs (Some Real
>time examples would highly appriciated), and also somebody please
>expalin what kind of shell scripts One is expected to write to run on
>SAS on Unix, I would appriciate any of help.
>Thank you for Your time