|
Dave/Bruce, "C" is an alternate form that some older systems used and which the /400 mostly tolerates. It won't work right in a CHAIN, SETLL, or READE because the database routines don't do the comparisons using the human-readable field contents, rather they compare bit-by-bit for the two strings. Naturally the string in the READE keylist shows the final nybble of the packed number as '1111', but the record actually has '1100', so they don't match. I got burned by this once in 1987, and haven't used a packed field in an index since then. If I really have to have an index over a packed number, I create a logical which maps the packed field to zoned and then use that in the key. Dave Shaw Spartan International, Inc. Spartanburg, SC -----Original Message----- From: Leland, David [mailto:dleland@Harter.com] Wouldn't that be considered invalid data? I thought packed fields could only end w/ "D" or "F". Dave -----Original Message----- From: Bruce Odum [mailto:Bruce.Odum@cbs.fiserv.com] Has anyone ever had a problem using Reade with a partial key and one of the keys is packed and the data in the packed field ends with a C and not a F? Any ideas on why this would not work? +--- | 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.