Using and Administering
Purpose
Returns information about jobs that have been dispatched.
Syntax
llq [-?] [-H]
[-v] [-x] [-s]
[ -l] [joblist] [-u
userlist] [-h hostlist]
[-c classlist]
[-f category_list] [-r
category_list]
Flags
- -?
- Provides a short usage message.
- -H
- Provides extended help information.
- -v
- Outputs the name of the command, release number, service level, service
level date, and operating system used to build the command.
- -x
- Provides extended information about the selected job. If the
-x flag is used with the -r, -s, or
-f flag, an error message is generated.
CPU usage and other resource consumption information on active jobs can
only be reported using the -x flag if the LoadLeveler administrator
has enabled it by specifying A_ON and A_DETAIL for the ACCT keyword in the
LoadLeveler configuration file.
Normally, llq connects with the central manager to obtain job
information. When you specify -x, llq connects to
the schedd machine that received the specified job to get extended job
information.
When specified without -l, CPU usage for active jobs is reported
in the short format. Using -x can produce a very long report
and can cause excess network traffic.
- -s
- Provides information on why a selected list of jobs remain in the
NotQueued, Idle or Deferred state. Along with this flag, users must
specify a list of jobs. The user can also optionally supply a list of
machines to be considered when determining why the job(s) cannot run.
If a list of machines is not provided, the default is the list of machines in
the LoadLeveler cluster. For each job, llq determines why
the job remains in one of the given states instead of Running.
- -l
- Specifies that a long listing be generated for each job for which status
is requested. Fields included in the long listing are shown in Results.
If -l is not specified, then the standard listing is
generated as shown in Results.
- joblist
- Is a blank-delimited list of jobs of the form
host.jobid.stepid where:
- -u userlist
- Is a blank-delimited list of users. When used with the
-h option, only the user's jobs monitored on the machines in
the hostlist are queried. When used alone, only the
user's jobs monitored on the schedd machine are queried.
- -h hostlist
- Is a blank-delimited list of machines. If the -s flag is
not specified, all jobs monitored on machines in this list are queried.
If the -s flag is specified, the list of machines is considered
when determining why a job remains in Idle state. When issued with the
-u option, the userlist is used to further select jobs
for querying.
- -c classlist
- Is a blank-delimited list of classes. When used with -h,
only those jobs monitored on the machines in the hostlist are
queried.
- -f category_list
- Is a blank-delimited list of categories you want to query. Each
category you specify must be preceded by a percent sign. The
category_list cannot contain duplicate entries. This flag
allows you to create a customized version of the standard llq
listing. You cannot use this flag with the -l flag.
The output fields produced by this flag all have a fixed length. The
output is displayed in the order in which you specify the categories.
category_list can be one or more of the following:
-
- %a
- Account number
- %c
- Class
- %cc
- Completion code
- %dc
- Completion date
- %dd
- Dispatch Date
- %dh
- Hold date
- %dq
- Queue date
- %gl
- LoadLeveler group
- %gu
- UNIX group
- %h
- Host (First hostname if more than one is allocated to the job)
- %id
- Step ID
- %is
- Virtual image size
- %jn
- Job name
- %jt
- Job type
- %nh
- Number of hosts allocated to the job
- %o
- Job owner
- %p
- User priority
- %sn
- Step name
- %st
- Status
- -r category_list
- Is a blank-delimited list of formats (categories) you want to
query. Each category you specify must be preceded by a percent
sign. The category_list cannot contain duplicate
entries. This flag allows you to create a customized version of the
standard llq listing. You cannot use this flag with the
-l flag. The output produced by this flag is considered raw,
in that the fields can be variable in length. Output fields are
separated by an exclamation point (!). The output is displayed in the
order in which you specify the formats. category_list can be
one or more of the formats listed under the -f flag.
If the -u or -h options are not specified, and if no
jobid is specified, then all jobs are queried.
The -u and -h options override the jobid
parameters.
Examples
This example generates a long listing for job 8, job step 2 submitted to
machine gold:
llq -l gold.8.2
This example generates a standard listing for all job steps of job name 12
submitted to the local machine:
llq 12
Results
In this section, the term "job step" refers to either a serial job
step or a parallel task.
Standard Listing: The
standard listing is generated when you do not specify the
-l option with the llq command. The following is
sample output from the llq -h mars command, where the machine
mars has two jobs running and one job waiting:
+--------------------------------------------------------------------------------+
|Id Owner Submitted ST PRI Class Running On |
|------------------------ ---------- ----------- -- --- ------------ ----------- |
|mars.498.0 brownap 5/20 11:31 R 100 silver mars |
|mars.499.0 brownap 5/20 11:31 R 50 No_Class mars |
|mars.501.0 brownap 5/20 11:31 I 50 silver |
| |
|3 job steps in queue, 1 waiting, 0 pending, 2 running, 0 held. |
+--------------------------------------------------------------------------------+
The standard listing includes the following fields:
- Id
- job identifier presented in the format:
host.jobid.stepid. When the llq command
returns information about a job owned by a schedd in the same domain, then the
domain of the hostname won't appear in the output. However, when
the llq command reports information about a job owned by a schedd in a
different domain, the fully qualified hostname is always included. Due
to space limitations, the host's domain may be truncated to fit in the
space allocated to the Id field. If the domain is truncated, a dash (-)
will appear at the end to indicate that characters have been left out.
To see the full job ID, run llq with the -l flag.
- Owner
- userid of the job submitter.
- Submitted
- date and time of job submission.
- ST
- current job status (state). Job status can be:
-
- C
- Completed
- CA
- Cancelled
- CP
- Complete Pending
- D
- Deferred
- H
- User Hold
- HS
- User Hold and System Hold
- I
- Idle
- NR
- Not Run
- NQ
- Not Queued
- P
- Pending
- R
- Running
- RM
- Removed
- RP
- Remove Pending
- S
- System Hold
- ST
- Starting
- SX
- Submission Error
- TX
- Terminated
- V
- Vacated
- VP
- Vacate Pending
- X
- Rejected
- XP
- Reject Pending
For a detailed explanation of job states, see LoadLeveler Job States.
- PRI
- user priority of the job, where the values are defined with the
user_priority keyword in the job command file or changed by the
llprio command. See llprio - Change the User Priority of Submitted Job Steps
- Class
- job class.
- Running On
- if running, the machine the job is running on. This is blank when
the job is not running. For parallel jobs, only the first machine is
shown.
Customized, Formatted Standard Listing: A customized and
formatted standard listing is generated when you specify llq with
the -f flag. The following is sample output from this
command:
llq -f %id %c %dq %dd %gl %h
+--------------------------------------------------------------------------------+
|Step Id Class Queue Date Disp. Date LL Group Running On |
|----------------- ---------- ----------- ----------- ---------- --------------- |
|ll6.2.0 No_Class 04/08 09:19 04/08 09:21 No_Group ll6.pok.ibm.com |
|ll6.1.0 No_Class 04/08 09:19 04/08 09:21 No_Group ll6.pok.ibm.com |
|ll6.3.0 No_Class 04/08 09:19 04/08 09:21 No_Group ll5.pok.ibm.com |
| |
|3 job steps in queue, 0 waiting, 0 pending, 3 running, 0 held |
| |
+--------------------------------------------------------------------------------+
Customized, Unformatted Standard Listing: A customized and
unformatted (raw) standard listing is generated when you specify
llq with the -r flag. Output fields are separated
by an exclamation point (!). The following is sample output from this
command:
llq -r %id %c %dq %dd %gl %h
+--------------------------------------------------------------------------------+
|ll6.pok.ibm.com.2.0!No_Class!04/08 09:19!04/08 09:21!No_Group!ll6.pok.ibm.com |
|ll6.pok.ibm.com.1.0!No_Class!04/08 09:19!04/08 09:21!No_Group!ll6.pok.ibm.com |
|ll6.pok.ibm.com.3.0!No_Class!04/08 09:19!04/08 09:21!No_Group!ll5.pok.ibm.com |
+--------------------------------------------------------------------------------+
The Long Listing: The
long listing is generated when you specify the -l option with the
llq command. This section contains sample output for two
llq commands: one querying a serial job and one querying a
parallel job. Following the sample output is an explanation of all
possible fields displayed by the llq command.
The following is sample output for the llq -l command for the
serial job
"c163n12.ppd.pok.ibm.com.9":
+--------------------------------------------------------------------------------+
| |
|=============== Job Step c163n12.ppd.pok.ibm.com.9.0 =============== |
| Job Step Id: c163n12.ppd.pok.ibm.com.9.0 |
| Job Name: c163n12.ppd.pok.ibm.com.9 |
| Step Name: batch_job_1 |
| Structure Version: 9 |
| Owner: loadl |
| Queue Date: Mon Jun 28 10:33:59 EDT 1999 |
| Status: Running |
| Dispatch Time: Mon Jun 28 10:34:02 EDT 1999 |
| Completion Date: |
| Completion Code: |
| User Priority: 50 |
| user_sysprio: 0 |
| class_sysprio: 45 |
| group_sysprio: 0 |
| System Priority: -4042 |
| q_sysprio: -4042 |
| Notifications: Complete |
| Virtual Image Size: 1 kilobytes |
| Checkpoint: |
| Restart: yes |
| Hold Job Until: |
| Cmd: batch1.cmd |
| Args: arg_1 arg_2 arg_3 |
| Env: |
| In: /dev/null |
| Out: job1.c163n12.9.0.out |
| Err: job1.c163n12.9.0.err |
|Initial Working Dir: /test/loadl |
| Dependency: |
| Resources: spice3f5(2) |
| Requirements: (Memory > 32) && (Arch == "R6000") && (OpSys == "AIX43") |
| Preferences: (Memory > 128) && (Feature == "ESSL") |
| Step Type: Serial |
| Min Processors: |
| Max Processors: |
| Allocated Host: c163n12.ppd.pok.ibm.com |
| Node Usage: shared |
| Submitting Host: c163n12.ppd.pok.ibm.com |
| Notify User: loadl@c163n12.ppd.pok.ibm.com |
| Shell: /bin/ksh |
| LoadLeveler Group: No_Group |
| Class: small |
| Cpu Hard Limit: 1800 seconds |
| Cpu Soft Limit: 600 seconds |
| Data Hard Limit: -1 |
| Data Soft Limit: -1 |
| Core Hard Limit: -1 |
| Core Soft Limit: -1 |
| File Hard Limit: -1 |
| File Soft Limit: -1 |
| Stack Hard Limit: -1 |
| Stack Soft Limit: -1 |
| Rss Hard Limit: -1 |
| Rss Soft Limit: -1 |
|Step Cpu Hard Limit: 3599 seconds |
|Step Cpu Soft Limit: 1769 seconds |
|Wall Clk Hard Limit: 4000 seconds |
|Wall Clk Soft Limit: 3600 seconds |
| Comment: Test batch job 1. |
| Account: 99999 |
| Unix Group: loadl |
| NQS Submit Queue: |
| NQS Query Queues: |
|Negotiator Messages: |
|Adapter Requirement: |
|Step CPUs: |
|Step Virtual Memory: |
|Step Real Memory: |
|Step Adapter Memory: |
+--------------------------------------------------------------------------------+
The following is sample output for the
llq -l -x c163n12.6.0 command, where
c163n12.6.0 is a parallel job.
+--------------------------------------------------------------------------------+
| |
|***************** llq -l -x : PARALLEL JOB ****************************** |
| |
|=============== Job Step c163n12.ppd.pok.ibm.com.6.0 =============== |
| Job Step Id: c163n12.ppd.pok.ibm.com.6.0 |
| Job Name: c163n12.ppd.pok.ibm.com.6 |
| Step Name: 0 |
| Structure Version: 9 |
| Owner: loadl |
| Queue Date: Mon Jun 28 09:35:21 EDT 1999 |
| Status: Running |
| Dispatch Time: Mon Jun 28 09:35:21 EDT 1999 |
| Completion Date: |
| Completion Code: |
| User Priority: 50 |
| user_sysprio: 0 |
| class_sysprio: 30 |
| group_sysprio: 0 |
| System Priority: 0 |
| q_sysprio: 0 |
| Notifications: Complete |
| Virtual Image Size: 376 kilobytes |
| Checkpoint: |
| Restart: yes |
| Hold Job Until: |
| Env: MANPATH=/usr/local/man:/usr/share/man: LANG=en_US LOGIN= ...|
| In: /dev/null |
| Out: poe5_1.c163n12.6.0.out |
| Err: poe5_1.c163n12.6.0.err |
|Initial Working Dir: /test/loadl |
| Dependency: |
| Task_geometry: |
| Resources: |
| Step Type: General Parallel |
| Node Usage: not_shared |
| Submitting Host: c163n12.ppd.pok.ibm.com |
| Notify User: loadl |
| Shell: /bin/ksh |
| LoadLeveler Group: No_Group |
| Class: Parallel |
| Cpu Hard Limit: 3600 seconds |
| Cpu Soft Limit: 1200 seconds |
| Data Hard Limit: -1 |
| Data Soft Limit: -1 |
| Core Hard Limit: -1 |
| Core Soft Limit: -1 |
| File Hard Limit: -1 |
| File Soft Limit: -1 |
| Stack Hard Limit: -1 |
| Stack Soft Limit: -1 |
| Rss Hard Limit: -1 |
| Rss Soft Limit: -1 |
|Step Cpu Hard Limit: 5400 seconds |
|Step Cpu Soft Limit: 2400 seconds |
|Wall Clk Hard Limit: 6000 seconds |
|Wall Clk Soft Limit: 3600 seconds |
| Comment: |
| Account: 99999 |
| Unix Group: loadl |
| DCE Principal: tvdfs |
| User Space Windows: 8 |
| NQS Submit Queue: |
| NQS Query Queues: |
|Negotiator Messages: |
|Adapter Requirement: (css0,LAPI,shared,US),(css0,MPI,shared,US) |
| |
+--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+
|--------------- Detail for c163n12.ppd.pok.ibm.com.6.0 --------------- |
| Running Host: c163n12.ppd.pok.ibm.com |
| Machine Speed: 1.000000 |
| Starter User Time: 0+00:00:00.200000 |
|Starter System Time: 0+00:00:00.340000 |
| Starter Total Time: 0+00:00:00.540000 |
| Starter maxrss: 1720 |
| Starter ixrss: 11392 |
| Starter idrss: 13520 |
| Starter isrss: 0 |
| Starter minflt: 1352 |
| Starter majflt: 2 |
| Starter nswap: 0 |
| Starter inblock: 0 |
| Starter oublock: 0 |
| Starter msgsnd: 0 |
| Starter msgrcv: 0 |
| Starter nsignals: 1 |
| Starter nvcsw: 76 |
| Starter nivcsw: 27 |
| Step User Time: 0+00:00:12.0 |
| Step System Time: 0+00:00:00.830000 |
| Step Total Time: 0+00:00:12.830000 |
| Step maxrss: 1368 |
| Step ixrss: 15528 |
| Step idrss: 426068 |
| Step isrss: 0 |
| Step minflt: 5947 |
| Step majflt: 12 |
| Step nswap: 0 |
| Step inblock: 0 |
| Step oublock: 0 |
| Step msgsnd: 0 |
| Step msgrcv: 0 |
| Step nsignals: 322 |
| Step nvcsw: 771 |
| Step nivcsw: 591 |
| Step CPUs: 18 |
| Step Virtual Memory: 180 megabytes |
| Step Real Memory: 90 megabytes |
| Step Adapter Memory: 2097152 bytes |
|--------------------------------------------------------------------------------|
|Node |
|---- |
| |
| Name : |
| Requirements : |
| Preferences : |
| Node minimum : 2 |
| Node maximum : 2 |
| Node actual : 2 |
| Allocated Hosts : c163n12.ppd.pok.ibm.com:RUNNING:css0(1,LAPI,US,1M), |
| css0(2,MPI,US,1M),css0(3,LAPI,US,1M),css0(4,MPI,US,1M) |
| + c163n11.ppd.pok.ibm.com:RUNNING:css0(1,LAPI,US,1M), |
| css0(2,MPI,US,1M),css0(3,LAPI,US,1M),css0(4,MPI,US,1M) |
| Master Task |
| ----------- |
| |
| Executable : /bin/poe |
| Exec Args : /test/loadl/ivp_600 -euilib us -ilevel 6 -labelio yes -pmdl|
| Num Task Inst: 1 |
| Task Instance: c163n12:-1 |
| |
| Task |
| ---- |
| |
| Num Task Inst: 4 |
| Task Instance: c163n12:0:css0(1,LAPI,US,1M),css0(2,MPI,US,1M) |
| Task Instance: c163n12:1:css0(3,LAPI,US,1M),css0(4,MPI,US,1M) |
| Task Instance: c163n11:2:css0(1,LAPI,US,1M),css0(2,MPI,US,1M) |
| Task Instance: c163n11:3:css0(3,LAPI,US,1M),css0(4,MPI,US,1M) |
| |
+--------------------------------------------------------------------------------+
The long listing includes these fields:
- Job Step ID
- The job step identifier.
- Job Name
- The name of the job.
- Step Name
- The name of the job step
- Structure Version
- An internal version identifier.
- Owner
- The userid of the user submitting the job.
- Queue Date
- The date and time that LoadLeveler received the job.
- Status
- The status (state) of the job. A job's status can be:
- Cancelled
- Completed
- Complete Pending
- Deferred
- Idle
- Not Queued
- Not Run
- Pending
- Rejected
- Reject Pending
- Removed
- Remove Pending
- Running
- Starting
- Submission Error
- System Hold
- System and User Hold
- Terminated
- User Hold
- Vacated
- Vacate Pending
For a detailed explanation of these job states, see LoadLeveler Job States.
- Dispatch Time
- the time the job was dispatched.
- Completion Date
- date and time job completed or exited.
- Completion Code
- the status returned by the wait3 UNIX system call.
- User Priority
- The priority of the job, as specified by the user in the job command, or
changed by the llprio command.
- user_sysprio
- The user system priority of the job, where the value is defined in the
administration file.
- class_sysprio
- The class priority of the job, where the value is defined in the
administration files.
- group_sysprio
- The group priority of the job, where the value is defined in the
administration files.
- System Priority
- The overall system priority of the job, where the value is defined by the
SYSPRIO expression in the configuration file.
- q_sysprio
- The adjusted system priority of the job (See How Does a Job's Priority Affect Dispatching Order?.)
- Notifications
- The notification status for the job, where:
- always
- indicates notification is sent through the mail for all four notification
categories below.
- complete
- indicates notification is sent through the mail only when the job
completes.
- error
- indicates notification is sent through the mail only when the job
terminates abnormally.
- never
- indicates notification is never sent.
- start
- indicates notification is sent through the mail only when starting or
restarting the job.
- Virtual Image Size
- of the executable that was submitted.
- Checkpoint
- checkpoint status (yes or no)
- Restart
- restart status (yes or no)
- Hold Job Until
- job is deferred until this date and time.
- Cmd
- name of the executable that was submitted.
- Args
- arguments that were passed to the executable.
- Env
- environment variables to be set before executable runs. Appears
only when the -x option is specified.
- In
- file to be used for stdin.
- Out
- file to be used for stdout.
- Err
- The file to be used for stderr.
- Init Working Directory
- The directory from which the job is run. The relative directory
from which the stdio files are accessed, if appropriate.
- Dependency
- Job dependencies as specified at job submission.
- Requirements
- Job requirements as specified at job submission.
- Preferences
- Job preferences as specified at job submission.
- Task_geometry
- Reflects the settings for the task_geometry keyword in the job command
file.
- Resources
- Reflects the settings for the resources keyword in the job command
file.
- Blocking
- Reflects the settings for the blocking keyword in the job command
file.
- Step Type
- Type of job step (serial or parallel).
- Min Processors
- The minimum number of processors needed for this job.
- Max Processors
- The maximum number of processors needed for this job.
- Allocated Hosts
- The machines that have been allocated for this job.
- Node Usage
- A request that a node be shared or not shared; the user specifies
this request while submitting the job.
- Submitting Host
- The name of the machine to which the job is submitted.
- Notify User
- The user to be notified by mail of a job's status.
- Shell
- The shell to be used when the job runs.
- LoadLeveler Group
- The LoadLeveler group associated with the job.
- Class
- The job's class as specified at job submission.
- CPU Hard Limit
- CPU hard limit as specified at job submission.
- CPU Soft Limit
- CPU soft limit as specified at job submission.
- Data Hard Limit
- Data hard limit as specified at job submission.
- Data Soft Limit
- Data soft limit as specified at job submission.
- Core Hard Limit
- Core hard limit as specified at job submission.
- Core Soft Limit
- Core soft limit as specified at job submission.
- File Hard Limit
- File hard limits as specified at job submission.
- File Soft Limit
- File soft limit as specified at job submission.
- Stack Hard Limit
- Stack hard limit as specified at job submission.
- Stack Soft Limit
- Stack soft limit as specified at job submission.
- Rss Hard Limit
- RSS hard limit as specified when job was submitted.
- Rss Soft Limit
- RSS soft limit as specified at job submission.
- Job Cpu Hard Limit
- Job CPU hard limit as specified at job submission.
- Job Cpu Soft Limit
- Job CPU soft limit as specified at job submission.
- Wall Clock Hard Limit
- Wall clock hard limit as specified at job submission.
- Wall Clock Soft Limit
- Wall clock soft limit as specified at job submission.
- NQS Submit Queue
- The name of the NQS pipe queue to which the NQS job will be routed.
- NQS Query Queue
- The NQS queue names you can use to monitor the job.
- Comment
- The comment specified by the comment keyword in the job command
file.
- Account
- The account number specified in the job command file.
- UNIX Group
- The effective UNIX group name.
- DCE Principal
- The DCE pricipal name associated with the process that submitted the job
to LoadLeveler.
- User Space Windows
- The number of switch adapter windows assigned to the job.
- Negotiator Messages
- Informational message(s) for jobs in the Idle or NotQueued state.
- Adapter Requirement
- Reflects the settings of the network keyword in the job command
file.
- Step CPUs
- The total Consumable CPUs for the job step.
- Step Virtual Memory
- The total Consumable Virtual Memory for the job step.
- Step Real Memory
- The total Consumable Memory for the job step.
- Step Adapter Memory
- The total adapter pinned memory for the job step.
Other fields displayed when issuing llq -x -l are:
- maxrss
- maximum resident set size utilized.
- ixrss
- size of the text segment of the jobs.
- idrss
- size of the data segement of the jobs.
- isrss
- Integral unshared stack used.
- minflt
- # Page faults (re-claimed).
- majflt
- # Page faults (I/O required).
- nswap
- # times swapped out.
- inblock
- # times file system performed input.
- oublock
- # times file system performed output.
- msgsnd
- # of IPC messages sent.
- msgrcv
- # of IPC messages received.
- nsignals
- # of signals delivered.
- nvcsw
- # of context switches due to voluntarily giving up processor.
- nivcsw
- # of involuntary context switches.
Other fields displayed for parallel jobs are:
- Allocated Hosts
- allocated hostname information in the format hostname:task
status:adapter usage. The adapter usage information
is in the format adapter name (adapter window ID,network protocol,mode,
adapter window memory).
- Task Instance
- task instance information in the format hostname:task
ID:adapter usage. The adapter usage information is
in the format adapter name (adapter window ID,network protocol,mode,
adapter window memory).
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]