Re: QMHSNDPM in serviceprogram

Hello Bruce

Thank you for your mail. In a service-program I call QMHSNDPM like this:

QMHSNDPM( 'CPE3025'
: 'QCPFMSG *LIBL'
: *blank
: 0
: '*ESCAPE'
: '*PGMBDY'
: 1
: MsgKey
: dsEC
: 7
: '*NONE MSGSPTS '
: 0
);

I call the subprocedure from my program msgspts. This works alright from an interactive job. It brings the message-text of CPE3025 and ends.

If I submit the call to msgspts, the OS tells me, that the job ended normally. I see nothing - except the start- and end-message - in the system log. Accordingly I don't find a spooled file as joblog in the outq QEZJOBLOG. But the submitted job ended abnormally with an *escape-message. So why does the OS tell me, that it ended normally?

Best regards

Jan

Am 15.10.2014 um 22:23 schrieb Bruce Vining:

An approach I've taken in my message handling *SRVPGM is to specify a call
stack entry value of *PGMBDY and and a call stack entry qualification value
of '*NONE ' + the name of my caller. I use the Retrieve Call Stack
(QWVRCSTK) API to determine the name of my caller. This seems to work
pretty well (or at least no one has complained).

Bruce Vining

On Wed, Oct 15, 2014 at 2:36 PM, Joep Beckeringh <joep.beckeringh@xxxxxxxxxx

wrote:
Hi Scott,

Yes, I used something like that as well. But instead of counting the call
stack entries I had the caller pass its name (from the PSDS) as a
parameter, so the call to QMHSNDPM can use *PGMNAME with the call stack
entry qualification parameter.

Joep Beckeringh



Op 15 okt. 2014, om 19:57 heeft Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>
het volgende geschreven:

Hi there Joep,

Yes, that has always been a dilemna for me as well. Unfortunately,

there's no perfect solution. In some applications using *PGMBDY 1 works
nicely -- because I want to send to whomever called my service program.

But, for the other circumstance where I have a "send error" utility

called from a program, and I want to send to that program's caller, there's
no easy solution. The best I've come up with is to accept a parameter with
the number of call stack levels. So the "send error" procedure accepts
this parameter, and uses call stack '*' and call stack count is the
parameter. That way, my program can specify 2, 3, 4... whatever it needs
to go to the level that program desires.

Of course, that's clumsy because I have to count the call stack levels,

etc, but it's the best I've found.

*CTLBDY could work nicely if you always use ACTGRP(*NEW) (or in some

other way put every program in a diff activation group) -- but there are
many circumstances where this isn't practical, either.

-SK

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing 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.