×
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.
On 22/12/2007, at 6:45 AM, Chris Bipes wrote:
That works because you are using small numbers. In RPGLE it should be
defined as 10U 0 for true unsigned binary. Large numbers that turn on
the high order bit become negative and cause all sorts of issues.
Unsigned should only be used when is explicitly defined in the API
interface. From the "Data types and APIs" section of the Information
Centre:
Binary data
In the API parameter tables, BINARY(2), BINARY(4), and BINARY(8)
represent numeric data. These parameters must be signed, 2-, 4-, or 8-
byte numeric values with a precision of 15 (halfword), 31 (fullword),
or 43 bits and 1 high-order bit for the sign. Numeric parameters that
must be unsigned numeric values are explicitly defined as BINARY(x)
UNSIGNED.
Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists
http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------
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.
midrange.com
