L-Date fields

Fellow MI geeks:

Does anybody have any idea why Type L (date) fields in a
file would show up as 
double precision float fields in the data returned
from the QUSLFLD and/or 
QDBRTVFD API calls? The customer is on V4R4, and his
file works fine on both 
of our V4R4 machines, as well as our V4R2
machine.

--
James H. H. Lampert

P.S.: Please forgive the funky
formatting; my ISP's web-mail interface throws 
in random carriage returns
for no apparent reason. --JHHL

P.P.S.: Regarding the whole breakpoint
thread, what about adding a breakpoint 
on an MI instruction number (e.g.
"ADDBKP '/002A'")?
--JHHL