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



James,

I'm not sure you could get it to fail quietly. Even if you could, do
you really want to? The whole idea behind triggers to to make sure
"something" always happens.

The problem is of course your good friend the cycle, RPG programs or
in you case the RPG PEP don't support recursion.

If you want to correct the problem, simply convert your RPG module
into a NOMAIN one (assuming you have a prototype and procedure
interface this is very easy). Now add a C-language module PEP to your
program that calls the RPG procedure to do the work.

The C PEP is easy:

#include <stdio.h>
#include <stdlib.h>

void MyRpgleTrigger(char *, int *);

main(int argc, char **argv)
{
// Call RPGLE proc
// Pass pointer to trigger buffer and buffer length
MyRpgleTrigger(argv[1], (int *) argv[2]);
}

HTH,

Charles


On Mon, Oct 6, 2008 at 1:24 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx> wrote:
We've had a recent report (naturally, while I was on vacation) of this
exception occurring with an "AFTER" trigger (the names have been changed
to protect the innocent):

Message ID . . . . . . : CEE9901 Date sent . . . . . . : 09/25/08 Time sent . . . . . . : 12:13:45
Message . . . . : Application error. RNX8888 unmonitored by FOOBAR at
> Statement *N, instruction X'0000'.


Message ID . . . . . . : RNX8888 Date sent . . . . . . : 09/25/08 Time sent . . . . . . : 12:13:45
Message . . . . : FOOBAR was called recursively.

The trigger program (called FOOBAR here) is mixed-language, with an ILE
RPG main calling ILE C functions and procedures.

Now the normal (and desired) behavior here is for recursive triggering
to just fail quietly, rather than lock up the job, or (worse) go into a
potentially system-crashing recursion loop. So far as I'm aware, this is
an isolated incident, but I vaguely recall hearing of similar incidents
in the past.

I quite honestly have no clue what could be going on here. Can somebody
point me in the right direction?

--
James H. H. Lampert
Touchtone Corporation

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.