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

Reply via email to