Lab00, CISC181, Spring 2004

Welcome

The Sun Rays are XTerminals that you can use to access the machine called strauss. Strauss is where you will do your actual programming in this course. In lab, you'll access strauss via the Sun Rays.

Note: Outside of lab, you may access strauss from any computer connected to the Internet, provided you have the right access software (e.g., a secure shell client program.) Your instructor will say more about that in lecture.

Goals for Lab Zero

1. Make sure you know how to log in and out of the Sun Rays.
2. Make sure you know how to access the web on the Sun Rays.
3. Make sure you can find the CIS181 home page.
4. Make sure you can logon to WebCT and find CISC181.
5. Make sure you know how to create a text file with either vi or emacs.
   If you already know one or both of these editors, use the one you are most comfortable with. If you don't know either one, learn emacs (start with Chapter 15 in Anderson, plus the material below.) You'll create a text file, and submit it both online via WebCT and on paper.
6. Make sure you can create a C++ program, compile it, run it, script the results, and submit via WebCT and on paper.
7. Make sure you understand the lab policies. There may be a quiz on these next week!

Goals 1 and 2: Login/Logout and Web on the Sun Rays

Info on logging in and out and accessing the web on the Sun Rays is at the following link:

http://copland.udel.edu/~pconrad/UnixAtUD/SunRay.html

That link also has information on what to do if you don't yet have a University Unix account. Finally, there is also information on that page that will help you pull up an "XTerm on Strauss"; you'll need that when you get to Goals 5 and 6.

Goals 3 and 4: CISC181 homepage and WebCT

http://copland.udel.edu/~pconrad/cisc181

There, you should find the main web page for the course. You should find a link to the syllabus, and a link to the labs directory, where the lab you are now reading can be found. Some of the links will lead you, for the time being, to empty directories which will soon be filled with your projects, homework assignments, source code examples, and lecture notes.

Then, click on the link that says "WebCT". This should take you to a login screen, and then directly to the WebCT page for this course. Alternatively, you can go to the main WebCT page, and click "logon".

http://www.udel.edu/webct

Once you are on WebCT, be sure to find the calendar link, and check out the reading assignments for the next two weeks.

Goal 5: Creating a text file with vi or emacs

Open an XTerm on strauss (If you don't know how and/or are not sure what "Xterm on Strauss" means, follow this link to the Sun Ray documentation: http://copland.udel.edu/~pconrad/UnixAtUD/SunRay.html).

If you are NOT yet familiar with vi or emacs, start learning emacs. Go to an xterm on strauss, and type "xemacs". For more instructions on what to do, follow this link:

http://copland.udel.edu/~pconrad/UnixAtUD/EmacsTips.html

If you are already familiar with vi or emacs, go ahead and use vi or emacs to create a text file called "lab00.dat" containing the following, each on a separate line: your name, your hometown, your favorite US state other than the one in which your hometown is located, and your unix userid.) For example, Prof. Conrad's file would look like this:

When you are finished, send the file to the printer in Willard 009 with the following Unix command:

qpr -q whlps lab00.dat

Also, upload this file as part of your submission for Lab00 in WebCT. But DON'T SUBMIT YET! Just upload for now. You'll hit submit at the end of lab, after you've also uploaded your C++ program and script file.

If you aren't sure how to do this, check the following link for help, or ask your TA:

http://www.udel.edu/webct/student/c2answer.html

