|
Rich, I've seen 'die' procedures elsewhere, Scott Klement's IFS routines for one. But I don't think you'll be able to get the first level text to what you want. Note, you may want see how you like it when ZZZ_PH is called from another program, after all you wouldn't usually call ZZZ_PH from the command line. This will provide a better idea of how the 2,3,xx call stack count would work. HTH, 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 > > Current Conditions in Des Moines, IA > Overcast > Temp 55.4F > Winds out of the North at 13mph > > > -- > This is the RPG programming on the AS400 / iSeries (RPG400-L) > mailing list > To post a message email: RPG400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/rpg400-l > or email: RPG400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/rpg400-l. > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.