×
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.
Why put on a global program-level MONMSG? If something unexpected pops up
I often find it much easier to fix the situation and take a Retry than to
start the whole process again.
And, no, you don't even have to put a GOTO ERRORTRAP. You can leave off
even the GOTO and just have it ignore all errors. I've seen it. :-(
As far as the send a message and alert the troops one can often do that by
a job that constantly monitors QBATCH for jobs in a MSGW and alerts the
proper individual. Not hard to roll your own and there are a plethora of
packages out there to do this for you.
From: Wayne McAlpine <wayne.mcalpine@xxxxxxxxxxxxxxxxx>
I thought the only thing you could put on a program-level MONMMSG is a
GOTO. I typically monitor messages at the command level and reserve the
program-level MONMSG for unanticipated errors, using a GOTO ERRORTRAP
routine to produce a program dump and send a message.
Rob Berendt
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.
midrange.com
