>When using Debug Tool under CICS, every time a CALL statement is encountere=
>d the debugger steps into the called program.
>Is there a way to just have the called program called and not show its inte=
>rnal workings.
>
>We are using Debug Tool v14.1, z/OS v2.2, COBOL v6 and CICS TS v5.4.
I think
Sound like you need to open a PMR...
From: IBM Mainframe Discussion List on behalf of
Gadi Ben-Avi
Sent: Wednesday, February 14, 2018 10:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IBM Debug tool issue
Same thing,
The called program is entered in a debug
Same thing,
The called program is entered in a debug session
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Frank Swarbrick
Sent: Thursday, February 15, 2018 12:22 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IBM Debug tool issue
What happens if you use STEP OVER instead of STEP?
From: IBM Mainframe Discussion List on behalf of
Gadi Ben-Avi
Sent: Wednesday, February 14, 2018 6:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IBM Debug tool issue
For example, the first program has a
] On Behalf
Of Elardus Engelbrecht
Sent: Wednesday, February 14, 2018 2:59 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: IBM Debug tool issue
Gadi Ben-Avi wrote:
>When using Debug Tool under CICS, every time a CALL statement is encountered
>the debugger steps into the called program.
>I
Gadi Ben-Avi wrote:
>When using Debug Tool under CICS, every time a CALL statement is encountered
>the debugger steps into the called program.
>Is there a way to just have the called program called and not show its
>internal workings.
It depends.
Assuming 'show its internal workings' are deb
Hi,
When using Debug Tool under CICS, every time a CALL statement is encountered
the debugger steps into the called program.
Is there a way to just have the called program called and not show its internal
workings.
We are using Debug Tool v14.1, z/OS v2.2, COBOL v6 and CICS TS v5.4.
Thanks
Ga
