CpSc 212 Handin

The handin Command

Programs and other files can be submitted for grading electronically using the handin command. The syntax of the handin command is as follows:

handin.<course>.<section>  <assignment>   <filelist>

where

<course> is the number of the course (212)
<section> is the number of your section
<assignment> is the number of the assignment
<filelist> is a list of the files to be handed in

For example, a student in 212 section 1 could hand in files prog3.java, list.java, and list2.java for assignment 3 with the command

handin.212.1  3  prog3.java list.java list2.java

Note that the complete command name in this example is handin.212.1, i.e.,

no blanks.

Wild card characters in file names are allowed, but directory names are not. Thus all files in the current directory may be handed in for assignment 3 by using the command

   handin.212.1  3  *

but not

   handin.212.1  3  .

As an additional example, all files ending in .java in the current directory could be handed in by

   handin.212.1  3  *.java

Notes:

Be sure to submit all the source files needed to compile and run your program under Solaris on the CS Suns (or other designated system). You can also include test data that you used or documentation/comment files, if you wish.
Do not submit executables,class files, core dumps, etc.
If the command works successfully, it will list the number of bytes transferred for each file handed in. Note: Sometimes (rarely) there is a false error message at the end, but if all files are listed, there should be no problem.
You can resubmit files or submit additional files by using the handin command again. Existing files (with the same name) handed in again will be overwritten. To delete a previously handed-in file that is not to be replaced, or to make other corrections, send email to your instructor.
It may be helpful for you to submit a .doc file listing the files needed to compile and run your program if there is anything special that is required. You can also include documentation about the status of the program (what works and what doesn't) or other information about your program.
Be very careful to hand in all of the files needed for your program, and compile and test your program(s) using exactly the same files that you hand in. Always retest the program after making any change (including comments), and after transferring a file from one system to another.
To avoid submitting files as the wrong assignment or for the wrong section, you should set up an alias for the handin command for your course and section. This can be done by placing an alias command such as
```
          alias handin handin.212.1
```
into your .alias or .cshrc file. After doing this, you can handin files with a command such as
```
          handin  3  *.java
```
(Note that the alias command will not become effective until the next time that you log in or open a window, unless you use the source command to activate the alias.)