Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
jay falck — — source: Informix-list mailing list archive (1991-1998)
We have an application which needs to unload data from tables based on
certain runtime selection criteria. When run as an unload statement from
dbaccess (we are running SE 5.01) all of the data unloads but one of the
float fields has a very small number 1.????e-269 in it. The same unload
statement from 4gl unloads everything up to the row before the row with
the bad data. Is this a known bug? Do I need to run a routine check on
the data each night to correct this problem? Any ideas what might be
causing this problem? For all rows where this problem exists, the very
small number is the same. The rows were inserted on different days and
in some case a re-ipl of the system had been performed. Any ideas and
suggestions will be most appreciated.
Thanks in advance.
--
Jay Falck jfalck@eden.com
Unix System Administrator jfalck@access.texas.gov
Central Reservation Center 512-389-8962
Texas Parks & Wildlife Dept 512-389-8998 (Fax)
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.