Re: ILE - Tried to refer to an object that no longer exists...

It sounds to me like a similar problem someone was having when an
activation group was closed.  The only way to get the system to
re-open an activation group once it's closed is to sign off and
back on ending the default activation group.  There was quite a
bit of discussion a while back on this and the reasons were gone
into why this was happening and it made sense.

It sounds like when you are running this program and it crashes,
it is crashing in the service program which causes that activation
group to close.

When you try to run the program again the current activation group
(*default?) tries to use it's pointer to the service program which
is no longer in memory, which causes your error.

This is caused differently than another person's problem that had
the same result (he was reclaiming the activation group) but some
of the solutions should benefit you.

Here are some links to the thread discussing the issue in detail:
The initial question/message:
http://archive.midrange.com/rpg400-l/200105/msg00019.html
John Taylor's explanation of why this is happening:
http://archive.midrange.com/rpg400-l/200105/msg00053.html
John Taylor's possible solutions:
http://archive.midrange.com/rpg400-l/200105/msg00067.html

Regards,

Jim Langston

Me transmitte sursum, Caledoni!

"Stone, Brad V (TC)" wrote:
> 
> Ok, this one is odd.
> 
> Has anyone had a problem where you're running a program that uses
> subprocedures and then it crashes (in developement or testing only, of
> course <bg>).
> 
> So, you try to start up the program again and it crashes right away giving
> you a "tried to refer to an object that no longer exists" error on the
> service program containing the subprocedure(s) you were using?
> 
> This may not be _exactly_ how it happens, but it is annoying and if it's
> happened to you, you know what I'm talking about.
> 
> The reason I'm asking is last night one of our plants went to run their
> nightlies and got this error.  The only thing I can think of how this would
> happen is if they were running other programs that day that used a
> particular service program that the nightly program does as well, and one of
> those prior programs crashed.
> 
> Signing off and signing back on always fixes this problem and the crash no
> longer exists.  Reclaiming activations groups does not work (but that may be
> becuase we're using the *DFTACTGRP for some, by accident).
> 
> Thanks!
> 
> Brad
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---