× 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.



Jason Glodowski wrote:
> 
> I am calling QGYOLSPL API and am getting the following in the APIERROR DS
> 
> AEBYTPRV OF APIERROR = 144
> AEBYTAVL OF APIERROR = 26
> AEEXCPID OF APIERROR = 'GUI0042'
> 
> >From QSYS/QGUIMSG, the error tells me the following:
> 
> &1 is not valid for status.
> 
> Can someone point me to what status is not valid?
> 

The values for the replacements (&1 etc) are in the exception-data field
of the error code structure (starting at offset 16, I think).  You can
get the readable message using QMHRTVM passing the message id and the
replacement text.

While developing code that's calling an API, I think it's better to set
the bytes-provided field (AEBYTPRV) to zero.  That way, you get the
error messages in the joblog where they're much easier to interpret (and
much harder to ignore).  Once you get it working, you can set the
bytes-provided to a non-zero value, although leaving it permanently at
zero means you will always be able to debug failures more easily.


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.