Documentation for using Debug Tool?
Documentation for using Debug Tool?
We're replacing CA Intertest with IBM Debug tool. Does anyone know if there is some documentation available on using Debug tool? It's been installled by the sys admins. ~ john
-
- Global moderator
- Posts: 3720
- Joined: Sat Dec 19, 2009 8:32 pm
- Skillset: Systems programming, SAS, COBOL, CICS, JCL, SMS, VSAM, etc.
- Referer: other forum
- Location: Dubuque, Iowa, USA
Re: Documentation for using Debug Tool?
http://www.s390.ibm.com and look for the Information Center for your version of z/OS. All IBM documentation is available on their web site.
-
- Global moderator
- Posts: 3720
- Joined: Sat Dec 19, 2009 8:32 pm
- Skillset: Systems programming, SAS, COBOL, CICS, JCL, SMS, VSAM, etc.
- Referer: other forum
- Location: Dubuque, Iowa, USA
Re: Documentation for using Debug Tool?
I should have said, "all publicly available IBM documentation" -- they do have restricted materials.
-
- Posts: 1
- Joined: Fri Jul 30, 2010 8:21 pm
- Skillset: cobol,jcl,db2,vsam,cics
- Referer: through friends
Re: Documentation for using Debug Tool?
i want mainframe materials pls forward for me
-
- Global moderator
- Posts: 3720
- Joined: Sat Dec 19, 2009 8:32 pm
- Skillset: Systems programming, SAS, COBOL, CICS, JCL, SMS, VSAM, etc.
- Referer: other forum
- Location: Dubuque, Iowa, USA
Re: Documentation for using Debug Tool?
Your request is so vague it cannot be satisfied. Are you wanting hardware information or software information or both? For hardware, are you wanting z11, z10, z9, or other hardware data? For software, are you wanting tutorials, manuals, specification sheets, or what?
A typical mainframe installation will usually have somewhere between 1,000 and 2,000 manuals for hardware and software, with the page count usually upwards of 2 million pages. Just asking for "mainframe materials" shows a complete and total lack of understanding of the mainframe and its history.
Furthermore, many manuals are copyrighted and cannot be posted nor linked to nor provided to you -- you have to get them yourself.
I strongly recommend you go to http://www.s390.ibm.com and spend a few weeks reading before attempting to post another question -- at least then you are more likely to ask something that can actually be answered!
A typical mainframe installation will usually have somewhere between 1,000 and 2,000 manuals for hardware and software, with the page count usually upwards of 2 million pages. Just asking for "mainframe materials" shows a complete and total lack of understanding of the mainframe and its history.
Furthermore, many manuals are copyrighted and cannot be posted nor linked to nor provided to you -- you have to get them yourself.
I strongly recommend you go to http://www.s390.ibm.com and spend a few weeks reading before attempting to post another question -- at least then you are more likely to ask something that can actually be answered!
Re: Documentation for using Debug Tool?
We have COBOL CICS Intertest installed. Howver, can anyone help me with this - a CICS program is calling a batch subroutine. An ASRA abend is occuring when this batch subroutine is called. How can I intercept the line of code within this batch code.
Thanks
Yogesh
Thanks
Yogesh
-
- Posts: 341
- Joined: Thu Feb 24, 2011 12:05 am
- Skillset: 30 years on IBM mainframes
- Referer: Searched for Frank Yeager
Re: Documentation for using Debug Tool?
Not sure what you mean by "batch". I've heard people call all subroutines "batch", but only because there is no CICS tran code that points to it.
If you simply mean a normal subroutine, then you'll have to make sure it gets compiled with the Intertest-enabled compile options. It's going to look VERY close to what you use to Intertest compile a main program. (In my shop, ALL programs get compiled like this)
After you're sure it's available to Intertest, then put a stop/break in the calling program first. Then, when that program stops, bring up the source code for the subroutine and put a stop/break in it. Not sure which command shows the source code from another program, but I'm sure it's in your quickref.
Then go ahead and let the calling program continue. Intertest should stop when it gets to the normal stop/break point.
And something else that's going to cause you confusion: The IBM debugger is actually named "Debug Tool", Intertest is ANOTHER debugging tool from a private company.
If you simply mean a normal subroutine, then you'll have to make sure it gets compiled with the Intertest-enabled compile options. It's going to look VERY close to what you use to Intertest compile a main program. (In my shop, ALL programs get compiled like this)
After you're sure it's available to Intertest, then put a stop/break in the calling program first. Then, when that program stops, bring up the source code for the subroutine and put a stop/break in it. Not sure which command shows the source code from another program, but I'm sure it's in your quickref.
Then go ahead and let the calling program continue. Intertest should stop when it gets to the normal stop/break point.
And something else that's going to cause you confusion: The IBM debugger is actually named "Debug Tool", Intertest is ANOTHER debugging tool from a private company.
-
- Similar Topics
- Replies
- Views
- Last post
-
- 1
- 3568
-
by samb01
View the latest post
Thu Jan 28, 2021 2:54 pm
-
- 1
- 7408
-
by enrico-sorichetti
View the latest post
Tue Sep 21, 2021 6:04 pm
-
- 1
- 2068
-
by prino
View the latest post
Mon Sep 05, 2022 2:12 am