Re: Using API QTWCHKSP

["Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>]

Hello Albert,

You wrote:
>I was defining the length variable like this:
>D ReceiverLen     s              4b 0 inz(1024))

>Which apparently is not the same as
>D ReceiverLen             1      4b 0 inz(1024)

That's right.  The first is a stand-alone field which holds 4 digits of
data (i.e., 2-bytes).  The second is a data structure subfield that is
4-bytes long (therefore can hold much larger numbers).

What you were doing was to pass 2 bytes in a parameter where the API was
expecting 4 bytes so the API read the next two bytes of storage as part of
the parameter and thus broke.

Since you are obviously using RPG IV you should define the fields as 10I 0
and get true 4-byte integers which is what the API expects.

D ReceiverLen     s             10I 0 inz(1024))

will work as expected.

**** MEMORISE THIS ******
When using APIs BIN(2) and BIN(4) mean INTEGER data types.  Use data type
I and forget that RPG has data type B.  BIN(2) == 5I 0, BIN(4) == 10I 0.
*************************

In fact forget the weird B data type altogether!  Unless your database
uses them you have no need for them and should use type I instead.

Regards,
Simon Coulter.

--------------------------------------------------------------------
   FlyByNight Software         AS/400 Technical Specialists
   http://www.flybynight.com.au/

   Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\
   Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /
                                                             X
                 ASCII Ribbon campaign against HTML E-Mail  / \
--------------------------------------------------------------------