Re: Service Program Issues

[Scott Mildenberger <scottmildenberger@xxxxxxxxx>]

Mike,

This can occur if an object was replaced, maybe the
service program or something it is using.  The service
program will resolve it's references at activation
time.  So, on subsequent calls it won't reresolve
objects thus if an object was replaced then it's
pointer to the old one won't be pointing to anything.

Not sure if that is clear, what I'm trying to say is
that some program was probably replaced and the
service program is pointing to the old one that is now
deleted.

Scott Mildenberger


--- Mike Silvers <msilvers@HBS-INC.COM> wrote:
> 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'.
> 


__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com