|
View previous topic :: View next topic
|
| Author |
Message |
Santty
New User
Joined: 20 Nov 2007
Posts: 37
Location: USA
|
|
|
|
Back in Xpediter days, if you debugged a program like XXXX, when you got to the call to an common program P1, you couldn't step through it and you'd have to set a breakpoint just after the LINK call and use the 'go' command to execute past it.
In DTCN I'm not finding a way to do this. The progamP1 I'm calling is not in debugger but I need the call to work so I can continue debugger information after the call. When I use step through the program the call occurs to the program P1, you can see it's working fine so it's DTCN stopping the call from working - and setting the breakpoint right after the LINK call is not working in DTCN like it did in XPED.
Anyone experience this and know the solution?
Am i missing anything here? |
|
| Back to top |
|
 |
Santty
New User
Joined: 20 Nov 2007
Posts: 37
Location: USA
|
|
|
|
This is the answer for the question:
To prevent Debug Tool from stopping at every EXEC CICS RETURN statement in your
application and suppress this message, set the TEST level to ERROR by using the
SET TEST ERROR command.
--- There will be an PF9=OPT option in DTCN hit it and change the TEST Level to ERROR |
|
| Back to top |
|
|
Anuj Dhawan
Superior Member
Joined: 22 Apr 2006
Posts: 6250
Location: Mumbai, India
|
|
|
|
| Great, Thanks for posting back what worked for you. Appreciate that. |
|
| Back to top |
|
|
|
|
