× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



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




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.