Intertest Batch issue with called assembler program

drowelf · Posted: Thu Jan 20, 2022 4:16 am

Howdy,

Long time mainframe programmer, but new to Intertest Batch. I have a Cobol program which calls an assembler routine. I have the names of both programs on the Monitored Programs list at the start of my Intertest Batch Session from within ISPF. Now I can trace the main program, but when I get to the call of my assembler routine, it does not step into the program. I've tried switching the order of the programs and issuing both 'At entry All' and the At {module name} Entry commands but no avail, I never get stopped at the entry to my assembler routine.

Any help would be appreciated.

sergeyken · Posted: Thu Jan 20, 2022 8:35 am

In fact, there are two questions:

1) What is the reason?

99.99% - the Assembler routine is using some non-standard entry code, not recognized (or incorrectly recognized) by Intertest.

2) How to fix/workaround it?

Cannot answer this question. Never used this Intertest, and even hate any “intellectual artificial intelligence tools” supposed to “help” in debugging any code.

As for myself, those thingies do create more problems than solve any of them. Hours or days spent on setting-up any debugger usually help to detect a bug which can be easily detected after 1-3-5 test runs with intermediate debug print statements.

PeterHolland · Posted: Thu Jan 20, 2022 2:28 pm

drowelf · Posted: Fri Jan 21, 2022 12:53 am

I figured out what the issue was. Its all a matter of names. The load module with the called routine had a different name than the CSECT within the routine. Once I made them match Intertest was able to see my entry breakpoints and step into the module.

sergeyken · Posted: Fri Jan 21, 2022 1:06 am