RE: QMHSNDPM in serviceprogram

Joep,

The idea is to have the service program "caller" obtain its own invocation pointer, and then pass that invocation pointer to the service program calling the QMHSNDPM API. You will still have to provide the call stack counter on that API call, but that will be the value relative to the call level identified by the invocation pointer, not the service program. This enables you to use the *PGMBDY special value as the call stack entry qualifier, as if the QMHSNDPM API call had been performed by the service program caller itself.

Cheers,
Carsten

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of j.beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx
Sent: 16. oktober 2014 14:55
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: RE: QMHSNDPM in serviceprogram

But _INVP takes one parameter; from the documentation:

The relative invocation is a literal value between 0 and scope-1 where scope is the procedure's scoping level. A value of 0 indicates that an invocation pointer to the currently executing procedure is to be returned.
A value of 1 indicates that an invocation pointer for the most recent invocation of the procedure identified as the owner of the currently executing procedure is returned. Increasing values for relative invocation refer to the further static nesting of the currently executing procedure, where invocation pointers to the most recent invocations of those uplevel procedures are returned.

Remarkably like the call stack counter we started with :-)

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.