×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Dave Boettcher wrote:
It is also possible to twiddle the bits. Years ago we had the
problem of a mainframe file using Hex C instead of Hex F for
numeric. The code below fixed it.
c bitoff '67' Bits84
There were definitions that Bits84 overlaid the number with
the decimal data error, but it's been years and that part
seems to have been misplaced.
FWiW: The 0xC is a valid hex sign nibble in Binary Coded Decimal
[BCD] which should not ever result [nor ever have resulted] in a decimal
data error. To change data from a non-preferred [but valid] sign value,
to have the preferred-positive[ed] sign nibble [e.g. 0xF], then any
mapping of data into the field will do that. For example, the SQL:
update filename set fieldx = fieldx*1 /* FWiW the multiplication by one
is probably not required, because the intuitively useless request to
assign a field to itself is unlikely to be optimized by the removal of
its action */
Regards, Chuck
This mailing list archive is Copyright 1997-2025 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.
midrange.com
