Do those error message procedures use the internal job id or something like
that to log/store messages? (ie, the trigger program writes errors using
the job id, and on %error the program doing the I/O can retrieve errors
using that same id).

I put together a similar system to that a few years ago for communicating
between jobs and ajax web applications. When an ajax application is called
a unique ID is passed in as well.

In the CGI program we set a message as to what we're doing (ie,
initializing, processing, reading record x of xxxxx, etc) that the client
can check every xxx seconds during the ajax call so instead of just a
swirling graphic there's real interaction being sent back to the user so
they know things aren't "locked up".

Brad
www.bvstools.com

On Sat, Oct 3, 2015 at 5:55 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:


Nathan
how du expect that triggers should signal back to the client (program)
in a
common way that is supported in any program language SQL etc.?


Henrik,

In the code sample I posted previously, it showed calls to a procedure
named trgMsgAdd(), which I use to return messages to ILE "callers". The
same procedure would be used to "log" messages which might subsequently be
retrieved from applications which might be running in other language
environments (Java, PHP, Python, Ruby, Etc.)
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



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.