Abend0B0 is rarely a z/OS defect, more likely an error in the program requesting a SWA service. It can even be due to a JCL error (e.g. if you specify SUB=MSTR and the datasets are in the wrong catalog it will abend0B0). Check the reason code in register 15 which will give a fairly precise cause. The dump would show the calling component, which would either confirm it is Zara or Db2 or find some other module :) Generally an easy problem to diagnose but you may need to get a SLIP dump.
On Tue, Dec 17, 2019 at 7:07 AM Tom Conley <pinnc...@rochester.rr.com> wrote: > On 12/16/2019 10:54 AM, Brown, Duncan wrote: > > I don't have any support for my z/OS 2.1 system. Yea, I know... > > > > We have an issue with DB2 v12 Image copies abending with a ABEND0B0 and > I want to be able to search 'something' to figure out if it's a z/OS > issue. I do have an issue open with IBM for DB2 and with ASG for Zara. > Both are saying that the problem is with each other's software. So, if > it's not Zara or DB2 then I'm guessing it might be z/OS. > > It there a way for me to search through fixes? I know that this is a > long shot, but we won't be up on a supported version of z/OS for a few > months. > > IBMLink is the search engine for fixes. You can also try Dr. Google. > Since you're not supported for z/OS V2R1, you should do a RECEIVE ORDER > ALL to get all the maintenance possible for V2R1. > > Regards, > Tom Conley > > ---------------------------------------------------------------------- > 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
