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


  1.  Home
  2. RPG400-L
  3. October 2014

Re: QMHSNDPM in serviceprogram

*CTLBDY 1 would send to one before the last control boundary... that's not the same as the "program that called your routine". (Control boundaries occur when the activation group changes, and you can have loads of programs all run in the same activation group.)

Maybe you meant to say *PGMBDY 1?



On 10/14/2014 4:24 AM, j.beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
Jan Grove (or should that be just Jan?),

You send the message to the call stack entry three levels up. What
probably happens that in you batch job that call stack entry does not
exist, so QMHSNDPM sends an escape message to your routine, which you
automatically handle by specifying an error data structure.

So the question is, why do you use call stack entry '*' with call stack
count 3? I would use *CTLBDY and 1; that sends the message to the program
that called your routine.

Joep Beckeringh



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.