Let Capture build the transaction message with non-LOB columns first and LOB columns last instead of in strict column sequence order.

Please consider changing Capture to build transaction messages with all non-LOB data first, then add on the LOB data after all other non-LOB data no matter what the sequence numbers.  This would prevent the risk of splitting a message on non-LOB data.

Capture builds transaction messages based on the column sequence.  This poses a risk if the size of the transaction exceeds the limit defined by MAX_MESSAGE_SIZE for its SendQ and the transaction is split into separate messages by Capture.  Suppose there is a Db2 table defined as:

            Seq      Col Name        Col Type/Len

            1          COL_A            CHAR(50)

            2          COL_B            CLOB(100 K)

            3          COL_C            CHAR(100)

For this example, MAX_MESSAGE_SIZE=200 for the associated SendQ.  If a transaction comes in that contains a full 100K of LOB data, then COL_A, COL_B, and some part of COL_C would fit into the first message with the remaining data for COL_C being sent in a separate message.  Obviously, this example does not account for internal Db2 overhead like header data, but the concept should be acceptable.  When the split is done on the non-LOB data, it throws message ASN7170E.  This inactivates the associated SendQ and has the potential for data loss if truncation occurs on the message.

When adding a new column to a Db2 table, the norm is to add that new column to the end of the existing Db2 table structure.  That is, the new column would have a column sequence one greater than the last column of the existing table.  In prior versions there would be a need to drop/recreate a table to add a column if an existing LOB column needed to be located physically last on the table.  Where columns are physically located on the table (column sequence) is no longer a concern for Db2 processes and should not be for Capture either.