Paul, and others. Thanks for the hints and pointers. I got dragged into other problems and didn't get a chance to work on this - so it'll sit until next week. The thing that is causing us to scratch our collective heads on this one is the job runs multiple times daily and just restarting it with the same inputs causes it to work correctly. I hadn't thought about the possibility of region size being too small. We upgraded to IDMS 17 about 2 months ago but beyond that have put nothing in on the systems side that would touch this environment. The upgrade to IDMS may have caused a region problem so I did have the programmer put the change in to that.
I'll let y'all know what the resolution is once we figure it out. Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Strauss Sent: Friday, December 03, 2010 11:41 AM To: [email protected] Subject: Re: strange issues with LE abending, looking for pointers as to where to even look.. Hi Rex, LE has been around quite a while and has been very reliable for the last several years. You don't say what changed in the environment since this started happening. Something must have. I've seen your name on this list for many things so I know your an experienced systems programmer. I'll still list what I would do in this situation. You said this was IDMS 17 and LE. Any other 3rd party products in the middle of this? Check for compatibility levels between IDMS 17, LE, COBOL and any other products used in the abending job. Take the easy route and increase the region in the job. Sometimes jobs run out of region and can't put out a message saying that or taking a dump because it would need more region to do that. Track job execution using GTF, Mainview, Omegamon, Strobe or whatever monitoring products you have to narrow down what module is having the problem. Have the programmer trace execution with COBOL commands. And what I usually see as the culprit, check for back level modules in STEPLIB, Link List, and possibly LPA. I've seen applications programmers copy SYS1.SCEERUN to their own library and run with it for years until an operating system upgrade causes their job to abend. Look also for COBOL runtimes from years ago that may be STEPLIBed to. These should be pulled from the LE SYS1.SCEERUN library. Thank You, Paul Strauss Integrated Technology Delivery, Global Services, IBM L0DB z/OS MVS/Program Products/Security 150 Kettletown Rd. Southbury, CT 06488 (203) 272-2758 [email protected] From: "Pommier, Rex R." <[email protected]> To: [email protected] Date: 12/03/2010 11:30 AM Subject: strange issues with LE abending, looking for pointers as to where to even look.. Sent by: IBM Mainframe Discussion List <[email protected]> Hi list, I just got a call from an applications programmer. They're having some strange issues showing up in LE with programs abending with S0C4 and S0C7 abends, but not where they've seen before. For example, yesterday, they received a S0C7 in a job. They reran the job using the same inputs and it ran clean. But the abend didn't give them any indication as to what was happening. Here's the JES log of the abend. +CEE0374C CONDITION=CEE3207S TOKEN=00030C87 59C3C5C5 00000000 649 WHILE RUNNING PROGRAM UNKNOWN AT THE TIME OF INTERRUPT PSW 078D1000 80093EAA GPR 0-3 8708D300 0007F98C C7D14040 00BFF048 GPR 4-7 8007F978 00093EA8 0007F98C 000941B0 GPR 8-B 000942E0 00094B00 0008B068 0006FD28 GPR C-F 0007F828 0007F9CC 00000000 00000000 IEA995I SYMPTOM DUMP OUTPUT 662 SYSTEM COMPLETION CODE=0C7 REASON CODE=00000000 TIME=05.48.39 SEQ=02747 CPU=0000 ASID=0060 PSW AT TIME OF ERROR 070C0000 80D0F35E ILC 6 INTC 07 NO ACTIVE MODULE FOUND NAME=UNKNOWN DATA AT PSW 00D0F358 - F933908C 30044740 C8389180 GR 0: 00000880 1: 000B0780 2: 01DFB680 3: 0708D4B0 4: 00FDD858 5: 00093EA8 6: 0007F98C 7: 0000001B 8: 01F97D80 9: 0708D448 A: 0008B068 B: 01DFAFE8 C: 80D0EE60 D: 084C7E70 E: 0000030B F: 00000000 END OF SYMPTOM DUMP IEF450I USACU011 S0015GSI - ABEND=S0C7 U0000 REASON=00000000 -S0015GSI *S0C7 700 1340 .00 .00 .0 The abend this morning was a S0C4 with the same symptoms. S0C4 "while running program unknown". PSW is 'no active module found". They just restarted the job at the abending step and it ran fine. Environment is z/OS 1.10 and IDMS release 17. Batch COBOL calling IDMS. Any ideas as to where to even start looking? Thanks. Rex The information contained in this e-mail may contain confidential and/or privileged information and is intended for the sole use of the intended recipient. If you are not the intended recipient, you are hereby notified that any unauthorized use, disclosure, distribution or copying of this communication is strictly prohibited. If you received this e-mail in error, please reply to sender and destroy or delete the message and any attachments. Thank you. ---------------------------------------------------------------------- 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
