|
Howard, In a message dated 98-06-10 10:35:41 EDT, you write: > The sign is the 'F' part of your example, if it were a > numeric field vs. a date field, the first time any > arithmatic operation was done on the field the 'Fox' would > change to 'C' or 'D' depending upon the value of the result. <<snip>> Now _that's_ interesting! I didn't know that DB2/400 had started using the "C". We transferred data from a mainframe to the /400 under V3R0M05, some of which contained packed, unsigned fields that had the "C" in the sign byte. It took two days to figure out that, despite the fact that the file wasn't open for update, the "C" was automatically converted to an "F" in the database when the data was read -- immediately disabling our "position to" function in a subfile against the same data (which still held the "C" value) on the first invocation after data transfer!!! Does this mean that the "C" would no longer be converted in the latter instance? TIA! Dean Asmussen Enterprise Systems Consulting, Inc. Fuquay-Varina, NC USA E-Mail: DAsmussen@aol.com Things you never hear -- Bill Clinton saying "Yeah, I did it. So what?" +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.