Stopping and Aborting a Session

By PenchalaRaju.Yanamala

You can stop or abort a session just as you can stop or abort any task. You can
also abort a session by using the ABORT() function in the mapping logic.
Session errors can cause the Integration Service to stop a session early. You
can control the stopping point by setting an error threshold in a session, using the
ABORT function in mappings, or requesting the Integration Service to stop the
session. You cannot control the stopping point when the Integration Service
encounters fatal errors, such as loss of connection to the target database.

If a session fails as a result of error, you can recover the workflow to recover the
session.

Related Topics:
Recovery Options
Row Error Logging

Threshold Errors

You can choose to stop a session on a designated number of non-fatal errors. A

non-fatal error is an error that does not force the session to stop on its first
occurrence. Establish the error threshold in the session properties with the Stop
on Errors option. When you enable this option, the Integration Service counts
non-fatal errors that occur in the reader, writer, and transformation threads.

The Integration Service maintains an independent error count when reading

sources, transforming data, and writing to targets. The Integration Service counts
the following non-fatal errors when you set the Stop on Errors option in the
session properties:

Reader errors. Errors encountered by the Integration Service while reading the
source database or source files. Reader threshold errors can include alignment
errors while running a session in Unicode mode.
Writer errors. Errors encountered by the Integration Service while writing to the
target database or target files. Writer threshold errors can include key constraint
violations, loading nulls into a not null field, and database trigger responses.
Transformation errors. Errors encountered by the Integration Service while
transforming data. Transformation threshold errors can include conversion
errors, and any condition set up as an ERROR, such as null input.

When you create multiple partitions in a pipeline, the Integration Service

maintains a separate error threshold for each partition. When the Integration
Service reaches the error threshold for any partition, it stops the session. The
writer may continue writing data from one or more partitions, but it does not affect
the ability to perform a successful recovery.

Note: If alignment errors occur in a non line-sequential VSAM file, the Integration
Service sets the error threshold to 1 and stops the session.

Fatal Error

A fatal error occurs when the Integration Service cannot access the source,
target, or repository. This can include loss of connection or target database
errors, such as lack of database space to load data. If the session uses a
Normalizer or Sequence Generator transformation, the Integration Service
cannot update the sequence values in the repository, and a fatal error occurs.

If the session does not use a Normalizer or Sequence Generator transformation,

and the Integration Service loses connection to the repository, the Integration
Service does not stop the session. The session completes, but the Integration
Service cannot log session statistics into the repository.

ABORT Function

Use the ABORT function in the mapping logic to abort a session when the
Integration Service encounters a designated transformation error.

User Command

You can stop or abort the session from the Workflow Manager. You can also stop
the session using pmcmd.

Integration Service Handling for Session Failure

The Integration Service handles session errors in different ways, depending on

the error or event that causes the session to fail.

Table 7-1 describes the Integration Service behavior when a session fails:

Table 7-2. Integration Service Behavior for Failed Sessions

Cause for Session Errors Integration Service Behavior
- Integration Service performs the
Error threshold met due to reader errors
following tasks:
-Stop command using Workflow Manager -
or pmcmd Stops reading.
-
Continues processing data.
-Continues writing and committing data
to targets.
If the Integration Service cannot finish
processing and committing data, you
need to issue the Abort command to
stop the session.
Abort command using Workflow Manager 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 within
60 seconds, it kills the DTM process
and terminates the session.
-Fatal error from database Integration Service performs the
 following tasks:
- -
Error threshold met due to writer errors Stops reading and writing.
-Rolls back all data not committed to
the target database.
If the session stops due to fatal error,
the commit or rollback may or may not
be successful.
-Error threshold met due to transformation Integration Service performs the
errors following tasks:
- -
ABORT( ) Stops reading.
-Invalid evaluation of transaction control -Flags the row as an abort row and
expression continues processing data.
-Continues to write to the target
database until it hits the abort row.
-Issues commits based on commit
intervals.
-Rolls back all data not committed to the
target database.