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



Rich,

I'm wondering if having a PSSR subroutine would make a difference.  You could 
send the message to * and 1, which would be the program/procedure that invoked 
die.  Since die isn't monitored, the PSSR would be invoked.

Just thinking out loud ;-)

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
 

> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Rich Duzenbury
> Sent: Thursday, March 17, 2005 3:04 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: RE: Proper way to die...
> 
> 
> On Thu, 2005-03-17 at 13:39 -0600, Christen, Duane J. wrote:
> > What you want to do is leave the call stack entry at '*' 
> (current call stack
> > entry) and change the call stack count to 1 (previous x 
> entries). This will
> > send the message to the caller of die.
> > 
> Duane, thanks for the suggestion.
> 
> I gave it a try, and I still receive RNQ0202, Inquiry, sev 99
> "The call to 'DIE' ended in error".
> 
> Perhaps one cannot effectively have a 'die' procedure, and 
> must instead
> code all of the QMHSNDPM calls inline of the procedure that 
> is failing?
> 
> --
> Regards,
> Rich
> 


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.