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



Hello to all,
I've been working with ILE for a couple months now and have been trying to
get a grip on the message handling in ILE.  I've read enough information to
make my head spin, without a real answer of what I need to do.

In our 'pre-ILE' world, when an unexpected error was found, the PSSR routine
called a CL program that would display a nice little screen to the user.
This screen had information on it that would help the programmer determine
the problem.  The user was instructed to take  a print screen and to call
the help desk with the information.  A dump was also generated when the user
exited the info screen.

Okay, how can I get this same type of thing to take place in the ILE world.
I've tried all sorts of combinations to percolate the message, but it just
doesn't work the way it use to.  Since this is the 'new way' of doing
things, maybe I'm wrong to want it to work the way it used to.

I've looked in the archives, but I haven't had much luck finding the
information I need.  Can anyone give me some direction as to what I'm
missing?  Good 'ol PSSR just doesn't cut it anymore.

Thanks!!
Jade

+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.