(If you accidently hit submit before you get your C++ program uploaded, don't freak out; your TA can reset the assignment so that you can try it again. Your TA might not be able to fix it on 2/11, because its the first week of the semester and his TA account might not be active yet. But if not, he can fix it up for you by next lab on 2/18, or at the latest on 2/25, and you can make it up then without penalty.)

Goal 6: C++ programming on Strauss

1. Create a file lab00.cc that contains the following (except substitute your name and Unix user id for those of Jane Doe, and use today's date.)
   
   DO NOT include your student number (NEVER include that number in anything you submit in this class!)

   // lab00.cc Jane Doe doej@udel.edu 2/10/04 // traditional first program (Anderson, p. 383) #include <iostream> using namespace std; int main() { cout << "Hello, world!" << endl; }

2. Once you've created this program, use the following command to compile it (compile means: translate from C++ into machine language, or it cannot be translated because of errors, report the errors) with one of the following commands. At this point in the semester, you may use either one (later on, I may tell you to use one or the other.) Note that the first command is CAPITAL CC, not lowercase cc.

CC lab00.cc

OR

g++ lab00.cc

The first command (CC) is a commercial compiler, supplied by Sun Microsystems. The second command, g++ is an open source compiler, supplied by the GNU project, which is staffed by volunteer programmers. From time to time, we may discover differences, but for now, I don't care which one you use. Sometimes if you have a tricky syntax error it is useful to try both, because sometimes one gives you more useful error messages than the other.

3. In both cases, a new file is produced called "a.out". To execute this file (run your program, type the following:

./a.out

You might be able to get away with just typing a.out without the leading ./, or you might not; it all depends on how your account is set up. (It has to do with the Unix concept of the "path"; you'll read about that in the Anderson text later on.)

If all goes well, you should see something like the following:

> CC lab00.cc > ./a.out Hello, world! >

4. You are now ready to use the "script" command to make a record of your work.

Note that you must be careful when using the script command. The script command will wipe out your work if you are not careful!

The thing to remember is: on the command line, type "script" followed by the name of a .txt file; for example:

script lab00.txt

This is correct!!!!

Never put "script" followed by the name of a .cc file. It will wipe out your .cc file!

script lab00.cc

WRONG!!! WRONG !!!! WRONG!!!!

Ok, now that we have that out of the way...

Type "script lab00.txt". Then go through the following steps:

• list your program (type "cat lab00.cc" to do this.)
• compile your program (type "CC lab00.cc" or "g++ lab00.cc" to do this)
• run your program (type "./a.out")
• exit from the script (type "exit").

5. Now, use "cat lab00.txt" to make sure your script looks ok, and use the following command to print both your .cc file and your .txt file. (Yes, I want you to print both of them, and submit both of them, even though the .cc file is contained inside the .txt. file. Humor me. We'll talk more about that in lecture.)

qpr -q whlps lab00.txt 

qpr -q whlps lab00.cc 

And finally, you are done with Goal 6!

Goal 7: Understanding Lab Policies

First, lets get this out of the way: Lab attendance is mandatory.

If you were in my CISC105 last semester, you may recall that we had a pretty laissez-faire attitude about lab attendance. However, my boss (Dr. Carberry) and I had a talk about that, and the result is that I'm going to be a bit stricter about that in this and future semesters. Attendance will be recorded. Be sure to sign the attendance sheet and return it to the TA before leaving your lab session.

Lab attendance is reported on WebCT as, for example, LA0211 (lab attendance for 02/11/04.) Grades are marked as P, A, E, or U for "Present", "Absent", "Excused", or "Unknown". You must at least make an appearance to be counted present.

Please read about more lab policies by following http://copland.udel.edu/~pconrad/cisc181/04S/labs/lab_policy.html

Finishing up: What to turn in for this lab

1. Be sure that you have a printed copy of your three files: lab00.dat, lab00.cc, and lab00.txt (script file).. Hand these to your TA before leaving the room. If you are making up this lab, hand it to him on 2/18/04 during Lab01, or at the very latest on 2/25/04 during Lab02 (that should only be for students who for whatever reason, added the class late.)
   
2. Be sure that you uploaded a copy of all three files to WebCT (lab00.dat, lab00.cc, and lab00.txt). Then, click submit to sent these to your TA.
   
3. Grading:
   • printing each of the three files is 10 points each (30 points total)
   • submitting each of the three files is 10 points each (30 points total)
   • the correctness of the content is worth 40 points

Next Steps:

Do your reading assignment (found on the Calendar in WebCT) and complete the "prelab exercises" in the Lab manual for Chapter 1 before coming to lab next week (2/18/04)

(Note: this originally said: 1/25/04, which of course should have been 2/25/04, but that was wrong anyway, since next week's lab is 2/18/04, not 2/25/04. Anyway, the TA's will accept the work up through 2/25/04, just this one time.)