Re: MIDRANGE-L Digest V2 #689

[Jon.Paris@xxxxxxxxxx]

The original RPG B(inary) data type - like it's COBOL equivalent - wants to
constrain the value that it represents to a whole number of digits.  For
example a 2 byte integer can hold values up to 32K, however if you were to
try to define a 5 digit binary field in RPG, you would find that the
compiler would allocate 4 bytes not 2.  This is because the value 99,999
(i.e. the largest 5 digit number) cannot be contained within 2 bytes.  So,
if you define it as being a 4B field, then if the API (or whatever) returns
a value larger than 9,999 it would be truncated with unpredictable results.
If you define the field as 5I however, there is no truncation possible.

An additional benefit is performance - in order to ensure that the B field
contains only the permitted number of digits, it is 'filtered' through a
packed decimal field of the required number of digits.  To be honest I'm
not 100% certain that the RPG compiler always does this - I know the COBOL
compiler does and the 'rules' are the same.


>Jon,
>Could you explain why this is?

>Bill

>> I doubt it has any relevance to your problem, but I notice you define
all
>> of the binary fields as type B.  This is not a good idea - you should be
>> using type I(nteger) i.e. 10 I  0  (not 9 B 0).


+---
| 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
+---