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

You could be right.  The problem is we're phasing in ILE and we still have a
few that don't care to learn "why" they need to do certain things.  So even
though we tell them to compile to *CALLER, and explain why in ways they can
understand (ie opnqryfs, overrides,etc) that doesn't mean that the CLLE in
front will be compiled correctly.

I'm still curious as to why it happens, though.

> -----Original Message-----
> From: Joel Fritz [mailto:JFritz@sharperimage.com]
> Sent: Friday, June 29, 2001 10:30 AM
> To: 'RPG400-L@midrange.com'
> Subject: RE: ILE - Tried to refer to an object that no longer 
> exists...
> 
> 
> I think your post has the answer.  I'm willing to bet this 
> only happens when
> the service program is created to run in the caller's 
> activation group and
> the caller is running in the default activation group.  This 
> has happened to
> me enough in testing that I'm starting to think about doing 
> it right the
> first time. I may wait until I've solved my problem with the 
> 's' on the d
> spec for standalone variables. <g>  
> 
> I think making the caller run in a named activation group is 
> the way to go.
> 
> > -----Original Message-----
> > From: Stone, Brad V (TC) [mailto:bvstone@taylorcorp.com]
> > Sent: Friday, June 29, 2001 6:07 AM
> > To: 'RPG400-L@midrange.com'
> > Subject: ILE - Tried to refer to an object that no longer exists...
> > 
> > 
> > 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
> > +---
> > 
> +---
> | 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
> +---
> 
+---
| 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
+---