• Subject: Unexpected results using API "QUSRMBRD"
  • From: bvining@xxxxxxxxxxxx
  • Date: Thu, 7 Jan 99 14:58:35 CST

David,

What type of reformatting is being required?  QUSRMBRD is one of the
original V1R3 APIs and has not (in a very quick review of its history)
had any major formatting problems.  When using the API are you using
the includes provided in the QSYSINC library?  If not, can you compare
your definition of the receiver variable to how it's defined in QSYSINC?

Some common errors if you are defining the receiver yourself is that the
System API Reference documentation is in Base 0  for offsets while
languages such as RPG and COBOL are Base 1.  Another common error for RPG
is to inadvertently define 2-byte binary/integer fields rather than
4-byte fields.

Again, a clarification on what you expected vs what you got would help
alot here.

Bruce Vining

>
>     I am getting "unexpected results" in my receiver variable when using
>     the API QUSRMBRD. Apparently the format as descibed in the manual and
>     on-line help does not correspond to the data format actually being
>     returned! I appear to be able to get expected results by modifying the
>     receiver format layout, but it makes me uncomfortable to think that
>     what I'm doing is not as described by IBM. Can anyone shed any light
>     on this situation in particular and/or APIs in general?
>
>     Thanks,
>
>     David Stobberingh
>     Nationwide Credit, Phoenix, AZ
>

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


This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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].