Re: Question on how to debug S0C7 (data exception) abend
Kirk Talman wrote: It came from a T shirt. Reminds me of a T-shirt I got from a family member who was at Kariba for holidays many many many years ago. On that stands: My friends went to Zimbabwe. All I got was this lousy T-shirt! That T-shirt is now serving as a rag to remove bugs (real bugs, not program bugs!) from my car. ;-D My current knowledge of German is mostly at the T shirt level. Google Translate, while inaccurate, can probably help you, but I know from my Afrikaans background that Afrikaans, German, Flemish and Netherlands have some grammatical issues you need to be aware. ;-D I will creep back under my rock... don't want to wake up poor Darren (IBM-MAIN's daddy) ... ;-D 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
Re: Question on how to debug S0C7 (data exception) abend
We were able to find the 2 records causing the S0C7 abends in the COBOL/Syncsort application. Thanks for the help. Norma Mowry DECC-Mechanicsburg Operating Systems Support (ESB11) (717)-605-7865 DSN:430 e-mail address: norma.e.mowry@mail.mil -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Elardus Engelbrecht Sent: Friday, July 05, 2013 10:18 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend Lizette Koehler kindly wrote: 1) LE Traps any abends - does some stuff, then returns control to the abend process Yes. By default as supplied by IBM. With TRAP(OFF) you get nasty side-effects according to LE diagnostic guide. Check the run-time options with RPTOPTS. Norma Mowry wrote: This is a batch job, executing a COBOL Program, it looks like the program is doing an internal sort using syncsort. I can see in the dump the statement failing is a ZAP, but also say a S0C4 abend before the S0C7 abend. Ask your programmers to put in display or trace statements so you can see exactly where in the program and where in the data is the program now just before abend. Or use LE DEBUG run-time options. 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: Question on how to debug S0C7 (data exception) abend
From: Gerhard Postpischil gerh...@valley.net Somewhat off topic, but if that was supposed to be German, it's wrong. I only have a rudimentary knowledge of Yiddish, but I believe it's wrong there, too. (Die) alte Kacker is the valid masculine plural. (Der) alter Kacker is the masculine singular. (Die) alte Kackerin is the feminine singular. I assume you meant the second form, unless you are suffering from multiple personality disorder g Gerhard Postpischil It came from a T shirt. Although my pre Ellis Island family name had an umlaut in it, I am told that my German heritage suffered an interruption on the first day of WWI when the citizens of N KY quit speaking the mother tongue and took down the signs written in it. I had one course in undergraduate. In graduate school, I passed a language exam in German only after two tries. The text was a paper by Wolfgang Pauli on pair production in freien raum (sp?), which was related to my thesis topic. If only macro assembler had been a possible choice then My current knowledge of German is mostly at the T shirt level. - The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
Sorry, This is a batch job, executing a COBOL Program, it looks like the program is doing an internal sort using syncsort. I can see in the dump the statement failing is a ZAP, but also say a S0C4 abend before the S0C7 abend. It seemed to me that the registers associated with the ZAP were bad. The programmers are going to re-compile the program and test again. Norma Mowry DECC-Mechanicsburg Operating Systems Support (ESB11) (717)-605-7865 DSN:430 e-mail address: norma.e.mowry@mail.mil -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Comstock Sent: Wednesday, July 03, 2013 08:44 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend On 7/3/2013 5:10 AM, Mowry, Norma E CIV DISA ESB (US) wrote: We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry Way too little information to help. Is this batch or online? What language is it written in? What version of z/OS? Other messages around the time of the abend? etc. Kind regards, -Steve Comstock -- 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: Question on how to debug S0C7 (data exception) abend
Unless LE has changed, this is my understanding 1) LE Traps any abends - does some stuff, then returns control to the abend process 2) The IPCS LEDATA is needed in some cases to go back to the CEE and DSA control blocks to find out what the real abend was. If my understanding is incorrect, I hope someone will correct this. If it is correct then the LE CRIME SCENE INVESTIGATION Share presentation should help in identifying this issue. If there is an S0C4 before the S0C7 and it is in a WER process, contact Syncsort for assistance. They have always been great even if it is not their issue. Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mowry, Norma E CIV DISA ESB (US) Sent: Friday, July 05, 2013 4:53 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend Sorry, This is a batch job, executing a COBOL Program, it looks like the program is doing an internal sort using syncsort. I can see in the dump the statement failing is a ZAP, but also say a S0C4 abend before the S0C7 abend. It seemed to me that the registers associated with the ZAP were bad. The programmers are going to re-compile the program and test again. Norma Mowry DECC-Mechanicsburg Operating Systems Support (ESB11) (717)-605-7865 DSN:430 e-mail address: norma.e.mowry@mail.mil -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Comstock Sent: Wednesday, July 03, 2013 08:44 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend On 7/3/2013 5:10 AM, Mowry, Norma E CIV DISA ESB (US) wrote: We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry Way too little information to help. Is this batch or online? What language is it written in? What version of z/OS? Other messages around the time of the abend? etc. Kind regards, -Steve Comstock -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
Lizette Koehler kindly wrote: 1) LE Traps any abends - does some stuff, then returns control to the abend process Yes. By default as supplied by IBM. With TRAP(OFF) you get nasty side-effects according to LE diagnostic guide. Check the run-time options with RPTOPTS. Norma Mowry wrote: This is a batch job, executing a COBOL Program, it looks like the program is doing an internal sort using syncsort. I can see in the dump the statement failing is a ZAP, but also say a S0C4 abend before the S0C7 abend. Ask your programmers to put in display or trace statements so you can see exactly where in the program and where in the data is the program now just before abend. Or use LE DEBUG run-time options. 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
Re: Question on how to debug S0C7 (data exception) abend
On 7/3/2013 12:11 PM, Kirk Talman wrote: As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. Somewhat off topic, but if that was supposed to be German, it's wrong. I only have a rudimentary knowledge of Yiddish, but I believe it's wrong there, too. (Die) alte Kacker is the valid masculine plural. (Der) alter Kacker is the masculine singular. (Die) alte Kackerin is the feminine singular. I assume you meant the second form, unless you are suffering from multiple personality disorder g Gerhard Postpischil Bradford, Vermont -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
On 7/3/2013 10:26 PM, Farley, Peter x23353 wrote: Assuming that IPCS is available to the application staff. In some shops it is not generally available, but reserved for the systems staff. And there is the issue of training in the product, which isn't always available either (outside of reading the FM's). Personally I have no problem using SYSUDUMP, but these days I most frequently use an interactive debugger to solve application errors. Not all production application dump analyzers are created equal. I haven't had the privilege of using recent versions of ABEND-AID, but I can personally vouch for the effectiveness of Macro4's Dumpmaster product. I have found that LE dumps are somewhat less than useful when interrupted or circumvented by the locally installed dump analyzer and/or poorly chosen installation defaults. In my experience, lack of training and training updates is the most frequent root cause of loss of knowledge of how to debug this simple issue. Thanks, Peter. Ahem. For example http://www.trainersfriend.com/Assembler_courses/C414descrpt.htm http://www.trainersfriend.com/COBOL_Courses/D732descr.htm http://www.trainersfriend.com/COBOL_Courses/D735descr.htm http://www.trainersfriend.com/PL_I_courses/E732descr.htm http://www.trainersfriend.com/PL_I_courses/E735descr.htm http://www.trainersfriend.com/Language_Environment_courses/M735descr.htm -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-355-2752 http://www.trainersfriend.com * To get a good Return on your Investment, first make an investment! + Training your people is an excellent investment * Try our tool for calculating your Return On Investment for training dollars at http://www.trainersfriend.com/ROI/roi.html Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shmuel Metz (Seymour J.) Sent: Wednesday, July 03, 2013 9:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend In caajsdjjn4zk-csejvp4exf4ctxc5dnv6cfr5a19pnovvvgq...@mail.gmail.com, on 07/03/2013 at 07:16 AM, John McKown john.archie.mck...@gmail.com said: Being old, I have occasionally turned off LE's abend handling and just gone for the throat using a recent compile (with generated assembler shown) and a SYSUDUMP. SYSMDUMP, TYVM. The programmers have forgotten how to do this entirely. Some things are best forgotten. IPCS isn't perfect, but it's better than highlighters and paper clips, or the electronic equivalent. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
S0C7 is the most simple cause of abend I can imagine. The only problem is to find the position in the program (that is: the source line) where the error occured. If you have this, you know the name of the variable causing the error, and the rest is a piece of cake. To get this, you need no tool. Simply look at reg 13 at the time of abend. This is the address of the current save area. The word 2 after the word at which reg 13 points to contains the address of the higher save area. There at position 16 (word 5) you find the address of the entry of the current procedure or function (which should be a little lower than the content of the current PSW at the time of error). Subtracting this from the PSW, you get the error offset - related to the beginning of the procedure or function. And, by looking at the PPA1 control block (which you can find by adding the content of EPA + 12 to the EPA address), you will get the name of the procedure (at PPA1 + X'38'), at least this is true for the current PL/1 and C compilers (maybe COBOL, too). Then you have the function name and the offset; now it's time to look at the compile listing. Of course you have it at hand, because it's production run, so the compile listing must have been archived during the deployment of the program. If you need classes for your mainframe developers to do dump analysis in Germany, Austria or Switzerland (or other countries), please contact me offline. Kind regards Bernd Am 03.07.2013 20:11, schrieb Kirk Talman: There have been several various good answers to this problem. As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. - Apparently one can be in Operating Systems Support w/o having been an application programmer. One of the advantages many of us older persons on this list and in the industry have is that we have seen it before. The idea that a person working in any technical job on a mainframe would not know what a S0C7 is and how to go after it is amazing to me. At one time there were machines w/o packed arithmetic, but now, apparently, training in system administration functions is considered adequate. Who on this list learned the majority of what they know via instruction? Most people learned most things by doing. The work we do is a craft, part art, part science. - The idea in this day and age of not having a tool to give diagnostic information when an abend occurs may indicate a lack of understanding by management, but is still amazing. IBMs Fault Analuzer is not, I think, expensive but is quite adequate to the task even in complex CICS/DB2/IMS/MQ environments. If I were told there were less expensive products available, I would not be surprised. - On the other hand, I recently had to modify a program older than the company. In code and macros I saw names of persons now high level managers. The code had a S0C7 recovery section that was miscoded because invalid assumptions were made about the effect of ignoring records causing the abend. And the people who own' the code were reluctant to fix the root cause even when the fix was spelled out for them. They finally did so only when embarrassed publicly. - The best education comes while acquiring scars and observing same in ones peers. IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 07/03/2013 07:10:18 AM: From: Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 07:11 AM Subject: Question on how to debug S0C7 (data exception) abend Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
B37s. --- bernd.oppol...@t-online.de wrote: From: Bernd Oppolzer bernd.oppol...@t-online.de To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend Date: Thu, 4 Jul 2013 17:01:29 +0200 S0C7 is the most simple cause of abend I can imagine. The only problem is to find the position in the program (that is: the source line) where the error occured. If you have this, you know the name of the variable causing the error, and the rest is a piece of cake. To get this, you need no tool. Simply look at reg 13 at the time of abend. This is the address of the current save area. The word 2 after the word at which reg 13 points to contains the address of the higher save area. There at position 16 (word 5) you find the address of the entry of the current procedure or function (which should be a little lower than the content of the current PSW at the time of error). Subtracting this from the PSW, you get the error offset - related to the beginning of the procedure or function. And, by looking at the PPA1 control block (which you can find by adding the content of EPA + 12 to the EPA address), you will get the name of the procedure (at PPA1 + X'38'), at least this is true for the current PL/1 and C compilers (maybe COBOL, too). Then you have the function name and the offset; now it's time to look at the compile listing. Of course you have it at hand, because it's production run, so the compile listing must have been archived during the deployment of the program. If you need classes for your mainframe developers to do dump analysis in Germany, Austria or Switzerland (or other countries), please contact me offline. Kind regards Bernd Am 03.07.2013 20:11, schrieb Kirk Talman: There have been several various good answers to this problem. As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. - Apparently one can be in Operating Systems Support w/o having been an application programmer. One of the advantages many of us older persons on this list and in the industry have is that we have seen it before. The idea that a person working in any technical job on a mainframe would not know what a S0C7 is and how to go after it is amazing to me. At one time there were machines w/o packed arithmetic, but now, apparently, training in system administration functions is considered adequate. Who on this list learned the majority of what they know via instruction? Most people learned most things by doing. The work we do is a craft, part art, part science. - The idea in this day and age of not having a tool to give diagnostic information when an abend occurs may indicate a lack of understanding by management, but is still amazing. IBMs Fault Analuzer is not, I think, expensive but is quite adequate to the task even in complex CICS/DB2/IMS/MQ environments. If I were told there were less expensive products available, I would not be surprised. - On the other hand, I recently had to modify a program older than the company. In code and macros I saw names of persons now high level managers. The code had a S0C7 recovery section that was miscoded because invalid assumptions were made about the effect of ignoring records causing the abend. And the people who own' the code were reluctant to fix the root cause even when the fix was spelled out for them. They finally did so only when embarrassed publicly. - The best education comes while acquiring scars and observing same in ones peers. IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 07/03/2013 07:10:18 AM: From: Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 07:11 AM Subject: Question on how to debug S0C7 (data exception) abend Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN _ Netscape. Just the Net You Need. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
Ok. In this case you need no dump analysis; the error message is sufficient (as is the case with many system errors, for example S806 - system cannot find module XYZ ...). One of the first statements in my dump analysis handout: we normally only cover S0Cx errors - for most other errors we don't need no dump analysis. Simply look into MVS System Codes. Kind regards Bernd Am 04.07.2013 17:03, schrieb Richard Pinion: B37s. --- bernd.oppol...@t-online.de wrote: From: Bernd Oppolzer bernd.oppol...@t-online.de To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend Date: Thu, 4 Jul 2013 17:01:29 +0200 S0C7 is the most simple cause of abend I can imagine. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
Bernd has summarized this situation more than adequately. Norma Mowry did not provide us with full information about the COBOL compiler that produced the offending program, but if it is a fairly recent Enterprise COBOL compiler it would, given the right compiler options, almost certainly be possible to shoot this 0c7 at the source-program level. That said, it is clear that the applications staff here lacks some skills it should have. If COBOL is itsr development language, there must be someone who can read LE dumps available. Not all system ABENDs are so easy to deal with as 0c7's. Let me also note that another implicit assumption has figured in these discussions. If the ABEND occurred in SYNCHSORT code, it would almost certainly have provided diagnostic information that was identifiable as such. It is still possible, albeit very unlikely, that the error is in the record/sort-field description provided to SYNCHSORT; and that description should be checked. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
On 7/4/2013 9:21 AM, Bernd Oppolzer wrote: Ok. In this case you need no dump analysis; the error message is sufficient (as is the case with many system errors, for example S806 - system cannot find module XYZ ...). One of the first statements in my dump analysis handout: we normally only cover S0Cx errors - for most other errors we don't need no dump analysis. Simply look into MVS System Codes. Kind regards Bernd Right. In our courses we take a similar approach: 1. Debug at the highest level possible (messages, codes, application outputs, source code, dump) 2. Always assume the error is in software (not hardware) unless definite proof to the contrary exists 3. Always assume the error is in your software (you are not likely to debug system errors), unless proof to the contrary exists 4. Use only the relevant information (keep it simple. Watch out for 'rapture of the dump'.) Still, for 1) above, one mustn't be afraid of diving into a dump if it's called for. -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-355-2752 http://www.trainersfriend.com * To get a good Return on your Investment, first make an investment! + Training your people is an excellent investment * Try our tool for calculating your Return On Investment for training dollars at http://www.trainersfriend.com/ROI/roi.html Am 04.07.2013 17:03, schrieb Richard Pinion: B37s. --- bernd.oppol...@t-online.de wrote: From: Bernd Oppolzer bernd.oppol...@t-online.de To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend Date: Thu, 4 Jul 2013 17:01:29 +0200 S0C7 is the most simple cause of abend I can imagine. -- 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: Question on how to debug S0C7 (data exception) abend
Richard Pinion wrote: B37s. 222 is easier to handle ;-D Ok, perhaps 322, 722, 822 or 878 are also easy. 622 is somewhat difficult to explain to an angry TSO user, but manageable. My users don't like 722 for obvious reasons. I wonder why, oh, why? ;-D 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
Re: Question on how to debug S0C7 (data exception) abend
If you have an LE Dump (CEEDUMP, CEESNAP), it's still easier, because LE gives you the traceback of the function or procedure calls, where you find all the information including the offsets I mentioned in my previous post, and you don't even need to do any calculations. If you compiled your programs using the GONUMBER options (which makes them larger, but not - much - slower), the LE Dump will even tell you the source line numbers at every call level. Again: ask for classes in German (or English) covering all those subjects; I do classes customized esspecially to the needs of your installation. Kind regards Bernd Am 04.07.2013 17:28, schrieb John Gilmore: Bernd has summarized this situation more than adequately. Norma Mowry did not provide us with full information about the COBOL compiler that produced the offending program, but if it is a fairly recent Enterprise COBOL compiler it would, given the right compiler options, almost certainly be possible to shoot this 0c7 at the source-program level. That said, it is clear that the applications staff here lacks some skills it should have. If COBOL is itsr development language, there must be someone who can read LE dumps available. Not all system ABENDs are so easy to deal with as 0c7's. Let me also note that another implicit assumption has figured in these discussions. If the ABEND occurred in SYNCHSORT code, it would almost certainly have provided diagnostic information that was identifiable as such. It is still possible, albeit very unlikely, that the error is in the record/sort-field description provided to SYNCHSORT; and that description should be checked. John Gilmore, Ashland, MA 01721 - USA -- 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: Question on how to debug S0C7 (data exception) abend
It's a bona fide US holiday, which trumps even Friday. I should not take on someone with a bona fide Germanic name, but German happens to be the closest thing I have to a (distant) second language. (Der) alter Kacker is the masculine singular. Definite article 'der' changes adjective from marked masculine 'alter' to 'alte'. As opposed to indefinite article as in 'ein alter Mann'. If you're old enough to remember the venerable statesman Konrad Adenauer, he was referred to 'Der Alte', . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Gerhard Postpischil gerh...@valley.net To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 11:44 PM Subject:Re: Question on how to debug S0C7 (data exception) abend Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On 7/3/2013 12:11 PM, Kirk Talman wrote: As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. Somewhat off topic, but if that was supposed to be German, it's wrong. I only have a rudimentary knowledge of Yiddish, but I believe it's wrong there, too. (Die) alte Kacker is the valid masculine plural. (Der) alter Kacker is the masculine singular. (Die) alte Kackerin is the feminine singular. I assume you meant the second form, unless you are suffering from multiple personality disorder g Gerhard Postpischil Bradford, Vermont -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
On 7/4/2013 1:43 PM, Skip Robinson wrote: Definite article 'der' changes adjective from marked masculine 'alter' to 'alte'. As opposed to indefinite article as in 'ein alter Mann'. That's why I put the definite articles in parenthesis. In Kirk's original post, he used the indefinite article, which would have translated as Ein alter Kacker. Gerhard Postpischil Bradford, Vermont -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
It's a bona fide US holiday, which trumps even Friday. I disagree. Many on the list are not Americans. You didn't hear any of we Canadians trumpeting our holiday on July 1st. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
Ted, that would be locality of reference. I suppose you'd complain if someone in Australia said It's Friday, because many on the list aren't Australian? Sheesh. Over-sensitive Canadians... On Thu, Jul 4, 2013 at 3:57 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: It's a bona fide US holiday, which trumps even Friday. I disagree. Many on the list are not Americans. You didn't hear any of we Canadians trumpeting our holiday on July 1st. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- zMan -- I've got a mainframe and I'm not afraid to use it -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
I don't like the Friday digressions! Sheesh. Insensitive Americans... - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: zMan zedgarhoo...@gmail.com Sender: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Date: Thu, 4 Jul 2013 16:30:43 To: IBM-MAIN@LISTSERV.UA.EDU Reply-To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend Ted, that would be locality of reference. I suppose you'd complain if someone in Australia said It's Friday, because many on the list aren't Australian? Sheesh. Over-sensitive Canadians... On Thu, Jul 4, 2013 at 3:57 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: It's a bona fide US holiday, which trumps even Friday. I disagree. Many on the list are not Americans. You didn't hear any of we Canadians trumpeting our holiday on July 1st. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- zMan -- I've got a mainframe and I'm not afraid to use it -- 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: Question on how to debug S0C7 (data exception) abend
Ah. So it was really a comment on topic drift--I'm with ya there! On Thu, Jul 4, 2013 at 5:54 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: I don't like the Friday digressions! Sheesh. Insensitive Americans... - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -Original Message- From: zMan zedgarhoo...@gmail.com Sender: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Date: Thu, 4 Jul 2013 16:30:43 To: IBM-MAIN@LISTSERV.UA.EDU Reply-To: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend Ted, that would be locality of reference. I suppose you'd complain if someone in Australia said It's Friday, because many on the list aren't Australian? Sheesh. Over-sensitive Canadians... On Thu, Jul 4, 2013 at 3:57 PM, Ted MacNEIL eamacn...@yahoo.ca wrote: It's a bona fide US holiday, which trumps even Friday. I disagree. Many on the list are not Americans. You didn't hear any of we Canadians trumpeting our holiday on July 1st. - Ted MacNEIL eamacn...@yahoo.ca Twitter: @TedMacNEIL -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN -- zMan -- I've got a mainframe and I'm not afraid to use it -- 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 -- zMan -- I've got a mainframe and I'm not afraid to use it -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
On Wed, Jul 3, 2013 at 4:10 AM, Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil wrote: We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. This sounds like an application issue, not a systems issue. If IPCS is available to the applications staff, put a //SYSMDUMP in the job. If IPCS is not available, use //SYSUDUMP. IF ABENDAID is available, it should do an excellent job of pinpointing the point of failure as well as showing records associated with open files. If ABENDAID is available and not providing enough information add //ABNLDUMP DD DUMMY and //SYSUDUMP to get both abend aid and sysudump information. It will be useful to the application staff to have the following: Compile listing with object code listed Assembler listing Binder maps if code is statically linked. Is the I/O occurring in the program that gets the 0c7? Or is the I/O in a separate program that puts the record into working storage and the working storage gets passed around. If Modify location where I/O is done and create additional working storage The working storage shoudl be 8 bytes longer then the largest record. Initialize the first 8 bytes to a unique value: X'BEEFCAFEDEADBEEF'. After each I/O, copy the record to the new buffer + 8. Once abend occurs, search for unique identifier. Good luck Norma Mowry -- 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: Question on how to debug S0C7 (data exception) abend
On Wed, 3 Jul 2013 11:10:18 + Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil wrote: :We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Why can't you find it? Look at which instruction is getting the 0C7 and see how that field is populated. -- Binyamin Dissen bdis...@dissensoftware.com http://www.dissensoftware.com Director, Dissen Software, Bar Grill - Israel Should you use the mailblocks package and expect a response from me, you should preauthorize the dissensoftware.com domain. I very rarely bother responding to challenge/response systems, especially those from irresponsible companies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
The LE is clearly involved. It would help to know what language---COBOL?---this application was written in and to have a DCB for the input file that contains the offending record. You have provided too little information to enable anyone to help you. John Gilmore, Ashland, MA 01721 - USA -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
Would adding a CEEOPTS DD override work? I've never tried it but maybe? //CEEOPTS DD * TERMTHDACT(UAONLY) DYNDUMP(*USERID,DYNAMIC,TDUMP) -Original Message- From: Mowry, Norma E CIV DISA ESB (US) [mailto:norma.e.mowry@mail.mil] Sent: Wednesday, July 03, 2013 7:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Question on how to debug S0C7 (data exception) abend We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry -- 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: Question on how to debug S0C7 (data exception) abend
Being old, I have occasionally turned off LE's abend handling and just gone for the throat using a recent compile (with generated assembler shown) and a SYSUDUMP. The programmers have forgotten how to do this entirely. They require AbendAid to pinpoint the problem for them or it is unfixable. AbendAid is a wonderful tool and can really save time. But it is like wearing a powered exoskeleton all the time. The muscles atrophy and you can't walk on your own after a while. Oh, well, I'm old and so not very forward thinking. On Wed, Jul 3, 2013 at 7:08 AM, Sambataro, Anthony (NIH/NBS) [E] anthony.sambat...@nih.gov wrote: Would adding a CEEOPTS DD override work? I've never tried it but maybe? //CEEOPTS DD * TERMTHDACT(UAONLY) DYNDUMP(*USERID,DYNAMIC,TDUMP) -Original Message- From: Mowry, Norma E CIV DISA ESB (US) [mailto:norma.e.mowry@mail.mil] Sent: Wednesday, July 03, 2013 7:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Question on how to debug S0C7 (data exception) abend We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry -- 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 -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
The program abending is written in COBOL. Norma Mowry DECC-Mechanicsburg Operating Systems Support (ESB11) (717)-605-7865 DSN:430 e-mail address: norma.e.mowry@mail.mil -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John Gilmore Sent: Wednesday, July 03, 2013 07:28 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend The LE is clearly involved. It would help to know what language---COBOL?---this application was written in and to have a DCB for the input file that contains the offending record. You have provided too little information to enable anyone to help you. John Gilmore, Ashland, MA 01721 - USA -- 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: Question on how to debug S0C7 (data exception) abend
Thanks all for the help... In this case we don't have abendaid to help find the issue. Sorry I forgot to mention that the program taking the abend is COBOL and that the program abending is doing a sort using syncsort. Norma Mowry -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of John McKown Sent: Wednesday, July 03, 2013 08:16 To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend Being old, I have occasionally turned off LE's abend handling and just gone for the throat using a recent compile (with generated assembler shown) and a SYSUDUMP. The programmers have forgotten how to do this entirely. They require AbendAid to pinpoint the problem for them or it is unfixable. AbendAid is a wonderful tool and can really save time. But it is like wearing a powered exoskeleton all the time. The muscles atrophy and you can't walk on your own after a while. Oh, well, I'm old and so not very forward thinking. On Wed, Jul 3, 2013 at 7:08 AM, Sambataro, Anthony (NIH/NBS) [E] anthony.sambat...@nih.gov wrote: Would adding a CEEOPTS DD override work? I've never tried it but maybe? //CEEOPTS DD * TERMTHDACT(UAONLY) DYNDUMP(*USERID,DYNAMIC,TDUMP) -Original Message- From: Mowry, Norma E CIV DISA ESB (US) [mailto:norma.e.mowry@mail.mil] Sent: Wednesday, July 03, 2013 7:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Question on how to debug S0C7 (data exception) abend We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry -- 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 -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! John McKown -- 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: Question on how to debug S0C7 (data exception) abend
On 7/3/2013 5:10 AM, Mowry, Norma E CIV DISA ESB (US) wrote: We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry Way too little information to help. Is this batch or online? What language is it written in? What version of z/OS? Other messages around the time of the abend? etc. Kind regards, -Steve Comstock -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
I have occasionally used SLIP+IPCS to debug an application program. The best advice I can offer is to set a SLIP trap for *any* abend. That is, do not specify an abend code. Something like SL SET,J=,END In a complex the task environment, it's possible that the abend you see (S0C7) is a consequence of some other abend. By not specifying a code, you have a better chance of seeing the original failure. . . JO.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile jo.skip.robin...@sce.com From: Steve Comstock st...@trainersfriend.com To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 05:44 AM Subject:Re: Question on how to debug S0C7 (data exception) abend Sent by:IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU On 7/3/2013 5:10 AM, Mowry, Norma E CIV DISA ESB (US) wrote: We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry Way too little information to help. Is this batch or online? What language is it written in? What version of z/OS? Other messages around the time of the abend? etc. Kind regards, -Steve Comstock -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
You might look at some of these Share Proceedings. They may help ● LE Crime Scene Investigation - Finding Debugging Clues in LE Dumps ● Slowed Down by LE? Perhaps the CEEPIPI Service Can Help! ● LE for Dummies ● COBOL Performance - Myths and Realities ● Comparing and Contrasting XML Features of DB2 and COBOL - When to Use Which One? ● Language Environment Futures Workshop ● What's New in LE for z/OS ● Look What I Found Under the Bar! ● Introducing LE Callable Services, plus a User's View of Why and How You Should Exploit Them in Your Applications ● Diagnosing Application Problems Under LE ● Migrating to LE Conforming Assembler, If You Need to ● Heaps of fun with LE Heaps ● Understanding the LE Storage Report ● The direction of LE's AMODE 64 support If you cannot access them, let me know. They are found on www.share.org Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mowry, Norma E CIV DISA ESB (US) Sent: Wednesday, July 03, 2013 4:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Question on how to debug S0C7 (data exception) abend We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
I found this thread that might help in an internet search. They maybe helpful http://ibmmainframeforum.com/viewtopic.php?t=7035 Redbooks: z/OS Diagnostic Data Collection and Analysis http://www.redbooks.ibm.com/abstracts/sg247110.html?Open Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Lizette Koehler Sent: Wednesday, July 03, 2013 6:34 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend You might look at some of these Share Proceedings. They may help ● LE Crime Scene Investigation - Finding Debugging Clues in LE Dumps ● Slowed Down by LE? Perhaps the CEEPIPI Service Can Help! ● LE for Dummies ● COBOL Performance - Myths and Realities ● Comparing and Contrasting XML Features of DB2 and COBOL - When to Use Which One? ● Language Environment Futures Workshop ● What's New in LE for z/OS ● Look What I Found Under the Bar! ● Introducing LE Callable Services, plus a User's View of Why and How You Should Exploit Them in Your Applications ● Diagnosing Application Problems Under LE ● Migrating to LE Conforming Assembler, If You Need to ● Heaps of fun with LE Heaps ● Understanding the LE Storage Report ● The direction of LE's AMODE 64 support If you cannot access them, let me know. They are found on www.share.org Lizette -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Mowry, Norma E CIV DISA ESB (US) Sent: Wednesday, July 03, 2013 4:10 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Question on how to debug S0C7 (data exception) abend We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry -- 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: Question on how to debug S0C7 (data exception) abend
On 7/3/2013 8:34 AM, Mowry, Norma E CIV DISA ESB (US) wrote: The program abending is written in COBOL. That invalidates my first guess g Back in the late sixties I diagnosed my first 0C7, in a colleague's production program that had been running problem free for some time. He was reading SMF records with BSAM (to identify spanning problems). The storage dump showed the failing instruction to be operating with valid data. It took an AHA moment to realize that the dump didn't match the data - he issued READ instructions without the expected CHECK or WAIT, making the code dependent on system load. Gerhard Postpischil Bradford, Vermont -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
As someone pointed out, a s0c7 may not really be due to a bad data field in the last record READ. But, to answer that question, if you did get an SVC dump using SLIP and you included RGN, SWA, TRT: use IP SUMMARY REGS FORMAT to get the DEB chain printed or follow it yourself to find the OPEN DCBs at the time of the SLIP matching. The DCB has the next record pointer at +4C . It should be in the buffer so you might need to back up one record. AbendAid and Fault Analyzer do this for you but it does not sound like you have those. If the pgm used READ INTO or the compile specified AWO, the record actually being processed is moved from the buffer. If the record description contains an OCCURS DEPENDING ON clause (a variable length table), sometimes the program is not handling examining table entries in a record validly. In the REGS FORMAT report, look for an RTM2WA which may be useful since that will show the PSW and regs, in case you are not adept at reading the RBs. use IP SYSTRACE TIME(LOCAL) to find the interrupt code 0007 to verify the PSW (this will cross check with the RTM2WA PSW and/or the PRB), and look for other errors in the trace (do a find on RCVY). If this abend is in a COBOL internal SORT, in a COBOL input or output procedure, the RBs will show the SORT VERB by a LINK to the in-house SORT routine and the input/output procedures are then run from that RB, not the jobstep PRB. regards, Joe D'Alessandro -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
There have been several various good answers to this problem. As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. - Apparently one can be in Operating Systems Support w/o having been an application programmer. One of the advantages many of us older persons on this list and in the industry have is that we have seen it before. The idea that a person working in any technical job on a mainframe would not know what a S0C7 is and how to go after it is amazing to me. At one time there were machines w/o packed arithmetic, but now, apparently, training in system administration functions is considered adequate. Who on this list learned the majority of what they know via instruction? Most people learned most things by doing. The work we do is a craft, part art, part science. - The idea in this day and age of not having a tool to give diagnostic information when an abend occurs may indicate a lack of understanding by management, but is still amazing. IBMs Fault Analuzer is not, I think, expensive but is quite adequate to the task even in complex CICS/DB2/IMS/MQ environments. If I were told there were less expensive products available, I would not be surprised. - On the other hand, I recently had to modify a program older than the company. In code and macros I saw names of persons now high level managers. The code had a S0C7 recovery section that was miscoded because invalid assumptions were made about the effect of ignoring records causing the abend. And the people who own' the code were reluctant to fix the root cause even when the fix was spelled out for them. They finally did so only when embarrassed publicly. - The best education comes while acquiring scars and observing same in ones peers. IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 07/03/2013 07:10:18 AM: From: Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 07:11 AM Subject: Question on how to debug S0C7 (data exception) abend Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry - The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
On Wed, Jul 3, 2013 at 1:11 PM, Kirk Talman rkueb...@tsys.com wrote: There have been several various good answers to this problem. As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. - Apparently one can be in Operating Systems Support w/o having been an application programmer. One of the advantages many of us older persons on this list and in the industry have is that we have seen it before. The I've never been in applications. I came out of college directly into systems programming. The reasons were: (1) I confused the bleep out of the applications' manager who referred me to the systems' manager (I have a candidate for you. I don't understand a damn thing he's saying!) (2) I knew OS JCL (they were converting from DOS/VS; (3) I was a bit twiddler even out of college (read the PoPS manual the the OS/MVS Data Areas manual). I'm still quite weird, but have not, yet, embraced making Linux kernel changes. -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! John McKown -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
On 7/3/2013 12:11 PM, Kirk Talman wrote: There have been several various good answers to this problem. As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. - Apparently one can be in Operating Systems Support w/o having been an application programmer. One of the advantages many of us older persons on this list and in the industry have is that we have seen it before. The idea that a person working in any technical job on a mainframe would not know what a S0C7 is and how to go after it is amazing to me. At one time there were machines w/o packed arithmetic, but now, apparently, training in system administration functions is considered adequate. Who on this list learned the majority of what they know via instruction? Most people learned most things by doing. The work we do is a craft, part art, part science. - The idea in this day and age of not having a tool to give diagnostic information when an abend occurs may indicate a lack of understanding by management, but is still amazing. IBMs Fault Analuzer is not, I think, expensive but is quite adequate to the task even in complex CICS/DB2/IMS/MQ environments. If I were told there were less expensive products available, I would not be surprised. - On the other hand, I recently had to modify a program older than the company. In code and macros I saw names of persons now high level managers. The code had a S0C7 recovery section that was miscoded because invalid assumptions were made about the effect of ignoring records causing the abend. And the people who own' the code were reluctant to fix the root cause even when the fix was spelled out for them. They finally did so only when embarrassed publicly. - The best education comes while acquiring scars and observing same in ones peers. Hmmm. Well, the education with the biggest impact on memory and behavior comes that way. But 'best'? It might be better if one were educated to create applications that worked correctly, how to use the avialable tools most effectively, how to find and fix errors. The best way to get that is being taught by an excellent mentor who knows the way the company's code works and who can explain things clearly and patiently. After that, ahem, I would suggest a well-designed class that demonstrates techniques for design, coding, testing, debugging and maintenance. Such a class might even be designed to almost force the students into making errors along the way - fixing problems in the context of a training environment instead of production. At least a little bit like 'real life'. But, of course, I'm biased that way. -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-355-2752 http://www.trainersfriend.com * To get a good Return on your Investment, first make an investment! + Training your people is an excellent investment * Try our tool for calculating your Return On Investment for training dollars at http://www.trainersfriend.com/ROI/roi.html IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 07/03/2013 07:10:18 AM: From: Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 07:11 AM Subject: Question on how to debug S0C7 (data exception) abend Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
I am wondering how people can get along not being able to go through a dump. Maybe I am way off base here but this would seem pretty straight forward to me. You have the entry point to the abend and you have the entry point of the problem program. Subtract one from the other and you have the instruction that was being executed at the time of the abend (another way of saying the line of code in the Cobol program). My initial guess is it is going to be a F8 instruction (zero and add packed could be wrong my memory is old and fails from time to time). Being a Cobol program there are easy ways to find what is in the data without looking for it in a dump. If you have access to the source code add a display command of the fields in use by the instruction failing. But that does not lead to why is it abending is it poor coding or is it bad data? If bad data you need to go address why bad data got to this point. Maybe I am just o old, but I would have assisted the applications programmer in this manner before setting a slip trap. Just maybe application programmers do not debug there dumps any longer. Carl Swanson Mobile:215.688.1459 Email: carl.swans...@verizon.net -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Steve Comstock Sent: Wednesday, July 03, 2013 2:45 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend On 7/3/2013 12:11 PM, Kirk Talman wrote: There have been several various good answers to this problem. As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. - Apparently one can be in Operating Systems Support w/o having been an application programmer. One of the advantages many of us older persons on this list and in the industry have is that we have seen it before. The idea that a person working in any technical job on a mainframe would not know what a S0C7 is and how to go after it is amazing to me. At one time there were machines w/o packed arithmetic, but now, apparently, training in system administration functions is considered adequate. Who on this list learned the majority of what they know via instruction? Most people learned most things by doing. The work we do is a craft, part art, part science. - The idea in this day and age of not having a tool to give diagnostic information when an abend occurs may indicate a lack of understanding by management, but is still amazing. IBMs Fault Analuzer is not, I think, expensive but is quite adequate to the task even in complex CICS/DB2/IMS/MQ environments. If I were told there were less expensive products available, I would not be surprised. - On the other hand, I recently had to modify a program older than the company. In code and macros I saw names of persons now high level managers. The code had a S0C7 recovery section that was miscoded because invalid assumptions were made about the effect of ignoring records causing the abend. And the people who own' the code were reluctant to fix the root cause even when the fix was spelled out for them. They finally did so only when embarrassed publicly. - The best education comes while acquiring scars and observing same in ones peers. Hmmm. Well, the education with the biggest impact on memory and behavior comes that way. But 'best'? It might be better if one were educated to create applications that worked correctly, how to use the avialable tools most effectively, how to find and fix errors. The best way to get that is being taught by an excellent mentor who knows the way the company's code works and who can explain things clearly and patiently. After that, ahem, I would suggest a well-designed class that demonstrates techniques for design, coding, testing, debugging and maintenance. Such a class might even be designed to almost force the students into making errors along the way - fixing problems in the context of a training environment instead of production. At least a little bit like 'real life'. But, of course, I'm biased that way. -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-355-2752 http://www.trainersfriend.com * To get a good Return on your Investment, first make an investment! + Training your people is an excellent investment * Try our tool for calculating your Return On Investment for training dollars at http://www.trainersfriend.com/ROI/roi.html IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 07/03/2013 07:10:18 AM: From: Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 07:11 AM Subject: Question on how to debug S0C7 (data exception) abend Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find
Re: Question on how to debug S0C7 (data exception) abend
Kirk: We had one of these issues and the programmer said since its a system 0C7 its the systems people's responsibility . I called up to his manager and dispensed him out the door . Ed On Jul 3, 2013, at 1:11 PM, Kirk Talman wrote: There have been several various good answers to this problem. As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. - Apparently one can be in Operating Systems Support w/o having been an application programmer. One of the advantages many of us older persons on this list and in the industry have is that we have seen it before. The idea that a person working in any technical job on a mainframe would not know what a S0C7 is and how to go after it is amazing to me. At one time there were machines w/o packed arithmetic, but now, apparently, training in system administration functions is considered adequate. Who on this list learned the majority of what they know via instruction? Most people learned most things by doing. The work we do is a craft, part art, part science. - The idea in this day and age of not having a tool to give diagnostic information when an abend occurs may indicate a lack of understanding by management, but is still amazing. IBMs Fault Analuzer is not, I think, expensive but is quite adequate to the task even in complex CICS/DB2/IMS/MQ environments. If I were told there were less expensive products available, I would not be surprised. - On the other hand, I recently had to modify a program older than the company. In code and macros I saw names of persons now high level managers. The code had a S0C7 recovery section that was miscoded because invalid assumptions were made about the effect of ignoring records causing the abend. And the people who own' the code were reluctant to fix the root cause even when the fix was spelled out for them. They finally did so only when embarrassed publicly. - The best education comes while acquiring scars and observing same in ones peers. IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 07/03/2013 07:10:18 AM: From: Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 07:11 AM Subject: Question on how to debug S0C7 (data exception) abend Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry - The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you -- 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: Question on how to debug S0C7 (data exception) abend
You too? First name wouldn't have been Walter by any chance, would it? Same programmer went to the DOS/VS sysprog with a DOS message similar to PROGRAM TERMINATED BY PROGRAM REQUEST. Insisted the wasn't a TERMINATE verb anywhere in his program, must be a compiler problem. On Jul 3, 2013 2:50 PM, Ed Gould edgould1...@comcast.net wrote: Kirk: We had one of these issues and the programmer said since its a system 0C7 its the systems people's responsibility . I called up to his manager and dispensed him out the door . Ed On Jul 3, 2013, at 1:11 PM, Kirk Talman wrote: There have been several various good answers to this problem. As a certified alte kacker, I would like to comment on what this tells us about the state of mainframe IT. - Apparently one can be in Operating Systems Support w/o having been an application programmer. One of the advantages many of us older persons on this list and in the industry have is that we have seen it before. The idea that a person working in any technical job on a mainframe would not know what a S0C7 is and how to go after it is amazing to me. At one time there were machines w/o packed arithmetic, but now, apparently, training in system administration functions is considered adequate. Who on this list learned the majority of what they know via instruction? Most people learned most things by doing. The work we do is a craft, part art, part science. - The idea in this day and age of not having a tool to give diagnostic information when an abend occurs may indicate a lack of understanding by management, but is still amazing. IBMs Fault Analuzer is not, I think, expensive but is quite adequate to the task even in complex CICS/DB2/IMS/MQ environments. If I were told there were less expensive products available, I would not be surprised. - On the other hand, I recently had to modify a program older than the company. In code and macros I saw names of persons now high level managers. The code had a S0C7 recovery section that was miscoded because invalid assumptions were made about the effect of ignoring records causing the abend. And the people who own' the code were reluctant to fix the root cause even when the fix was spelled out for them. They finally did so only when embarrassed publicly. - The best education comes while acquiring scars and observing same in ones peers. IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU wrote on 07/03/2013 07:10:18 AM: From: Mowry, Norma E CIV DISA ESB (US) norma.e.mowry@mail.mil To: IBM-MAIN@LISTSERV.UA.EDU, Date: 07/03/2013 07:11 AM Subject: Question on how to debug S0C7 (data exception) abend Sent by: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU We have a production job that is abending with S0C7 reason 0007. I set a slip to capture a dump but I can't seem to find the input record that is causing the S0C7 in this dump. I also have a CEEDUMP but that's not real helpful in diagnosing the issue. I looked a setting a slip with a trace but don't think that will do any good to get to the problem record. Norma Mowry --**--- The information contained in this communication (including any attachments hereto) is confidential and is intended solely for the personal and confidential use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this communication in error and that any review, dissemination, copying, or unauthorized use of this information, or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. Thank you --**--** -- 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: Question on how to debug S0C7 (data exception) abend
In caajsdjjn4zk-csejvp4exf4ctxc5dnv6cfr5a19pnovvvgq...@mail.gmail.com, on 07/03/2013 at 07:16 AM, John McKown john.archie.mck...@gmail.com said: Being old, I have occasionally turned off LE's abend handling and just gone for the throat using a recent compile (with generated assembler shown) and a SYSUDUMP. SYSMDUMP, TYVM. The programmers have forgotten how to do this entirely. Some things are best forgotten. IPCS isn't perfect, but it's better than highlighters and paper clips, or the electronic equivalent. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2http://patriot.net/~shmuel We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
Assuming that IPCS is available to the application staff. In some shops it is not generally available, but reserved for the systems staff. And there is the issue of training in the product, which isn't always available either (outside of reading the FM's). Personally I have no problem using SYSUDUMP, but these days I most frequently use an interactive debugger to solve application errors. Not all production application dump analyzers are created equal. I haven't had the privilege of using recent versions of ABEND-AID, but I can personally vouch for the effectiveness of Macro4's Dumpmaster product. I have found that LE dumps are somewhat less than useful when interrupted or circumvented by the locally installed dump analyzer and/or poorly chosen installation defaults. In my experience, lack of training and training updates is the most frequent root cause of loss of knowledge of how to debug this simple issue. Peter -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shmuel Metz (Seymour J.) Sent: Wednesday, July 03, 2013 9:46 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: Question on how to debug S0C7 (data exception) abend In caajsdjjn4zk-csejvp4exf4ctxc5dnv6cfr5a19pnovvvgq...@mail.gmail.com, on 07/03/2013 at 07:16 AM, John McKown john.archie.mck...@gmail.com said: Being old, I have occasionally turned off LE's abend handling and just gone for the throat using a recent compile (with generated assembler shown) and a SYSUDUMP. SYSMDUMP, TYVM. The programmers have forgotten how to do this entirely. Some things are best forgotten. IPCS isn't perfect, but it's better than highlighters and paper clips, or the electronic equivalent. -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: Question on how to debug S0C7 (data exception) abend
In 01bc01ce7820$59608f30$0c21ad90$@verizon.net, on 07/03/2013 at 03:05 PM, Carl Swanson carl.swans...@verizon.net said: You have the entry point to the abend and you have the entry point of the problem program. In many situations it's easy to get the wrong addresses from the dump if you don't understand how things work. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see http://patriot.net/~shmuel/resume/brief.html We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
