[Yes, I realize I'm replying to an old posting] On 11 February 2015 at 09:28, Nick Jones <[email protected]> wrote:
> We saw this internally recently-- > I believe this specific 878-10 is due to the installation of a ++APAR for > OA43495 which I think is for new hardware toleration. Either some versions > of the ++APAR don't have part IOSVFMTC included which has updates to IOS > formatters that are called as part of IP STATUS, or IOSVFMTC wasn't applied > to the miglib that IPCS brings up. > > see canceled apar OA45781: ABEND878-10 on IPCS ANALYZE or IPCS IOSK, due to > zero ULUT pointer in an analyzed dump > > This should be corrected by making sure your miglib has the updated IOSVFMTC > in it, or making sure you are on the latest ++APAR build. > -- > Nick Jones > z/OS Service Aids I've bumped into this a couple of times recently. I'd like to fix it, but it's not obvious to me what needs to be done. We look at dumps from all sorts of z/OS levels, so on our main Support image (currently running z/OS 2.2) we have a list of MIGLIBs and a little bit of REXX to present a menu and set IPCS up for the appropriate dump. Just now I'm looking at a customer dump from z/OS 2.1, and getting the bogus GETMAIN for X'7FFF4000' bytes. Do I understand correctly that the problem lies in the 2.1 MIGLIB I'm using on this z/OS 2.2 system? If so, how can I get a suitable 2.1 MIGLIB to copy to this image - in other words how can I ensure that the fix is applied? Do I need to make sure OA43495 (or its 2.1 PTF) is applied on a 2.1 system, and only then recopy MIGLIB? Or is there a way I can apply the maintenance directly to the 2.1 MIGLIB on the 2.2 system? Clearly the copy used just for IPCS doesn't need to be formally maintained, though it would doubtless be a good idea. Or... Have I misunderstood: Is the problem not with the 2.1 MIGLIB at all? Is there perhaps maintenance needed to z/OS 2.2 IPCS itself? Also FWIW, APAR OA45781 is not known to any IBM service I have access to. Thanks for any pointers! Tony H. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
