Our mapping tool is based on the number of cyls field sent by the q dasd details for our ECKD. But I suppose I can¹t use this cmd to preserve the concept for LUN DASD, can I ? So, I think I have to use the DISKBKLS to preserve the same concept. But there is something I don¹t understand in the report :
I remember the OPEN guys told me that a meta volume must have LUNs with the same size. Is that true ? Does the report only shows ONE meta volume because there is a chaining 5100-510B ? Does it mean that if this is there is a LUN before & after, the chaining will be always broken to make the difference between a LUN and a MV ? Alain Benveniste Le 21/11/07 21:49, « Romanowski, John (OFT) » <[EMAIL PROTECTED]> a écrit : > on some occasions SCSIDISC will report LUN_SIZE_(bytes) as a negative number. > Seen that only for large LUNs. > On other occasions some of the fields, LUN_SIZE too, will be reported as > XXXXX¹s > > > > 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. > > > From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf > Of Steve Wilkins > Sent: Wednesday, November 21, 2007 3:43 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Questions about LUN DASD volumes > > Compliments of Eric R. Farman, a sample of the SCSIDISC output: > > _FCP_CH_ ______WWPN______ _____LUN_ID_____ _VENDOR_ PROD MODL _SERIAL_ CODE > _BLK_SIZE_ _DISKBLKS_ __LUN_SIZE_(bytes)__ > 0000B098 5005076300CA04DA 5100000000000000 IBM 2105 F20 10013262 .178 > 512 7617216 3900014592 > 0000B098 5005076300CA04DA 5101000000000000 IBM 2105 F20 10113262 .178 > 512 7617216 3900014592 > 0000B098 5005076300CA04DA 5102000000000000 IBM 2105 F20 10213262 .178 > 512 7617216 3900014592 > 0000B098 5005076300CA04DA 5103000000000000 IBM 2105 F20 10313262 .178 > 512 7617216 3900014592 > 0000B098 5005076300CA04DA 5104000000000000 IBM 2105 F20 10413262 .178 > 512 195328 100007936 > 0000B098 5005076300CA04DA 5105000000000000 IBM 2105 F20 10513262 .178 > 512 195328 100007936 > 0000B098 5005076300CA04DA 5106000000000000 IBM 2105 F20 10613262 .178 > 512 195328 100007936 > 0000B098 5005076300CA04DA 5107000000000000 IBM 2105 F20 10713262 .178 > 512 1953152 1000013824 > 0000B098 5005076300CA04DA 5108000000000000 IBM 2105 F20 10813262 .178 > 512 1953152 1000013824 > 0000B098 5005076300CA04DA 5109000000000000 IBM 2105 F20 10913262 .178 > 512 1953152 1000013824 > 0000B098 5005076300CA04DA 510A000000000000 IBM 2105 F20 10A13262 .178 > 512 1953152 1000013824 > 0000B098 5005076300CA04DA 510B000000000000 IBM 2105 F20 10B13262 .178 > 512 1953152 1000013824 > > Regards, Steve. > > Steve Wilkins > IBM z/VM Development > > >
