Identifying job stream instances in the plan
In earlier versions than 8.3 the plan had a fixed duration of one
day. Since version 8.3 the plan can cover a period lasting several
days or less than one day. This change has added the possibility to
have in the same plan more than one instance of the same job stream
with the same name, and also the need to define a new convention to
uniquely identify each job stream instance in the plan. Each job stream
instance is identified in the plan by the following values:
- workstation
- Specifies the name of the workstation on which the job stream is scheduled to run.
- jobstreamname
- Corresponds to the job stream name used in earlier versions of HCL Workload Automation.
- scheddateandtime
- Represents when the job stream instance is planned to start in the preproduction plan. It corresponds to the day specified in the run cycle set in the job stream definition by an on clause and the time set in the job stream definition by an at or schedtime keyword. If set, the schedtime keyword is used only to order chronologically the job stream instances in the preproduction plan while, if set, the at keyword also represents a dependency for the job stream. For more information about these keywords refer to on, at and schedtime.
You can use any of the two types of identifiers, workstation#jobstreamname and scheddateandtime instead of workstation#jobstream_id, to uniquely identify a job stream instance when managing job streams in the plan using the conman command-line program. The default convention used to identify a job stream instance, both in this guide and in the command-line interfaces of the product, is the one that uses workstation#jobstreamname and scheddateandtime. For more information on how to specify a job stream instance in a command using conman, refer to Selecting job streams in commands.