Re: What we must do before we claim the zlinux server is in production stage?
Pretty good list, Tom, I would add: 1) Reporting for the auditors (racf violations, etc) 2) Get EREP running and be able to produce reports in case the CE's need them This includes the collection of erep data, of course. 3) Hopefully you already have a scheduler or vmserve to run nightly tasks. 4) If you have RACF, backup the db and practice restoring it. 5) Hopefully you've set up prop or something similar to catch important messages and act on them. Either clear up the problem or send an email to yourself about it. (Mailit is a useful tool for this) I had dozens of little rexx execs for stuff like this. Purge diskacnt's 191 files older than 90 days, etc. 6) If you have perfkit, make sure you are capturing console messages and doing something with them. Perfkit will check the health of the system based on your specs. But you've gotta be seeing the msgs. Mary Anne On Tue, Jun 2, 2009 at 12:51 PM, Tom Duerbusch duerbus...@stlouiscity.comwrote: A lot of it also depends on local practices. 1. Backupsscheduled..and monitored. 2. Disaster recovery. 3. Someone, other than yourself, trained, on fixing common problems. 4. Usually, the working size is bigger as you have more users. Change the virtual size and monitor the vdisk swap disks. 5. SET SHARE a little higher, but only if you really need to. 6. Perhaps QUICKDSP OFF. Only if q drops have become a problem. 7. Some method for Operations (or others) to make sure the machine is operating properly. 8. Automated startup and shutdown. 9. Be comfortable with restores. 10. Be comfortable with applying maintenance, and backing it out. 11. Documentation (what? did I say that...n) 12. Make a decision if it should be in its own LPAR, without VM. I doubt most of us have that case. 13. Should it be part of a VSWITCH, or have dedicated OSA addresses, perhaps with the port (ethernet) dedicated if it needs the bandwidth. 14. Some sort of IP fail over. 15. Service contracts on your hardware/software. 16. A good performance monitor. (I don't have one, money, but it makes things a lot easier and faster to respond and debug.) Does all of this really, really get done up front? Noop. Eventually, it will, when enough people scream! Tom Duerbusch THD Consulting Dave Jones d...@vsoft-software.com 6/1/2009 6:37 PM Hi, Sunny. Can you explain what you mean by 'more special'? Give it more access to real resources? Insure that it gets dispatched before the test guests? Have a good one. sunny...@wcb.ab.ca wrote: We put the test, develop and production zlinux environment in the same z/VM partition. So what we must do to make the production zLinux more 'special' than others? I understand it is the shared environment. Sunny Hu sunny...@wcb.ab.ca This message is intended only for the addressee. It may contain privileged or confidential information. Any unauthorized disclosure is strictly prohibited. If you have received this message in error, please notify us immediately so that we may correct our internal records. Please then delete the original email. Thank you. (Sent by Webgate2) -- Dave Jones V/Soft www.vsoft-software.com Houston, TX 281.578.7544
VM Shutdown
How we could know that when last VM system shutdown and IPL'd as VM User?. Regards Philip
Re: VM Shutdown
*q cplevel* 08:43:46 z/VM Version 5 Release 4.0, service level 0802 (64-bit) 08:43:46 Generated at 01/19/09 14:51:47 EDT 08:43:46 *IPL at 02/16/09 16:08:28 EDT* Ready; T=0.01/0.01 08:43:46 On Wed, Jun 3, 2009 at 8:33 AM, Philip Hitti philiphi...@googlemail.comwrote: How we could know that when last VM system shutdown and IPL'd as VM User?. Regards Philip -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: VM Shutdown
On Wednesday, 06/03/2009 at 08:40 EDT, Philip Hitti philiphi...@googlemail.com wrote: How we could know that when last VM system shutdown and IPL'd as VM User?. QUERY CPLEVEL will tell you when the system was IPLed. You cannot tell when the system was shut down except by analysis of the security log or operator's console log. (Everyone DOES have ESM auditing active for the SHUTDOWN command, right?) Alan Altmark z/VM Development IBM Endicott
Re: VM Shutdown
QUERY CPLEVEL shows last IPL date. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Philip Hitti Sent: Wednesday, June 03, 2009 8:33 AM To: IBMVM@LISTSERV.UARK.EDU Subject: VM Shutdown How we could know that when last VM system shutdown and IPL'd as VM User?. Regards Philip Confidentiality Note: This e-mail, including any attachment to it, may contain material that is confidential, proprietary, privileged and/or Protected Health Information, within the meaning of the regulations under the Health Insurance Portability Accountability Act as amended. If it is not clear that you are the intended recipient, you are hereby notified that you have received this transmittal in error, and any review, dissemination, distribution or copying of this e-mail, including any attachment to it, is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you.
Re: VM Shutdown
Q CPLOAD is interesting too: Module CPLOAD was loaded from minidisk on volume ZV54RS at cylinder 39. Parm disk number 1 is on volume ZV54RS, cylinders 39 through 158. Last start was a system IPL. it should tell if the last IPL was caused by a CP abend. 2009/6/3 Wakser, David david.wak...@infocrossing.com QUERY CPLEVEL shows last IPL date. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Philip Hitti Sent: Wednesday, June 03, 2009 8:33 AM To: IBMVM@LISTSERV.UARK.EDU Subject: VM Shutdown How we could know that when last VM system shutdown and IPL'd as VM User?. Regards Philip -- Kris Buelens, IBM Belgium, VM customer support
Re: LUMINEX Channel Gateway
Jim, I'm using Luminex at one of my customers for zVM and zVSE work. Under zVM, it's mainly used for HiDRO backups and its worked fine. The only thing I did was to 'initialize' the tapes HiDRO was going to use. That involved writing a quick exec that just wrote a volser on the virtual tape. I use the TAPELOAD module in my own execs for the operators to use. We've been using it for over a year now with good results. Give me a call if you have questions. Ed Neidhardt Mainline Information Systems, Inc. 770-321-0841 Office ed.neidha...@mainline.com - Original Message - From: Jim Bohnsack jab...@cornell.edu To: IBMVM@LISTSERV.UARK.EDU Sent: Monday, June 01, 2009 11:39 AM Subject: LUMINEX Channel Gateway We have just installed a LUMINEX Channel Gateway. It comes with a strange TAPELOAD module that seems to get tapes mounted, but it acts kind of strange. Has anyone in VM land used this thing? Maybe I should say this software because I've been told that LUMINEX makes S/W. Would DFSMSRM or VMBACKUP work with it or am I going to have to cobble up some code to use their TAPELOAD? Jim -- Jim Bohnsack Cornell University (972) 596-6377 home/office (972) 342-5823 cell jab...@cornell.edu
Re: What we must do before we claim the zlinux server is in production stage?
Don't forget we use billard tables for eating tables and que sticks for pot passers ;) Jim Dodds Systems Programmer Kentucky State University 400 East Main Street Frankfort, Ky 40601 502 597 6114 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Tuesday, June 02, 2009 5:19 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: What we must do before we claim the zlinux server is in production stage? Give him some slack. He is from Kentucky where they attempt to saddle and ride most anything that runs. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Martin, Terry R. (CMS/CTR) (CTR) Sent: Tuesday, June 02, 2009 2:05 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: What we must do before we claim the zlinux server is in production stage? If that was to happen with me on the mainframe Wow, and all of this time I thought z/VM ran on the mainframe. Thank You, Terry Martin Lockheed Martin - Information Technology z/OS z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 terry.mar...@cms.hhs.gov -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Dodds, Jim Sent: Tuesday, June 02, 2009 1:30 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: What we must do before we claim the zlinux server is in production stage? Bravo, It is amazing that Opies here think that if you can back it up you can restore. I don't know how many times they have not been able to restore files and their solution is to change backup software. If that was to happen with me on the mainframe side I would be unemployed. I agree with Adam you should test a restore of a sample size of files from your backups in my opinion at least quarterly and whenever the backup parameters change. Jim Dodds Systems Programmer Kentucky State University 400 East Main Street Frankfort, Ky 40601 502 597 6114 -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Adam Thornton Sent: Tuesday, June 02, 2009 1:16 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: What we must do before we claim the zlinux server is in production stage? On Jun 2, 2009, at 11:51 AM, Tom Duerbusch wrote: A lot of it also depends on local practices. 1. Backupsscheduled..and monitored. And RESTORED, whether you need to or not, on some schedule. A good test, I'd say, is to pick ten files at random from the backup catalogue every so often and restore them to a temporary location, and then verify those files. (Assuming you can spare your tape library long enough, because ten random files is a lot of loading/unloading/ seeking.) Seriously: your backup regimen is USELESS if you cannot restore the files you backed up, and when you need them is NOT the time to find out that the tapes haven't been being written correctly. Adam
Re: VM Shutdown
QUERY CPLEVEL Last line of results will show you date and time of last IPL Steve -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Philip Hitti Sent: Wednesday, June 03, 2009 8:33 AM To: IBMVM@LISTSERV.UARK.EDU Subject: VM Shutdown How we could know that when last VM system shutdown and IPL'd as VM User?. Regards Philip
IBM VTS in a VM/VSE environment.
I have been reviewing entries in both lists and it appears that VM and VSE neither have a easy way of move virtual tape volumes from the VTS to and external tape media for offsite storage. I have been told that MVS has a facility (copy extract) to do this. For VSE I guess we could use Ditto tape copy to move virtual tapes to real one would be an option. One would need to write a rexx program to read a tape catalog/tape report and build the job to stack the tapes on one real tape. Is this the only option in VSE. Is there anything in VM. I guess I also find it hard to believe that the VTS itself has no internal/ backend process to do this. I have dual posted this query Thanks for your comments Hans
Re: Clean Linux Guest Shutdown
On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown - r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam
Re: Clean Linux Guest Shutdown
Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Because I also use my exec to shutdown individual Linux guests for various reasons also. On Wed, Jun 3, 2009 at 2:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh -- *From:* The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] *On Behalf Of *Mark Pace *Sent:* Wednesday, June 03, 2009 10:55 AM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netwrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: IBM VTS in a VM/VSE environment.
On 6/3/09 1:13 PM, Tom Duerbusch duerbus...@stlouiscity.com wrote: Once you get a VSE system up (via tape), you have VSE Virtual Tape available. You can use that with the IP flavor (instead of the VSAM flavor) to store VSE Virtual Tapes. Now, you can get a TB USB drive for around $1,500 and they are portable. How about buying 3, (Grandfather, father, son), and copy the offsite data tapes, this way? I'm still concerned about IP performance. The bottleneck will be the USB port speed, not the network. And where are you paying $1500 for a USB drive? Most of the vendors around here are ~$200 for 1TB USB drives. Consider also ESATA drives. They're significantly faster than the USB ones and generally not that much more expensive.
Re: Clean Linux Guest Shutdown
Mike, Per the linux doc for SLES10 it states that the following change be made : In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h Is there something else from a linux standpoint that needs to be done ? Thank you, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Have you updated each Linux guest so that they are registered to receive and respond to the SIGNAL SHUTDOWN service? Check your Linux distribution for the proper means to register for the SIGNAL SHUTDOWN service, and how to respond appropriately. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Robert J McCarthy bob.mccar...@custserv.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/03/2009 12:43 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Clean Linux Guest Shutdown I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob 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. E-mails 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 e-mail.
Re: Clean Linux Guest Shutdown
Have you updated each Linux guest so that they are registered to receive and respond to the SIGNAL SHUTDOWN service? Check your Linux distribution for the proper means to register for the SIGNAL SHUTDOWN service, and how to respond appropriately. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Robert J McCarthy bob.mccar...@custserv.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/03/2009 12:43 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Clean Linux Guest Shutdown I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob 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. E-mails 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 e-mail.
Re: Clean Linux Guest Shutdown
You could use the CP SIGNAL SHUTDOWN command before you actually did the SHUTDOWN. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Adam Thornton Sent: Wednesday, June 03, 2009 10:50 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam
Re: Clean Linux Guest Shutdown
Issue Q SIGNALS, Q SHUTDOWN, Q SIGNAL SHUTDOWNTIME from your VM system and post those here. What does your /etc/zipl.conf look like? Post that too. IIRC, there wasn't anything needed on SLES 10. I for sure didn't change anything in /etc/inittab on SLES 10. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:11 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Clean Linux Guest Shutdown Mike, Per the linux doc for SLES10 it states that the following change be made : In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h Is there something else from a linux standpoint that needs to be done ? Thank you, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Have you updated each Linux guest so that they are registered to receive and respond to the SIGNAL SHUTDOWN service? Check your Linux distribution for the proper means to register for the SIGNAL SHUTDOWN service, and how to respond appropriately. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Robert J McCarthy bob.mccar...@custserv.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/03/2009 12:43 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Clean Linux Guest Shutdown I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob 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. E-mails 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 e-mail.
Re: Clean Linux Guest Shutdown
On 6/3/2009 at 1:43 PM, Robert J McCarthy bob.mccar...@custserv.com wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h This is entirely unnecessary. If you leave the switch as -r it will still work. This makes it possible to have a common /etc/inittab for all architectures and still get the desired results. Mark Post
Re: Clean Linux Guest Shutdown
That assumption is correct, even if you use the ALL parameter. That causes the signal to be sent to all guests that have registered to receive it, but not to those who haven't registered. The actual shutdown is via the SHUTDOWN command which is separate from the SIGNAL command. The command, itself, does not shut the guests down, it tells them to do their own orderly shutdown. That is presumably why they registered to receive the signal. You could test on a single guest without any problems for the others or for the system. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Marcy, Attached are the responses that you requested : q SIGNALS Signalled Timeout UseridSignalSignal Status By Remaining DFNORVAR SHUTDOWN Enabled - - ZORACLE1 SHUTDOWN Enabled - - DFNREPSHUTDOWN Enabled - - NSBDX02 SHUTDOWN Enabled - - NSBDX01 SHUTDOWN Enabled - - TDCPWK01 SHUTDOWN Enabled - - TDCPM01 SHUTDOWN Enabled - - TQRTOR01 SHUTDOWN Enabled - - NDRTWB01 SHUTDOWN Enabled - - IFNETLSHUTDOWN Enabled - - IFNILOG SHUTDOWN Enabled - - IFNINFO SHUTDOWN Enabled - - IFNORSTG SHUTDOWN Enabled - - IFNORSTO SHUTDOWN Enabled - - NPSTOR01 SHUTDOWN Enabled - - TFNPOR01 SHUTDOWN Enabled - - ZORACLE3 SHUTDOWN Enabled - - DFNILOG SHUTDOWN Enabled - - DFNINFO SHUTDOWN Enabled - - ZORACLE5 SHUTDOWN Enabled - - ZORACLE7 SHUTDOWN Enabled - - ZORACLE6 SHUTDOWN Enabled - - ZORACLE4 SHUTDOWN Enabled - - ZORACLE8 SHUTDOWN Enabled - - ZORACLE2 SHUTDOWN Enabled - - DFNWEBSHUTDOWN Enabled - - DFNETLSHUTDOWN Enabled - - DFNORWAR SHUTDOWN Enabled - - DFNORRUL SHUTDOWN Enabled - - DFNORSTG SHUTDOWN Enabled - - ZORACLEA SHUTDOWN Enabled - - ZORACLE9 SHUTDOWN Enabled - - Ready; T=0.01/0.01 14:21:34 Q shutdown System shutdown time: 30 seconds Ready; T=0.01/0.01 14:22:33 q signal shutdowntime System default shutdown signal timeout: 1200 seconds Ready; T=0.01/0.01 14:23:09 The contents of one of the zipl files is as follows: dfnorvar:~ # cat /etc/zipl.conf # Modified by YaST2. Last modification on Tue Mar 10 14:01:45 UTC 2009 [defaultboot] defaultmenu = menu :menu default = 1 prompt = 1 target = /boot/zipl timeout = 10 1 = ipl 2 = Failsafe ###Don't change this comment - YaST2 identifier: Original name: ipl### [ipl] image = /boot/image target = /boot/zipl ramdisk = /boot/initrd,0x100 parameters = root=/dev/dasda1 TERM=dumb ###Don't change this comment - YaST2 identifier: Original name: failsafe### [Failsafe] image = /boot/image-2.6.16.60-0.21-default target = /boot/zipl ramdisk = /boot/initrd-2.6.16.60-0.21-default,0x100 parameters = root=/dev/dasda1 TERM=dumb 3 dfnorvar:~ # Thank you, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Marcy Cortes Sent: Wednesday, June 03, 2009 2:16 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Issue Q SIGNALS, Q SHUTDOWN, Q SIGNAL SHUTDOWNTIME from your VM system and post those here. What does your /etc/zipl.conf look like? Post that too. IIRC, there wasn't anything needed on SLES 10. I for sure didn't change anything in /etc/inittab on SLES 10. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:11 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Clean Linux Guest Shutdown Mike, Per the linux doc for SLES10 it states that the following change be made : In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h Is there something else from a linux standpoint that needs to be done ? Thank you, Bob -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mike Walter Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Have
Re: Clean Linux Guest Shutdown
In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation.
Re: Clean Linux Guest Shutdown
On 6/3/2009 at 2:52 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF This is also unnecessary. It just causes the guest to log itself off, which z/VM doesn't really care about one way or the other. Mark Post
Re: Clean Linux Guest Shutdown
On 6/3/2009 at 2:44 PM, Robert J McCarthy bob.mccar...@custserv.com wrote: -snip- Q shutdown System shutdown time: 30 seconds Ready; T=0.01/0.01 14:22:33 q signal shutdowntime System default shutdown signal timeout: 1200 seconds This raises a question for me. Is the 30 second System shutdown time added to the 1200 second System default shutdown signal timeout to get the amount of time z/VM will wait before doing the shutdown? (I seem to remember reading that somewhere.) In any case, I really just think it's a case of your guests need more than that amount of time to all shut down cleanly. If it's only a few here and there, and they're different each time, I would say you've got things set up correctly, you're just not waiting long enough. Mark Post
Re: Clean Linux Guest Shutdown
Hmm. OK. Bob, you are getting 1-2 minutes and not the 1200? Everything else you have set up looks just like what we have set up and we are getting our whole 1200. Marcy This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Post Sent: Wednesday, June 03, 2009 12:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: [IBMVM] Clean Linux Guest Shutdown On 6/3/2009 at 2:52 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF This is also unnecessary. It just causes the guest to log itself off, which z/VM doesn't really care about one way or the other. Mark Post
Re: Clean Linux Guest Shutdown
Be aware CP SIGNAL ALL tells all the non-linux guests like the Shared File System servers VMSERVS,U,R to shutdown. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That assumption is correct, even if you use the ALL parameter. That causes the signal to be sent to all guests that have registered to receive it, but not to those who haven't registered. The actual shutdown is via the SHUTDOWN command which is separate from the SIGNAL command. The command, itself, does not shut the guests down, it tells them to do their own orderly shutdown. That is presumably why they registered to receive the signal. You could test on a single guest without any problems for the others or for the system. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.
Re: Clean Linux Guest Shutdown
True -- VM doesn't care whether a guest logs off in response to a SIGNAL SHUTDOWN. But VM sysprogs may care. It becomes clear when searching the VM console log that the Linux actually did actually complete graceful shutdown. Staying disconnected doesn't prove anything. (But I think that I'll add a CP QUERY SIGNALS to the end of our SHUTDOWN EXEC). If you're looking at the VM console log to determine if guests are getting shutdown within the allotted time, that saves time searching Linux syslogs to get the same information. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Mark Post mp...@novell.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 06/03/2009 01:59 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Clean Linux Guest Shutdown On 6/3/2009 at 2:52 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF This is also unnecessary. It just causes the guest to log itself off, which z/VM doesn't really care about one way or the other. Mark Post 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. E-mails 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 e-mail.
Re: Clean Linux Guest Shutdown
That might not be a bad thing when you are getting ready to shut the system down. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Romanowski, John (OFT) Sent: Wednesday, June 03, 2009 12:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Be aware CP SIGNAL ALL tells all the non-linux guests like the Shared File System servers VMSERVS,U,R to shutdown. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That assumption is correct, even if you use the ALL parameter. That causes the signal to be sent to all guests that have registered to receive it, but not to those who haven't registered. The actual shutdown is via the SHUTDOWN command which is separate from the SIGNAL command. The command, itself, does not shut the guests down, it tells them to do their own orderly shutdown. That is presumably why they registered to receive the signal. You could test on a single guest without any problems for the others or for the system. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.
Re: Clean Linux Guest Shutdown
Mark Post wrote: On 6/3/2009 at 2:52 PM, Marcy Cortes marcy.d.cor...@wellsfargo.com wrote: In /etc/zipl.conf, change parameters = root=/dev/dasda1 TERM=dumb To parameters = root=/dev/dasda1 TERM=dumb vmpoff=LOGOFF vmhalt=LOGOFF This is also unnecessary. It just causes the guest to log itself off, which z/VM doesn't really care about one way or the other. Mark Post It may be unnecessary, but I like to see them go away when they are finished shutting down. I also prefer my desktop to actually turn off instead of displaying a message saying you can power off now but maybe I am . :) -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: Clean Linux Guest Shutdown
I'm with you Stephen, I like to see them logoff also. Then I'm really sure they are down. On Wed, Jun 3, 2009 at 4:18 PM, Stephen Frazier ste...@doc.state.ok.uswrote: It may be unnecessary, but I like to see them go away when they are finished shutting down. I also prefer my desktop to actually turn off instead of displaying a message saying you can power off now but maybe I am . :) -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317
Re: Clean Linux Guest Shutdown
Dude, you need to run Linux on your desktop ;-) Scott It may be unnecessary, but I like to see them go away when they are finished shutting down. I also prefer my desktop to actually turn off instead of displaying a message saying you can power off now but maybe I am . :) -- Stephen Frazier Information Technology Unit Oklahoma Department of Corrections 3400 Martin Luther King Oklahoma City, Ok, 73111-4298 Tel.: (405) 425-2549 Fax: (405) 425-2554 Pager: (405) 690-1828 email: stevef%doc.state.ok.us
Re: Clean Linux Guest Shutdown
On 6/3/2009 at 4:18 PM, Stephen Frazier ste...@doc.state.ok.us wrote: -snip- It may be unnecessary, but I like to see them go away when they are finished shutting down. I also prefer my desktop to actually turn off instead of displaying a message saying you can power off now but maybe I am . :) All of which has nothing to do with trying to figure out the OP's problem. I didn't say the parms were useless or undesirable, but they are completely unrelated to what he's experiencing. Mark Post
Re: Clean Linux Guest Shutdown
On Wed, Jun 3, 2009 at 8:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. From the peanut - uh performance gallery... If you have a lot of Linux servers, the orderly shutdown may actually take quite some paging resources to complete. When the shutdown is making them all do this at once, it may take much longer than when you pace it a bit. Seen with those who set LDUBUFF wrong. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
Re: Clean Linux Guest Shutdown
That makes sense ... if it doesn't just seem longer (remember, pacing takes time, too - it is just spent waiting idly instead of waiting for the work to be done) and paging during SHUTDOWN is something you really have to worry about. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij Sent: Wednesday, June 03, 2009 2:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown On Wed, Jun 3, 2009 at 8:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. From the peanut - uh performance gallery... If you have a lot of Linux servers, the orderly shutdown may actually take quite some paging resources to complete. When the shutdown is making them all do this at once, it may take much longer than when you pace it a bit. Seen with those who set LDUBUFF wrong. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
Re: Clean Linux Guest Shutdown
That might not be a bad thing when you are getting ready to shut the system down. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Romanowski, John (OFT) Sent: Wednesday, June 03, 2009 12:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Be aware CP SIGNAL ALL tells all the non-linux guests like the Shared File System servers VMSERVS,U,R to shutdown. From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That assumption is correct, even if you use the ALL parameter. That causes the signal to be sent to all guests that have registered to receive it, but not to those who haven't registered. The actual shutdown is via the SHUTDOWN command which is separate from the SIGNAL command. The command, itself, does not shut the guests down, it tells them to do their own orderly shutdown. That is presumably why they registered to receive the signal. You could test on a single guest without any problems for the others or for the system. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Robert J McCarthy Sent: Wednesday, June 03, 2009 11:05 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Richard and Mark, Am I right in assuming that CP SIGNAL will only shutdown the guests and not vm, particularily if I use the table ? I could safely test this routine on one guest without impacting other guests. Thank you, Bob From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 2:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown Why not CP SIGNAL SHUTDOWN ALL instead of the table. Regards, Richard Schuh From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Mark Pace Sent: Wednesday, June 03, 2009 10:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown I have an exec I run that runs through a table and sends the command to each linux. 'CP SIGNAL SHUTDOWN ' linux ' WITHIN 60' On Wed, Jun 3, 2009 at 1:49 PM, Adam Thornton athorn...@sinenomine.netmailto:athorn...@sinenomine.net wrote: On Jun 3, 2009, at 12:43 PM, Robert J McCarthy wrote: I am trying to develop a shutdown procedure to cleanly shutdown my linux guests, prior to shutting down vm. Reading the documentation in the virtualization cookbook for SLES10 and the vm CP COMMANDS manual; I have setup the following : 1. In each linux guest's /etc/inittab; I have changed the shutdown -r to shutdown -h 2. In my autolog1 exec I have placed the following command: CP SET SIGNAL SHUTDOWN 1200 ( To allow the guests 20 minutes to respond) Note: I have also entered the command manually When I issue the shutdown, vm shuts down before most if not all linux guests have responded or completed shutdown; always within a minute or two. As a result I end up with file corruption in some linux guests after vm is re-IPLed and the guests are brought back up. Is there a better way to accomplish a clean linux shutdown. Thank you, Bob Our SYSVINIT drop-in-replacement for a list-of-machines-in-autolog would do the trick. It may be overkill. Adam -- Mark Pace Mainline Information Systems 1700 Summit Lake Drive Tallahassee, FL. 32317 This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.
Re: Clean Linux Guest Shutdown
I have also written a shutdown exec to cleanly shutdown all of my z/Linux guests and log them off once they are logged off a send a message to the console stating this. This works well and I have not had any problems. The one thing I would mention is that we have some large Oracle guests with large (5TB) data bases. To ensure that the Oracle shutdown script has time to complete cleanly I make sure that my time out value is very large at least 30 minutes. Now it normally does not take nearly that long but if you add in the possibility of paging as Rob mentioned you could be pushing the envelope and if the Oracle shutdown scripts do not complete cleanly you run the very real risk of corrupting ASM and believe me that is no fun. I have been there! So if you are running these types of workloads make sure you give the shutdown process plenty of time to complete cleanly. Thank You, Terry Martin Lockheed Martin - Information Technology z/OS z/VM Systems - Performance and Tuning Cell - 443 632-4191 Work - 410 786-0386 terry.mar...@cms.hhs.gov -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Schuh, Richard Sent: Wednesday, June 03, 2009 5:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown That makes sense ... if it doesn't just seem longer (remember, pacing takes time, too - it is just spent waiting idly instead of waiting for the work to be done) and paging during SHUTDOWN is something you really have to worry about. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Rob van der Heij Sent: Wednesday, June 03, 2009 2:21 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Clean Linux Guest Shutdown On Wed, Jun 3, 2009 at 8:00 PM, Schuh, Richard rsc...@visa.com wrote: Why not CP SIGNAL SHUTDOWN ALL instead of the table. From the peanut - uh performance gallery... If you have a lot of Linux servers, the orderly shutdown may actually take quite some paging resources to complete. When the shutdown is making them all do this at once, it may take much longer than when you pace it a bit. Seen with those who set LDUBUFF wrong. Rob -- Rob van der Heij Velocity Software http://www.velocitysoftware.com/
Re: IBM VTS in a VM/VSE environment.
Thank you all for your replies. This list is very creative with solutions to problems. Thanks you all again. Tom. I reviewed the Red Book on the TS7700 and found the EXPORT feature very interesting. It sounds like it is a standalone feature and doesn't require z/OS unless you Need to review this in more detail. Hans -Original Message- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Tom Duerbusch Sent: June 3, 2009 1:13 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IBM VTS in a VM/VSE environment. It can be a problem. Most smaller shops are happy just getting an IBM VTS (or any VTS) and wouldn't consider the extra cost of the full VTS system with offsite capabilities. In the newer VTS systems (TS whatever), there is an option, that is kind of neat. You can export VTS tapes, the physical tape (which is made of multiple virtual tapes) to another VTS unit. There is also a dual tape feature, in which certain virtual tapes, will be put on two physical tapes. Well, for those tapes, create a small pool of physical tapes that are used for these copies. Then export these copies (they are physically ejected from the VTS and can only be used by importing them into another VTS. This is great if your disaster recovery plans also include a newer VTS. But for the rest of us.. Produce physical tapes for offsite, by copying. Hopefully, you are encrypting the tapes to be sent offsite. Well, producing physical copies comes with its own set of problems. Your VTS was defined with a virtual tape volume size of XX GB. When the VTS virtual tape hits this size, and End of Volume signal is generated and an new virtual volume is obtained. Copying these tapes can be expensive. Let's say that the virtual tape volume size is 2 GB. You need at least a 3590 tape (any size) to hold the data. They are relatively cheap, when compare to a TS1120 tape (that has hardware encryption). 1:1 is easy at the disaster recovery site, but expensive to buy and a real pain to produce these tapes. (Operator mounts and tracking all these tapes) I stack the tapes. You can get a lot of virtual tapes on a physical tape. For most, but not all tapes (I'll get to that later) I have another Dynam catalog DSN name, starting with a V (for vault), that is file X on a tape. Then I just do a TDYNCOPY of the tape DSN from the VTS to the physical tape. And I just run along with that process. Note that a DSN that was a multi volume DSN of 2 GB volumes, will be combined by TDYNCOPY to a signal volume. In most cases, this is ok. For some DSNs, you can't combine volumes that way. For example VMBACKUP, senses EOV and puts trailing information at the end of the tape, which includes the volser of the next tape that will be used. It also puts information at the front of each tape, of the volser of the previous tape, and some info on what should be on this tape. Any backup product that, for restores, allow you to bypass the first xx tapes, have something like that encoded. For these tapes, you have to do a physical tape copy (like DITTO), recording the internal VOLSER. Now, do you create physical tapes for each of these? Or do you still stack them, and unstack them if and when a disaster recovery is needed? Do you buy some older 3590 drives so you don't waste your expensive TS1120 tapes? However, recently I've been playing around with another option. External dasd. Once you get a VSE system up (via tape), you have VSE Virtual Tape available. You can use that with the IP flavor (instead of the VSAM flavor) to store VSE Virtual Tapes. Now, you can get a TB USB drive for around $1,500 and they are portable. How about buying 3, (Grandfather, father, son), and copy the offsite data tapes, this way? I'm still concerned about IP performance. Another variant is to use a laptop with the extra hard drive. Use the extra hard drive as your VSE Virtual Tape storage area, and send the extra drive off site. In both cases, encryption is also a transparent option. These options might not work well in the larger shops, but they can afford the hardware for proper duplication. But for us smaller shops.(I'm in the 2 TB size now) (Sorry Hans, I didn't get out of meetings until lunch time, so no 10:30 call today.) Tom Duerbusch THD Consulting Hans Rempel h...@hmrconsultants.com 6/3/2009 9:38 AM I have been reviewing entries in both lists and it appears that VM and VSE neither have a easy way of move virtual tape volumes from the VTS to and external tape media for offsite storage. I have been told that MVS has a facility (copy extract) to do this. For VSE I guess we could use Ditto tape copy to move virtual tapes to real one would be an option. One would need to write a rexx program to read a tape catalog/tape report and build the job to stack the tapes on one real tape. Is this the only option in VSE. Is there anything in VM. I guess I also find it hard to believe that
Gavin Appleton is out of the office.
I will be out of the office starting 04/06/2009 and will not return until 08/06/2009. I will respond to your message when I return.
