[ts-gen] questions on journal tables

[Bill Pippin]

Nils,

About the intermittent failure to post order status messages to the
joural that you have observed:

> I find the order journaling extremly useful. However, sometimes I am
> experiencing difficulties to catch all messages. 
> I observered incomplete updates especially of the table OrderStatus;
> for example 'Submitted' of an record missing, then 'Filled' coming in.  

Please consider trying out the most recent release.  The shim now
indicates journal post successes and failures with comments in the
log, as explained in the NEWS file.  For that matter, there have been
many improvements in the way commands and comments are logged, again
see the NEWS file.

By its nature, an intermittent problem is difficult to debug.  If
you still see intermittent loss of order status message posts with
the new shim, please let us know on the mailing list, and keep the
relevant log file around for diagnostic purposes.

Questions I would find of interest, given the lack of an expected
order status message in the journal to indicate that an order had
been submitted:

    1.  Was there a 'Submitted' order status message from the IB tws?

    2.  If so, did the log show the proper number of OrderStatus
        inserts?

    3.  Otherwise, was there a 418 warning in the log?

    4.  In any case, was there any kind of mysql error message
        text printed to the standard error?  (Please consider
        capturing the stderr to a log file, so such messages
        are not lost.)

You may well find the problem does not reoccur.  There have been many
changes to the shim, and in particular, the database version change
is in part due to the deletion of the account code attribute from
the value list of the OrderStatus table insert query, as explained
in the NEWS file.

This eliminates one possible cause of insert query failure, which
you would know of only if you were capturing the stderr, as noted
in (4) above.

Thanks,

Bill