Perhaps I'm over simplifying things, but have you explored MONMSG?
Warmest Regards,
Richard Reeve
________________________________
From: Dennis Lovelady <iseries@xxxxxxxxxxxx>
To: RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>
Sent: Sun, August 15, 2010 7:44:26 AM
Subject: Programmatically locating, and allowing response to message causing job
*MSGW
A number of times I have run across a situation where I'd like to
programmatically identify the exact message that's causing a job to wait for
reply. For example one of my current tasks emulates WRKSBMJOB, but with
some special client-based processing. I have it working quite well, and
we're all pleased, but the option to respond to whatever message is causing
MSGW status eludes me.
I had the same issue with a WRKSPLF work alike and we finally abandoned the
MSGW idea.
As administrator for some systems a few years ago, we also developed an
application that would sent out pager messages when certain conditions
occurred (such as same-old, same-old MSGW status), and we'd have liked to be
able to send out the exact message that was awaiting response. For that, we
pored through the job's SBMMSGQ until (if) we found it. But that's horribly
inefficient and often unfruitful. Besides, we did not identify a method
that allowed response other than good-ole DSPMSG from an interactive job.
Since it has come up again, I'd like to see what others may have come up
with for this sort of thing, if you can share.
Dennis E. Lovelady
AIM/Skype: delovelady MSN: fastcounter@xxxxxxxxxxxx
<
http://www.linkedin.com/in/dennislovelady>
www.linkedin.com/in/dennislovelady --
Love sometimes expresses itself in sacrifice.
- Kirk, "Metamorphosis", stardate 3220.3
midrange.com
