Re: Indicator set on call to qcmdexec -- RPG400-L

× 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 11 Sep 2013 14:03, Needles,Stephen J wrote:

<<SNIP>>
If I remember this right...it will only tell you if the API call
was successful, not whether or not the command being executed was
successful. So I don't think a failing ALCOBJ command run by the
QCMDEXC API will result in the indicator being set to an error
condition. This is because the API did not fail...the command it was
passed failed. Two different events. The API can successfully manage
the error and return to the caller with a positive, "I did my task"
indicator even though the ALCOBJ command itself failed.

The Execute Command (QCMDEXC) API /resignals/ the exception message back to the caller as the indication of the failure of the command execution; making it appear almost as if the program that called the API had directly invoked the CL command. A small number of additional error messages may be used to communicate that the invocation of the API failed, versus the command invocation via the API having failed; the docs seem to confuse what can occur in each of QCMDCHK and QCMDEXC.

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.