Table of Contents
Advertisement
Task Instance: c250f10c12ap13-hf0:44:,MCM0:CPU< 3 >
Task Instance: c250f10c12ap13-hf0:45:,MCM1:CPU< 19 >
Task Instance: c250f10c12ap13-hf0:46:,MCM2:CPU< 35 >
Task Instance: c250f10c12ap13-hf0:47:,MCM3:CPU< 51 >
Task Instance: c250f10c12ap13-hf0:48:,MCM0:CPU< 4 >
Task Instance: c250f10c12ap13-hf0:49:,MCM1:CPU< 20 >
Task Instance: c250f10c12ap13-hf0:50:,MCM2:CPU< 36 >
Task Instance: c250f10c12ap13-hf0:51:,MCM3:CPU< 52 >
Task Instance: c250f10c12ap13-hf0:52:,MCM0:CPU< 5 >
Task Instance: c250f10c12ap13-hf0:53:,MCM1:CPU< 21 >
Task Instance: c250f10c12ap13-hf0:54:,MCM2:CPU< 37 >
Task Instance: c250f10c12ap13-hf0:55:,MCM3:CPU< 53 >
Task Instance: c250f10c12ap13-hf0:56:,MCM0:CPU< 6 >
Task Instance: c250f10c12ap13-hf0:57:,MCM1:CPU< 22 >
Task Instance: c250f10c12ap13-hf0:58:,MCM2:CPU< 38 >
Task Instance: c250f10c12ap13-hf0:59:,MCM3:CPU< 54 >
Task Instance: c250f10c12ap13-hf0:60:,MCM0:CPU< 7 >
Task Instance: c250f10c12ap13-hf0:61:,MCM1:CPU< 23 >
Task Instance: c250f10c12ap13-hf0:62:,MCM2:CPU< 39 >
Task Instance: c250f10c12ap13-hf0:63:,MCM3:CPU< 55 >
--------------------------------------------------------------------------------
1 job step(s) in query, 0 waiting, 0 pending, 1 running, 0 held, 0 preempted
Querying machine status
You use the llstatus command to ascertain the status information about machines in the
LoadLeveler cluster.
The llstatus command features three levels of output: cluster, machine_group, and
machine. The default output is cluster, which gives a summary for the machines in the cluster.
The level is set by exporting the environment variable LOAD_STATUS_LEVEL or is specified
on the command line.
You receive the output similar to the output shown in Example 2-18 when you issue the
llstatus command.
Example 2-18 llstatus command
$ llstatus
Active
5/6
Schedd
3/4
Startd
3/4
The Central Manager is defined on c250f10c12ap01-hf0.ppd.pok.ibm.com
Absent:
1
Startd:
Down
Drained
0
Schedd:
Down
Drained
0
The output in Example 2-18 indicates that there are six machines that are defined in the
administration file or database, and five machines reported their status to the Resource
Manager daemon. Of the four machines that are known by the Central Manager to be Schedd
1 job steps
64 running tasks
Draining
Flush
0
0
Draining
0
0
Suspend
0
0
Chapter 2. Application integration
151
Advertisement
Table of Contents
