IBM Debug tool issue
>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 what you want is STEP OVER, not STEP INTO in Debug Tool Cheers, TomR >> COBOL is the Language of the Future! << -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM Debug tool issue
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 <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Gadi Ben-Avi <gad...@malam.com> 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 statement: CALL C-KVOLVAAD USING .. A breakpoint is set for the statement before the call, so the program stop. The user issue the STEP command. The display moves to the first statement in the called program. The user wants the called program to be executed, and the cursor moved to the next statement. As far as I know, all programs are compiled with the TEST option to enable debugging. BTW, if the program is run in batch, it works as expected. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 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. >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 debug statements, breakpoints, variables, debug messages, etc. How are they compiled and called in the first place? If they're setup so to show debug things, then you'll have to recompile them with different compiler/linkage settings or just change the parameters of these programs. Perhaps you should show us the CALL statements and what compile/runtime parameters/options are used? Also show us how the debugger 'steps into that program'. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא באחריות לכל נזק, ו/או אובדן, שיבוש או פגיעה במידע כלשהו שנגרם מסיבות של תקיפה חיצונית ו/או זדונית על הארגון. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא באחריות לכל נזק, ו/או אובדן, שיבוש או פגיעה במידע כלשהו שנגרם מסיבות של תקיפה חיצונית ו/או זדונית על הארגון. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM Debug tool issue
What happens if you use STEP OVER instead of STEP? From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Gadi Ben-Avi <gad...@malam.com> 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 statement: CALL C-KVOLVAAD USING .. A breakpoint is set for the statement before the call, so the program stop. The user issue the STEP command. The display moves to the first statement in the called program. The user wants the called program to be executed, and the cursor moved to the next statement. As far as I know, all programs are compiled with the TEST option to enable debugging. BTW, if the program is run in batch, it works as expected. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 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. >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 debug statements, breakpoints, variables, debug messages, etc. How are they compiled and called in the first place? If they're setup so to show debug things, then you'll have to recompile them with different compiler/linkage settings or just change the parameters of these programs. Perhaps you should show us the CALL statements and what compile/runtime parameters/options are used? Also show us how the debugger 'steps into that program'. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא באחריות לכל נזק, ו/או אובדן, שיבוש או פגיעה במידע כלשהו שנגרם מסיבות של תקיפה חיצונית ו/או זדונית על הארגון. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IBM Debug tool issue
For example, the first program has a statement: CALL C-KVOLVAAD USING .. A breakpoint is set for the statement before the call, so the program stop. The user issue the STEP command. The display moves to the first statement in the called program. The user wants the called program to be executed, and the cursor moved to the next statement. As far as I know, all programs are compiled with the TEST option to enable debugging. BTW, if the program is run in batch, it works as expected. Gadi -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] 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. >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 debug statements, breakpoints, variables, debug messages, etc. How are they compiled and called in the first place? If they're setup so to show debug things, then you'll have to recompile them with different compiler/linkage settings or just change the parameters of these programs. Perhaps you should show us the CALL statements and what compile/runtime parameters/options are used? Also show us how the debugger 'steps into that program'. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN הודעה זו נשלחה אליך מטעם חברה בקבוצת מלם תים וייתכן שהיא מוגנת תחת סודיות מסחרית. כל הצעה, התחייבות או מצג מטעם החברה, מחייבים מסמך נפרד וחתום על ידי מורשה החתימה של החברה. החברה רשאית לנטר כל תכתובת העוברת בשרתיה והיא לא תישא באחריות לכל נזק, ו/או אובדן, שיבוש או פגיעה במידע כלשהו שנגרם מסיבות של תקיפה חיצונית ו/או זדונית על הארגון. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
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. >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 debug statements, breakpoints, variables, debug messages, etc. How are they compiled and called in the first place? If they're setup so to show debug things, then you'll have to recompile them with different compiler/linkage settings or just change the parameters of these programs. Perhaps you should show us the CALL statements and what compile/runtime parameters/options are used? Also show us how the debugger 'steps into that program'. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IBM Debug tool issue
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 Gadi ? ?? ? ?? ??? ??? ?? ? ??? ?? ??. ?? , ?? ??? ?, ??? ? ?? ??? ? ?? ?? ?. ? ? ?? ?? ?? ?? ?? ??? ??? ???, ?/?? ?, ? ?? ? ? ? ? ?? ?? ? ??? ?/?? ?? ?? ??. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
