RE: Preventing a recursive call...

One technique that I use doesn't prevent them doing the recursive call, it
just prevents it from being a problem.

In the C/L program I create a duplicate of the RPG program in QTEMP (using
the current time as part of the name) and then I call that program.

Albert York                          



        -----Original Message-----
        From:   Feador, Jerry [SMTP:JFeador@xxxxxxxxxx]
        Sent:   Monday, March 03, 2003 12:46 PM
        To:     'RPG programming on the AS400 / iSeries'
        Subject:        Preventing a recursive call...

        Hi All,

                Does anybody have a clue as to how I can prevent a recursive
call
        from a command?

                The scenario is.... I have a command which calls a CL(1)
which calls
        a CL(2) which calls an RPG... at this point it's allowed, and
common, to get
        to a command line, where everybody forgets that they've called the
command
        once already - calling the command again generates a recursive call
error in
        the RPG program...

                I've searched the archives and tried every combination of
MONMSG's
        and *PSSR's that I can come up with, yet the error prevails...

                Any ideas on how I can get the first CL(1) to end if the
command is
        already in effect (or running, or whatever)?

                TIA,
                        Jerry

                
        _______________________________________________
        This is the RPG programming on the AS400 / iSeries (RPG400-L)
mailing list
        To post a message email: RPG400-L@xxxxxxxxxxxx
        To subscribe, unsubscribe, or change list options,
        visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
        or email: RPG400-L-request@xxxxxxxxxxxx
        Before posting, please take a moment to review the archives
        at http://archive.midrange.com/rpg400-l.