Am 18.04.2011 um 15:22 schrieb Vic: > >>> The first problem is that I want to start a job in a held state. the >>> qsub >>> man page says I can use the "-h" option to do this - but unfortunately, >> >> what options do you use in addition - it's a plain `qsub`? > > Not quite. > > The command I used was > > qsub -h -b y -cwd -now yes -N RSMTest2 -q test.q make -f rsm.make ARCH=M64 > USE_AVI=NO STATIC_BUILD=YES
Don't use "-now yes" - it will try to schedule an immediate job (i.e. a job which will run in an interactive queue). If it can't schedule it right now, it will only bail out with the error you mention below. As mentioned: you can try to append some random string to: -N RSMTest2_Fht3en4C option to have an unique name and submit the follow up job with this random pattern in: -hold_jid "*Fht3en4C" argument. -- Reuti >> It should return instantly > > It doesn't. > > I do get a job number (missed that earlier!), but I get "Waiting for > immediate job to be scheduled." in the xterm, and no control. Ctrl-Z > doesn't work, and Ctrl-C just kills the job. > >> And you are not a manager on your own I assume. > > No. And the users I'm writing these scripts for most certainly won't be > managers... > >> `qrls` yields the same >> result (although `qhold` and `qrls` use `qalter` in the end)? > > qrls works. I didn't know about that command :-) > > And strangely, repeating my "qsub -h" command now works as well - it > returns with the job in a held state. > > I don't know what's going on here. I need this to be absolutely reliable, > and there is some strangeness going on... > > Vic. > > _______________________________________________ > users mailing list > [email protected] > https://gridengine.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] https://gridengine.org/mailman/listinfo/users
