× 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 24/12/2009, at 2:44 PM, Loyd Goodbar wrote:

Re-reading Bruce's response, should the bytes provided by the size of the
entire error structure, as I've indicated,

Yes.

or the size of the "response
data", presumably including the exception ID, reserved space, and exception
data?

No, although that will seem to work. A properly written API will fill only the amount of space you tell it about. In this case the bytes provided would be less than the actual amount available and everything will work but you'll get less substitution data than you might expect.

I assumed it was the size of the structure, and have been wrong many
times before. :)

You're not wrong but you don't need to assume. From the manual:

:quote.
Bytes provided. The number of bytes that the calling application provides for the error code.
:equote.

It would be much clearer if the technical writer had included the word structure after error code. If you care sufficiently you can open a documentation APAR or send the (dis)Information Centre some feedback,

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 / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.