×
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.
One of my biggest issues is programmers who use the "Global Monitor
Message" {GMM}. The "MONMSG CPF0000 EXEC(Goto EOP)" is a great tool
that is not used properly.
There are a lot of "experts" who have "standard error handling routines"
that resend the messages back to the job's message queue & do nothing
else with the error. The program does not tell anyone about the error
unless a programmer actually reads the joblogs. I have seen a 6 hour
job finish in 10 minutes because of the GMM, all because of a simple
authority problem.
These "standard error handling routines" need to be modified to actually
tell someone "Hey, there is an error here!" The message should be sent
to the QSYSOPR message queue & not the user, because in my experience,
the users will ignore the message & do whatever they can to get rid of
it, including shutting down the connection.
The GMM should never be used in a nightly job stream or for that matter
any long running process.
The GMM should be used if you are writing commands or creating menus.
\Vincent
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
