HCL Workload Automation, Version 9.4

showcpus

Displays information about workstations and links.

The displayed information is updated only while HCL Workload Automation (batchman) is running on the workstations. If batchman is up or down is confirmed on screen by the Batchman LIVES or Batchman down message when you issue the conman start command.

You must have list access to the object being shown if the enListSecChk option was set to yes on the master domain manager when the production plan was created or extended.

Syntax

{showcpus | sc} [[domain!]workstation]
     [;info|;link]
     [;offline]

{showcpus | sc} [[domain!]workstation] [;getmon]

Arguments

domain
Specifies the name of a domain. The default is the domain in which the command is run.
workstation
Specifies the name of a workstation. The default is the workstation where the command is run. When no domain and no workstation are specified, the output can be the following:
  • The following command displays all the workstations that are in the domain of the workstation where the command was run, plus all the connected domain managers if the workstation is a domain manager. 
    conman "sc"
  • The following command displays all the workstations that are in the domain of the workstation where the command was run, without the connected domain managers. 
    conman "sc @"
info
Displays information in the info format.
link
Displays information in the link format.
offline
Sends the output of the command to the conman output device. For information about this device, see Offline output.
getmon
Returns the list of event rules defined for the monitor running on the specified workstation in the following format: 
<rule_name>::<eventProvider>#<eventType>:<scope>
The rule scope is automatically generated information about rule attributes, such as the workstations where it is used, a job or file name, and so on.

The header of the output contains also the time stamp of when the rule configuration package was last generated.

Note: This option is not valid on dynamic workload broker workstations (or dynamic domain managers). In this case, you can retrieve the information about the active rules defined in these workstations in the TWA_home\TWS\monconf\TWSObjectsMonitor.cfg file on the master domain manager.

Results

When the getmon parameter is not used, the output of the command is produced in three formats, standard, info, and link. The default value is standard. The meaning of the characters displayed depends on the type of format you select.

When run on a workstation with a version of IBMIBM® Workload Scheduler earlier than version 8.6, the sc command shows as FTA the workstation types introduced with IBM Workload Scheduler version 8.6, pool, dynamic pool, agent and remote engine.

When the getmon parameter is used, the list of rules is provided as separate output.

Examples

  1. To display information about the workstation on which you are running conman in the info format, run the following command: 
    showcpus ;info
    A sample output for this command is: 
    CPUID         VERSION   TIME ZONE               INFO
MASTER         8.6.0.0  US/Pacific              Linux 2.6.5-7.191-s390 #1 SM
FTA1           8.6.0.0                          Linux 2.4.9-e.24 #1 Tue May
FTA2           8.6.0.0                          HP-UX B.11.11 U 9000/785
  2. To display link information for all workstations, run the following command: 
    sc @!@;link
    A sample output is the following: 
    CPUID       HOST      FLAGS  ADDR  NODE
MASTER     MASTER     AF T  51099  9.132.239.65
FTA1       FTA1       AF T  51000  CPU235019
FTA2       FTA2       AF T  51000  9.132.235.42
BROKER1    MASTER     A  T  51111  9.132.237.17
  3. To display information about the workstation, run the following command: 
    showcpus
    If you run this command in an environment when the primary connection of the workstation with its domain or higher manager is not active, you receive the following output: 
    CPUID   RUN    NODE     LIMIT FENCE  DATE     TIME    STATE    METHOD DOMAIN
MASTER  360 *WNT  MASTER   10    0 03/05/2010 1348   I J   E          MASTERDM
FTA1    360  WNT  FTA      10    0 03/05/2010 1348 FTI JW M           MASTERDM
FTA2    360  WNT  FTA      10    0 03/05/2010 1348 FTI JW M           MASTERDM
FTA3    360  WNT  MANAGER  10    0 03/05/2010 1348 LTI JW M           DOMAIN1
FTA4    360  WNT  FTA      10    0 03/05/2010 1348 F I J  M           DOMAIN1
FTA5    360  WNT  FTA      10    0 03/05/2010 1348   I J  M           DOMAIN1
SA1     360  WNT  S-AGENT  10    0 03/05/2010 1348 F I J  M           DOMAIN1
XA_FTA4 360  OTHR X-AGENT  10    0 03/05/2010 1348 L I J  M           DOMAIN1
FTA6    360  WNT  MANAGER  10    0 03/05/2010 1348 F I J  M           DOMAIN2
FTA7    360  WNT  FTA      10    0 03/05/2010 1349 F I J  M           DOMAIN2
FTA7    360  WNT  FTA      10    0 03/05/2010 1349 F I J  M           DOMAIN2
BROKER  360  OTHR BROKER   10    0 03/05/2010 1349 LTI JW             MASTERDM
    If you run this command in an environment when the primary connection of the workstation with its domain or higher manager is active and at least one secondary connection is not active, you receive the following output: 
    CPUID   RUN     NODE     LIMIT FENCE   DATE    TIME    STATE     METHOD DOMAIN
