Adam, 

Thanks for your response.  Specifying -q queue@host doesn't achieve what I'm looking to do.  In my case, I'm trying to set up a drmaa runner that will send the job to a torque host that is different from the one that is set in /var/spool/torque/server_name on the client host.  Configuring the drmaa runner with -q queue@host doesn't do this for me.  It still sends the job to the torque host specified in  /var/spool/torque/server_name.

Any other suggestions?  

- Bart


On Wed, Jun 26, 2013 at 4:06 PM, Adam Brenner <aebrenne@uci.edu> wrote:
Bart,

I believe drmaa://-q somehost@queue-name

will work. However I could be very wrong. It has been a while since I
messed with the actual drmaa runners.


--
Adam Brenner
Computer Science, Undergraduate Student
Donald Bren School of Information and Computer Sciences

Research Computing Support
Office of Information Technology
http://www.oit.uci.edu/rcs/

University of California, Irvine
www.ics.uci.edu/~aebrenne/
aebrenne@uci.edu

On Wed, Jun 26, 2013 at 1:28 PM, Bart Gottschalk <bgottsch@umn.edu> wrote:
> Is it possible to specify the torque host as part of a DRMAA runner URL?  I
> haven't been able to find a native_options parameter to allow for this.  I'm
> using the old style cluster configuration.
>
> drmaa://[native_options]/
>
> Also, I haven't been able to find a list of native_options anywhere.  Does
> such a list exist?  If so, where?
>
> ___________________________________________________________
> Please keep all replies on the list by using "reply all"
> in your mail client.  To manage your subscriptions to this
> and other Galaxy lists, please use the interface at:
>   http://lists.bx.psu.edu/
>
> To search Galaxy mailing lists use the unified search at:
>   http://galaxyproject.org/search/mailinglists/