One alternative might be to request an interactive job (-I), which will cause their qsub to block until the job gets scheduled and connect your terminal to the running instance. Of course if your submitted application doesn't actually take any interactive input, it'll probably just automatically run to completion--which is arguably the minimum functionality that you're looking for.
Another option would be to write a shell script that loops while calling qstat, waiting for your job to complete.
Torque/PBS
Looking briefly through the man page for their "qsub", I don't see any direct equivalent. http://www.clusterresources.com/torquedocs21/commands/qsub.shtml
One alternative might be to request an interactive job (-I), which will cause their qsub to block until the job gets scheduled and connect your terminal to the running instance. Of course if your submitted application doesn't actually take any interactive input, it'll probably just automatically run to completion--which is arguably the minimum functionality that you're looking for.
Another option would be to write a shell script that loops while calling qstat, waiting for your job to complete.