How to run interactive jobs

If you want to use a GUI or have a short program you want to test or debug, we suggest using the "qlogin" command. This will automatically grab a compute node with 1 core and an interactive shell. The example below details how to use qlogin to grab a compute node.

First load the "sge" module:
[abc123@login01 ~]$ module load sge

Now type "qlogin" to get an interactive shell:

[abc123@login01 ~]$ qlogin
local configuration not defined - using global configuration
Your job 6644 ("QLOGIN") has been submitted
waiting for interactive job to be scheduled ...
Your interactive job 6644 has been successfully scheduled
Establishing /cm/shared/apps/sge/var/cm/qlogin_wrapper session to host ...
[abc123@compute004 ~]$

Now you can load the module and run your application.

* NOTE * - When using qlogin with parallel applications you will need to specify how many cores you will use. The batch scheduler, Grid Engine, by default interprets this as only 1 core and assigns a node accordingly. The problem with this is our compute nodes offer 32 cores. So, if you are running a 32 core job and Grid Engine *thinks its only using 1 core, Grid Engine could potentially place you on a node that is already running active jobs (or vice versa). To fix this you'll need to tell qlogin how many cores you expect to use.
[abc123@login01 ~]$ qlogin -pe threaded 32

Change "32" to the number of cores you expect to use during your interactive session.

-- AdminUser - 08 Nov 2016

This topic: Main > WebHome > RunningJobs > RunningYourInteractiveJobsThroughBatch
Topic revision: 20 Nov 2019, AdminUser
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding UTSA Research Support Group? Send feedback