When used with jobstream.job, this specifies the name of the workstation on which the job stream runs. When used with jobnumber, it specifies the workstation on which the job runs. Except when also using schedid, wildcard characters are permitted. This argument might be required depending on the workstation where you launch the command, as follows:
  • If you launch the command on the workstation where the target jobs have run, the workstation argument is optional.
  • If you launch the command on a hosted workstation, the workstation argument is required. Hosted workstations are:
    • extended agents
    • agents
    • pools
    • dynamic pools
Specifies the name of the job stream in which the job runs. Wildcard characters are permitted.
(hhmm [date])
Indicates the time and date the job stream instance is located in the preproduction plan. The value hhmm corresponds to the value assigned to the schedtime keyword in the job stream definition if no at time constraint was set. After the job stream instance started processing, the value of hhmm [date] is set to the time the job stream started. The use of wildcards in this field is not allowed. When issuing inline conman commands from the shell prompt enclose the conman command in double quotes " ". For example, run this command as follows:
conman "sj my_workstation#my_js(2101 02/23).@"
Specifies the unique job stream identifier. See Arguments for more information on job stream identifiers.
Indicates that the job stream identifier is used in selecting the job stream.
Specifies the name of the job. Wildcard characters are permitted.
Specifies the job number.
See the following section.
Specifies the name of the HCL Workload Automation network agent that interfaces with the remote HCL Workload Automation network containing the target job. The two colons (::) are a required delimiter. Wildcard characters are permitted. For more information refer to Managing internetwork dependencies.
Note: HCL Workload Automation helps you to identify the correct job stream instance when the job stream selection provides an ambiguous result if more than one instance satisfy your selection criteria. For example when more than one instances of WK1#J1 are included in the production plan and so the job stream selection provides an ambiguous result the following prompt is automatically generated to allow you to choose the correct instance:
Process WK1#J1[(0600 03/04/19),(0AAAAAAAAAAAABTB)]
        (enter "y" for yes, "n" for no)?y
Command forwarded to batchman for WK1#J1[(0600 03/04/19),(0AAAAAAAAAAAABTB)]
Process WK1#J1[(1010 03/04/19),(0AAAAAAAAAAAABTC)]
        (enter "y" for yes, "n" for no)?n
In the output only the job stream instance scheduled on (0600 03/04/19) and with identifier 0AAAAAAAAAAAABTB is selected to run the command.