No one appeared even to take the step of inquiring what caused the 0C1 or 0C4.
It is very unlikely that extents have anything to do with this, as an extent problem would usually result in some sort of fetch failure, well preceding a module execution problem.. It is possible that reentrancy has something to do with this. I would start by getting a dump of the failure. And seeing if the module that is in storage is actually what you think it is (and possibly compare that to a similar dump (if you can get one) when it works. Then see what caused the abend. If it was just an 0C4 then reentrancy and the key of the program storage seems quite possibly to be involved. The dump should show you in what key the module was placed. PIC 1's are usually pretty easy to see too. Is the instruction address in your module (and was the program storage overlaid)? If running on a z9, the breaking event address might help determining where you branched from. Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- 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