MASTER  360 *WNT  MASTER   10    0  03/05/2010 1348    I J   E          MASTERDM
FTA1    360  WNT  FTA      10    0  03/05/2010 1348  FTI JW M           MASTERDM
FTA2    360  WNT  FTA      10    0  03/05/2010 1348  FTI JW M           MASTERDM
FTA3    360  WNT  MANAGER  10    0  03/05/2010 1348  FTI JW M           DOMAIN1
FTA4    360  WNT  FTA      10    0  03/05/2010 1348  F I J  M           DOMAIN1
FTA5    360  WNT  FTA      10    0  03/05/2010 1348  L I    M           DOMAIN1
SA1     360  WNT  S-AGENT  10    0  03/05/2010 1348  F I J  M           DOMAIN1
XA_FTA4 360  OTHR X-AGENT  10    0  03/05/2010 1348  L I J  M           DOMAIN1
FTA6    360  WNT  MANAGER  10    0  03/05/2010 1348  F I J  M           DOMAIN2
FTA7    360  WNT  FTA      10    0  03/05/2010 1349  F I J  M           DOMAIN2
    If you run this command in an environment when the primary connection of the workstation with its domain or higher manager and all secondary connections are active, you receive the following output: 
    CPUID   RUN     NODE     LIMIT FENCE   DATE    TIME     STATE    METHOD DOMAIN
MASTER  360 *WNT  MASTER   10    0  03/05/2010 1348    I J    E         MASTERDM
FTA1    360  WNT  FTA      10    0  03/05/2010 1348  FTI JW M           MASTERDM
FTA2    360  WNT  FTA      10    0  03/05/2010 1348  FTI JW M           MASTERDM
FTA3    360  WNT  MANAGER  10    0  03/05/2010 1348  FTI JW M           DOMAIN1
FTA4    360  WNT  FTA      10    0  03/05/2010 1348  F I J  M           DOMAIN1
FTA5    360  WNT  FTA      10    0  03/05/2010 1348  F I    M           DOMAIN1
SA1     360  WNT  S-AGENT  10    0  03/05/2010 1348  F I J  M           DOMAIN1
XA_FTA4 360  OTHR X-AGENT  10    0  03/05/2010 1348  L I J  M           DOMAIN1
FTA6    360  WNT  MANAGER  10    0  03/05/2010 1348  F I J  M           DOMAIN2
FTA7    360  WNT  FTA      10    0  03/05/2010 1349  F I J  M           DOMAIN2
  4. To get a list of active rule monitors on the workstation named CPU1, run this command: 
    sc CPU1 getmon
    You get the following output: 
    Monitoring configuration for CPU1:
*******************************************
*** Package Date : 04/22/2009 12:00 GMT ***
*******************************************
Rule1::FileMonitor#FileCreated:Workstation=CPU1,CPU2;File=”\tmp\filename”
Rule2::FileMonitor#ModificationCompleted:Workstation=CPU1,CPU3;File=”\staging\orders”
Rule3::TWSObjectsMonitor#JobSubmit:JobKey=CPU1#JS1.Job1
Rule5::TWSObjectsMonitor#JobLate:JobKey=CPU1#JS1.Job1

See also

From the Dynamic Workload Console you can perform the same task as follows:
  1. In the navigation bar at the top, click System Status and Health > Workload Monitoring > Monitor Workload.
  2. Select an engine.
  3. In Object Type, select Workstation.
  4. From the Query drop-down list, select a query to monitor workstations.
  5. Click Run to run the monitoring task.