How does a specification file work?
A simple specification file looks something like this: IN Foo /localdir/input*Stuff.1 OUT Bar /localdir/*output.1 The first line uses the IN keyword to indicate that any files(s) in local directory space that match the naming pattern in the pattern field are input files for this program. The filename Foo is the file name that the program will expect to use as input when it is running on a remote host. The pattern field indicates that all files whose paths file the /localdir/input*Stuff.1 pattern should be considered input files for this program. Each possible input file is considered a job and is named according to the part of the file name that does not match the pattern. Thus /localdir/inputAStuff.1 would be job A, /localdir/inputBStuff.1 would be job B, etc. The second line uses the OUT keyword to indicate that any file(s) in local directory space that match the naming pattern in the pattern field are output files for this program. The filename Bar is the name of the output file tha
