I am trying to run an ILE CL program in debug mode on one of our test boxes. I have run debug zillions of times, no problem. But something very strange is occuring, and what makes this even more odd is that I had this program successfully running in debug yesterday morning on the test box. It will run on our development box in debug, my co-worker can run it in debug on the test box. But for some reason, it will no longer run for me. Here is what happens: When I issue the command, STRDBG PGM(MYLIB/MYCLPGM) UPDPROD(*YES), all is well. The module source displays. Until I hit f10 and then issue the command to run the program: CALL PGM(MYLIB/MYCLPGM) PARM('9999'). Instead of going into the source and allowing me to step thru the code, the program takes off and runs. I still have to do an ENDDBG also before I attempt to put it back into debug mode again after this. If anyone has ever seen this occur before, information would be greatly appreciated.
No announcement yet.
Debug is simple, right?Page Title Module
Move Remove Collapse