1. check on behavior of sym-links

2. implement new 'ln' command in archive to the user can set up symlinks on
the archival storage system.

3. implement new 'help' command in archive so the local help info can be
accessed whenever the user likes.

4. implement rmdir, mv, mkdir in archive

5. extraneous directory creation at erdc, possibly elsewhere, when -p option
is used.  example below:

jim% archive put -p -C Wakes/towed-Re10000-Fr100-v000/run02-init *.tar &

creates the directory run02-init under the pre-existing path
Wakes/towed-Re10000-Fr100-v000 as expected.  However, at the same time, it
also creates the extraneous directory structure

Wakes/towed-Re10000-Fr100-v000/run02-init/Wakes/towed-Re10000-Fr100-v000/run02-init

The files are written to the correct location and the extraneous directory is
empty.  This is not a real problem except for the fact that it can be
confusing when hunting for files at some later date.

  ---Tom

6. allow migrate operation all by itself so one can prefetch data.