|
Sorry, maybe I wasn't clear.
This is a job that's overlooking other jobs. From this viewpoint, MONMSG
works for the other jobs, not for this one. Besides, sometimes the message
is a result of (for example) SNDUSRMSG or SNDMSG ... MSGQ(QSYSOPR)
MSGTYPE(*INQ) followed by RCVMSG.
Think WRKSBMJOB or WRKACTJOB. Each of these is able to respond to such
messages via option 7. That's what I want to emulate.
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
In case of fire, evacuate the building.
Do not use stairways.
Do not use elevators.
-- (sign by elevator in Boston's Federal Reserve Bank building)
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
--
This is the RPG programming on the IBM i / System i (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.
--
This is the RPG programming on the IBM i / System i (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.
--
This is the RPG programming on the IBM i / System i (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.
As an Amazon Associate we earn from qualifying purchases.
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.