From: Bob Cozzi <cozzi@xxxxxxxxx> > This works great! Thanks. > Is there data that suggests that this routine is as efficient or better than > calling the QMH message APIs to remove the message? > > From C, a simpler and more efficient option, especially if the exception > > path is take with some regularity, is to replace the signal handler with a > > branch-point exception handler that removes messages from the job log. It would seem to me that if you worry about efficiency (maybe you shouldn't) that it would be better to use the zero compare value to begin with, to prevent the message to get to the joblog in the first place. Something tells me that preventing it from getting to the log is better than removing it from the log.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.