Marcy, Our DR site is a IBM site, one of the biggest in France, and be sure I didn't keep this secret ! The feedback I got from the hard was "that's normal ...". A subsidiary question from me was : How would we do if we had to IPL our dozens of MVS 1stLVL. I stopped waiting for the answer ...
Alain Le 26/09/08 23:46, « Marcy Cortes » <[EMAIL PROTECTED]> a écrit : > That sounds like a bug (q dasd details not returning the real number of cyls). > Did you report that to IBM? > > > > > 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." > > > > ________________________________ > > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf > Of Alain Benveniste > Sent: Friday, September 26, 2008 11:50 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: [IBMVM] DASD VOLUME SIZES > > > I have experienced that q da details will NOT send back the real number of > cyls in this cicumstance specificaly : > > With a DS8300, that we use for DR, we saw that coding 0 END in a MDISK for a > 3380-K will give a wrong result when starting a MVS and checking the vtoc in > 3.4. 3380-K were emulated as expected but the size of the 3380-K was equal to > a 3390-3. So you could believe you have enough space to run your prod on that > dasd but your prod will fail with a 'no more space available'. > > > Alain > > > > > Le 25/09/08 19:21, « Howard Rifkind » <[EMAIL PROTECTED]> a écrit : > > > > Suggestion all good thanks folks... > >>>> Marcy Cortes <[EMAIL PROTECTED]> 9/25/2008 1:10 PM >>> > Q DASD DETAILS nnnn > > > > > 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:[EMAIL PROTECTED] On > Behalf Of David Kreuter > Sent: Thursday, September 25, 2008 10:04 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: [IBMVM] DASD VOLUME SIZES > > Howard: many ways. Here's one: add an mdisk statement with extents " 0 > END" to the directory. > link to the disk and do a Q V on its address. The response will show > you the amount of cylinders. > David > > ________________________________ > > From: The IBM z/VM Operating System on behalf of Howard Rifkind > Sent: Thu 9/25/2008 12:58 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: [IBMVM] DASD VOLUME SIZES > > > What would be the quickest way to find out the size of a volume which > currently has minidisks allocated on it. > > Cylinders? > > > > _____________ > LEGAL NOTICE > Unless expressly stated otherwise, this message is confidential and may > be privileged. It is intended for the addressee(s) only. > Access to this E-mail by anyone else is unauthorized. > If you are not an addressee, any disclosure or copying of the contents > of this E-mail or any action taken (or not taken) in reliance on it is > unauthorized and may be unlawful. If you are not an addressee, please > inform the sender immediately, then delete this message and empty from > your trash. > > > > > > _____________ > LEGAL NOTICE > Unless expressly stated otherwise, this message is confidential > and may be privileged. It is intended for the addressee(s) only. > Access to this E-mail by anyone else is unauthorized. > If you are not an addressee, any disclosure or copying of the > contents of this E-mail or any action taken (or not taken) in > reliance on it is unauthorized and may be unlawful. If you are not an > addressee, please inform the sender immediately, then delete this > message and empty from your trash. > > >
