RE: API QIMGCVTI

The 'specific issue' with '4B 0' is that when the API manual says
'Binary(4)' it wants a 4-byte variable.   4B 0 is a 4-digit, 2-byte
variable.   That causes big problems.

Since this is a common 'gotcha', I always tell people to make sure they're
using '10I 0' not '4B 0'.   The really important factor there is the
increase from 2 bytes to 4 bytes.

I could tell him to make sure he's using '9B 0' instead of '4B 0'.
You're right, that 9B 0 would work, so long as we didn't exceed 9 decimal
digits.

But why?   Why would I tell him to use '9B 0'?  Yes, it works 99.9% of the
time, but '10I 0' works ALL of the time.   '10I 0' also performs better.
It's not significantly harder to type '10I 0' than '9B 0'.  Once defined,
you use it in EXACTLY the same way.  There's no downside to using '10I 0'
that I can see.   So, if I have to recommend one or the other, I'm going
to recommend using '10I 0'.


On Fri, 13 Dec 2002, Bob Cozzi wrote:
>
> Have you found a specific issue with 4B values? I never use them and
> haven't for years, but I've been under the impression that they can be
> used interchangably with 10i0 values provided the numeric range isn't
> outside the scope of the variable.
>