×
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.
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 :-)
Joep Beckeringh
From:
"Flensburg, Carsten" <Flensburg@xxxxxxxxxx>
Date:
16-10-2014 13:49
Subject:
RE: QMHSNDPM in serviceprogram
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
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.
midrange.com
