Academic Computing Sun Solaris Server

"uisacad", a Sun Solaris server, is the academic Unix system at UIS. This system is primarily for class projects requiring Unix software such as programming languages, statistical packages, database systems, web development tools, etc. The installed software includes:

Solaris 8, SAS, SPSS, Cobol, Oracle, C/C++, Perl, PHP, and Java programming tools, Apache Web server, FTP & Telnet servers, Samba, and a number of GNU utilities. 

Click here to apply for an account

How to logon to your account

Introduction to Unix

How to set up a personal web site
  
To publish from Netscape Composer  
    To transfer (ftp) your web pages and images to uisacad 

Getting Started with Oracle

Using Cobol

Running Java Server Pages (JSP), Servlets and Beans

Enabling CGI

Printing

Running SAS


How  to logon to your uisacad account

To establish a remote connection to your account on uisacad you will need a Telnet program. The easy way for telneting on Windows PCs is using Microsoft Telnet which comes with Windows:

Note: The first time you logon to your account you will be prompted to change your password.

From a Windows PC

  1. Click on Start on the Windows task bar (bottom left corner) and select Run

  2. Type:  telnet  uisacad.uis.edu

  3. When prompted, enter your login name (NetID) and Password

  4. After you successfully login, you will be in your home directory on uisacad

  5. To exit from your account, enter exit at the prompt

From a Macintosh: 

