Submitting job streams with a wildcard loses dependencies

You issue a submit of interdependent job streams using a wildcard. In certain circumstances you lose the dependencies in an anomalous way.

Cause and solution:

To understand the cause, follow this example, in which the job streams are represented by A, B, C, and their instances are represented by 1, 2:
  1. You have the following job streams and jobs in the Symphony file: 
    A1
B1 (A1,C1)
C1
    where B1 depends on A1 and C1.
  2. You submit all the jobs, using: 
    sbs @
    The planner creates the following Job Scheduler instances: 
    A2
B2 (A2,C1)
C2

    B2 now depends on A2 and C1. This is correct, because at the moment of submitting the B2 Job Scheduler C2 did not exist, so the highest instance available was C1.

  3. The planner then asks you to confirm that you want to submit the instances: 
    Do you want to submit A2?
Do you want to submit B2?
Do you want to submit C2?
  4. Assume that you do not want to submit the job streams A2 and C2, yet, so you reply "No" to the first and last questions. In these circumstances you lose the dependency on A2, but not on C1. This behavior is correct and logical but could be seen by some as anomalous.

To correct the situation, stop the agent on the workstation where the Job Scheduler is running and cancel the Job Scheduler. Then determine the correct sequence of actions to achieve the objective you want, and submit the appropriate jobs.