Re: IPCS error help
>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? Surely the necessary thing is to install the APAR (into the 2.1 miglib) and then use that updated MIGLIB (whether copied or not). It wouldn't surprise me if the release upon which you run the "install" does not need to be the target release, provided that you have identified the libraries that need updating (such that you could run it on 2.2). But I don't know for sure. Peter Relson rel...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
> > 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? You need to install PTF UA90783 (for APAR OA43495) on a z/OS 2.1 system, and then use that MIGLIB (or a copy of it) when processing dumps from z/OS 2.1 systems. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
[Yes, I realize I'm replying to an old posting] On 11 February 2015 at 09:28, Nick Jones 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
This solution is assuming that Jake is on the z13 ESP and has part of OA43495 ++APARs or PTFs applied. If this is not the case then, please open a PMR and we'll investigate the problem. Nick Jones z/OS Service Aids On Wed, 11 Feb 2015 08:28:23 -0600, Nick Jones wrote: >Hi All, > >By IPCS 2.2, i believe he means option 2.2 from the main panel which points to >IP STATUS. > > >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 > >-- >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
Re: IPCS error help
Jake, Please provide the following information. 1) When you initiate IPCS for this dump it will produce messages that indicate what level of IPCS, Post these messages completely. All of them BLS18223I Dump written by product-name sourceis an example of the message. 2) What is the size of the Dump Dataset you are trying to use? Cylinders/MB sizes. 3) Have you tried running each command found in 2.2 manually as suggested? If so, what were the results. It looks like it is doing ANALYZE STATUS SYSTEM STATUS FAILDATA STATUS CPU REGS You could try those one at a time to see which one fails. Lizette > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Elardus Engelbrecht > Sent: Wednesday, February 11, 2015 7:16 AM > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: IPCS error help > > Jake anderson wrote: > > >I am using the correct version of IPCS to view the dump. > > You still did not answered Peter Relson's question about the version. > > Please show the exact BLS18223I (or BLS18224I) message. > > Groete / Greetings > Elardus Engelbrecht > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
Hi All, By IPCS 2.2, i believe he means option 2.2 from the main panel which points to IP STATUS. 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 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
Jake anderson wrote: >I am using the correct version of IPCS to view the dump. You still did not answered Peter Relson's question about the version. Please show the exact BLS18223I (or BLS18224I) message. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
Hi Peter I tried with the same tso region size you have used. I am using the correct version of IPCS to view the dump. On 11 Feb 2015 18:18, "Peter Relson" wrote: > >I tried with tso region size 20 but no luck. > > What do you mean "no luck"? It still abended? Then try something bigger > than that. And if your site doesn't allow that, then talk to your site > people. > FWIW, my TSO logon panel shows size 2096128. > > >This happens specifically for IPCS 2.2 > > What is IPCS 2.2? > > I trust that you are using the proper IPCS to match the release of the > system that took the dump. If not, all bets are off. > > Peter Relson > z/OS Core Technology Design > > -- > 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
Re: IPCS error help
>I tried with tso region size 20 but no luck. What do you mean "no luck"? It still abended? Then try something bigger than that. And if your site doesn't allow that, then talk to your site people. FWIW, my TSO logon panel shows size 2096128. >This happens specifically for IPCS 2.2 What is IPCS 2.2? I trust that you are using the proper IPCS to match the release of the system that took the dump. If not, all bets are off. Peter Relson z/OS Core Technology Design -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
Jim Mulder wrote: > IPCS's ESTAE apparently chooses to format the reason code (x'10') as a > decimal number (16). That would not be my choice. Understood. That is the product developers choices. > I have to admit that I cheated, and found it documented in the comments in > module IGVVSERR (which is still not OCO, but >nonetheless it is probably pretty hard to access a listing unless you are an >ISV with access to VPL through IBM in Dallas). Ok. Thanks very much and thanks for showing the list. I hope you wont get in any trouble for publishing that list. Much appreciated! :-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
> Jim Mulder wrote: > > >> System ABEND 878, reason code 0010 > >> GPR 8R 9R 7FFF4000 10R 11R 7F809970 > >> System abend code 878, reason code 0016. > > Why two different reason codes (0010 and 0016)? IPCS's ESTAE apparently chooses to format the reason code (x'10') as a decimal number (16). That would not be my choice. > > Register 9 contains the size of the request (x'7FFF4000'), which > is too large to be satisfied, regardless of your region size. > > Thanks, this is great news for me! But where is it documented about > Register 9? Of course before posting, I grabbed my bookies, searched > for 878 and GETMAIN + STORAGE macros, but found references to GPR00 > and GPR15 only. I have to admit that I cheated, and found it documented in the comments in module IGVVSERR (which is still not OCO, but nonetheless it is probably pretty hard to access a listing unless you are an ISV with access to VPL through IBM in Dallas). EXIT-REGISTERS = Register 0 - Irrelevant Register 1 - Abend Code Register 2 - Register 2 of the GETMAIN/FREEMAIN caller Register 3 - Register 15 of the STORAGE OR SVC 120 entry of GETMAIN/FREEMAIN, otherwise register 3 of the GETMAIN/FREEMAIN caller Registers 4 - Registers 4 of the GETMAIN/FREEMAIN caller or AR0 of the STORAGE caller Registers 5-8 - Registers 5-8 of the GETMAIN/FREEMAIN caller Register 9 - Register 0 of the GETMAIN/FREEMAIN/STORAGE caller Register 10 - Register 1 of the GETMAIN/FREEMAIN/STORAGE caller Registers 11-13 - Registers 11-13 of the GETMAIN/FREEMAIN caller Register 14 - The return address of the caller of GETMAIN/FREEMAIN/STORAGE Register 15 - Abend reason code AR 3 - AR 15 of the STORAGE caller (bdry info) AR 10 - AR 1 of the STORAGE caller (alet) Keep in mind that since that is not documented in a book, it is should not be considered to be an interface, and is subject to change at the discretion of the VSM owners. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
On Tue, 10 Feb 2015 20:37:17 +0530, Jake anderson wrote: >I tried with tso region size 20 but no luck. This happens specifically >for IPCS 2.2 The only time I've had 878's on a region like that was SADumps. But like Jim, I tend not to use the 2.x commands. Big dumps in an interactive TSO session run slo - especially things like RSMDATA. I tend to bump them off to a batch job, and let them run as they will. Shane ... -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
Jim Mulder wrote: >> System ABEND 878, reason code 0010 >> GPR 8R 9R 7FFF4000 10R 11R 7F809970 >> System abend code 878, reason code 0016. Why two different reason codes (0010 and 0016)? > Register 9 contains the size of the request (x'7FFF4000'), which is too > large to be satisfied, regardless of your region size. Thanks, this is great news for me! But where is it documented about Register 9? Of course before posting, I grabbed my bookies, searched for 878 and GETMAIN + STORAGE macros, but found references to GPR00 and GPR15 only. Thanks in advance. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
> I was trying to open a dump dataset using IPCS 2.2 but it ended with below > message. > > System ABEND 878, reason code 0010 > PSW 070C1000 814F7878, module IEANUC01, CSECT IGVVSERR, offset 0E40 > Instruction area 00181610 0A0D18CE 18FB180C > GPR 0R 8400 1R 84878000 2R 7F809C10 3R 0002 > GPR 4R 007F8E78 5R 007933D0 6R 814F2830 7R 00FC5700 > GPR 8R 9R 7FFF4000 10R 11R 7F809970 > GPR 12R 4000 13R 000A0348 14R 3A9D53AC 15R 0010 > System abend code 878, reason code 0016. > Abend in host command SELECT or address environment routine ISPEXEC. > > I was able to open another DUMPS but it just ends only for a specific > dataset. Register 9 contains the size of the request (x'7FFF4000'), which is too large to be satisfied, regardless of your region size. That is likely due to a programming error in IPCS-related code, or something anomalous in the dump. A dump of the 878 abend would be needed for further diagnosis. I don't normally use the IPCS 2.x panels (I issue the IPCS command I want directly). I tried 2.2, and it looks like it is doing ANALYZE STATUS SYSTEM STATUS FAILDATA STATUS CPU REGS You could try those one at a time to see which one fails. Most likely it is ANALYZE - that entails some complex processing which is dependent on a lot of dump data. Jim Mulder z/OS System Test IBM Corp. Poughkeepsie, NY -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Re: IPCS error help
Hi John I tried with tso region size 20 but no luck. This happens specifically for IPCS 2.2 Jake On 10 Feb 2015 20:32, "John Eells" wrote: > Did you try to log off and log on again with more REGION? > > justmainfra...@gmail.com (Jake anderson) wrote: > >> Hi List, >> >> I was trying to open a dump dataset using IPCS 2.2 but it ended with below >> message. >> >> System ABEND 878, reason code 0010 >> PSW 070C1000 814F7878, module IEANUC01, CSECT IGVVSERR, offset 0E40 >> Instruction area 00181610 0A0D18CE 18FB180C >> GPR 0R 8400 1R 84878000 2R 7F809C10 3R 0002 >> GPR 4R 007F8E78 5R 007933D0 6R 814F2830 7R 00FC5700 >> GPR 8R 9R 7FFF4000 10R 11R 7F809970 >> GPR 12R 4000 13R 000A0348 14R 3A9D53AC 15R 0010 >> System abend code 878, reason code 0016. >> Abend in host command SELECT or address environment routine ISPEXEC. >> >> I was able to open another DUMPS but it just ends only for a specific >> dataset. >> >> z/OS : 2.1 >> > > -- > John Eells > z/OS Technical Marketing > IBM Poughkeepsie > ee...@us.ibm.com > > -- > 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
Re: IPCS error help
Did you try to log off and log on again with more REGION? justmainfra...@gmail.com (Jake anderson) wrote: Hi List, I was trying to open a dump dataset using IPCS 2.2 but it ended with below message. System ABEND 878, reason code 0010 PSW 070C1000 814F7878, module IEANUC01, CSECT IGVVSERR, offset 0E40 Instruction area 00181610 0A0D18CE 18FB180C GPR 0R 8400 1R 84878000 2R 7F809C10 3R 0002 GPR 4R 007F8E78 5R 007933D0 6R 814F2830 7R 00FC5700 GPR 8R 9R 7FFF4000 10R 11R 7F809970 GPR 12R 4000 13R 000A0348 14R 3A9D53AC 15R 0010 System abend code 878, reason code 0016. Abend in host command SELECT or address environment routine ISPEXEC. I was able to open another DUMPS but it just ends only for a specific dataset. z/OS : 2.1 -- John Eells z/OS Technical Marketing IBM Poughkeepsie ee...@us.ibm.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
IPCS error help
Hi List, I was trying to open a dump dataset using IPCS 2.2 but it ended with below message. System ABEND 878, reason code 0010 PSW 070C1000 814F7878, module IEANUC01, CSECT IGVVSERR, offset 0E40 Instruction area 00181610 0A0D18CE 18FB180C GPR 0R 8400 1R 84878000 2R 7F809C10 3R 0002 GPR 4R 007F8E78 5R 007933D0 6R 814F2830 7R 00FC5700 GPR 8R 9R 7FFF4000 10R 11R 7F809970 GPR 12R 4000 13R 000A0348 14R 3A9D53AC 15R 0010 System abend code 878, reason code 0016. Abend in host command SELECT or address environment routine ISPEXEC. I was able to open another DUMPS but it just ends only for a specific dataset. z/OS : 2.1 Jake -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
