Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
On Mon, 7 Jan 2008 12:08:27 -0500, Alan Altmark <[EMAIL PROTECTED]> wrote: >On Monday, 01/07/2008 at 11:26 EST, "Schuh, Richard" <[EMAIL PROTECTED]> >wrote: >> That was a nice change. When did it first appear? > >VM/ESA Version 1 Release 2. It was the result of FIN APAR VM57616 >(against VM/ESA V1R1), which described a problem with MDC and minidisks >that overlay system areas. Abends were the result. The documentation f or >MDC says "don't do that", but it would thought some people might miss th at >fine print and in the interest of family harmony, we added code. > >A look at that code reveals that any minidisk that starts on cyl 0 (even >if it isn't fp mini) is *exempt* from this check. So be very careful if >you have partial overlays. Ensure MDC is OFF for that minidisk. > >Alan Altmark >z/VM Development >IBM Endicott Nice to know! Is there another system in the shop with access to the same packs? Otherwise, it is probably a misformatted paging pack. (But is that the right error message?) Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com
Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
On Monday, 01/07/2008 at 11:26 EST, "Schuh, Richard" <[EMAIL PROTECTED]> wrote: > That was a nice change. When did it first appear? VM/ESA Version 1 Release 2. It was the result of FIN APAR VM57616 (against VM/ESA V1R1), which described a problem with MDC and minidisks that overlay system areas. Abends were the result. The documentation for MDC says "don't do that", but it would thought some people might miss that fine print and in the interest of family harmony, we added code. A look at that code reveals that any minidisk that starts on cyl 0 (even if it isn't fp mini) is *exempt* from this check. So be very careful if you have partial overlays. Ensure MDC is OFF for that minidisk. Alan Altmark z/VM Development IBM Endicott
Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
Interesting question, Richard! My first reaction was to search the z/VM Migration Guide to determine when this nice feature was first announced. While it may be in there, I can't seem to find it mentioned. Next I snatched up the message that Kris so nicely provided in his post: HCPLNM1152E, and checked the source code for HCPLNM. The source for HCPLNM is from z/VM 4.4, and the 1152E message appears as part of that base release. At least... there is no update code to the right, so it *should* be in the base of z/VM 4.4. Now someone needs to send in an RCF for the z/VM Migration Guide, right? Probably the person who asked the question: When did it first appear? ;-) Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Mike Walter z/VM Systems Manager Information Technology Services Hewitt Associates [EMAIL PROTECTED] Direct: +1 (847) 771-9212 Main: +1 (847) 295-5000 http://www.hewitt.com "Schuh, Richard" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" 01/07/2008 10:23 AM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject Re: AW: z/VM 5.2 Absurd System shutdown - PJBR That was a nice change. When did it first appear? Regards, Richard Schuh > -Original Message- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark > Sent: Monday, January 07, 2008 6:14 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: AW: z/VM 5.2 Absurd System shutdown - PJBR > > On Monday, 01/07/2008 at 02:45 EST, Kris Buelens > <[EMAIL PROTECTED]> > wrote: > > I tried them all again: PAGE, SPOL, TDSK is protected > > The only exception would be a full-pack minidisk overlay, but > it's nice to > know CP won't casually place a loaded weapon in your hand. > (I never tried > it before.) > > Alan Altmark > z/VM Development > IBM Endicott > The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email.
Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
That was a nice change. When did it first appear? Regards, Richard Schuh > -Original Message- > From: The IBM z/VM Operating System > [mailto:[EMAIL PROTECTED] On Behalf Of Alan Altmark > Sent: Monday, January 07, 2008 6:14 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: AW: z/VM 5.2 Absurd System shutdown - PJBR > > On Monday, 01/07/2008 at 02:45 EST, Kris Buelens > <[EMAIL PROTECTED]> > wrote: > > I tried them all again: PAGE, SPOL, TDSK is protected > > The only exception would be a full-pack minidisk overlay, but > it's nice to > know CP won't casually place a loaded weapon in your hand. > (I never tried > it before.) > > Alan Altmark > z/VM Development > IBM Endicott >
Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
On Monday, 01/07/2008 at 02:45 EST, Kris Buelens <[EMAIL PROTECTED]> wrote: > I tried them all again: PAGE, SPOL, TDSK is protected The only exception would be a full-pack minidisk overlay, but it's nice to know CP won't casually place a loaded weapon in your hand. (I never tried it before.) Alan Altmark z/VM Development IBM Endicott
Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
I tried them all again: PAGE, SPOL, TDSK is protected: Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:08 link * 1 1 MR cse Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:13 link * 2 2 MR DRCT Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:18 link * 3 3 MR PAGE HCPLNM1152E KRIS 0003 has not been linked because it would overlap system paging space. Ready KRIS at VMKBCT01 (01152); T=0.01/0.01 08:33:22 link * 4 4 MR Spool HCPLNM1152E KRIS 0004 has not been linked because it would overlap system spool space. Ready KRIS at VMKBCT01 (01152); T=0.01/0.01 08:33:27 link * 5 5 MR ckpt Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:31 link * 6 6 MR Warm Ready KRIS at VMKBCT01 ; T=0.01/0.01 08:33:35 link * 7 7 MR Tdsk HCPLNM1152E KRIS 0007 has not been linked because it would overlap system temporary disk space. Ready KRIS at VMKBCT01 (01152); T=0.01/0.01 08:33:38 So the problem is probably caused by that the page area was never properly formatted. 2008/1/7, Alan Ackerman <[EMAIL PROTECTED]>: > On Fri, 4 Jan 2008 14:09:05 +0100, Fritz, Wilhelm <[EMAIL PROTECTED]> wr > ote: > > Sounds like you have some other minidisk defined overlaying your page spa > ce. When one of your > virtual machines writes to it, it causes paging errors. > > Take a look at your directory. You should have NO other minidisks defined > in the range 0-3338 > on device 520PG1 02D5. (Or overlaying the other page pack, either.) > > Alan Ackerman > Alan (dot) Ackerman (at) Bank of America (dot) com > -- Kris Buelens, IBM Belgium, VM customer support
Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
On Fri, 4 Jan 2008 14:09:05 +0100, Fritz, Wilhelm <[EMAIL PROTECTED]> wr ote: Sounds like you have some other minidisk defined overlaying your page spa ce. When one of your virtual machines writes to it, it causes paging errors. Take a look at your directory. You should have NO other minidisks defined in the range 0-3338 on device 520PG1 02D5. (Or overlaying the other page pack, either.) Alan Ackerman Alan (dot) Ackerman (at) Bank of America (dot) com >-Ursprüngliche Nachricht- >Von: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] >Auftrag von Jose Raul Baron >Gesendet: Freitag, 4. Januar 2008 13:27 >An: IBMVM@LISTSERV.UARK.EDU >Betreff: z/VM 5.2 Absurd System shutdown - PJBR > > >Hi, list. We are experiencing some problems with unpredictable and so fa r >inevitable system shutdowns for aparently unknown reasons. > >- We are running 4 SLES9 Linux images under z/VM 5.2 >- If we keep only 3 images, this problem doesn't seem to appear. It has >happened only with 4 images running at once. >- OPERATOR 191 console registers suddenly (but it can be like this for >HOURS) the following message: > >xx:yy:zz HCPPAW415E Six continuous paging errors have occurred o n >DASD 02D5 volume 520PG1. >(this message appears some 25-30 times per second) > >- Disk 2D5 has been hardware-checked successfully, so it has no hardware >errors. >- Latest RSU has been applied by IBM-advise. This is our level: > > q cplevel > z/VM Version 5 Release 2.0, service level 0702 (64-bit) > Generated at 12/21/07 19:33:42 MAI > IPL at 01/04/08 11:46:43 MAI > > Ready; > q cmslevel > CMS Level 22, Service Level 702 > Ready; > >- These were some system indicators at the time of the latest shutdown: > >PROCESSOR >= > >AVGPROC-009% 01 >MDC READS-00/SEC WRITES-00/SEC HIT RATIO-000% >PAGING-2/SEC STEAL-000% >Q0-1(0) DORMANT-00018 >Q1-0(0) E1-0(0) >Q2-0(0) EXPAN-001 E2-0(0) >Q3-4(0) EXPAN-001 E3-0(0) >PROC -009% >LIMITED-0 > >PAGE AREAS >== >EXTENT EXTENT TOTAL PAGES HIGH% >VOLID RDEV STARTEND PAGES IN USE PAGE USED >-- -- -- -- -- -- >520PAG 033F 1 3338 600840 30602 31676 5% >520PG1 02D5 0 3338 601020 11660 11835 1% > -- -- >SUMMARY1174K 42262 3% >USABLE 1174K 42262 3% > >SPOOL AREA >== >EXTENT EXTENT TOTAL PAGES HIGH% >VOLID RDEV STARTEND PAGES IN USE PAGE USED >-- -- -- -- -- -- >520SPL 0315 1 3338 600840 118407 160305 19% > -- -- >SUMMARY 600840 118407 19% >USABLE600840 118407 19% >* * * End of File * * * > >- So it shows neither PAGE nor SPOOL bottleneck. CPU values are also >acceptably low. >- We have 8 GB total RAM in this LPAR. >- Our Linux RAM definitions are: > >USER LINUX1 LINUX1 3G3G BG >USER LINUX2 LINUX2 2560M 2560M BG >USER LINUX3 LINUX3 2560M 2560M BG >USER LINUX4 LINUX4 256M 256M BG > >- Aparently no great usage of system resources was being done at the tim e of >shutdown (see above). > >Any help will be extremely welcome !! > >Saludos, Best Regards, >José R. Barón >Dpto. Sistemas >CALCULO S. A. >Tel. 91 330 86 44 >e-mail: [EMAIL PROTECTED] >Do not print this e-mail unless necessary > = == =
Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
On Jan 4, 2008 4:24 PM, Aria Bamdad <[EMAIL PROTECTED]> wrote: > Cylinder zero is ok for other CP areas but NOT for TDISK. Don't > define a TDSK area on cylinder zero. Certainly not (had not even thought about that one). And I would be very reluctant for parm disks, and not checkpoint and warmstart either. And XLINK by default also uses part of the first tracks (though you should not need XLINK on spool or page packs, I think). And don't give a general user a disk starting on cylinder 0 either unless you really know what you're doing... Too many ways too hurt yourself, which is why we don't use cylinder 0. But it was not the explanation for the original poster's problem. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
Re: AW: z/VM 5.2 Absurd System shutdown - PJBR
Cylinder zero is ok for other CP areas but NOT for TDISK. Don't define a TDSK area on cylinder zero. Aria. On Fri, 4 Jan 2008 14:29:15 +0100 Fritz, Wilhelm said: >Thanks for the clarification, Rob. >I didn't know that. > >Willy > > >On Jan 4, 2008 2:09 PM, Fritz, Wilhelm <[EMAIL PROTECTED]> wrote: > >> Why does your paging device start on cyl 0?!?: > >> Shouldn't it start on Cyl 1, like 520PAG? > >Does not have to. CP knows enough to stay out of the first track(s) >but I think most folks do keep the first cylinder out. >In his case, those might be the only tracks where CP could page on that = >disk :-) > >Rob >
AW: z/VM 5.2 Absurd System shutdown - PJBR
Thanks for the clarification, Rob. I didn't know that. Willy -Ursprüngliche Nachricht- Von: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Auftrag von Rob van der Heij Gesendet: Freitag, 4. Januar 2008 14:17 An: IBMVM@LISTSERV.UARK.EDU Betreff: Re: z/VM 5.2 Absurd System shutdown - PJBR On Jan 4, 2008 2:09 PM, Fritz, Wilhelm <[EMAIL PROTECTED]> wrote: > Why does your paging device start on cyl 0?!?: > Shouldn't it start on Cyl 1, like 520PAG? Does not have to. CP knows enough to stay out of the first track(s) but I think most folks do keep the first cylinder out. In his case, those might be the only tracks where CP could page on that disk :-) Rob
AW: z/VM 5.2 Absurd System shutdown - PJBR
Why does your paging device start on cyl 0?!?: -- PAGE AREAS == EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- 520PAG 033F 1 3338 600840 30602 31676 5% 520PG1 02D5 0 3338 601020 11660 11835 1% -- Shouldn't it start on Cyl 1, like 520PAG? Regards, Willy Fritz -Ursprüngliche Nachricht- Von: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] Auftrag von Jose Raul Baron Gesendet: Freitag, 4. Januar 2008 13:27 An: IBMVM@LISTSERV.UARK.EDU Betreff: z/VM 5.2 Absurd System shutdown - PJBR Hi, list. We are experiencing some problems with unpredictable and so far inevitable system shutdowns for aparently unknown reasons. - We are running 4 SLES9 Linux images under z/VM 5.2 - If we keep only 3 images, this problem doesn't seem to appear. It has happened only with 4 images running at once. - OPERATOR 191 console registers suddenly (but it can be like this for HOURS) the following message: xx:yy:zz HCPPAW415E Six continuous paging errors have occurred on DASD 02D5 volume 520PG1. (this message appears some 25-30 times per second) - Disk 2D5 has been hardware-checked successfully, so it has no hardware errors. - Latest RSU has been applied by IBM-advise. This is our level: q cplevel z/VM Version 5 Release 2.0, service level 0702 (64-bit) Generated at 12/21/07 19:33:42 MAI IPL at 01/04/08 11:46:43 MAI Ready; q cmslevel CMS Level 22, Service Level 702 Ready; - These were some system indicators at the time of the latest shutdown: PROCESSOR = AVGPROC-009% 01 MDC READS-00/SEC WRITES-00/SEC HIT RATIO-000% PAGING-2/SEC STEAL-000% Q0-1(0) DORMANT-00018 Q1-0(0) E1-0(0) Q2-0(0) EXPAN-001 E2-0(0) Q3-4(0) EXPAN-001 E3-0(0) PROC -009% LIMITED-0 PAGE AREAS == EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- 520PAG 033F 1 3338 600840 30602 31676 5% 520PG1 02D5 0 3338 601020 11660 11835 1% -- -- SUMMARY1174K 42262 3% USABLE 1174K 42262 3% SPOOL AREA == EXTENT EXTENT TOTAL PAGES HIGH% VOLID RDEV STARTEND PAGES IN USE PAGE USED -- -- -- -- -- -- 520SPL 0315 1 3338 600840 118407 160305 19% -- -- SUMMARY 600840 118407 19% USABLE600840 118407 19% * * * End of File * * * - So it shows neither PAGE nor SPOOL bottleneck. CPU values are also acceptably low. - We have 8 GB total RAM in this LPAR. - Our Linux RAM definitions are: USER LINUX1 LINUX1 3G3G BG USER LINUX2 LINUX2 2560M 2560M BG USER LINUX3 LINUX3 2560M 2560M BG USER LINUX4 LINUX4 256M 256M BG - Aparently no great usage of system resources was being done at the time of shutdown (see above). Any help will be extremely welcome !! Saludos, Best Regards, José R. Barón Dpto. Sistemas CALCULO S. A. Tel. 91 330 86 44 e-mail: [EMAIL PROTECTED] Do not print this e-mail unless necessary
