Table of Contents

Search

  1. Preface
  2. Understanding Pipeline Partitioning
  3. Partition Points
  4. Partition Types
  5. Pushdown Optimization
  6. Pushdown Optimization and Transformations
  7. Real-time Processing
  8. Commit Points
  9. Row Error Logging
  10. Workflow Recovery
  11. Stopping and Aborting
  12. Concurrent Workflows
  13. Grid Processing
  14. Load Balancer
  15. Workflow Variables
  16. Parameters and Variables in Sessions
  17. Parameter Files
  18. FastExport
  19. External Loading
  20. FTP
  21. Session Caches
  22. Incremental Aggregation
  23. Session Log Interface
  24. Understanding Buffer Memory
  25. High Precision Data

Advanced Workflow Guide

Advanced Workflow Guide

Rules and Guidelines for Running Concurrent Instances of the Same Instance Name

Rules and Guidelines for Running Concurrent Instances of the Same Instance Name

Use the following rules and guidelines when you run concurrent instances of the same instance name:
  • The Integration Service overwrites variables between concurrent workflow runs when the variables are the same for each run.
  • You can stop or abort a workflow by run ID from
    pmcmd
    .
  • You can stop or abort workflow tasks by run ID from
    pmcmd
    .
  • The Workflow Monitor does not display the run ID for each instance. The run ID appears in the workflow log, session log, and the Run Properties panel of the Workflow Monitor.
  • When you configure a concurrent workflow to run with the same instance name, the log file names always contain time stamps.


Updated June 25, 2020