event masking -- MI400

× 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.

Is anyone familiar with event masking? It's something that the OS does and it prevents debugging, not sure if preventing debugging is the goal or just a side effect.

The scenario is that I've tapped into an entry point in the SEPT and I'm trying to debug that program when called through the SEPT. The breakpoint never displays and I get this strange message:

Cause . . . . . : The breakpoint statement or instruction /0001 in

program TEST was already processed when the machine notification was received. The
program call for the breakpoint may no longer exist.
Technical description . . . . . . . . : The process was probably masked for

events when the breakpoint instruction was run. You cannot use the ADDBKP
command to stop the program at an instruction while the process is masked
for events.

If my test program calls another program, I get the same error trying to debug the second program. So I'm just looking for more information about this event masking, what it does, why it's used and if there is a way to turn it off.

BTW, this is on a V4R4 box.

Thanks.

--Matt

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.