RE: QMHSNDPM

Sharon,

Each procedure call is a new call stack entry. QMHSNDPM/QMHRMVPM need to know what call stack level to work on. One way is to interrogate the call stack. I haven't done that but I believe others on the list have.

I recently encountered this scenario and used the called program (where the screens are displayed from) message queue for the API's. I wasn't creating a shell though.

HTH,

Rick

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Wintermute, Sharon
Sent: Wednesday, May 12, 2010 1:26 PM
To: RPG programming on the IBM i / System i
Subject: QMHSNDPM



I have several shell routines that were subroutine based using Message Control subfiles. I am trying to create a basic shell that is procedure based and the main holdup is QMHSNDPM/QMHRMVPM.



I can get a /include version to work at the main level, but once you get nested within procedures it doesn't work very well. It looks like I need to interrogate the call stack in order to get back to the initial PEP. Am I headed in the right direction?



TIA,



Sharon Wintermute

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.