The Exception Datastore provides the only method for preventing an Apply Engine from stopping when it encounters an unanticipated invalid data condition. Depending on business requirements, the exception datastore can be used to initiate correction of the invalid data in the source datastore or more likely, prompt modification of the script. Changes to the script may be as simple as adding INVALID Commands for the newly discovered invalid data, modification of source data DESCRIPTIONS, addition of new or modified target datastores and/or descriptions and additional processing logic. Frequently a combination of these items will be required.
Thorough testing will generally uncover most invalid data conditions. The natural evolution of source and target datastores and applications may however create new exception conditions. Precisely therefore, recommends the use of Source and Target exception datastores when testing all scripts but advises customers not to use them in a production environment. Contact Support@precisely.com if you are unsure about when and how to use an exception datastore.
Example
DATASTORE file://<source_exception_file_name.dat>
OF DB2CDC
AS SOURCE_EXP
DESCRIBED BY DUMMY;DATASTORE cdc://<host_name>:<port>/<publisher_name>/<engine_name>
OF IMSCDC
AS CDCIN
DESCRIBED BY GROUP IMS_SEG
EXCEPTION SOURCE_EXP;