infa_gita

• Jul 29th, 2012

 

When Integration Service is executing session task and if we issue the stop command the integration service performs the following tasks:

Stops reading.
Continues processing data.
Continues writing and committing data to targets.

If the Integration Service cannot finish processing and committing data, we need to issue the Abort command to stop the session.
But if we issue the abort command, the integration service performs same tasks like the stop command but it has timeout period of 60 seconds. If the integration service cannot finish processing and committing data within the timeout period, it kills the DTM process and terminates the session. Hope this helped you.

Vicky

• Sep 15th, 2012

 

Stop waits for all running objects to complete and then terminate the process however abort stops the entire object running immediately.
Eg: A workflow is in running state and it’s having 5 sessions in it and only 2 sessions are running.
STOP: It will wait for the running sessions to complete their process and then terminate the workflow. Remaining 3 sessions will not run.
ABORT: It will kill the running session immediately and thus the workflow.

Sudha Rani

• Nov 6th, 2012

 

If we have to do stop it will stop that step only.again we have to start the workflow then that time it will start which step u have to stop that step only it start run the workflow
then abort says we have to done abort it will stop entirely. again we have to start the workflow at time it will run the workflow first step on words

Satish

• Mar 4th, 2014

 

STOP ensures current session activity / threads on Informatica server are complete and ends the workflow.
ABORT kills current session activity / threads on Informatica server irrespective of its state and ends the workflow.