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



I've got the problem (see below) when using a command calling a CL program
that then calls a chain of RPGIV programs ending in a service program.
The problem surfaces when the command is executed for the second time.  It
seems, when accessing the service program which provides some core I/O
functions, it crashes out.  There's no reclaiming or other such activities
going on.  All the programs are either in *DFTACTGRP or *CALLER.
The OS/400 version is V4R4.

In the following GO4289M is the module in the service program

Any help appreciated
The dump.....

    MSGID      TYPE                    SEV   DATE       TIME       FROM
PGM       LIBRARY     INST     TO PGM       LIBRARY      INST
    MCH3402    Escape                  40    05/12/01   15:01:04   QRNXIO
      QSYS        *STMT    QRNXIO       QSYS         *STMT
                                     From module . . . . . . . . :
QRNXDBIO
                                     From procedure  . . . . . . :
_QRNX_DB_CHAIN
                                     Statement . . . . . . . . . :   6

                                     To module . . . . . . . . . :
QRNXDBIO
                                     To procedure  . . . . . . . :
_QRNX_DB_CHAIN
                                     Statement . . . . . . . . . :   6

                                     Message . . . . :   Tried to refer to
all or part of an object that no longer
                                       exists.
                                     Cause . . . . . :   The most common
cause is that a stored address to an
                                       object is no longer correct because
that object was deleted or part of the
                                       object was deleted.
CPF2479    Escape                  40    05/12/01   15:01:04   QMHSNDPM
QSYS        0A43     QRNXIE       QSYS         *STMT
                                     To module . . . . . . . . . : QRNXMSG

                                     To procedure  . . . . . . . :
SignalException
                                     Statement . . . . . . . . . :   20

                                     Message . . . . :   Call stack entry
not found.
                                     Cause . . . . . :   Call stack entry
GO4289M, specified for the send, receive,
                                       move or delete message operation,
could not be found in the call stack.
                                       Recovery  . . . :   Change the call
stack entry name or be sure the
                                       specified entry is in the call
stack when doing the requested operation.
CEE3201    Diagnostic              10    05/12/01   15:01:04   QLEAWI
QSYS        *STMT    QRNXIE       QSYS         *STMT
                                     From module . . . . . . . . : QLEDEH

                                     From procedure  . . . . . . :   Q LE
leDefaultEh
                                     Statement . . . . . . . . . :   120

                                     To module . . . . . . . . . : QRNXERR

                                     To procedure  . . . . . . . :
_QRNX_UNEXP
                                     Statement . . . . . . . . . :   9

                                     Message . . . . :   Exception
recursion detected.
                                     Cause . . . . . :   An unhandled
exception occurred in an exception handler.
                                       Recovery  . . . :   Do not let an
exception that occurs in your exception
                                       handler go unhandled.
CEE9901    Escape                  30    05/12/01   15:01:04   QLEAWI
QSYS        *STMT    GO4240R      ZGPL         *STMT
                                     From module . . . . . . . . : QLETOOL

                                     From procedure  . . . . . . :   Q LE
AWIRaise
                                     Statement . . . . . . . . . :   190

                                     To module . . . . . . . . . : GO4240R

                                     To procedure  . . . . . . . : GO4240R

                                     Statement . . . . . . . . . :   50300

                                     Message . . . . :   Application
error.  *N unmonitored by *N at statement *N,
                                       instruction X'4000'.
                                     Cause . . . . . :   The application
ended abnormally because an exception
                                       occurred and was not handled.  The
name of the program to which the
                                       unhandled exception is sent is *N
*N . The program was stopped at the
                                       high-level language statement
number(s) *N at the time the message was sent.
                                        If more than one statement number
is shown, the program is an optimized ILE
                                       program.  Optimization does not
allow a single statement number to be
                                       determined.  If *N is shown as a
value, it means the real value was not
                                       available. Recovery  . . . :   See
the low level messages previously listed
                                       to locate the cause of the
exception.  Correct any errors, and then try the
                                       request again.






Regards
Adam White
adam@slic-systems.com
www.slic-systems.com/




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.