Displays information about resources.

The displayed information is updated only as long as HCL Workload Automation (batchman) is running. Whether 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.


{showresources | sr} [[[folder/]workstation#][folder/]resourcename]

{showresources | sr} [[[folder/]workstation#][folder/]resourcename]
     [;deps[;keys | info | logon]]


Specifies the name of the workstation on which the resource is defined. The default is the workstation on which conman is running.
Specifies the name of the resource. Wildcard characters are permitted.
Displays a single column list of the objects selected by the command.
Displays information in the deps format. Use keys, info, or logon to modify the display.
Displays information in the info format.
Displays information in the logon format.
Sends the output of the command to the conman output device. For information about this device, see Offline output.
Displays a unique identifier that identifies a resource. Resources are no longer identified in the plan solely by their names, but also by the folder in which they are defined. The name and folder association is mapped to a unique identifier. You can verify the unique identifier for resources by submitting the composer list command, together with the ;showid filter, or by submitting the conman command, showresources, in combination with the ;showid filter.

Identifying resources by their unique identifier avoids the problem that occurred in previous versions when objects were renamed in the plan. For example, if an object was renamed and then carried forward to a new production plan, references to the old object name were lost. With the implementation of the unique identifier, this will no longer occur and dependencies will be correctly resolved.

When deleting a folder, a prompt, or resource, if there are still objects in the plan that reference these objects, then another folder, prompt, or resource cannot be renamed with the name of the deleted folder, prompt or resource for the number of days specified by folderDays. However, a brand new folder, prompt, or resource can be created with the name of the deleted object. For more information about the folderDays option see Global options - detailed description.


The output of the command is produced in three formats: standard, keys, and deps. The arguments keys, info, and logon modify the deps display.


To display information about all resources on the workstation on which you are running conman, run the following command:
A sample output is:
CPU#Resource      Total Available    Qty UsedBy
CPUA #JOBSLOTS    16        16       No holders of this resource
To display information about the jobslots resource on workstation CPUA stored in folder myfolder,in the deps format, run the following command:
sr myfolder/CPUA#JOBSLOTS;deps
A sample output is the following:
                                               (Est)  (Est)
Workstation Job Stream SchedTime Job  State Pr Start Elapse RetCode Dependencies

CPUA       #JOBSLOTS Dependencies are:

  FTAA     #SCHED_F+ 0600 03/04 ****** HOLD 55(03/04)              [03/04/18];#33
                         (CPUA#)JOBMDM HOLD 30(03/04)              #1(PRMT3);-16 JOBSLOTS-

  FTAA     #SCHED_F+ 1010 03/04 ****** HOLD 55(03/04)              [03/04/18];#34
                         (CPUA#)JOBMDM HOLD 30(03/04)              #1(PRMT3);-16 JOBSLOTS-

  FTAA     #SCHED_F+ 0600 03/05 ****** HOLD 55(03/05)              [03/04/18];#35
                         (CPUA#)JOBMDM HOLD 30(03/05)              #1(PRMT3);-16 JOBSLOTS-

See also

From the Dynamic Workload Console you can perform the same task as follows:
  1. In the Welcome page, select Monitor your workload, or in the navigation bar at the top of the page, click Monitoring & Reporting > Workload Monitoring > Monitor Workload.
  2. Select an engine.
  3. In Object Type, select Resource.
  4. From the Query drop-down list, select All Resources in plan or another task to monitor resources.
  5. Click Run to run the monitoring task.