COBOL abend U4083-3
I know this is likely an application problem. But the programmers are likely going to request help in debugging this error. The manual states that it is most likely a memory overlay problem. But I have no idea how I, with no application knowledge, can determine which COBOL statement in their program is causing the overlay. Is there anything that I can suggest other than using SSRANGE? ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ceea9170/8.0 -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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: COBOL abend U4083-3
Hi As SLIP storage alternation TRAP would do this, or maybe the LE HEAPCHK if the HEAP also currupted . The STACK LE options ? McKown, John wrote: I know this is likely an application problem. But the programmers are likely going to request help in debugging this error. The manual states that it is most likely a memory overlay problem. But I have no idea how I, with no application knowledge, can determine which COBOL statement in their program is causing the overlay. Is there anything that I can suggest other than using SSRANGE? ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ceea9170/8.0 -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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 -- Miklos Szigetvari Development Team ISIS Information Systems Gmbh tel: (+43) 2236 27551 570 Fax: (+43) 2236 21081 E-mail: [EMAIL PROTECTED] Info: [EMAIL PROTECTED] Hotline: +43-2236-27551-111 Visit our Website: http://www.isis-papyrus.com --- This e-mail is only intended for the recipient and not legally binding. Unauthorised use, publication, reproduction or disclosure of the content of this e-mail is not permitted. This email has been checked for known viruses, but ISIS accepts no responsibility for malicious or inappropriate content. --- -- 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: COBOL abend U4083-3
SSRANGE would be a good place to start also get an Assembler Listing of the Program in question so you can pinpoint the instruction and registers for the offending transaction. If this is a CICS transaction also take a look at CEEMSGS and CEEOUT McKown, John [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/01/2008 11:18 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject COBOL abend U4083-3 I know this is likely an application problem. But the programmers are likely going to request help in debugging this error. The manual states that it is most likely a memory overlay problem. But I have no idea how I, with no application knowledge, can determine which COBOL statement in their program is causing the overlay. Is there anything that I can suggest other than using SSRANGE? ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ceea9170/8.0 -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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 *** IMPORTANT NOTE* The opinions expressed in this message and/or any attachments are those of the author and not necessarily those of Brown Brothers Harriman Co., its subsidiaries and affiliates (BBH). There is no guarantee that this message is either private or confidential, and it may have been altered by unauthorized sources without your or our knowledge. Nothing in the message is capable or intended to create any legally binding obligations on either party and it is not intended to provide legal advice. BBH accepts no responsibility for loss or damage from its use, including damage from virus. -- 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: COBOL abend U4083-3
I'm going way back here (it's been a while since I had to debug Cobol), but when they linked the program, did they get any kind map? If so, it's almost like debugging an assembler program except the Cobol compiler provides, or did when I coded in it, a more compartmentalized layout of the statements. How about the LIST or OFFSET options? Were they specified as compiler options? -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of McKown, John Sent: Friday, February 01, 2008 11:18 AM To: IBM-MAIN@BAMA.UA.EDU Subject: COBOL abend U4083-3 I know this is likely an application problem. But the programmers are likely going to request help in debugging this error. The manual states that it is most likely a memory overlay problem. But I have no idea how I, with no application knowledge, can determine which COBOL statement in their program is causing the overlay. Is there anything that I can suggest other than using SSRANGE? ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ceea9170/8.0 -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology The information contained in this e-mail message may be privileged and/or confidential. It is for intended addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, reproduction, distribution or other use of this communication is strictly prohibited and could, in certain circumstances, be a criminal offense. If you have received this e-mail in error, please notify the sender by reply and delete this message without copying or disclosing it. -- 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: COBOL abend U4083-3 - resend with correct Reply-to
McKown, John wrote: I know this is likely an application problem. But the programmers are likely going to request help in debugging this error. The manual states that it is most likely a memory overlay problem. But I have no idea how I, with no application knowledge, can determine which COBOL statement in their program is causing the overlay. Is there anything that I can suggest other than using SSRANGE? ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ceea9170/8.0 Compile with TEST(SYM); this should give you the source statement line in error, as well as a formatted dump of all the datat items, on your CEEDUMP. Alternatively, the CEEDUMP might have an offset into the offending module and that should help you get back to the source statement in error. In more sophisticated bugs regarding storage, you might look at John Monti's excellent SHARE presentations on LE Debugging. -- Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 http://www.trainersfriend.com z/OS Application development made easier * Our classes include + How things work + Programming examples with realistic applications + Starter / skeleton code + Complete working programs + Useful utilities and subroutines + Tips and techniques -- 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: COBOL abend U4083-3
McKown, John wrote: I know this is likely an application problem. But the programmers are likely going to request help in debugging this error. The manual states that it is most likely a memory overlay problem. But I have no idea how I, with no application knowledge, can determine which COBOL statement in their program is causing the overlay. Is there anything that I can suggest other than using SSRANGE? ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ceea9170/8.0 Compile with TEST(SYM); this should give you the source statement line in error, as well as a formatted dump of all the datat items, on your CEEDUMP. Alternatively, the CEEDUMP might have an offset into the offending module and that should help you get back to the source statement in error. In more sophisticated bugs regarding storage, you might look at John Monti's excellent SHARE presentations on LE Debugging. Kind regards, -Steve Comstock The Trainer's Friend, Inc. 303-393-8716 http://www.trainersfriend.com z/OS Application development made easier * Our classes include + How things work + Programming examples with realistic applications + Starter / skeleton code + Complete working programs + Useful utilities and subroutines + Tips and techniques -- 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: COBOL abend U4083-3 - resend with correct Reply-to
The manual says that u4083-3 is due to a save area backwards pointer containing zeros. When applications were first migrated to LE many years ago, some assember subroutines needed to be updated to chain save areas correctly. Check for a new assembler subroutine in the run unit (or one that has never been called before). If you believe there is really an overlay of the save area, and the data pattern is not immediately identifiable to something in the application, the next suspects I would visit are any tables (especially a table is loaded from an input file) and sub-routine CALLs. The BLL cells may be incorrectly used: the CALL USING may not match the ENTER USING. Also, mismatched Linkage Section descriptions can allow for access beyond the expected data area. Similarly, depending on the compiler, the parameter list for one CALL is sometimes used for subsequent CALLs and may contain an addresses for some other data area than the intended one. regards, JVD -- 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
Fw: COBOL abend U4083-3
If the problem is recreatable and you can recompile and rerun, then I agree that using SSRANGE is probably your EASIEST solution (if it is a storage overlay problem). As the manual talks about savearea chains, the other thing that I would suggest looking at is the compiler options versus the linkage-editor (binder) options. Sometimes programmers compile creating AMODE(24) programs and then override with binder AMODE(31) attributes. This can certainly cause problems. Do you have Abend-Aid, DumpMaster or other aids (or use CeeDump)? As much as many systems programmers don't like those, they often DO provide easy solutions to such problems. Paul D'Angelo Paul.D'[EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]... SSRANGE would be a good place to start also get an Assembler Listing of the Program in question so you can pinpoint the instruction and registers for the offending transaction. If this is a CICS transaction also take a look at CEEMSGS and CEEOUT McKown, John [EMAIL PROTECTED] Sent by: IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU 02/01/2008 11:18 AM Please respond to IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU To IBM-MAIN@BAMA.UA.EDU cc Subject COBOL abend U4083-3 I know this is likely an application problem. But the programmers are likely going to request help in debugging this error. The manual states that it is most likely a memory overlay problem. But I have no idea how I, with no application knowledge, can determine which COBOL statement in their program is causing the overlay. Is there anything that I can suggest other than using SSRANGE? ref: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/ceea9170/8.0 -- John McKown Senior Systems Programmer HealthMarkets Keeping the Promise of Affordable Coverage Administrative Services Group Information Technology -- 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
