Versions Compared

Old Version 2

changes.mady.by.user Rodrigo Rivero

Saved on

compared with

New Version Current

changes.mady.by.user user-eb51a

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • It restarts from the point of failure, even if the point of failure was inside one or more Processing Sequence "blocks", such as a LOOP or WHILE block, or in a conditional block such as IF or CASE.
  • Any loop indices and all Processing Sequence variables retain the values they had at the point of failure.
  • The Processing Sequence executes the same version of the Processing Sequence definition with the Processing Sequence run was started, even if that is not the current definition.
Note
Note:  If the Processing Sequence execution was suspended explicitly using the SUSPEND Processing Sequence directive, the Processing Sequence restarts immediately after the SUSPEND directive.

...

  • The error arose through a Processing Sequence error status being raised.   Processing Sequence that end in error as a result of abnormal program termination of a program used by an Activity, Transformation Map or the Processing Sequence engine cannot be restarted.
Note
Note:  Processing Sequence run history and version history can be purged using the Database Housekeeping function.   If the necessary information has been purged, it will not be possible to restart the affected Processing Sequence run.