Displays information about prompts.

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.


{showprompts | sp} [[folder/]promptselect]

{showprompts | sp} [[folder/]promptselect]
     [;deps[;keys | info | logon]]


[[folder/]promptname | [[folder/]workstation#]msgnum][;state[;...]]
Specifies the name of a global prompt. Wildcard characters are permitted.
Specifies the name of the workstation on which an unnamed prompt is issued. The default is the workstation on which conman is running.
Specifies the message number of an unnamed prompt.
Specifies the state of prompts to be displayed. The states are as follows:
The prompt was replied to with y.
The prompt was replied to with n.
The prompt was issued, but no reply was given.
The prompt has not been issued.
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 prompt. Prompts 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 prompts by submitting the composer list command, together with the ;showid filter, or by submitting the conman command, showprompts, in combination with the ;showid filter.

Identifying prompts 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.

Note: Prompt numbers assigned to both global and local prompts change when the production plan is extended.


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 the status of all prompt issued on the workstation on which you are running conman, run the following command:
a sample is the following:
State Message or Prompt
ASKED 1(PRMT3) !continue?
INACT 3(CPUA#SCHED_12[(0600 03/12/18),
      (0AAAAAAAAAAAABST)]) Are you ready to process job1?
INACT 5(CPUA#SCHED_12[(1010 03/12/18),(0AAAAAAAAAAAABSU)]) 
      Are you ready to process job2?
INACT 7(CPUA#SCHED_22[(0600 03/12/18),(0AAAAAAAAAAAABTR)]) 
      Are you ready to process job3?
To display the status of all mis prompts that have been issued, in the deps format, run the following command:
sp mis@;asked;deps 
To display the status of prompt number 7 on workstation CPUA, stored in folder myfolder, run the following command:
sp myfolder/CPUA#7 
The output of the command is:
INACT 7(myfolder/CPUA#SCHED_22[(0600 03/12/18),(0AAAAAAAAAAAABTR)]) 
      Are you ready to process job3?

See also

From the Dynamic Workload Console you can perform the same task as follows:
  1. In the navigation bar at the top, click Monitoring and Reporting > Workload Monitoring > Monitor Workload.
  2. Select an engine.
  3. In Object Type, select Prompt.
  4. In the Query drop-down list, select All Prompts in plan, which will list all prompts regardless of their status, or create and select another task.