SV: Debug Tool know how...
Thank You, but I already have the Reference manual and the User Guide... ..and I have read them both :(( (Or at least big parts of them.) Unfortunately the behaviour of DT doesn't correspond to the manuals (at points where I have found info about) - plus that there is a lot that is not explained. Thomas -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Timur Alpaslan Skickat: den 5 mars 2008 13:05 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: Debug Tool know how... Hi! You can try the address; http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp for IBM System z Enterprise Development Tools Compilers information centerCheers Timur Alpaslan Date: Wed, 5 Mar 2008 12:42:51 +0100 From: [EMAIL PROTECTED] Subject: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Hi! Anyone that can point me to a mailing list or resource about IBM's Debug Tool ? I'm trying to use it on a COBOL program and have some diificulties with its idiosyncrasys. TIA Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SV: Debug Tool know how...
Hi! There's also a Redbook SG24-7372-00 published June 2007 called IBM Application Development and Problem Determination Tools V7 for System z which can be rather handy to have a look at sometimes. Have you tried it? It's free to download from IBM. Cheers Timur Date: Wed, 5 Mar 2008 13:22:54 +0100 From: [EMAIL PROTECTED] Subject: SV: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Thank You, but I already have the Reference manual and the User Guide... ..and I have read them both :(( (Or at least big parts of them.) Unfortunately the behaviour of DT doesn't correspond to the manuals (at points where I have found info about) - plus that there is a lot that is not explained. Thomas -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Timur Alpaslan Skickat: den 5 mars 2008 13:05 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: Debug Tool know how... Hi! You can try the address; http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp for IBM System z Enterprise Development Tools Compilers information centerCheers Timur Alpaslan Date: Wed, 5 Mar 2008 12:42:51 +0100 From: [EMAIL PROTECTED] Subject: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Hi! Anyone that can point me to a mailing list or resource about IBM's Debug Tool ? I'm trying to use it on a COBOL program and have some diificulties with its idiosyncrasys. TIA Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
SV: SV: Debug Tool know how...
Yes, I have looked into it. But my problems is like: The manual says You can use the DT variable %CU or %BLOCK in place of names of current items, e g AT CHANGE %CU:VARIABLE-NAME , etc. But I get syntax error for that and so on. I also get other errors regarding qualification of variables. The manual is very short on syntax and its restrictions. So I need some advice from someone that have used DT a lot. Or whatever examples of DT code that can be found. Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Timur Alpaslan Skickat: den 5 mars 2008 13:55 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: Debug Tool know how... Hi! There's also a Redbook SG24-7372-00 published June 2007 called IBM Application Development and Problem Determination Tools V7 for System z which can be rather handy to have a look at sometimes. Have you tried it? It's free to download from IBM. Cheers Timur Date: Wed, 5 Mar 2008 13:22:54 +0100 From: [EMAIL PROTECTED] Subject: SV: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Thank You, but I already have the Reference manual and the User Guide... ..and I have read them both :(( (Or at least big parts of them.) Unfortunately the behaviour of DT doesn't correspond to the manuals (at points where I have found info about) - plus that there is a lot that is not explained. Thomas -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Timur Alpaslan Skickat: den 5 mars 2008 13:05 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: Debug Tool know how... Hi! You can try the address; http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp for IBM System z Enterprise Development Tools Compilers information centerCheers Timur Alpaslan Date: Wed, 5 Mar 2008 12:42:51 +0100 From: [EMAIL PROTECTED] Subject: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Hi! Anyone that can point me to a mailing list or resource about IBM's Debug Tool ? I'm trying to use it on a COBOL program and have some diificulties with its idiosyncrasys. TIA Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SV: SV: Debug Tool know how...
Sorry! I'm not a direct user of the product. I'll suggest you contact IBM SW Support such tah they can help you with details. Date: Wed, 5 Mar 2008 14:09:53 +0100 From: [EMAIL PROTECTED] Subject: SV: SV: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Yes, I have looked into it. But my problems is like: The manual says You can use the DT variable %CU or %BLOCK in place of names of current items, e g AT CHANGE %CU:VARIABLE-NAME , etc. But I get syntax error for that and so on. I also get other errors regarding qualification of variables. The manual is very short on syntax and its restrictions. So I need some advice from someone that have used DT a lot. Or whatever examples of DT code that can be found. Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Timur Alpaslan Skickat: den 5 mars 2008 13:55 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: Debug Tool know how... Hi! There's also a Redbook SG24-7372-00 published June 2007 called IBM Application Development and Problem Determination Tools V7 for System z which can be rather handy to have a look at sometimes. Have you tried it? It's free to download from IBM. Cheers Timur Date: Wed, 5 Mar 2008 13:22:54 +0100 From: [EMAIL PROTECTED] Subject: SV: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Thank You, but I already have the Reference manual and the User Guide... ..and I have read them both :(( (Or at least big parts of them.) Unfortunately the behaviour of DT doesn't correspond to the manuals (at points where I have found info about) - plus that there is a lot that is not explained. Thomas -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Timur Alpaslan Skickat: den 5 mars 2008 13:05 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: Debug Tool know how... Hi! You can try the address; http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp for IBM System z Enterprise Development Tools Compilers information centerCheers Timur Alpaslan Date: Wed, 5 Mar 2008 12:42:51 +0100 From: [EMAIL PROTECTED] Subject: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Hi! Anyone that can point me to a mailing list or resource about IBM's Debug Tool ? I'm trying to use it on a COBOL program and have some diificulties with its idiosyncrasys. TIA Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SV: Debug Tool know how...
On Wed, Mar 5, 2008 at 8:09 AM, Thomas Berg [EMAIL PROTECTED] wrote: Yes, I have looked into it. But my problems is like: The manual says You can use the DT variable %CU or %BLOCK in place of names of current items, e g AT CHANGE %CU:VARIABLE-NAME , etc. But I get syntax error for that and so on. I also get other errors regarding qualification of variables. The manual is very short on syntax and its restrictions. So I need some advice from someone that have used DT a lot. Or whatever examples of DT code that can be found. I am a DT user but unfortunately I do not know the answer to your question. What I do know is that the concepts of CU and BLOCK seem to be language-dependent and I have never found them very helpful when debugging Cobol programs. Also, our shop is still using version 5.1, which is not very current, and DT seems to change quite substantially from release to release. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
SV: SV: Debug Tool know how...
[mailto:[EMAIL PROTECTED] För Don Leahy Skickat: den 5 mars 2008 14:49 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: Debug Tool know how... On Wed, Mar 5, 2008 at 8:09 AM, Thomas Berg [EMAIL PROTECTED] wrote: Yes, I have looked into it. But my problems is like: The manual says You can use the DT variable %CU or %BLOCK in place of names of current items, e g AT CHANGE %CU:VARIABLE-NAME , etc. But I get syntax error for that and so on. I also get other errors regarding qualification of variables. The manual is very short on syntax and its restrictions. So I need some advice from someone that have used DT a lot. Or whatever examples of DT code that can be found. I am a DT user but unfortunately I do not know the answer to your question. What I do know is that the concepts of CU and BLOCK seem to be language-dependent and I have never found them very helpful when debugging Cobol programs. Also, our shop is still using version 5.1, which is not very current, and DT seems to change quite substantially from release to release. We runs ver 7.1 (upgraded recently from 6.1). If You have some examples of AT CHANGE and LIST with qualified variables I would be pleased if You can send any to me. BTW, I'm trying to use this code in pre-saved PDS-members to be run automatically in DT, if that make any difference. Thanks, Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
SV: Debug Tool know how...
You are right. But as the PMR way is a slow lane and I prefer to be sure that the error is in the product rather than behind the keyboard I need some more data. As nearly always, when You should do a PMR or write a RCF You don't have the time. I will try at comp.lang.cobol as You suggested. There must be *someone* else than me that have (tried to) done similar things in DT. Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Bill Klein Skickat: den 5 mars 2008 16:32 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Debug Tool know how... If you find cases where the manual says something will work (or you read it as saying that) and the product doesn't support it, then I would say that is DEFINITELY a place where you should create a support PMR. If you have questions about how to (and the manuals aren't clear), and it is for COBOL, you can try posting it to comp.lang.cobol Usenet group. I don't know how many debut tool users there are in that group, but there may be some. (Most of the contributors are PC/Linux/Unix COBOL users, but some are from IBM Enterprise COBOL shops. I would Certainly create RCF's (Readers Comment Forms) on anything that you think needs to be changed or expanded in the documentation). Thomas Berg [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] pa.myntet.se. .. Yes, I have looked into it. But my problems is like: The manual says You can use the DT variable %CU or %BLOCK in place of names of current items, e g AT CHANGE %CU:VARIABLE-NAME , etc. But I get syntax error for that and so on. I also get other errors regarding qualification of variables. The manual is very short on syntax and its restrictions. So I need some advice from someone that have used DT a lot. Or whatever examples of DT code that can be found. Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Timur Alpaslan Skickat: den 5 mars 2008 13:55 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: Debug Tool know how... Hi! There's also a Redbook SG24-7372-00 published June 2007 called IBM Application Development and Problem Determination Tools V7 for System z which can be rather handy to have a look at sometimes. Have you tried it? It's free to download from IBM. Cheers Timur Date: Wed, 5 Mar 2008 13:22:54 +0100 From: [EMAIL PROTECTED] Subject: SV: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Thank You, but I already have the Reference manual and the User Guide... ..and I have read them both :(( (Or at least big parts of them.) Unfortunately the behaviour of DT doesn't correspond to the manuals (at points where I have found info about) - plus that there is a lot that is not explained. Thomas -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Timur Alpaslan Skickat: den 5 mars 2008 13:05 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: Debug Tool know how... Hi! You can try the address; http://publib.boulder.ibm.com/infocenter/pdthelp/v1r1/index.jsp for IBM System z Enterprise Development Tools Compilers information centerCheers Timur Alpaslan Date: Wed, 5 Mar 2008 12:42:51 +0100 From: [EMAIL PROTECTED] Subject: Debug Tool know how... To: IBM-MAIN@BAMA.UA.EDU Hi! Anyone that can point me to a mailing list or resource about IBM's Debug Tool ? I'm trying to use it on a COBOL program and have some diificulties with its idiosyncrasys. TIA Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN
Re: SV: Debug Tool know how...
On Wed, Mar 5, 2008 at 9:15 AM, Thomas Berg [EMAIL PROTECTED] wrote: [mailto:[EMAIL PROTECTED] För Don Leahy Skickat: den 5 mars 2008 14:49 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: Debug Tool know how... On Wed, Mar 5, 2008 at 8:09 AM, Thomas Berg [EMAIL PROTECTED] wrote: Yes, I have looked into it. But my problems is like: The manual says You can use the DT variable %CU or %BLOCK in place of names of current items, e g AT CHANGE %CU:VARIABLE-NAME , etc. But I get syntax error for that and so on. I also get other errors regarding qualification of variables. The manual is very short on syntax and its restrictions. So I need some advice from someone that have used DT a lot. Or whatever examples of DT code that can be found. I am a DT user but unfortunately I do not know the answer to your question. What I do know is that the concepts of CU and BLOCK seem to be language-dependent and I have never found them very helpful when debugging Cobol programs. Also, our shop is still using version 5.1, which is not very current, and DT seems to change quite substantially from release to release. We runs ver 7.1 (upgraded recently from 6.1). If You have some examples of AT CHANGE and LIST with qualified variables I would be pleased if You can send any to me. BTW, I'm trying to use this code in pre-saved PDS-members to be run automatically in DT, if that make any difference. Thanks, Thomas Fully qualified names work for me: AT LABEL CXXMU21::CXXMU21:CXXMU21:MAIN-OUTPUT Where CXXMU21 is my load module name. This also works for me: AT LABEL %BLOCK:MAIN-OUTPUT And so does AT LABEL %CU:MAIN-OUTPUT But not: AT LABEL %CU:%BLOCK:MAIN-OUTPUT and AT LABEL %LOAD::%CU:%BLOCK:MAIN-OUTPUT For the Cobol programs that I work with the variables %LOAD, %CU and %BLOCK always have the same value. But DT doesn't seem to like it when you use multiple variables. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
SV: SV: Debug Tool know how...
-Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Don Leahy Skickat: den 5 mars 2008 17:40 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: Debug Tool know how... On Wed, Mar 5, 2008 at 9:15 AM, Thomas Berg [EMAIL PROTECTED] wrote: [mailto:[EMAIL PROTECTED] För Don Leahy Skickat: den 5 mars 2008 14:49 We runs ver 7.1 (upgraded recently from 6.1). If You have some examples of AT CHANGE and LIST with qualified variables I would be pleased if You can send any to me. BTW, I'm trying to use this code in pre-saved PDS-members to be run automatically in DT, if that make any difference. Thanks, Thomas Fully qualified names work for me: AT LABEL CXXMU21::CXXMU21:CXXMU21:MAIN-OUTPUT Where CXXMU21 is my load module name. This also works for me: AT LABEL %BLOCK:MAIN-OUTPUT And so does AT LABEL %CU:MAIN-OUTPUT But not: AT LABEL %CU:%BLOCK:MAIN-OUTPUT and AT LABEL %LOAD::%CU:%BLOCK:MAIN-OUTPUT Thanks! Looks like what I'm coding. (Except that I use AT CHANGE.) Is that C++ modules ? Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SV: Debug Tool know how...
On Wed, Mar 5, 2008 at 11:55 AM, Thomas Berg [EMAIL PROTECTED] wrote: Thanks! Looks like what I'm coding. (Except that I use AT CHANGE.) Is that C++ modules ? Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) Not C++. Enterprise Cobol V3.3 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: SV: SV: Debug Tool know how...
Thomas Berg wrote: -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Don Leahy Skickat: den 5 mars 2008 17:40 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: Debug Tool know how... On Wed, Mar 5, 2008 at 9:15 AM, Thomas Berg [EMAIL PROTECTED] wrote: [mailto:[EMAIL PROTECTED] För Don Leahy Skickat: den 5 mars 2008 14:49 We runs ver 7.1 (upgraded recently from 6.1). If You have some examples of AT CHANGE and LIST with qualified variables I would be pleased if You can send any to me. BTW, I'm trying to use this code in pre-saved PDS-members to be run automatically in DT, if that make any difference. Thanks, Thomas Fully qualified names work for me: AT LABEL CXXMU21::CXXMU21:CXXMU21:MAIN-OUTPUT Where CXXMU21 is my load module name. This also works for me: AT LABEL %BLOCK:MAIN-OUTPUT And so does AT LABEL %CU:MAIN-OUTPUT But not: AT LABEL %CU:%BLOCK:MAIN-OUTPUT and AT LABEL %LOAD::%CU:%BLOCK:MAIN-OUTPUT Thanks! Looks like what I'm coding. (Except that I use AT CHANGE.) Is that C++ modules ? Thomas _ Thomas Berg Specialist IT Utveckling Swedbank AB (Publ) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Thomas, Some experiments with AT CHANGE confirm Don's observations about qualified names in COBOL. I've found that the Debug Tool 7.1 seems to allow at most one variable-based name, provided it's the first name reference in a series of name references. E.g., for a variable named xyz, in block blk1, in compile unit comp1, in load module lm1, you can successfully follow AT CHANGE with: lm1::comp1:blk1:xyz [no debug tool variables] %block:xyz[block qualification variable] %cu:blk1:xyz [compile unit qualification variable] %cu:xyz [compile unit qualification, omitting block specification] %load::blk1:xyz[load module qualification, with block name] %load::comp1:xyz[load module qualification, with compile unit name] %load::comp1:blk1:xyz [load module qualification, with both compile unit and block name] Any attempt to precede a debug tool variable reference with either another debug tool variable reference, or an explicit load module / compile unit / block name seems to fail. I'm not sure whether this is a feature or a problem; as you've noted, the documentation leaves some room for interpretation. For what it's worth, in COBOL, the compile unit name is the first PROGRAM-ID in the source module. The block name is the same as the compile unit name, unless you are referencing variables defined in nested programs. A variable defined in a nested program's DATA DIVISION would have the block name of the nested program's PROGRAM-ID, but would have the compile unit name of the outermost program's PROGRAM-ID. Most typically (i.e., in the absence of nested programs), compile unit name and block name are the same, and you would normally only specify one of the two. Load module name is, of course, the member name of the executable program in the load library. Hope this helps, Hunter Cobb The Trainer's Friend, Inc. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
SV: SV: SV: Debug Tool know how...
-Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Hunter Cobb Skickat: den 5 mars 2008 21:28 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: SV: Debug Tool know how... Thomas, Some experiments with AT CHANGE confirm Don's observations about qualified names in COBOL. I've found that the Debug Tool 7.1 seems to allow at most one variable-based name, provided it's the first name reference in a series of name references. E.g., for a variable named xyz, in block blk1, in compile unit comp1, in load module lm1, you can successfully follow AT CHANGE with: lm1::comp1:blk1:xyz [no debug tool variables] %block:xyz[block qualification variable] %cu:blk1:xyz [compile unit qualification variable] %cu:xyz [compile unit qualification, omitting block specification %load::blk1:xyz[load module qualification, with block name] %load::comp1:xyz[load module qualification, with compile unit name] %load::comp1:blk1:xyz [load module qualification, with both compile unit and block name] Any attempt to precede a debug tool variable reference with either another debug tool variable reference, or an explicit load module / compile unit / block name seems to fail. I'm not sure whether this is a feature or a problem; as you've noted, the documentation leaves some room for interpretation. This seems to contradict Your first (succesfully) example ? Or do I missinterpret You ? For what it's worth, in COBOL, the compile unit name is the first PROGRAM-ID in the source module. The block name is the same as the compile unit name, unless you are referencing variables defined in nested programs. A variable defined in a nested program's DATA DIVISION would have the block name of the nested program's PROGRAM-ID, but would have the compile unit name of the outermost program's PROGRAM-ID. Most typically (i.e., in the absence of nested programs), compile unit name and block name are the same, and you would normally only specify one of the two. Load module name is, of course, the member name of the executable program in the load library. Hope this helps, Hunter Cobb The Trainer's Friend, Inc. Many thanks for the help! (With the use of AT ENTRY I made some progress...) But how do ordinary cobol qualification work ? Like xyz OF abc OF ghi etc. I don't seem to get it right, despite profreading the variable names and quals in the program. Do DT require ALL quals for a variable ? Like xyz OF abc OF def OF ghi OF jkl despite that xyz OF abc OF ghi would be enough unique for COBOL. (It's now quite late here, I will continue tomorrow.) A part of my log: ... * The ENTRY SISGB10 :: SISGB10 breakpoint is replaced. AT ENTRY SISMB10 PERFORM QUALIFY CU SISMB10 ; AT CHANGE WB20-CLNR-XX OF WB20-IMPORT-AVTAL-EV OF SISMB20-DS PERFORM LIST WB20-CLNR-XX OF WB20-IMPORT-AVTAL-EV OF SISMB20-DS ; END-PERFORM ; AT CHANGE WB20-CLNR-LIKV-XX OF WB20-IMPORT-EV OF SISMB20-DS PERFORM LIST WB20-CLNR-LIKV-XX OF WB20-IMPORT-EV OF SISMB20-DS ; END-PERFORM ; AT CHANGE CLNR-LIKV OF MOD-BUFFER PERFORM LIST CLNR-LIKV OF MOD-BUFFER ; END-PERFORM ; END-PERFORM ; * The Entry breakpoint command for SISMB10 : SISMB10 has been * deferred until the CU appears. * The ENTRY SISMB10 breakpoint is replaced. * *** Commands file commands end *** GO ; GO ; * The variable WB20-CLNR-XX is undefined or is incorrectly * qualified. GO ; * The variable WB20-CLNR-LIKV-XX is undefined or is incorrectly * qualified. GO ; * The variable WB20-CLNR-XX is undefined
Re: SV: SV: SV: Debug Tool know how...
The first example has no debug tool variables (strings that begin with a %); debug tool seems to be happy with explicit names in various combinations, it's only when you attempt to use a debug tool variable that it gets fussy. The only time I found a problem with explicit names (not sure it qualifies as a problem) was when I specified the load module name (either explicitly named, or via %LOAD) and the variable name, with no intervening compile unit or block names. In that case, debug tool was unhappy. Hunter Cobb The Trainer's Friend, Inc. - Thomas Berg wrote: -Ursprungligt meddelande- Från: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] För Hunter Cobb Skickat: den 5 mars 2008 21:28 Till: IBM-MAIN@BAMA.UA.EDU Ämne: Re: SV: SV: Debug Tool know how... Thomas, Some experiments with AT CHANGE confirm Don's observations about qualified names in COBOL. I've found that the Debug Tool 7.1 seems to allow at most one variable-based name, provided it's the first name reference in a series of name references. E.g., for a variable named xyz, in block blk1, in compile unit comp1, in load module lm1, you can successfully follow AT CHANGE with: lm1::comp1:blk1:xyz [no debug tool variables] %block:xyz[block qualification variable] %cu:blk1:xyz [compile unit qualification variable] %cu:xyz [compile unit qualification, omitting block specification %load::blk1:xyz[load module qualification, with block name] %load::comp1:xyz[load module qualification, with compile unit name] %load::comp1:blk1:xyz [load module qualification, with both compile unit and block name] Any attempt to precede a debug tool variable reference with either another debug tool variable reference, or an explicit load module / compile unit / block name seems to fail. I'm not sure whether this is a feature or a problem; as you've noted, the documentation leaves some room for interpretation. This seems to contradict Your first (succesfully) example ? Or do I missinterpret You ? For what it's worth, in COBOL, the compile unit name is the first PROGRAM-ID in the source module. The block name is the same as the compile unit name, unless you are referencing variables defined in nested programs. A variable defined in a nested program's DATA DIVISION would have the block name of the nested program's PROGRAM-ID, but would have the compile unit name of the outermost program's PROGRAM-ID. Most typically (i.e., in the absence of nested programs), compile unit name and block name are the same, and you would normally only specify one of the two. Load module name is, of course, the member name of the executable program in the load library. Hope this helps, Hunter Cobb The Trainer's Friend, Inc. Many thanks for the help! (With the use of AT ENTRY I made some progress...) But how do ordinary cobol qualification work ? Like xyz OF abc OF ghi etc. I don't seem to get it right, despite profreading the variable names and quals in the program. Do DT require ALL quals for a variable ? Like xyz OF abc OF def OF ghi OF jkl despite that xyz OF abc OF ghi would be enough unique for COBOL. (It's now quite late here, I will continue tomorrow.) A part of my log: ... * The ENTRY SISGB10 :: SISGB10 breakpoint is replaced. AT ENTRY SISMB10 PERFORM QUALIFY CU SISMB10 ; AT CHANGE WB20-CLNR-XX OF WB20-IMPORT-AVTAL-EV OF SISMB20-DS PERFORM LIST WB20-CLNR-XX OF WB20-IMPORT-AVTAL-EV OF SISMB20-DS ; END-PERFORM ; AT CHANGE WB20-CLNR-LIKV-XX OF WB20-IMPORT-EV OF SISMB20-DS PERFORM LIST WB20-CLNR-LIKV-XX OF WB20-IMPORT-EV OF SISMB20-DS ; END-PERFORM ; AT CHANGE CLNR-LIKV OF MOD-BUFFER PERFORM LIST CLNR-LIKV OF MOD-BUFFER ; END-PERFORM ; END-PERFORM ; * The Entry breakpoint command for SISMB10 : SISMB10 has been * deferred until the CU appears. * The ENTRY SISMB10 breakpoint is replaced. * *** Commands file commands end *** GO
