Skip to content

Disable OpenPBS Job Query

What is query_other_jobs?

In PBS (Portable Batch System), the query_other_jobs option determines whether users can see the jobs that other users have submitted to the system.

  • Default Setting: True (Enabled by default)

Possible Values:

  • True — Users can see jobs submitted by other users.
  • False — Users can only see their own jobs.

Defalut Value

What Happens When query_other_jobs is Enabled (True)?

When query_other_jobs is set to True, users have the ability to view jobs that have been submitted by other users. This enhances transparency and coordination.

  • Job Visibility: All users can see each other's jobs.
  • Transparency: Users can check the status of any job on the system, even if they didn’t submit it.
  • Collaboration: It’s easier for users to coordinate and manage resources, especially in shared environments where multiple users are utilizing the same resources.

What Happens When query_other_jobs is Disabled (False)?

When query_other_jobs is set to False, job visibility is limited to only the user's own jobs. This ensures privacy but limits transparency.

  • Job Visibility: Users can only see their own jobs, not those submitted by others.
  • Privacy: Job details are kept private between users, so no one can see what others are working on.
  • Limited Collaboration: Users can’t check the status of other users' jobs, making it harder to coordinate resources in a multi-user environment.

How to Set query_other_jobs to False

To disable this feature, run the following command:

qmgr -c "set server query_other_jobs = False"

Defalut Value

Example of qstat with Disabled Query

Defalut Value

When Should You Enable query_other_jobs?

You should enable query_other_jobs in environments where users need to:

  • Coordinate job statuses in a shared or collaborative environment.
  • Increase transparency so users can see each other’s job progress, helping to manage system resources more effectively.
  • Avoid conflicts by ensuring users know what jobs are running and if resources are being over-utilized.

When Should You Disable query_other_jobs?

You should disable query_other_jobs when:

  • Privacy is a priority and you want to ensure that job details are only visible to the user who submitted them.
  • Security-sensitive systems where job-related information should not be shared between users.
  • Isolated environments where users don’t need to view the status of others’ jobs for coordination or resource management.