Service Program Issues

All,

I realize that this is a long one..... but I am now stumped as to why this
is occurring -- anyone have any ideas?

I am receiving a weird error at indeterminate times.  Here is the situation.
I have a service program that uses non-exported procedures as well as
exported procedures.  The service program also accesses files.  I have an
RPG program that access the exported procedures of the service program.
Most of the time, there are no problems.  Everything works well.  Every so
often, I get  a strange error.  This error occurs when accessing a procedure
in the service program that has been accessed successfully from the same
program earlier in the same job.

The job log shows the errors as follows:
Tried to refer to all or part of an object that no longer exists.
Call stack entry not found.
Exception recursion detected.
Application error.  *N unmonitored by *N at statement *N, instruction
  X'4000'.

The first error has second level text as:
Message ID . . . . . . :   MCH3402       Severity . . . . . . . :   40
Message type . . . . . :   Escape
Date sent  . . . . . . :   02/14/03      Time sent  . . . . . . :   16:46:37

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.

The second error second level text is:
Message ID . . . . . . :   CPF2479       Severity . . . . . . . :   40
Message type . . . . . :   Escape
Date sent  . . . . . . :   02/14/03      Time sent  . . . . . . :   16:46:37

Message . . . . :   Call stack entry not found.
Cause . . . . . :   Call stack entry SRV1VLDL, 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.

The third error has second level text of:
Message ID . . . . . . :   CEE3201       Severity . . . . . . . :   10
Message type . . . . . :   Diagnostic
Date sent  . . . . . . :   02/14/03      Time sent  . . . . . . :   16:46:3

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.

And last, but not least, the fourth error second level text is as follows:
Message ID . . . . . . :   CEE9901       Severity . . . . . . . :   30
Message type . . . . . :   Escape
Date sent  . . . . . . :   02/14/03      Time sent  . . . . . . :   16:46:37

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.

=======================================
Mike Silvers
Senior Programmer/Analyst
IBM Certified Expert
Hainey Business Systems
Main Office:  (717) 718-9601 ext 237
Branch Office:  (410) 901-9015
http://www.hbs-inc.com
=======================================