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

Thank you for your mail. Do you have a sample of using the _INVP builtin, that you could share?

Best regards

Jan

Am 16.10.2014 um 13:48 schrieb Flensburg, Carsten:
A similar approach can be employed by using the _INVP builtin to get the invocation pointer of the caller, and then specify that invocation pointer as call stack identifier when calling the QMHSNDPM API (or QMHMOVPM/QMHRSNEM).

Cheers,
Carsten

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Bruce Vining
Sent: 15. oktober 2014 22:24
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: QMHSNDPM in serviceprogram

An approach I've taken in my message handling *SRVPGM is to specify a call stack entry value of *PGMBDY and and a call stack entry qualification value
of '*NONE ' + the name of my caller. I use the Retrieve Call Stack
(QWVRCSTK) API to determine the name of my caller. This seems to work pretty well (or at least no one has complained).

This communication is intended only for use by the addressee.It may contain confidential or privilegedinformation.
If you receive this communication unintentionally, please inform us immediately and delete this e-mail and any attachments.
Warning: Although we have taken reasonable precautions to ensure no viruses are present in this email, we cannot accept
responsibility for any loss or damage arising from the use of this email or attachments.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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.