Return to Top Document

SAS on GSU's Unix computer:on screen viewing

To access SAS on the GSU's Unix computer system named cheetah you will first access GSU's Unix computer system named panther. Using the cheetah computer is the same as using panther, but to get to cheetah you must rlogin cheetah from panther. Although you can execute most Unix commands on both panther and cheetah, SAS is only available on cheetah, and pine (the email program) is NOT available on cheetah. Among the reasons for this roundabout access path is the fact that the easiest way to get a printed copy of SAS output is to email the output files to yourself and request your email program to print out the email message.

Below is a sample session . First you must access GSU's panther computer using on campus facilities or offcampus facilities.

Additional examples of SAS can be found in Introduction to SAS.

Conventions for type formatting used below.


Logging into panther. After each entry, the students presses the return key. The password is actually entered but does not show.

UNIX(r) System V Release 4.0 (panther)

login: gs01xxxx
Password: 
Last login: Wed Mar 12 13:01:44 from 131.96.45.35
*************************************************************************
* ** Send mail to help@gsu.edu for any questions about this system. **  *
*                                                                       * 
*  03/06/95:  The GSU Computer Ethics Policy has been approved and the  *
*             current version is available on the gopher, through GSU's *
*             home page, and in /usr/local/doc/GSU_Computer_Policy      *
*                                                                       *
*             Remember: Do NOT share your userid and/or password        *
*             with ANYONE.  Do NOT use any userid that you are not      *
*             authorized to use.                                        *
*                                                                       *
* ** Send mail to help@gsu.edu for any questions about this system. **  *
************************************************************************* 

You have new mail.

The student, having successfully logged into cheetah, remotely logs in to cheetah. Notice that no password is required using the rlogin.

 

panther:1 %rlogin cheetah
IRIX Release 6.1 IP21 cheetah
Copyright 1987-1995 Silicon Graphics, Inc. All Rights Reserved.
Last login: Mon Feb 10 14:54:37 EST 1997 by dscbms@panther.Gsu.EDU
*************************************************************************
* ** Send mail to help@gsu.edu for any questions about this system. **  *
*                                                                       * 
*  03/06/95:  The GSU Computer Ethics Policy has been approved and the  *
*             current version is available on the gopher, through GSU's *
*             home page, and in /usr/local/doc/GSU_Computer_Policy      *
*                                                                       *
*             Remember: Do NOT share your userid and/or password        *
*             with ANYONE.  Do NOT use any userid that you are not      *
*             authorized to use.                                        *
*                                                                       *
* ** Send mail to help@gsu.edu for any questions about this system. **  *
************************************************************************* 

Notice that the line number prompts started over at 1. The student has access to any files or directories that are created during the panther session. All files are jointly available between the two systems panther and cheetah.

The student looks at the directory of files made available by the instructor, ~dscbms. The files prefixed with "hatco." refer directly to examples in the text by Hair, Anderson, Tatham, and Black.

 

cheetah:1 %ls ~dscbms/files
aanews.read*          hatco.disc2*          missing.dich*
aaup*                 hatco.discHold        missing.univ*
aaup.doc*             hatco.discHold.3*     multiv.normal*
aaup.read*            hatco.discRndm*       
	[This list of files is only suggestive.
		Only files with an * are shareable]
hatco.clus.pca*       hplots                usnews.doc*
hatco.cor*            jet*                  usnews.read*
hatco.cor.manl*       missing*
hatco.d*              missing.64*

To see the contents of the file hatco.univ, Unix's more command is used. More prints one screenful at a time and waits for the user to press the spacebar. The letter q can be pressed to quit the screen listings.

There are no line numbers in this SAS program command file.

cheetah:2 %more ~dscbms/files/hatco.univ


       DATA hatco  ;
       options ls=79;
       options ps=60;
       INFILE '~dscbms/class/dsc8450/files/hatco';
            INPUT X1 X2 X3 X4 X5 X6 X7 X8 X9 X10 X11 X12 X13 X14;
       LABEL X1='DELIVERY SPEED'
              X2='PRICE LEVEL'
              X3='PRICE FLEXIBILITY'
              X4='MANUFACTURER IMAGE'
              X5='OVERALL SERVICE'
              X6='SALES FORCE IMAGE'
              X7='PRODUCT QUALITY'
              X8='SIZE OF FIRM'
              X9='USAGE LEVEL'
              X10='SATISFACTION LEVEL'
              X11='SPECIFICATION BUYING'
              X12='STRUCTURE OF PROCUREMENT'
              X13='TYPE OF INDUSTRY'
              X14='TYPE OF BUYING SITUATION';
        Proc means;
               var x1-x14;

--More--(88%)

       PROC UNIVARIATE PLOT NORMAL FREQ;
               var x1-x7 x9;
       Title 'This is a test run';

SAS is executed in line 3 using the SAS program command file hatco.univ in the instructor's subdirectory. SAS created two files.

Typically a user would not execute an uneditted SAS program command file from the instructor's file directory. Rather, typically a user would copy the instructor's file to his or her own file system on panther or cheetah, edit the program command, and then execute the editted copy. The copying and editting are not shown here.

