×
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.
But that's part of the problem. Don't let the user see any halt messages
by putting in the GMM. Then have it go to EOP with maybe nothing more
than a DSPJOBLOG OUTPUT(*PRINT) if even that. I never use a GMM. I put
detail on a particular area. And by detail, I do NOT mean MONMSG CPF0000
on a DLTF or some such thing. I monitor for particular messages that I
may expect. If it's highly likely that the file may not be there (QTEMP)
then I'll monitor for just "file not found" and then remove that message
from the joblog. If the DLTF fails because of something unexpected - then
a hard halt. Sure a stupid user may answer the message. But there's at
least a chance that someone may say something. Default, over simplified,
GMMs just get you into trouble.
Best to pipe it off to a batch job as much as you can so that your
monitoring software will alert you that a job in batch is stuck in MSGW.
Keeps it away from the user in their interactive job.
Rob Berendt
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
