...
Multiple Processes
Unlike Parallel Jobs, input and output (passive) stages can act as both an input and output in the one Server job. When a job contains such a design, the Server engine will synchronize execution so that any load processes are completed before performing the read processes. For example, consider the following job design:
...
| Gliffy |
|---|
| imageAttachmentId | att1973354503 |
|---|
| macroId | ee1a3ec3-b54f-409f-9175-fbad8a0e7aa5 |
|---|
| baseUrl | https://datamigrators.atlassian.net/wiki |
|---|
| name | Srv-Container-dbReadWrite |
|---|
| diagramAttachmentId | att1974108163 |
|---|
| containerId | 1432027151 |
|---|
| timestamp | 1629784240467 |
|---|
|
...
| Note |
|---|
Jobs that use DSJobName and DSJobController macros will no longer produce the same output after applying this transformation. Any easy solution would be to have the sequence capture these values and pass them to the child jobs as parameters. Any existing use of DSJobName and DSJobController would then be updated to use the parameters |
