Re: Performence Toolkit not working.
There are several things you could look for in MVS for a reason it crashed. Some of the things you could look for are the MVS syslog and/or LOGREC (EREP) and/or RMF data. There could be one of more SVC dumps that got taken under MVS just before the crash. As stated in another email a large number of MVS (z/OS) system don't run under z/VM so MVS has its own ways of keeping track of what is happening. Paul Feller AIT Mainframe Technical Support From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of saurabh khandelwal Sent: Saturday, August 06, 2011 11:39 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Performence Toolkit not working. So, does it mean, by installing z/VM performence tool kit will not tell us any detail about the guest running under z/VM ( MVS guest) . Basically my aim is to find out the reason behind crashing MVS guest suddenly , which are running under zVM. So can you please suggest, what will be the best solution to find root cause of MVS guest crashing. Thanks Regards Saurabh On Sun, Aug 7, 2011 at 2:50 AM, Les Koehler vmr...@tampabay.rr.commailto:vmr...@tampabay.rr.com wrote: Kris, Isn't MVS under VM different than just straight MVS on its own? Or have things changed since the old days? Les Kris Buelens wrote: MVS doesn't normally have anything to forward performance info to Perfkit. MVS has its own performance collection and reporting tools. 2011/8/6 saurabh khandelwal sourabhkhandelwal...@gmail.commailto:sourabhkhandelwal...@gmail.com Thanks for reply. Yes, I am trying to reach out the person, who has configured Performance toolkit in my site. So that I can get exact detail, how he configured this. As I am new with performance toolkit, I also wanted to ask is it possible to get MVS guest information from performance toolkit , which are running under z/VM. Thanks Regards Saurabh On Sat, Aug 6, 2011 at 1:44 PM, Jeff Gribbin jeff.grib...@gmail.commailto:jeff.grib...@gmail.comwrote: Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin -- Thanks Regards Saurabh Khandelwal -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
When MVS crashes, it doesn't get time to write any message into SYSLOG. So I didnt found anything in SYSLOG about MVS crashes. Thanks Regards Saurabh On Sun, Aug 7, 2011 at 5:42 PM, Feller, Paul pfel...@aegonusa.com wrote: There are several things you could look for in MVS for a reason it crashed. Some of the things you could look for are the MVS syslog and/or LOGREC (EREP) and/or RMF data. There could be one of more SVC dumps that got taken under MVS just before the crash. As stated in another email a large number of MVS (z/OS) system don’t run under z/VM so MVS has its own ways of keeping track of what is happening. ** ** *Paul Feller* *AIT Mainframe Technical Support* *From:* The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] *On Behalf Of *saurabh khandelwal *Sent:* Saturday, August 06, 2011 11:39 PM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: Performence Toolkit not working. ** ** So, does it mean, by installing z/VM performence tool kit will not tell us any detail about the guest running under z/VM ( MVS guest) . Basically my aim is to find out the reason behind crashing MVS guest suddenly , which are running under zVM. So can you please suggest, what will be the best solution to find root cause of MVS guest crashing. Thanks Regards Saurabh On Sun, Aug 7, 2011 at 2:50 AM, Les Koehler vmr...@tampabay.rr.com wrote: Kris, Isn't MVS under VM different than just straight MVS on its own? Or have things changed since the old days? Les Kris Buelens wrote: MVS doesn't normally have anything to forward performance info to Perfkit. MVS has its own performance collection and reporting tools. 2011/8/6 saurabh khandelwal sourabhkhandelwal...@gmail.com Thanks for reply. Yes, I am trying to reach out the person, who has configured Performance toolkit in my site. So that I can get exact detail, how he configured this. As I am new with performance toolkit, I also wanted to ask is it possible to get MVS guest information from performance toolkit , which are running under z/VM. Thanks Regards Saurabh On Sat, Aug 6, 2011 at 1:44 PM, Jeff Gribbin jeff.grib...@gmail.com wrote: Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin -- Thanks Regards Saurabh Khandelwal -- Thanks Regards Saurabh Khandelwal -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
Just a thought ... you're not trying to share DASD between the z/OS (MVS) systems in a, 'risky' way, are you? (Even more bizarre thought - you're not trying to share paging volumes between your z/VM systems, are you? This would certainly provide many opportunities for virtual machines to crash in peculiar ways. I once accidentally shared a page dataset between two OS/VS1 systems - I can state categorically, it does not work!) Jeff
Re: Performence Toolkit not working.
Volumes are shared between z/VM and z/OS . So in this case is it possible to get some more detail about MVS crash from z/VM. On Sun, Aug 7, 2011 at 11:18 PM, Jeff Gribbin jeff.grib...@gmail.comwrote: Just a thought ... you're not trying to share DASD between the z/OS (MVS) systems in a, 'risky' way, are you? (Even more bizarre thought - you're not trying to share paging volumes between your z/VM systems, are you? This would certainly provide many opportunities for virtual machines to crash in peculiar ways. I once accidentally shared a page dataset between two OS/VS1 systems - I can state categorically, it does not work!) Jeff -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
I think the question was: do you have multiple z/OS systems that are sharing dasd? On 8/7/11 2:09 PM, saurabh khandelwal sourabhkhandelwal...@gmail.com wrote: Volumes are shared between z/VM and z/OS . So in this case is it possible to get some more detail about MVS crash from z/VM. On Sun, Aug 7, 2011 at 11:18 PM, Jeff Gribbin jeff.grib...@gmail.com wrote: Just a thought ... you're not trying to share DASD between the z/OS (MVS) systems in a, 'risky' way, are you? (Even more bizarre thought - you're not trying to share paging volumes between your z/VM systems, are you? This would certainly provide many opportunities for virtual machines to crash in peculiar ways. I once accidentally shared a page dataset between two OS/VS1 systems - I can state categorically, it does not work!) Jeff
Re: Performence Toolkit not working.
There may not be message in SYSLOG right at the time of the crash but there could be messages before the crash that could help. As an example there could be messages about running out of CSA/SQA. Also please don't forget to look for any SVC dumps that might have happened before the crash and look at LOGERC for any errors that might help determine what happened. Paul Feller AIT Mainframe Technical Support From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of saurabh khandelwal Sent: Sunday, August 07, 2011 9:47 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Performence Toolkit not working. When MVS crashes, it doesn't get time to write any message into SYSLOG. So I didnt found anything in SYSLOG about MVS crashes. Thanks Regards Saurabh On Sun, Aug 7, 2011 at 5:42 PM, Feller, Paul pfel...@aegonusa.commailto:pfel...@aegonusa.com wrote: There are several things you could look for in MVS for a reason it crashed. Some of the things you could look for are the MVS syslog and/or LOGREC (EREP) and/or RMF data. There could be one of more SVC dumps that got taken under MVS just before the crash. As stated in another email a large number of MVS (z/OS) system don't run under z/VM so MVS has its own ways of keeping track of what is happening. Paul Feller AIT Mainframe Technical Support From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of saurabh khandelwal Sent: Saturday, August 06, 2011 11:39 PM To: IBMVM@LISTSERV.UARK.EDUmailto:IBMVM@LISTSERV.UARK.EDU Subject: Re: Performence Toolkit not working. So, does it mean, by installing z/VM performence tool kit will not tell us any detail about the guest running under z/VM ( MVS guest) . Basically my aim is to find out the reason behind crashing MVS guest suddenly , which are running under zVM. So can you please suggest, what will be the best solution to find root cause of MVS guest crashing. Thanks Regards Saurabh On Sun, Aug 7, 2011 at 2:50 AM, Les Koehler vmr...@tampabay.rr.commailto:vmr...@tampabay.rr.com wrote: Kris, Isn't MVS under VM different than just straight MVS on its own? Or have things changed since the old days? Les Kris Buelens wrote: MVS doesn't normally have anything to forward performance info to Perfkit. MVS has its own performance collection and reporting tools. 2011/8/6 saurabh khandelwal sourabhkhandelwal...@gmail.commailto:sourabhkhandelwal...@gmail.com Thanks for reply. Yes, I am trying to reach out the person, who has configured Performance toolkit in my site. So that I can get exact detail, how he configured this. As I am new with performance toolkit, I also wanted to ask is it possible to get MVS guest information from performance toolkit , which are running under z/VM. Thanks Regards Saurabh On Sat, Aug 6, 2011 at 1:44 PM, Jeff Gribbin jeff.grib...@gmail.commailto:jeff.grib...@gmail.comwrote: Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin -- Thanks Regards Saurabh Khandelwal -- Thanks Regards Saurabh Khandelwal -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
On Sunday, 08/07/2011 at 10:46 EDT, saurabh khandelwal sourabhkhandelwal...@gmail.com wrote: When MVS crashes, it doesn't get time to write any message into SYSLOG. So I didnt found anything in SYSLOG about MVS crashes. With an MVS crash, the last thing that happens is that MVS loads a disabled wait PSW with the address in the PSW set to a specific value called the wait state code. You need to look up the meaning of that code in the MVS System Codes book. Alan Altmark Senior Managing z/VM and Linux Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Re: Performence Toolkit not working.
On 8/7/2011 at 10:46 AM, saurabh khandelwal sourabhkhandelwal...@gmail.com wrote: When MVS crashes, it doesn't get time to write any message into SYSLOG. So I didnt found anything in SYSLOG about MVS crashes. Then you should be using the z/OS standalone dump utility to get a dump to send to the IBM support center. That's why you're paying them the big bucks for support. Mark Post
Re: Performence Toolkit not working.
Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin
Re: Performence Toolkit not working.
Thanks for reply. Yes, I am trying to reach out the person, who has configured Performance toolkit in my site. So that I can get exact detail, how he configured this. As I am new with performance toolkit, I also wanted to ask is it possible to get MVS guest information from performance toolkit , which are running under z/VM. Thanks Regards Saurabh On Sat, Aug 6, 2011 at 1:44 PM, Jeff Gribbin jeff.grib...@gmail.com wrote: Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
MVS doesn't normally have anything to forward performance info to Perfkit. MVS has its own performance collection and reporting tools. 2011/8/6 saurabh khandelwal sourabhkhandelwal...@gmail.com Thanks for reply. Yes, I am trying to reach out the person, who has configured Performance toolkit in my site. So that I can get exact detail, how he configured this. As I am new with performance toolkit, I also wanted to ask is it possible to get MVS guest information from performance toolkit , which are running under z/VM. Thanks Regards Saurabh On Sat, Aug 6, 2011 at 1:44 PM, Jeff Gribbin jeff.grib...@gmail.comwrote: Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin -- Thanks Regards Saurabh Khandelwal -- Kris Buelens, IBM Belgium, VM customer support
Re: Performence Toolkit not working.
Kris, Isn't MVS under VM different than just straight MVS on its own? Or have things changed since the old days? Les Kris Buelens wrote: MVS doesn't normally have anything to forward performance info to Perfkit. MVS has its own performance collection and reporting tools. 2011/8/6 saurabh khandelwal sourabhkhandelwal...@gmail.com Thanks for reply. Yes, I am trying to reach out the person, who has configured Performance toolkit in my site. So that I can get exact detail, how he configured this. As I am new with performance toolkit, I also wanted to ask is it possible to get MVS guest information from performance toolkit , which are running under z/VM. Thanks Regards Saurabh On Sat, Aug 6, 2011 at 1:44 PM, Jeff Gribbin jeff.grib...@gmail.comwrote: Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
So, does it mean, by installing z/VM performence tool kit will not tell us any detail about the guest running under z/VM ( MVS guest) . Basically my aim is to find out the reason behind crashing MVS guest suddenly , which are running under zVM. So can you please suggest, what will be the best solution to find root cause of MVS guest crashing. Thanks Regards Saurabh On Sun, Aug 7, 2011 at 2:50 AM, Les Koehler vmr...@tampabay.rr.com wrote: Kris, Isn't MVS under VM different than just straight MVS on its own? Or have things changed since the old days? Les Kris Buelens wrote: MVS doesn't normally have anything to forward performance info to Perfkit. MVS has its own performance collection and reporting tools. 2011/8/6 saurabh khandelwal sourabhkhandelwal123@gmail.**comsourabhkhandelwal...@gmail.com Thanks for reply. Yes, I am trying to reach out the person, who has configured Performance toolkit in my site. So that I can get exact detail, how he configured this. As I am new with performance toolkit, I also wanted to ask is it possible to get MVS guest information from performance toolkit , which are running under z/VM. Thanks Regards Saurabh On Sat, Aug 6, 2011 at 1:44 PM, Jeff Gribbin jeff.grib...@gmail.com wrote: Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin -- Thanks Regards Saurabh Khandelwal -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
The CP Monitor and VM Perfkit (that gets most of its input from the CP Monitor) do indeed not care about what happens inside a guest. Linux is an exception with its module that forwards things to Perfkit. The majority of MVS systems do not run under VM, hence the handshaking of MVS with VM is not very function rich. As to find reasons for a crash: that's not Perfkit's role, not even for CMS guests. As there is no console information, I'd go the same path as for CMS users: CP SEND CP mvsxyz TRACE PROG RUN TERMINAL or CP SEND CP mvsxyz TRACE PROG RUN PRINTER for the first alternative: be sure the have MVS' virtual console started and spooled somewhere. For the second: define a virtual printer at a low address, like CP SEND CP mvsxys DEFINE PRT 00E With this trace, every program check will be reported, but MVS keeps running and can attempt to perform its usual abend recovery. Also abends in user programs will be reported this way. For CMS we often found a first program check occurring, followed by a program check in the abend recovery routines. Such a TRACE has a very low overhead. When you'd fine such an abend just before the MVS crash, you can change the TRACE command and try to be more precise in your trace (e.g. limit the address range), and when an abend happens, take a VMDUMP, or display registers, As there can be many traces concurrently, issue CP SEND CP mvsxyz TRACE END ALL before issuing a new trace command. 2011/8/7 saurabh khandelwal sourabhkhandelwal...@gmail.com So, does it mean, by installing z/VM performence tool kit will not tell us any detail about the guest running under z/VM ( MVS guest) . Basically my aim is to find out the reason behind crashing MVS guest suddenly , which are running under zVM. So can you please suggest, what will be the best solution to find root cause of MVS guest crashing. Thanks Regards Saurabh On Sun, Aug 7, 2011 at 2:50 AM, Les Koehler vmr...@tampabay.rr.comwrote: Kris, Isn't MVS under VM different than just straight MVS on its own? Or have things changed since the old days? Les Kris Buelens wrote: MVS doesn't normally have anything to forward performance info to Perfkit. MVS has its own performance collection and reporting tools. 2011/8/6 saurabh khandelwal sourabhkhandelwal123@gmail.**comsourabhkhandelwal...@gmail.com Thanks for reply. Yes, I am trying to reach out the person, who has configured Performance toolkit in my site. So that I can get exact detail, how he configured this. As I am new with performance toolkit, I also wanted to ask is it possible to get MVS guest information from performance toolkit , which are running under z/VM. Thanks Regards Saurabh On Sat, Aug 6, 2011 at 1:44 PM, Jeff Gribbin jeff.grib...@gmail.com wrote: Saurabh, You have almost-certainly indentified the cause of your problem - it is NEVER, EVER safe to share the same CMS minidisk accessed in write-mode by more than one CMS user at the same time - it almost-guarantees that the disk file system will be damaged. DASD sharing always requires the sharing systems to be aware that the DASD is shared and take measures to ensure that the data is not corrupted - these can be via hardware functions such as RESERVE / RELEASE or via software processes that use a communications link to agree amongst themselves which system has write-permission at any one instant. CMS contains no sharing mechanism at all for its minidisks (think of a CMS user as a virtual Personal Computer - write-sharing a minidisk is like connecting two personal computers that have no knowledge of each others' existence to the same hard drive!) If you wish to share data in write-mode among CMS users then you need to look at the CMS Shared File System which uses a server to co-ordinate the I/O among many CMS clients. (In this client/server setup, it's only the DATA that is shared - the actual DASD is only read/written by the server which (of course) has complete knowledge of which clients are accessing which data.) Sharing minidisk-containing volumes between separate z/VM systems requires a lot of care if it is to be successful. If you can tell us a little more about your configuration and how you run it I'm sure that we can offer you some suggestions about how to achieve what you wish to do but ... in the meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk. Regards Jeff Gribbin -- Thanks Regards Saurabh Khandelwal -- Thanks Regards Saurabh Khandelwal -- Kris Buelens, IBM Belgium, VM customer support
Performence Toolkit not working.
Hello, We have zVM 5.4 System. And I am trying to login with PERFSVM id, I get below error while connecting. LOGON PERFSVM ENTER PASSWORD (IT WILL NOT APPEAR WHEN TYPED): 21:38:57 z/VM Version 5 Release 4.0, Service Level 1001 (64-bit), 21:38:57 built on IBM Virtualization Technology 21:38:57 There is no logmsg data 21:38:57 FILES: NO RDR, NO PRT, NO PUN 21:38:57 LOGON AT 21:38:57 PDT THURSDAY 08/04/11 21:38:57 GRAF L0004 LOGON AS PERFSVM USERS = 21FROM 10.159.14.88 z/VM V5.4.02010-02-16 14:54 DMSACP723I B (201) R/O DMSACP723I D (1CC) R/O DMSACP723I F (29D) R/O 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete DMSDKD1307T File system error detected by DMSAUD at address 00F1D940 (offset 000 007A8): DMSDKD1307T TRKAL request failed with code 8 during an I/O operation using virtu al device 191 (mode 'A') 21:38:57 HCPGIR450W CP entered; disabled wait PSW 000A 00F082CA To isolate this, I tried checking user directory for PERFSVM for 191 mini disk. USER PERFSVM PERFSVM 64M 512M ABDEG MACHINE ESA XAUTOLOG AUTOLOG1 ACCOUNT NAMESAVE MONDCSS IUCV *MONITOR MSGLIMIT 255 IUCV *IDENT FCXRES00 GLOBAL IUCV *IDENT FCXSYSTM GLOBAL IUCV ALLOW SHARE ABS 3% IPL CMS PARM AUTOCR OPTION QUICKDSP DIAG88 CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK 5VMPTK40 200 200 RR LINK 5VMPTK40 201 201 RR LINK 5VMPTK40 1CC 1CC RR LINK 5VMPTK40 29D 29D RR MDISK 191 3390 6250 120 540RES MR READ WRITEMULTIPLE MDISK 195 3390 6370 060 540RES MR READ WRITEMULTIPLE Also I logged using MAINT and enabled this product again . *set product prodid 5vmptk40 state enabled * But, still I am getting same error for evice 191 (mode 'A'). Can you help me resolve this isse, so tht I can run performence took lit -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
Looks like a corrupted disk.. if you have a backup - I would format the disk and restore it.. If not - you can try and copy as many files off of it as you can (you will likely be able to copy some files, but one or more will cause the system file error to occur). Corruption can be caused by things like two users linking the disk RW - or overlapping disks.. Scott Rohling On Fri, Aug 5, 2011 at 9:47 AM, saurabh khandelwal sourabhkhandelwal...@gmail.com wrote: Hello, We have zVM 5.4 System. And I am trying to login with PERFSVM id, I get below error while connecting. LOGON PERFSVM ENTER PASSWORD (IT WILL NOT APPEAR WHEN TYPED): 21:38:57 z/VM Version 5 Release 4.0, Service Level 1001 (64-bit), 21:38:57 built on IBM Virtualization Technology 21:38:57 There is no logmsg data 21:38:57 FILES: NO RDR, NO PRT, NO PUN 21:38:57 LOGON AT 21:38:57 PDT THURSDAY 08/04/11 21:38:57 GRAF L0004 LOGON AS PERFSVM USERS = 21FROM 10.159.14.88 z/VM V5.4.02010-02-16 14:54 DMSACP723I B (201) R/O DMSACP723I D (1CC) R/O DMSACP723I F (29D) R/O 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete DMSDKD1307T File system error detected by DMSAUD at address 00F1D940 (offset 000 007A8): DMSDKD1307T TRKAL request failed with code 8 during an I/O operation using virtu al device 191 (mode 'A') 21:38:57 HCPGIR450W CP entered; disabled wait PSW 000A 00F082CA To isolate this, I tried checking user directory for PERFSVM for 191 mini disk. USER PERFSVM PERFSVM 64M 512M ABDEG MACHINE ESA XAUTOLOG AUTOLOG1 ACCOUNT NAMESAVE MONDCSS IUCV *MONITOR MSGLIMIT 255 IUCV *IDENT FCXRES00 GLOBAL IUCV *IDENT FCXSYSTM GLOBAL IUCV ALLOW SHARE ABS 3% IPL CMS PARM AUTOCR OPTION QUICKDSP DIAG88 CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK 5VMPTK40 200 200 RR LINK 5VMPTK40 201 201 RR LINK 5VMPTK40 1CC 1CC RR LINK 5VMPTK40 29D 29D RR MDISK 191 3390 6250 120 540RES MR READ WRITEMULTIPLE MDISK 195 3390 6370 060 540RES MR READ WRITEMULTIPLE Also I logged using MAINT and enabled this product again . *set product prodid 5vmptk40 state enabled * But, still I am getting same error for evice 191 (mode 'A'). Can you help me resolve this isse, so tht I can run performence took lit -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
You could check 191 disk readability. Define a TDISK of the same size DDR 191 to it...see if a problem occurs. At a CMS level (format the TDISK for CMS) then copy all of the files from the 191 to this TDISK to see if CMS can read them. Frank M. Ramaekers Jr. From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of saurabh khandelwal Sent: Friday, August 05, 2011 10:47 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Performence Toolkit not working. Hello, We have zVM 5.4 System. And I am trying to login with PERFSVM id, I get below error while connecting. LOGON PERFSVM ENTER PASSWORD (IT WILL NOT APPEAR WHEN TYPED): 21:38:57 z/VM Version 5 Release 4.0, Service Level 1001 (64-bit), 21:38:57 built on IBM Virtualization Technology 21:38:57 There is no logmsg data 21:38:57 FILES: NO RDR, NO PRT, NO PUN 21:38:57 LOGON AT 21:38:57 PDT THURSDAY 08/04/11 21:38:57 GRAF L0004 LOGON AS PERFSVM USERS = 21FROM 10.159.14.88 z/VM V5.4.02010-02-16 14:54 DMSACP723I B (201) R/O DMSACP723I D (1CC) R/O DMSACP723I F (29D) R/O 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete DMSDKD1307T File system error detected by DMSAUD at address 00F1D940 (offset 000 007A8): DMSDKD1307T TRKAL request failed with code 8 during an I/O operation using virtu al device 191 (mode 'A') 21:38:57 HCPGIR450W CP entered; disabled wait PSW 000A 00F082CA To isolate this, I tried checking user directory for PERFSVM for 191 mini disk. USER PERFSVM PERFSVM 64M 512M ABDEG MACHINE ESA XAUTOLOG AUTOLOG1 ACCOUNT NAMESAVE MONDCSS IUCV *MONITOR MSGLIMIT 255 IUCV *IDENT FCXRES00 GLOBAL IUCV *IDENT FCXSYSTM GLOBAL IUCV ALLOW SHARE ABS 3% IPL CMS PARM AUTOCR OPTION QUICKDSP DIAG88 CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK 5VMPTK40 200 200 RR LINK 5VMPTK40 201 201 RR LINK 5VMPTK40 1CC 1CC RR LINK 5VMPTK40 29D 29D RR MDISK 191 3390 6250 120 540RES MR READ WRITEMULTIPLE MDISK 195 3390 6370 060 540RES MR READ WRITEMULTIPLE Also I logged using MAINT and enabled this product again . set product prodid 5vmptk40 state enabled But, still I am getting same error for evice 191 (mode 'A'). Can you help me resolve this isse, so tht I can run performence took lit -- Thanks Regards Saurabh Khandelwal _ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at privacy...@ailife.com.
Re: Performence Toolkit not working.
Hello, Saurabh. In this case, the CMS HELP command is your friendtry doing a HELP DMSDKD1307T From the help text, you will see that the error being reported is from the DMSAUD module in the TRKAL function. Return code 8 from the TRKAL function means: 8 No blocks are allocated and user area is unmodified. This is generally an indication of one of the following: - The number of blocks marked as available in the allocation map does not match block counts indicated in the minidisk label record. - Virtual storage for the disk's allocation map has been corrupted. - The allocation map on disk has been damaged due to pre-existing corruption. It appears that your 191 minidisk on the PERFSVM machine has been corrupted somehow, or that the virtual storage holding the minidisk's allocation map has been corrupted. You might first want to try increasing PERFSVM's virtual storage from its default of 64M to something biggerlike 256M. Hope this helps. DJ On 08/05/2011 10:47 AM, saurabh khandelwal wrote: Hello, We have zVM 5.4 System. And I am trying to login with PERFSVM id, I get below error while connecting. LOGON PERFSVM ENTER PASSWORD (IT WILL NOT APPEAR WHEN TYPED): 21:38:57 z/VM Version 5 Release 4.0, Service Level 1001 (64-bit), 21:38:57 built on IBM Virtualization Technology 21:38:57 There is no logmsg data 21:38:57 FILES: NO RDR, NO PRT, NO PUN 21:38:57 LOGON AT 21:38:57 PDT THURSDAY 08/04/11 21:38:57 GRAF L0004 LOGON AS PERFSVM USERS = 21FROM 10.159.14.88 z/VM V5.4.02010-02-16 14:54 DMSACP723I B (201) R/O DMSACP723I D (1CC) R/O DMSACP723I F (29D) R/O 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete DMSDKD1307T File system error detected by DMSAUD at address 00F1D940 (offset 000 007A8): DMSDKD1307T TRKAL request failed with code 8 during an I/O operation using virtu al device 191 (mode 'A') 21:38:57 HCPGIR450W CP entered; disabled wait PSW 000A 00F082CA To isolate this, I tried checking user directory for PERFSVM for 191 mini disk. USER PERFSVM PERFSVM 64M 512M ABDEG MACHINE ESA XAUTOLOG AUTOLOG1 ACCOUNT NAMESAVE MONDCSS IUCV *MONITOR MSGLIMIT 255 IUCV *IDENT FCXRES00 GLOBAL IUCV *IDENT FCXSYSTM GLOBAL IUCV ALLOW SHARE ABS 3% IPL CMS PARM AUTOCR OPTION QUICKDSP DIAG88 CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK 5VMPTK40 200 200 RR LINK 5VMPTK40 201 201 RR LINK 5VMPTK40 1CC 1CC RR LINK 5VMPTK40 29D 29D RR MDISK 191 3390 6250 120 540RES MR READ WRITEMULTIPLE MDISK 195 3390 6370 060 540RES MR READ WRITEMULTIPLE Also I logged using MAINT and enabled this product again . *set product prodid 5vmptk40 state enabled * But, still I am getting same error for evice 191 (mode 'A'). Can you help me resolve this isse, so tht I can run performence took lit -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544
Re: Performence Toolkit not working.
Possibly your A disk is full Sent from my iPhone On Aug 5, 2011, at 11:47, saurabh khandelwal sourabhkhandelwal...@gmail.com wrote: Hello, We have zVM 5.4 System. And I am trying to login with PERFSVM id, I get below error while connecting. LOGON PERFSVM ENTER PASSWORD (IT WILL NOT APPEAR WHEN TYPED): 21:38:57 z/VM Version 5 Release 4.0, Service Level 1001 (64-bit), 21:38:57 built on IBM Virtualization Technology 21:38:57 There is no logmsg data 21:38:57 FILES: NO RDR, NO PRT, NO PUN 21:38:57 LOGON AT 21:38:57 PDT THURSDAY 08/04/11 21:38:57 GRAF L0004 LOGON AS PERFSVM USERS = 21FROM 10.159.14.88 z/VM V5.4.02010-02-16 14:54 DMSACP723I B (201) R/O DMSACP723I D (1CC) R/O DMSACP723I F (29D) R/O 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete DMSDKD1307T File system error detected by DMSAUD at address 00F1D940 (offset 000 007A8): DMSDKD1307T TRKAL request failed with code 8 during an I/O operation using virtu al device 191 (mode 'A') 21:38:57 HCPGIR450W CP entered; disabled wait PSW 000A 00F082CA To isolate this, I tried checking user directory for PERFSVM for 191 mini disk. USER PERFSVM PERFSVM 64M 512M ABDEG MACHINE ESA XAUTOLOG AUTOLOG1 ACCOUNT NAMESAVE MONDCSS IUCV *MONITOR MSGLIMIT 255 IUCV *IDENT FCXRES00 GLOBAL IUCV *IDENT FCXSYSTM GLOBAL IUCV ALLOW SHARE ABS 3% IPL CMS PARM AUTOCR OPTION QUICKDSP DIAG88 CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK 5VMPTK40 200 200 RR LINK 5VMPTK40 201 201 RR LINK 5VMPTK40 1CC 1CC RR LINK 5VMPTK40 29D 29D RR MDISK 191 3390 6250 120 540RES MR READ WRITEMULTIPLE MDISK 195 3390 6370 060 540RES MR READ WRITEMULTIPLE Also I logged using MAINT and enabled this product again . set product prodid 5vmptk40 state enabled But, still I am getting same error for evice 191 (mode 'A'). Can you help me resolve this isse, so tht I can run performence took lit -- Thanks Regards Saurabh Khandelwal
Re: Performence Toolkit not working.
Thanks every one for replying me . I have noticed one thing in our setup. We have two z/VM running and their DASD are in shared mode.In both the system Performance tool kit user PERFSVM contain 191 ( Disk) , which part of same 540RES volume. I think this might be a reason to cause problem , that two system pointing to same RES volume Please correct me, if my understanding is wrong. Regards Saurabh On Fri, Aug 5, 2011 at 9:27 PM, Dave Jones d...@vsoft-software.com wrote: Hello, Saurabh. In this case, the CMS HELP command is your friendtry doing a HELP DMSDKD1307T From the help text, you will see that the error being reported is from the DMSAUD module in the TRKAL function. Return code 8 from the TRKAL function means: 8 No blocks are allocated and user area is unmodified. This is generally an indication of one of the following: - The number of blocks marked as available in the allocation map does not match block counts indicated in the minidisk label record. - Virtual storage for the disk's allocation map has been corrupted. - The allocation map on disk has been damaged due to pre-existing corruption. It appears that your 191 minidisk on the PERFSVM machine has been corrupted somehow, or that the virtual storage holding the minidisk's allocation map has been corrupted. You might first want to try increasing PERFSVM's virtual storage from its default of 64M to something biggerlike 256M. Hope this helps. DJ On 08/05/2011 10:47 AM, saurabh khandelwal wrote: Hello, We have zVM 5.4 System. And I am trying to login with PERFSVM id, I get below error while connecting. LOGON PERFSVM ENTER PASSWORD (IT WILL NOT APPEAR WHEN TYPED): 21:38:57 z/VM Version 5 Release 4.0, Service Level 1001 (64-bit), 21:38:57 built on IBM Virtualization Technology 21:38:57 There is no logmsg data 21:38:57 FILES: NO RDR, NO PRT, NO PUN 21:38:57 LOGON AT 21:38:57 PDT THURSDAY 08/04/11 21:38:57 GRAF L0004 LOGON AS PERFSVM USERS = 21FROM 10.159.14.88 z/VM V5.4.02010-02-16 14:54 DMSACP723I B (201) R/O DMSACP723I D (1CC) R/O DMSACP723I F (29D) R/O 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete 21:38:57 Command complete DMSDKD1307T File system error detected by DMSAUD at address 00F1D940 (offset 000 007A8): DMSDKD1307T TRKAL request failed with code 8 during an I/O operation using virtu al device 191 (mode 'A') 21:38:57 HCPGIR450W CP entered; disabled wait PSW 000A 00F082CA To isolate this, I tried checking user directory for PERFSVM for 191 mini disk. USER PERFSVM PERFSVM 64M 512M ABDEG MACHINE ESA XAUTOLOG AUTOLOG1 ACCOUNT NAMESAVE MONDCSS IUCV *MONITOR MSGLIMIT 255 IUCV *IDENT FCXRES00 GLOBAL IUCV *IDENT FCXSYSTM GLOBAL IUCV ALLOW SHARE ABS 3% IPL CMS PARM AUTOCR OPTION QUICKDSP DIAG88 CONSOLE 0009 3215 SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A LINK MAINT 190 190 RR LINK MAINT 19D 19D RR LINK MAINT 19E 19E RR LINK 5VMPTK40 200 200 RR LINK 5VMPTK40 201 201 RR LINK 5VMPTK40 1CC 1CC RR LINK 5VMPTK40 29D 29D RR MDISK 191 3390 6250 120 540RES MR READ WRITEMULTIPLE MDISK 195 3390 6370 060 540RES MR READ WRITEMULTIPLE Also I logged using MAINT and enabled this product again . *set product prodid 5vmptk40 state enabled * But, still I am getting same error for evice 191 (mode 'A'). Can you help me resolve this isse, so tht I can run performence took lit -- Dave Jones V/Soft Software www.vsoft-software.com Houston, TX 281.578.7544 -- Thanks Regards Saurabh Khandelwal
