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



John,

The open source and free iSeries-toolkit at www.iseries-toolkit.org
has pretty extensive support for job stacks. It can use the retrieve
job stack entry to get the caller's library, activation group, module,

etc. The message toolkit has some procedures that give you back
information based on the send message receive message technique.

Take a look at the Retrieve Job Stack module available
directly from CVS at:

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/iseries-toolkit/CVSROOT/src/qrpglesrc/rtvjobstk.irp?rev=HEAD&content-type=text/vnd.viewcvs-markup

You would need several supporting modules/service programs,
which are most easily retrieved from the downloads page. There is
some documentation that shows how this routine is used in a
CL at:

http://sourceforge.net/docman/display_doc.php?docid=10303&group_id=39365

David Morris

>>> jtaylor@rpg2java.com 04/18/02 10:25AM >>>

I'm using QMHRCVPM as part of a new error handler, and I've come across
the
need to know which program sent a particular message. Both RCVM0200
and
RCVM0300 will provide the name of the sending program, but neither
returns
the library that the program was executed from.

Have I missed something here? RCVM0300 will even give me the statement
number, but I can't find the libary anywhere.


Regards,

John Taylor


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.