|
David, > You are right, it won't help you if the program is no longer on the > stack. I am not sure what you are trying to accomplish, but when > I send an error message, I actually send two copies. Just an error handler that's flexible enough to be used with a variety of different applications. > To do what you are looking for, I would consider using the > iSeries-toolkit SndMsg procedure and add a call to the > retrieve job stack procedure in that program if some flag is set. > I would then write a message to a userspace, or ? showing > who sent what. You could then pull the message information > about the sender. The storage toolkit procedures that is > part of the iSeries-toolkit, makes building a userspace list > pretty easy. I have no control over the pgm that sends the message. In many cases, I won't even have the source. It looks like I'm simply SOL on this one. Thanks for the ideas. Regards, John Taylor
This mailing list archive is Copyright 1997-2026 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.