We have setup a Job sequence in a session where if we execute sequentially we are able to pass the value of parameter RUNID from one Job to another whereas when we are trying to execute them in parallel we are unable to pass the updated value to Job's.
Use Case 1: Sequential execution, where each RUNID variable is set in parent UPROC and passed to next UPROC
Use Case 2: Parallel execution, where each RUNID variable is set but updated value of the same in JOB 1 UPROC is not passed to JOB 2 UPROC
Component: Dollar Universe
Release: 6.x
As per scenario where the RUNID get value set during prior UPROC execution, which in case of parallel execution will not consider an update of value as all the UPROC's are started at same time, and will retain the value at start.
The working is as per design. For the use case of considering the updated value in each UPROC done via prior UPROC only sequential execution is recommended.
All the UPROC's i.e. in Case 1 or Case 2 run as session and if you filter the Job runs via session it will show all the UPROC status
Case 1 Case 2