I think your original problem description " I had a z/OS go into z/VM's ELIGIBLE list. The z/OS stopped completely and the console was unresponsive." and that decreasing its memory from 1G to 512M fixed it are the major clues.
It's possible z/VM memory is overcommitted (normal) but its default SRM values are sending guests into eligible list, especially since you say you're running linux guests. Are you running more linux guests than usual? or increased their memory size? did/are other guests going into eligible list too? If CP INDICATE QUEUES shows an En (like E3) in the 2nd column for one or more userids try CP QUERY SRM (write down response for reviewing ) and do this quick fix CP SET SRM STORBUF 300% 300% 300% -------------------------------------------------------- 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. -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Booher Sent: Thursday, March 20, 2008 3:25 PM To: [email protected] Subject: Re: z/OS on z/VM Eligible List Hello, The z800 runs a mixture of z/OS and zLinux guests. The overall LOAD of the z/VM is something like: AVGPROC-039% 02 XSTORE-000005/SEC MIGRATE-0000/SEC MDC READS-000001/SEC WRITES-000001/SEC HIT RATIO-100% STORAGE-092% PAGING-0000/SEC STEAL-000% Q0-00003(00000) DORMANT-00011 Q1-00003(00000) E1-00000(00000) Q2-00001(00000) EXPAN-002 E2-00000(00000) Q3-00018(00000) EXPAN-002 E3-00000(00000) PROC 0000-039% PROC 0001-040% LIMITED-00000 Ready; T=0.01/0.01 14:09:01 This z/os virutal machine has been acting weird all morning and I had to IPL it at least twice. Over the past couple of days, I'd been ATTaching and DETaching several DASD packs to this z/OS and running volume level backups. I didn't experience any problems until this morning, when the z/os console became unresponsive and the whole virutal machine shot craps. Here's the weirdest thing of all, I changed the NAME of the virtual machine in z/VMs directory and IPL'd again and I haven't had a problem yet (but I also lowered the memory size from 1GB to 512Mb). Does a virtual machine's CP control blocks survive LOGON/LOGOFF of the virtual machine? I'm wondering if all that ATTaching and DETaching wrecked something in CP in relation to this guest [kind of a longshot, I know]. db -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Raymond Noal Sent: Thursday, March 20, 2008 2:04 PM To: [email protected] Subject: Re: z/OS on z/VM Eligible List David, What other virtual machines do you have running along with this z/OS virtual machine? What is your CPU utilization? Is the z/VM system's paging rate high? (albeit a relative number when comparing different systems) You can add the QUICKDSP parameter to the OPTION statement in the z/VM directory to keep this virtual machine on the dispatch list. When you say the console was unresponsive, which console are you referring to? Is this the z/OS virtual machine console or a z/OS console? Some additional performance related information would be of great assistance for the list members to better advise you. HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978
