Thanks for the answers folks. Like I said it was something stupid. I saw
it for myself by putting a breakpoint in the subprocedure itself, and when
the program halted during execution, I did a wrkjob to display the call
stack. It didn't register with me that even if you have a subprocedure
bound to a main procedure, you're still dealing with multiple procedures in
the call stack. Bumped up the call level by one and it works great. Thanks
for the feedback.
Buzz Fenner
Systems Analyst/Network Administrator
870.930.3374
mailto:bfenner@xxxxxxxxxxxxxxxx
----------------------------------------------------------------------
message: 1
date: Wed, 03 Sep 2008 11:55:28 -0500
from: Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
subject: Re: QMHSNDPM, QMHRMVPM, & Error Message Subfiles
Hi Buzz,
When you send messages to the error subfile, you sent them to *CTLBDY --
and you say that worked, the messages showed by. (Personally, I'd never
rely on *CTLBDY for a message subfile -- but, that doesn't appear to be
the problem today..)
However, when you remove messages, you tell it to remove from call stack
'*' (Which means "remove messages sent to the RmvMsg subprocedure).
It's important that your 'remove' logic references the same queue as the
'send' logic. In this case, it doesn't, it references a totally
different queue. You may very well be successfully removing messages,
but they won't be the messages in your message subfile, since you're
removing from a different place.
------------------------------
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) digest list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/rpg400-l.
End of RPG400-L Digest, Vol 7, Issue 796
****************************************
--
PRIVACY WARNING: For auditing purposes, a copy of this message has been
saved in a permanent database.
--
PRIVACY WARNING: For auditing purposes, a copy of this message has been
saved in a permanent database.
midrange.com
