Re: Trigger weirdness with L-Date fields

A little clarification on some of the replies...

I suppose you have something like this:
H Datfmt(*ISO)

And I hope that your buffer data structure is formatted like this:
D NEW E DS EXTNAME(filename) QUALIFIED
D OLD DS LIKEDS(NEW)

And that your trigger parm is formatted something like

Why might it only be your date fields that are complaining about data
mapping errors? There are two possibilities:
1 - All fields are wrong and not just date fields. Contrary to popular
belief, DB2 will complain on writes on DDS defined files too and not just
sql defined files. But DDS files only complain on date fields. Not
legacy fields like character, numeric, etc. The reason it does that is
that a programmer may be overriding a numeric field with character data
because no one used "Monaco currency factor" and needed someplace in the
data buffer to store some custom character data. Date fields are new
enough that they didn't have to worry about breaking existing code. All
fields might be wrong if you calculated offsets wrong.
2 - You defined the dates wrong. Either by not following the suggestion
of an externally defined data structure, H spec or any number of things.

A dump of your data structures above might be helpful. And a dump of the
trigger program parameters would also be helpful.


Rob Berendt