The standard Macintosh Telnet program is BetterTelnet (you can download a copy from http://www.cstone.net/~rbraun/mac/telnet/)

  1. Open BetterTelnet

  2. Select Open Connection from the File menu

  3. Enter uisacad.uis.edu as the host name

  4. When prompted, enter your login name (NetID) and Password


Setting up a personal web site

Note: You must logon to your uisacad account and change your initial password before you can publish your web pages. (How  to logon to your uisacad account)

You can create a personal web site on uisacad. Your WWW documents must be stored in a directory named public_html under your home directory.  This directory is already created for you with world-executable and world-readable permissions. 

The welcome page for your web site should be named index.html. This page will be displayed when someone accesses you web site. The web address (URL) for your web site is: 

 
http://uisacad.uis.edu/~your-account-id/

Your-account-id is your login identifier. For example, the URL for the account named asmit01s  is

http://uisacad.uis.edu/~asmit01s/

You may use a text editor such as Notepad or more a sophisticated web development software such as FrontPage or Dreamweaver to create your html documents. FrontPage and Dreamweaver are available in all  Academic Computing labs on campus.


How to publish from Netscape Communicator 4.7 

1. Create your HTML document in Composer

2. Click Publish

3. Enter the Page Title and the HTML Filename

4. Under HTTP or FTP to publish to:  enter: 

                         ftp://uisacad.uis.edu/export/home/your_NetID/public_html

5. Enter your NetID for User name: 

6. Enter your Password

6. Click OK

Example:

After successful uploading you'll get a message box like this

The URL for the above page will be       http://uisacad.uis.edu/~asmit01s/test.html
     


To ftp  your web pages and images 

You can upload your web pages and images from your local computer hard drive or floppy disks to your account on uisacad server using an FTP program like WS_FTP (for Windows) or Fetch (for Mac).

For Example if your account is asmit01s and your html documents or images are on a floppy disk, follow the steps below to transfer your files to your account on uisacad using WS_FTP:

1. Launch WS_FTP

2. Enter server's name, your user ID and password:


3. Click OK

4. On the left side of the window, navigate to the directory on your hard disk or floppy that contains the files you wish to upload: 

5. Click on the public_html directory on the right side of the window. This takes you to your public_html directory. You have to save files in this directory to publish on the web. Select the file you want to transfer from the left side box. For Example asmit01s is transferring his file called test.html from his floppy disk (A drive). After selecting the file, click on button. Your file will be transferred to your account. Now the files are ready to be viewed on the web. 

The URL for the file called test.html for asmit01s account is

     http://uisacad.uis.edu/asmit01s/test.html
   

Steps for using Fetch to transfer files are similar.


Using Cobol

You may create your Cobol source files using one of the  editors on  uisacad (vi, joe, or emacs) To use joe, for example, log on to your account and enter the command:

joe myprogm.col

Or, you may wish to create your source file on a PC and upload the file to your account on uisacad using FTP.

To compile your source file, enter the command:

cob myprog.cbl

Any errors are displayed on the screen. If there are a lot of errors then you can direct the errors to a listing file so you can refer to them while applying corrections. The following command creates a listing file, myprog.lst:

cob -P myprog.cbl

Once you have cleared all your syntax and logic errors, you can create a program that you can run directly. To get the best speed you should create native pbject code. To do this, generate your program using:

cob -u0 myprog.int

This creates a native object code file myprog.gnt. You run this using the cobrun command.

Reference Manuals: The complete set of Micro Focus reference manuals are available in the HSB 109 computer lab. You may only use the manuals in the lab. 


Running Java Server Pages (JSP), Servlets and Beans

To enable your account for JSP, servlets and beans, send an email to System Administrator. Once your  home directory is jsp/java servlet enabled you should see two links listed in the directory. One is  jsp and the other is classes.  You must place your servlets and beans in the classes folder and your java server pages in the jsp folder.  Then to invoke a servlet you can use the URL:

http://uisacad.uis.edu:8080/student/servlet/your-account-id.servletname

All bean and servlet classes must be compiled manually and  packaged with your-account-id.
Example: package  your-account-id;

Then you can instantiate them from your jsp file with the directive:
<jsp:useBean id="mybean" scope="page" class="your-account-id.bean-name" >

JSP files can be accessed by using the URL:
http://uisacad.uis.edu:8080/student/jsp/our-account-id/jspfile.jsp

Servlets and JavaServer Pages (JSP) 1.0: A Tutorial


Enabling CGI

To enable your account for CGI, send an email to System Administrator. Once your home directory is cgi enabled you should see a link listed in the directory. The link name is mycgi. You must place your cgi scripts in the mycgi folder. Then to invoke a cgi script you can use the URL:

http://uisacad.uis.edu/cgi-bin/username/cgi_file.cgi

Where username is your login name and cgi_file.cgi is the name of your cgi script.


Printing

The default print queue for uisacad is HSB109_Q
located in the computer lab HSB 109.
To print a text file to that printer simply run the command:
enscript   file_name
 
To send a printjob to the Line Printer you can run the command:
lp  -d  lprint  filename


Running SAS

I.  Login to your account.

In any of the computer labs, double-click on the uisacad icon on the desktop (or telnet to uisacad.uis.edu). When the login prompt appears, type your user account name (your NetID).  When the password prompt appears, type in your password (your initial password is set to your birthdate in yyyymmdd format)

II. Create a program file within an editor.

Enter an editor emacs, joe, vi, or vim (Vi IMproved)

 The SAS program file should have a name with .sas at the end.

For example, to enter joe to create a file called

'prog1.sas', enter

$  joe prog1.sas

from the shell prompt.  The prompt may vary depending upon which shell is used.  The $ is the prompt for the Bourne shell. Now enter your SAS program statements into the editor .

Press Ctrl-kh to display the help screen in Joe. Press Ctrl-kx to save your file and exit from Joe

III..  From the shell $ prompt, run the SAS program. 

For example, enter  

$ sas prog1.sas             

at the $ prompt.

When the $ appears again, the program has run.

IV.  Check for errors. 

Entering

  $ more prog1.log

at the $ prompt echos the log file contents on your screen.  The log file lists program errors.  If you have misplaced a command in your SAS program, forgotten to enter a semi-colon at the end of a line, or are unable to read a data file correctly, then the errors from these mistakes will be listed in the SAS log file. 

If errors show up in the log file, go back to the editor and correct the lines in your program file.  Go to step III again and rerun the corrected program.

Please make all corrections to files, run them and check your .log and .lst files to make sure they are correct before printing.  Print only your good output.

V.  If no errors occurs in your program when you run SAS, then print the list file.  The list file is created only if there are no errors in the program.

For example, entering

$ lp prog1.lst&

from the $ prompt requests a print of your SAS output.  Ask a consultant in the lab to assist you with getting your printout from SAS.  If you want to print all 3 files from your run, enter:

$ lp prog1.sas prog1.log prog1.lst&

 MANUALs: Manuals can be checked out and used in the lab only.  There are a number of SAS manuals available in the Consultant's office bookshelf.

§         SAS Language

§         SAS Language and Procedures

§         SAS System for Regression

§         Introduction to SAS – The Intro to SAS is very valuable in understanding the structure of SAS programming.

To check out any of these manuals, present your UIS Identification card to the lab consultant and sign out the manual at the Log Sheet at the Consultant's Desk.  Bring the manual back to the consultant’s desk when you are finished using it.

There are many SAS explanations and examples presented in the SAS manuals.