It's likely that there is an error in your job submission script. Check to make sure it is trying to cd to the correct directory, load any necessary modules, etc. Make sure your submission script has a blank line at the end. Staff can assist if requested; please email email@example.com and let us know your username, which machine you are using, and the path to your submission script.
Putting the following line in your submission script will cause the system to send you emails about the status of your jobs:
#PBS -m abe
The emails that the system sends you will sometimes contain information regarding the nature of an error your job is experiencing. The emails will be sent to your MSI email account (your-MSIfirstname.lastname@example.org). Your MSI email may be checked by performing an ssh to login.msi.umn.edu and using an email client such as mutt.
If your job experiences an error there may be an error output file created that will contain information. Error outputfiles by default have names ending with .e followed by the job ID number, and are usually created in same directory as your submission script. Standard output files by default have names ending in .o followed by the job ID number. Standard output files may also be examined to determine if a job has executed properly.
The messages in your job output files and job status emails may help you or the MSI staff determine the source of a job error if one exists.
If it is determined that an error exists in code which you have written, MSI has debugging software resources available which may help you locate and fix the error.