Re: Stopping zOS
After stop sub-system, Z EOD, V XCF,,... ZOS is stoped, no I/O is running, what you need more? 2010/4/21 Elardus Engelbrecht elardus.engelbre...@sita.co.za Vernooij, CP wrote: After stopping all these subsystems, z/OS is still running. ;-) running, running and running while waiting for that magic command: Z EOD Thats one magic system, not subsystem. ;-D and perhaps if needed also that V XCF,... and reply after that. ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On my sandbox lpar, I do 1) $PJES2,ABEND and reply END 2) V GRS(TEST),Q 3) if any other systems in grs... V GRS(TEST),P and reply YES 4) go to HMC, do SYSTEM RESET CLEAR and it is really STOPPED. One would bring a production system down more gracefully, of course, but SYSTEM RESET CLEAR at the end assures that it is really stopped. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
http://bama.ua.edu/cgi-bin/wa?A2=ind0910L=ibm-mainP=R29080I=1X=- Use RESET CLEAR just to be sure On Tue, Apr 20, 2010 at 11:41 PM, R.S. r.skoru...@bremultibank.com.plwrote: McKown, John pisze: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tony Harminc Sent: Tuesday, April 20, 2010 11:39 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Stopping zOS On 20 April 2010 12:35, Mark Zelden mzel...@flash.net wrote: There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. Why? Tony H. The IP connectivity goes into the toliet and all the clients would need to reconnect. QUIESCE is not of any particular use, other than perhaps after a Z EOD to make sure that all I/O is complete. I.e. you'd never want to do a restart after doing a QUIESCE. IMHO the best way to stop I/O and clear or the reservations is to use HMC Reset icon. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl S d Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru S dowego, nr rejestru przedsi biorców KRS 025237 NIP: 526-021-50-88 Wed ug stanu na dzie 01.01.2009 r. kapita zak adowy BRE Banku SA (w ca o ci wp acony) wynosi 118.763.528 z otych. W zwi zku z realizacj warunkowego podwy szenia kapita u zak adowego, na podstawie uchwa y XXI WZ z dnia 16 marca 2008r., oraz uchwa y XVI NWZ z dnia 27 pa dziernika 2008r., mo e ulec podwy szeniu do kwoty 123.763.528 z . Akcje w podwy szonym kapitale zak adowym BRE Banku SA b d w ca o ci op acone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- Guy Gardoit z/OS Systems Programming -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
McKown, John pisze: -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tony Harminc Sent: Tuesday, April 20, 2010 11:39 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Stopping zOS On 20 April 2010 12:35, Mark Zelden mzel...@flash.net wrote: There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. Why? Tony H. The IP connectivity goes into the toliet and all the clients would need to reconnect. QUIESCE is not of any particular use, other than perhaps after a Z EOD to make sure that all I/O is complete. I.e. you'd never want to do a restart after doing a QUIESCE. IMHO the best way to stop I/O and clear or the reservations is to use HMC Reset icon. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2009 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 118.763.528 zotych. W zwizku z realizacj warunkowego podwyszenia kapitau zakadowego, na podstawie uchway XXI WZ z dnia 16 marca 2008r., oraz uchway XVI NWZ z dnia 27 padziernika 2008r., moe ulec podwyszeniu do kwoty 123.763.528 z. Akcje w podwyszonym kapitale zakadowym BRE Banku SA bd w caoci opacone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
carlos roberto visconde wrote: C DFSCMF What is that? #STOP (RACF) Only needed if you're using RACF remote sharing facility. Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
carlos roberto visconde cvisco...@ig.com.br wrote in message news:s2z57e8edb31004201004xaf69a7f7gcb732f8470f05...@mail.gmail.com... Try: $P P RMF P TSO P SDSF Z NET,QUICK F BPXOINIT,SHUTDOWN=FORKINIT F OMVS,STOPPFS=ZFS F OMVS,SHUTDOWN C DFSCMF $PJES2 #STOP (RACF) sds, visconde After stopping all these subsystems, z/OS is still running. ;-) Kees. For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
Vernooij, CP wrote: After stopping all these subsystems, z/OS is still running. ;-) running, running and running while waiting for that magic command: Z EOD Thats one magic system, not subsystem. ;-D and perhaps if needed also that V XCF,... and reply after that. ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
Elardus Engelbrecht elardus.engelbre...@sita.co.za wrote in message news:listserv%201004210425434348.0...@bama.ua.edu... Vernooij, CP wrote: After stopping all these subsystems, z/OS is still running. ;-) running, running and running while waiting for that magic command: Z EOD No, Z EOD closes some logs etc., but z/OS still keeps on running. Thats one magic system, not subsystem. ;-D and perhaps if needed also that V XCF,... and reply after that. Yes, that brings down z/OS, although a System Reset might also still be needed to tell hardware about it. ;-D Groete / Greetings Elardus Engelbrecht -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On 21 April 2010 02:41, R.S. r.skoru...@bremultibank.com.pl wrote: IMHO the best way to stop I/O and clear or the reservations is to use HMC Reset icon. Sure - it stops the I/O and resets the state of just about everything. So does a really big hammer, when swung by a skilled hand. But what happens to a DASD write operation that is in progress at the time of reset? Hint: Data transfer from the channel stops, but the write does not. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
Tony Harminc pisze: On 21 April 2010 02:41, R.S. r.skoru...@thank-you for-the-spam.com.pl wrote: IMHO the best way to stop I/O and clear [errata:] ALL the reservations is to use HMC Reset icon. Sure - it stops the I/O and resets the state of just about everything. So does a really big hammer, when swung by a skilled hand. But what happens to a DASD write operation that is in progress at the time of reset? Hint: Data transfer from the channel stops, but the write does not. So, what's your point? -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2009 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 118.763.528 zotych. W zwizku z realizacj warunkowego podwyszenia kapitau zakadowego, na podstawie uchway XXI WZ z dnia 16 marca 2008r., oraz uchway XVI NWZ z dnia 27 padziernika 2008r., moe ulec podwyszeniu do kwoty 123.763.528 z. Akcje w podwyszonym kapitale zakadowym BRE Banku SA bd w caoci opacone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On 21 April 2010 10:56, R.S. r.skoru...@bremultibank.com.pl wrote: IMHO the best way to stop I/O and clear [errata:] ALL the reservations is to use HMC Reset icon. Sure - it stops the I/O and resets the state of just about everything. So does a really big hammer, when swung by a skilled hand. But what happens to a DASD write operation that is in progress at the time of reset? Hint: Data transfer from the channel stops, but the write does not. So, what's your point? My point is that issuing an I/O reset (which is included in a system reset) while a system may be doing I/O is a very bad idea, because it can lead to data corruption, since the DASD record being written is padded with zeros to replace the missing data from the channel. Ensuring that all CPUs are in the stopped state first will avoid that. (This zero-padding is not part of the S/360/370/390/z I/O architecture, but it is specified behaviour for the various DASD control units supporting every disk from the 2311 up to the 3390. It is possible that some modern DASD subsystem doesn't do it anymore, but why take the chance?) Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On Wed, 21 Apr 2010 10:44:13 -0400, Tony Harminc t...@harminc.net wrote: On 21 April 2010 02:41, R.S. r.skoru...@bremultibank.com.pl wrote: IMHO the best way to stop I/O and clear or the reservations is to use HMC Reset icon. Sure - it stops the I/O and resets the state of just about everything. So does a really big hammer, when swung by a skilled hand. But what happens to a DASD write operation that is in progress at the time of reset? Hint: Data transfer from the channel stops, but the write does not. So what's your point? Are you suggesting that one should use QUIECE as the last thing when you ready to shutdown z/OS running in a local sysplex or a monoplex - then do a reset? Obviously you can't do this for a system in a sysplex. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
Tony Harminc pisze: My point is that issuing an I/O reset (which is included in a system reset) while a system may be doing I/O is a very bad idea, because it can lead to data corruption, since the DASD record being written is padded with zeros to replace the missing data from the channel. Ensuring that all CPUs are in the stopped state first will avoid that. (This zero-padding is not part of the S/360/370/390/z I/O architecture, but it is specified behaviour for the various DASD control units supporting every disk from the 2311 up to the 3390. It is possible that some modern DASD subsystem doesn't do it anymore, but why take the chance?) AFAIK we were talking about last command to complete shudown of the z/OS image. Not replacement for all the commands we issue like DSN1 stop DB2, or Z EOD. Any brute force termination of processes doing I/O would lead to data corruption. It regards any OS and any platform. -- Radoslaw Skorupka Lodz, Poland -- BRE Bank SA ul. Senatorska 18 00-950 Warszawa www.brebank.pl Sd Rejonowy dla m. st. Warszawy XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, nr rejestru przedsibiorców KRS 025237 NIP: 526-021-50-88 Wedug stanu na dzie 01.01.2009 r. kapita zakadowy BRE Banku SA (w caoci wpacony) wynosi 118.763.528 zotych. W zwizku z realizacj warunkowego podwyszenia kapitau zakadowego, na podstawie uchway XXI WZ z dnia 16 marca 2008r., oraz uchway XVI NWZ z dnia 27 padziernika 2008r., moe ulec podwyszeniu do kwoty 123.763.528 z. Akcje w podwyszonym kapitale zakadowym BRE Banku SA bd w caoci opacone. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On 21 April 2010 11:34, R.S. r.skoru...@bremultibank.com.pl wrote: Tony Harminc pisze: My point is that issuing an I/O reset (which is included in a system reset) while a system may be doing I/O is a very bad idea, because it can lead to data corruption, since the DASD record being written is padded with zeros to replace the missing data from the channel. Ensuring that all CPUs are in the stopped state first will avoid that. (This zero-padding is not part of the S/360/370/390/z I/O architecture, but it is specified behaviour for the various DASD control units supporting every disk from the 2311 up to the 3390. It is possible that some modern DASD subsystem doesn't do it anymore, but why take the chance?) AFAIK we were talking about last command to complete shudown of the z/OS image. Not replacement for all the commands we issue like DSN1 stop DB2, or Z EOD. Any brute force termination of processes doing I/O would lead to data corruption. It regards any OS and any platform. Sigh... This needs to be put out of its misery. I'm sorry I brought it up in this context. The kind of corruption you can get from doing an I/O reset during a DASD write is at a lower level than anything you can do with just stopping software running suddenly. There is a qualitative difference between a record not written, and one that is writtten with unexpected zeros. Naturally it's not likely when your system is essentially stopped (and certainly it's not a big problem we see on IBM-MAIN), but it is possible. And if you are actually running but hung for some reason, all the more reason to ensure your CPUs are stopped before the reset. Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Stopping zOS
How do you stop zOS? I stop all the subsystems, then stop JES, and finally Z EOD But then what actually stops zOS? SHUTDOWN in z/VM causes VM to go into a disabled wait. Does anything on zOS do the same thing? -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On 4/20/2010 12:28 PM, Mark Pace wrote: But then what actually stops zOS? SHUTDOWN in z/VM causes VM to go into a disabled wait. Does anything on zOS do the same thing? QUIESCE Gerhard Postpischil Bradford, VT -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On Tue, 20 Apr 2010 12:28:05 -0400, Mark Pace mpac...@gmail.com wrote: How do you stop zOS? I stop all the subsystems, then stop JES, and finally Z EOD But then what actually stops zOS? SHUTDOWN in z/VM causes VM to go into a disabled wait. Does anything on zOS do the same thing? Only in a sysplex of some sort (monoplex, basic, parallel). V XCF,sysname,OFFLINE ... which puts the system in a x'0A2' wait state with reason code 4. The command is invalid in a local sysplex - COUPLExx specifies COUPLE SYSPLEX(LOCAL) Otherwise you have to use the hardware reset function. There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Pace Sent: Tuesday, April 20, 2010 11:28 AM To: IBM-MAIN@bama.ua.edu Subject: Stopping zOS How do you stop zOS? I stop all the subsystems, then stop JES, and finally Z EOD But then what actually stops zOS? SHUTDOWN in z/VM causes VM to go into a disabled wait. Does anything on zOS do the same thing? -- Mark Pace VARY XCF,sysname,OFFLINE This will cause z/OS to tell all other systems in the SYSPLEX that it is shutting down. It then goes into a hard wait. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets(r) 9151 Boulevard 26 * N. Richland Hills * TX 76010 (817) 255-3225 phone * (817)-961-6183 cell john.mck...@healthmarkets.com * www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On 20 April 2010 12:35, Mark Zelden mzel...@flash.net wrote: There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. Why? Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tony Harminc Sent: Tuesday, April 20, 2010 11:39 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Stopping zOS On 20 April 2010 12:35, Mark Zelden mzel...@flash.net wrote: There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. Why? Tony H. The IP connectivity goes into the toliet and all the clients would need to reconnect. QUIESCE is not of any particular use, other than perhaps after a Z EOD to make sure that all I/O is complete. I.e. you'd never want to do a restart after doing a QUIESCE. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 . N. Richland Hills . TX 76010 (817) 255-3225 phone . (817)-961-6183 cell john.mck...@healthmarkets.com . www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets® is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
Try: $P P RMF P TSO P SDSF Z NET,QUICK F BPXOINIT,SHUTDOWN=FORKINIT F OMVS,STOPPFS=ZFS F OMVS,SHUTDOWN C DFSCMF $PJES2 #STOP (RACF) sds, visconde 2010/4/20 McKown, John john.mck...@healthmarkets.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tony Harminc Sent: Tuesday, April 20, 2010 11:39 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Stopping zOS On 20 April 2010 12:35, Mark Zelden mzel...@flash.net wrote: There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. Why? Tony H. The IP connectivity goes into the toliet and all the clients would need to reconnect. QUIESCE is not of any particular use, other than perhaps after a Z EOD to make sure that all I/O is complete. I.e. you'd never want to do a restart after doing a QUIESCE. -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarketsŽ 9151 Boulevard 26 . N. Richland Hills . TX 76010 (817) 255-3225 phone . (817)-961-6183 cell john.mck...@healthmarkets.com . www.HealthMarkets.comhttp://www.healthmarkets.com/ Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarketsŽ is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance CompanyŽ, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On Tue, 20 Apr 2010 12:39:22 -0400, Tony Harminc t...@harminc.net wrote: On 20 April 2010 12:35, Mark Zelden mzel...@flash.net wrote: There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. 1) If you still run a FEP (front end processor), it keeps running. It really doesn't like the fact that the host system went away and you didn't tell it. I've seen NCPs crash after this and even VTAM once you restarted the system. I admit I haven't done this in a very long time.. 2) Same issue with TCPIP. Although I suspect connections / links would just timeout and fail. It would look like a crashed system after a short period of time. 3) SYSPLEX / **GRS / MIM or anything else that relies on heart beats from a healthy system. I could name a bunch of other ISV products I know of also, but I won't. ** (this note from the operator commands manual): If this system is actively using global resource serialization to share global resources and the global resource serialization complex is not the same as the sysplex, issue a VARY GRS (*),QUIESCE command before issuing the QUIESCE command. Issuing a VARY GRS (*),QUIESCE command before issuing the QUIESCE command prevents the disruption of the global resource serialization ring. So it's a similar theme for all of these. There is so much connectivity from z/OS to other platforms and systems, you can't really live with a quiesced system and restart it. You might as well shut it down nicely and do a system reset. Mark -- Mark Zelden - Zelden Consulting Services - z/OS, OS/390 and MVS mailto:mzel...@flash.net Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html Systems Programming expert at http://expertanswercenter.techtarget.com/ -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
-Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of McKown, John Sent: Tuesday, April 20, 2010 9:57 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Stopping zOS -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Tony Harminc Sent: Tuesday, April 20, 2010 11:39 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Stopping zOS On 20 April 2010 12:35, Mark Zelden mzel...@flash.net wrote: There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. Why? Tony H. The IP connectivity goes into the toliet and all the clients would need to reconnect. QUIESCE is not of any particular use, other than perhaps after a Z EOD to make sure that all I/O is complete. I.e. you'd never want to do a restart after doing a QUIESCE. In the resource limited days here before the z9-BC I sometimes QUIESCEd the sandbox(s) for provide some marginally more resources to production during the few days of heavy load. Everything (except TCPIP connections) picked up nicely upon restart. Even a 3270 connection could resume if you'd not attempted to use it during the wait time. Once, when I didn't understand what I could do by declaring my z/OS TCPIP stack a router (and before the network folks configured just who they'd let be a router), I configured my sandbox as such by mistake. JUST BEFORE LEAVING FOR THE DAY. A couple hours later, ops called and said my sandbox was the reason the network was down. I told them to QUIESCE the sandbox. The network healed almost instantly. That wasn't the most pleasant post-mortem I've ever been part of :) But, yes, as an normal thing, there's very little point in QUIESCE or fully shutting down a monoplex LPAR these days. Dave Gibney Information Technology Services Washington State University -- John McKown Systems Engineer IV IT Administrative Services Group HealthMarkets® 9151 Boulevard 26 . N. Richland Hills . TX 76010 (817) 255-3225 phone . (817)-961-6183 cell john.mck...@healthmarkets.com . www.HealthMarkets.com Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets® is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company®, Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Stopping zOS
On 20 April 2010 12:39, Tony Harminc t...@harminc.net wrote: On 20 April 2010 12:35, Mark Zelden mzel...@flash.net wrote: There is also a QUIESCE command, which puts the system in a x'CCC' wait state that is restartable. You wouldn't want to normally do that these days. Why? I didn't phrase my question clearly; I wasn't asking about the wisdom of trying to restart, but about why the QUIESCE itself would be a bad idea. The original reason for QUIESCE, IIRC, is that it ensured that all CPUs in an MP would be stopped, whereas the old hit STOP would stop only the one whose STOP button you pressed. And in turn, the reason for hitting STOP before re-IPLing is to avoid that improbable but very nasty possibility of doing an I/O reset while a DASD write was in progress (for your JES checkpoint, say). Tony H. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