In the SAS program command file the INFILE command (4th from the top) instructs SAS to get the data from the instructor's file system. For your convenience the same type of INFILE command is included in all of the SAS program command files provided in DSc8450.

cheetah:3 %sas ~dscbms/files/hatco.univ

ls shows that SAS created two files hatco.univ.log and hatco.univ.lst in the students file system even though the program command file was in the instructor's file system.

cheetah:4 %ls
hatco.univ.log   hatco.univ.lst

To see the contents of the file hatco.univ.log, Unix's more command is used. More prints one screenful at a time and waits for the user to press the spacebar. The letter q can be pressed to quit the screen listings.

The SAS command lines in the .log file are numbered, but otherwise look very much like those in the original program command file. The .log file also refers to pages of printed output in the .lst file as well as other procedural comments.

cheetah:5 %more hatco.univ.log
1 The SAS System                                                                
                     13:13 Wednesday, March 12, 1997

NOTE: Copyright (c) 1989-1996 by SAS Institute Inc., Cary, NC, USA. 
NOTE: SAS (r) Proprietary Software Release 6.11  TS040
      Licensed to GEORGIA STATE UNIVERSITY, Site 0008840004.




This message is contained in the SAS news file, and is presented upon
initialization.  Edit the files "news" in the "misc/base" directory to
display site-specific news and information in the program command log.
The command line option "-nonews" will prevent this display.



NOTE: AUTOEXEC processing beginning;
 file is /usr/local/sas611/autoexec.sas.

NOTE: SAS initialization used:
      real time           1.35 seconds
      cpu time            0.18 seconds
--More--(26%)
      

NOTE: AUTOEXEC processing completed.

1          DATA hatco  ;
2          options ls=79;
3          options ps=60;
4          
5          INFILE '~dscbms/class/dsc8450/files/hatco';
6               INPUT X1 X2 X3 X4 X5 X6 X7 X8 X9 X10 X11 X12 X13 X14;
7          LABEL X1='DELIVERY SPEED'
8                 X2='PRICE LEVEL'
9                 X3='PRICE FLEXIBILITY'
10                X4='MANUFACTURER IMAGE'
11                X5='OVERALL SERVICE'
12                X6='SALES FORCE IMAGE'
13                X7='PRODUCT QUALITY'
14                X8='SIZE OF FIRM'
15                X9='USAGE LEVEL'
16                X10='SATISFACTION LEVEL'
17                X11='SPECIFICATION BUYING'
18                X12='STRUCTURE OF PROCUREMENT'
--More--(51%)
19                X13='TYPE OF INDUSTRY'
20                X14='TYPE OF BUYING SITUATION';

NOTE: The infile '~dscbms/class/dsc8450/files/hatco' is:
      File Name=/cheetah01/dsc/dscbms/class/dsc8450/files/hatco,
      Owner Name=dscbms,Group Name=dsc,
      Access Permission=rw-r--r-x,
      File Size (bytes)=4900

NOTE: 100 records were read from the infile '~dscbms/class/dsc8450/files/hatco'.
      The minimum record length was 48.
      The maximum record length was 48.
NOTE: The data set WORK.HATCO has 100 observations and 14 variables.
NOTE: DATA statement used:
      real time           0.52 seconds
      cpu time            0.08 seconds
      
^L2 The SAS System                                13:13 Wednesday, March 12, 199
--More--(77%)
7


21          Proc means;
22              var x1-x14;

NOTE: The PROCEDURE MEANS printed page 1.
NOTE: PROCEDURE MEANS used:
      real time           0.09 seconds
      cpu time            0.03 seconds
      

23         PROC UNIVARIATE PLOT NORMAL FREQ;
24              var x1-x7 x9;
25         Title 'This is a test run';
NOTE: The PROCEDURE UNIVARIATE printed pages 2-25.
NOTE: PROCEDURE UNIVARIATE used:
      real time           0.30 seconds
      cpu time            0.10 seconds
      

NOTE: The SAS System used:
--More--(94%)
      real time           2.50 seconds
      cpu time            0.45 seconds
      
NOTE: SAS Institute Inc., SAS Campus Drive, Cary, NC USA 27513-2414

Also, by typing more hatco.univ.lst the user can look at the analysis output file (.lst, pronounced "list" ) on the computer screen. Once the user is satisfied that the analysis is performed he or she can mail the files to himself or herself as is shown next. Once the files are mailed, they can be editted and printed or forwarded, for example. Remember, the instructor needs both the .log and the .lst file.

The following example shows unix instruction for emailing the .log file to (yourself at) the address gs01xxxx@panther.gsu.edu.
The filename is entered last, after the greater than symbol (<).
To identify the message better, you may insert a subject between the command mail and the address. For example insert all of the following. -s "This is a .log file"

cheetah:6 %mail gs01xxxx@panther.gsu.edu < hatco.univ.log

cheetah:7 %logout
Connection closed.
panther:2 %logout
Connection closed.

Return to Top of Document