qhold
Overview
qhold pauses (holds) specified jobs or tasks. Targets can be selected by job identifiers, user names, or hold types.
Options
Optional Parameters
| Option | Required | Type | Purpose |
|---|---|---|---|
-h <hold_list> | No | String | Specify hold types (such as u, o, s). |
-u <user_list> | No | String | Filter jobs by user. Use "*" for all users, or a specific user (e.g., userA). |
Positional Parameters
| Parameter | Required | Type | Purpose |
|---|---|---|---|
job_task_list | Yes (if -u is not used) | List | List of job/task identifiers to hold, e.g. 123, task456, userA.789. |
Examples
Example 1: Hold by job ID
qhold 123 task456
Effect: Holds job 123 and task task456.
Example 2: Hold by user
qhold -u userA
Effect: Holds all jobs for user userA.
Example 3: Hold by type (check compatibility)
qhold -h u job101
Effect: Attempts to hold job job101 with type "u". This may be limited by FSCHED/SGE differences.
Notes
Parameter Constraints
-
Mutual exclusion:
-u <user_list>andjob_task_listcannot be used together.qhold -u userA job101 # Error: conflicting parameters
-
Required condition:
- You must specify either
-uorjob_task_list.
- You must specify either
-
User filtering limits:
- If the user does not exist and
"*"is not used, the command errors as if the job does not exist.
- If the user does not exist and
Feature Differences
| SGE Feature | Current Status | Notes |
|---|---|---|
-h <hold_list> | Partial support (WIP) | Mapping may be incomplete; refer to SGE docs |
| Notification options | Not supported | Email notifications and related features are not implemented |
Additional Notes
- Job identifier format:
job_task_listmust follow SGE syntax (such as wildcards or range expressions). - For detailed hold type definitions, refer to the official SGE documentation.