Velocity Scheduler (vsched) for Serial Jobs

Miscellaneous tips:

• You can log in interactively even when type is set to batch
• Connecting to the compute node once your job has started differs for Windows and Linux:
  -- For Linux, ssh to the comput node
  -- ssh is not available on the Windows compute nodes; first make a secure connection to a login node, then connect to the compute node via Remote Desktop for Windows
• T: is useful both for scratch space and for speedier file access on the local node
• Commands in a batch script can either use explicit pathnames or rely on current working directories
• Your batch script can call a perl or python script
• Spaces and cases are sometimes important
• Use vsched –j from a batch node to obtain the Jobid for a machine
• Linux can hide special characters when moving files between systems. To clean up, use dos2unix:
  -sh-3.00$ dos2unix MyJob.sh
• FAQ

Remember:

• For jobs submitted from a Windows login node or run on a Windows cluster, you must always change your password with vsched to be recognized by vsched; if you change your password by any other means, issue vsched -r from a login node. More on registering your password with vsched
• You must submit your job with vsched -submit
• The path to your batch script cannot include spaces
• To share resources and avoid unnecessary billing, use vsched -cancel when you're done