Posted: Wed Oct 25, 2000 9:34 pm
I GOT IT - THANKS!
> -----Original Message-----
> From: Becky Gaster [SMTP:becky.gaster@deseretbook.com]
> Sent: Wednesday, October 25, 2000 5:46 PM
> To: informix-datastage@oliver.com
> Subject: ok, attachments dont work
>
> IMPORTANT - PLEASE READ
>
>
>
> Informix would like to inform you of an anomaly that has been
> discovered in release 4.X of DataStage. This problem is specific to
> upgraded job designs that use the ODBC Stage. This issue will only
> impact your applications if you are using the ODBC Stage.
>
> Specifically, in 4.x, the ODBC stage treats all input links to one
> ODBC stage as part of a single transaction group. Upgraded jobs using
> multiple input links in this fashion are also converted to this new
> logic. This may result in performance degradation because the
> transaction size is set to 1, and (depending on the complexity of
> Constraints), may induce incorrect behavior. Commit/rollback actions
> now apply to all the links collectively, instead of individually as
> before.
>
> This is recorded as GTAR 30997.
>
> Essentially, the stage assumes that each row of data will be passed to
> each link in the transaction group. When the links have constraints on
> them so that a row may not go to every link, behavior will not be as
> expected.
>
> For further information regarding this issue please contact Informix
> Technical Support at 800-729-3553.
>
> -----Original Message-----
> From: Becky Gaster [SMTP:becky.gaster@deseretbook.com]
> Sent: Wednesday, October 25, 2000 5:46 PM
> To: informix-datastage@oliver.com
> Subject: ok, attachments dont work
>
> IMPORTANT - PLEASE READ
>
>
>
> Informix would like to inform you of an anomaly that has been
> discovered in release 4.X of DataStage. This problem is specific to
> upgraded job designs that use the ODBC Stage. This issue will only
> impact your applications if you are using the ODBC Stage.
>
> Specifically, in 4.x, the ODBC stage treats all input links to one
> ODBC stage as part of a single transaction group. Upgraded jobs using
> multiple input links in this fashion are also converted to this new
> logic. This may result in performance degradation because the
> transaction size is set to 1, and (depending on the complexity of
> Constraints), may induce incorrect behavior. Commit/rollback actions
> now apply to all the links collectively, instead of individually as
> before.
>
> This is recorded as GTAR 30997.
>
> Essentially, the stage assumes that each row of data will be passed to
> each link in the transaction group. When the links have constraints on
> them so that a row may not go to every link, behavior will not be as
> expected.
>
> For further information regarding this issue please contact Informix
> Technical Support at 800-729-3553.
>