Re: Questions about LUN DASD volumes
How large is large? I can't put my hands on one larger than 70GB at the moment, and it looks fine. Will look for the huge disks tomorrow to try them. As for the fields reported as X, that's due to some kind of I/O error when trying to get a LUN to decribe itself. This sometimes occurs because of an ACL restriction, as some DASD controllers will gladly tell us a LUN exists, but reject any I/O directed at it. In those cases, description I/O such as the SCSI Inquiry or Read Capacity commands will fail, and we cannot fill in that information. Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY Romanowski, John (OFT) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/21/2007 03:49 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Questions about LUN DASD volumes 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 X?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)__ B098 5005076300CA04DA 5100 IBM 2105 F20 10013262 .1785127617216 3900014592 B098 5005076300CA04DA 5101 IBM 2105 F20 10113262 .1785127617216 3900014592 B098 5005076300CA04DA 5102 IBM 2105 F20 10213262 .1785127617216 3900014592 B098 5005076300CA04DA 5103 IBM 2105 F20 10313262 .1785127617216 3900014592 B098 5005076300CA04DA 5104 IBM 2105 F20 10413262 .178512 19532817936 B098 5005076300CA04DA 5105 IBM 2105 F20 10513262 .178512 19532817936 B098 5005076300CA04DA 5106 IBM 2105 F20 10613262 .178512 19532817936 B098 5005076300CA04DA 5107 IBM 2105 F20 10713262 .1785121953152 113824 B098 5005076300CA04DA 5108 IBM 2105 F20 10813262 .1785121953152 113824 B098 5005076300CA04DA 5109 IBM 2105 F20 10913262 .1785121953152 113824 B098 5005076300CA04DA 510A IBM 2105 F20 10A13262 .1785121953152 113824 B098 5005076300CA04DA 510B IBM 2105 F20 10B13262 .1785121953152 113824 Regards, Steve. Steve Wilkins IBM z/VM Development
Re: Questions about LUN DASD volumes
On Nov 21, 2007 10:48 AM, Steve Wilkins [EMAIL PROTECTED] wrote: SCSIDISC (the SCSI Discovery Tool) is a sample exec which provides target port and LUN information so one can discover the LUN topology which hangs off a System z FCP Subchannel. The help file for the tool (SCSIDISC SAMPHELP) indicates that it is Located on MAINT 194 or 2C2 disk. Regards, Steve. I copied SCSIDISC SAMPEXEC to SCSIDISC EXEC, but when I run it I get - DMSRTL2103E Error in compiled CMS system Rexx file; additional information: 4300 43 SCSIDISC EXEC 587 -- Mark Pace Mainline Information Systems
Re: Questions about LUN DASD volumes
Eric, large LUN that I referred to was a 957GB LUN in an IBM SVC 2145. reported LUN size (bytes) was correct, but prefixed with a minus sign. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Eric R Farman Sent: Monday, November 26, 2007 9:06 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes How large is large? I can't put my hands on one larger than 70GB at the moment, and it looks fine. Will look for the huge disks tomorrow to try them. As for the fields reported as X, that's due to some kind of I/O error when trying to get a LUN to decribe itself. This sometimes occurs because of an ACL restriction, as some DASD controllers will gladly tell us a LUN exists, but reject any I/O directed at it. In those cases, description I/O such as the SCSI Inquiry or Read Capacity commands will fail, and we cannot fill in that information. Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY Romanowski, John (OFT) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/21/2007 03:49 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Questions about LUN DASD volumes 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 X'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)__ B098 5005076300CA04DA 5100 IBM 2105 F20 10013262 .1785127617216 3900014592 B098 5005076300CA04DA 5101 IBM 2105 F20 10113262 .1785127617216 3900014592 B098 5005076300CA04DA 5102 IBM 2105 F20 10213262 .1785127617216 3900014592 B098 5005076300CA04DA 5103 IBM 2105 F20 10313262 .1785127617216 3900014592 B098 5005076300CA04DA 5104 IBM 2105 F20 10413262 .178512 19532817936 B098 5005076300CA04DA 5105 IBM 2105 F20 10513262 .178512 19532817936 B098 5005076300CA04DA 5106 IBM 2105 F20 10613262 .178512 19532817936 B098 5005076300CA04DA 5107 IBM 2105 F20 10713262 .1785121953152 113824 B098 5005076300CA04DA 5108 IBM 2105 F20 10813262 .1785121953152 113824 B098 5005076300CA04DA 5109 IBM 2105 F20 10913262 .1785121953152 113824 B098 5005076300CA04DA 510A IBM 2105 F20 10A13262 .1785121953152 113824 B098 5005076300CA04DA 510B IBM 2105 F20 10B13262 .1785121953152 113824 Regards, Steve. Steve Wilkins IBM z/VM Development
Re: Questions about LUN DASD volumes
You probably need to find RXSCSIFN SAMPMOD and copy it as RXUSERFN MODULE; SCSIDISC uses it. From SCSIDISC HELPCMS: SETUP - Located on MAINT 194 or 2C2 disk Find SCSIDISC SAMPEXEC - Copy to SCSIDISC EXEC Find RXSCSIFN SAMPMOD - Copy to RXUSERFN MODULE ATTACH FCP Subchannel (CH ID) to CMS machine 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 Mark Pace Sent: Monday, November 26, 2007 9:35 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes On Nov 21, 2007 10:48 AM, Steve Wilkins [EMAIL PROTECTED] wrote: SCSIDISC (the SCSI Discovery Tool) is a sample exec which provides target port and LUN information so one can discover the LUN topology which hangs off a System z FCP Subchannel. The help file for the tool (SCSIDISC SAMPHELP) indicates that it is Located on MAINT 194 or 2C2 disk. Regards, Steve. I copied SCSIDISC SAMPEXEC to SCSIDISC EXEC, but when I run it I get - DMSRTL2103E Error in compiled CMS system Rexx file; additional information: 4300 43 SCSIDISC EXEC 587 -- Mark Pace Mainline Information Systems
Re: Questions about LUN DASD volumes
Thanks, John. On Nov 26, 2007 9:47 AM, Romanowski, John (OFT) [EMAIL PROTECTED] wrote: You probably need to find RXSCSIFN SAMPMOD and copy it as RXUSERFN MODULE; SCSIDISC uses it. From SCSIDISC HELPCMS: SETUP - Located on MAINT 194 or 2C2 disk Find SCSIDISC SAMPEXEC - Copy to SCSIDISC EXEC Find RXSCSIFN SAMPMOD - Copy to RXUSERFN MODULE You mean I should have read something BEFORE I asked for help. ;-) I looked in the help for syntax, but never saw the part about setup. DOH! Apparently this only works for SCSI devices on a SAN. For testing purposes I'm only setup Point-to-Point. I guess I need to get that changed. -- Mark Pace Mainline Information Systems
Re: Questions about LUN DASD volumes
We are now dealing with file in excess of 54 gig since they can not be contained on a single mod54 minidisk we have been writing to sharefile but have found the perforamce to be dreadfull. Does anyone have performance numbers using SCSI devices on native z/VM, compared to sharefile. If the prefomance of SCSI on a lun was superior to that of sharefile it would solve a major problem here. Romanowski, John (OFT) John.Romanowski@ To oft.state.ny.us IBMVM@LISTSERV.UARK.EDU Sent by: Thecc IBM z/VM Operating System Subject [EMAIL PROTECTED] Re: Questions about LUN DASD ARK.EDU volumes 11/26/2007 09:47 AM Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU You probably need to find RXSCSIFN SAMPMOD and copy it as RXUSERFN MODULE; SCSIDISC uses it. From SCSIDISC HELPCMS: SETUP - Located on MAINT 194 or 2C2 disk Find SCSIDISC SAMPEXEC - Copy to SCSIDISC EXEC Find RXSCSIFN SAMPMOD - Copy to RXUSERFN MODULE ATTACH FCP Subchannel (CH ID) to CMS machine 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 Mark Pace Sent: Monday, November 26, 2007 9:35 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes On Nov 21, 2007 10:48 AM, Steve Wilkins [EMAIL PROTECTED] wrote: SCSIDISC (the SCSI Discovery Tool) is a sample exec which provides target port and LUN information so one can discover the LUN topology which hangs off a System z FCP Subchannel. The help file for the tool (SCSIDISC SAMPHELP) indicates that it is Located on MAINT 194 or 2C2 disk. Regards, Steve. I copied SCSIDISC SAMPEXEC to SCSIDISC EXEC, but when I run it I get - DMSRTL2103E Error in compiled CMS system Rexx file; additional information: 4300 43 SCSIDISC EXEC 587 -- Mark Pace Mainline Information Systems Visit our website at http://www.nyse.com Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Group, Inc.
Re: Questions about LUN DASD volumes
Don't know what 'sharefile' is but read IBM's performance comparison od dasd, fba, scsi on fcp, emulated fba at http://www.vm.ibm.com/perf/reports/zvm/html/iozone.html -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Gerard Graham Sent: Monday, November 26, 2007 9:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes We are now dealing with file in excess of 54 gig since they can not be contained on a single mod54 minidisk we have been writing to sharefile but have found the perforamce to be dreadfull. Does anyone have performance numbers using SCSI devices on native z/VM, compared to sharefile. If the prefomance of SCSI on a lun was superior to that of sharefile it would solve a major problem here. Romanowski, John (OFT) John.Romanowski@ To oft.state.ny.us IBMVM@LISTSERV.UARK.EDU Sent by: The cc IBM z/VM Operating System Subject [EMAIL PROTECTED] Re: Questions about LUN DASD ARK.EDU volumes 11/26/2007 09:47 AM Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU You probably need to find RXSCSIFN SAMPMOD and copy it as RXUSERFN MODULE; SCSIDISC uses it. From SCSIDISC HELPCMS: SETUP - Located on MAINT 194 or 2C2 disk Find SCSIDISC SAMPEXEC - Copy to SCSIDISC EXEC Find RXSCSIFN SAMPMOD - Copy to RXUSERFN MODULE ATTACH FCP Subchannel (CH ID) to CMS machine 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 Mark Pace Sent: Monday, November 26, 2007 9:35 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes On Nov 21, 2007 10:48 AM, Steve Wilkins [EMAIL PROTECTED] wrote: SCSIDISC (the SCSI Discovery Tool) is a sample exec which provides target port and LUN information so one can discover the LUN topology which hangs off a System z FCP Subchannel. The help file for the tool (SCSIDISC SAMPHELP) indicates that it is Located on MAINT 194 or 2C2 disk. Regards, Steve. I copied SCSIDISC SAMPEXEC to SCSIDISC EXEC, but when I run it I get - DMSRTL2103E Error in compiled CMS system Rexx file; additional information: 4300 43 SCSIDISC EXEC 587 -- Mark Pace Mainline Information Systems Visit our website at http://www.nyse.com Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Group, Inc.
Re: Questions about LUN DASD volumes
Thanks, John. I guess I'll have to get some larger 2145 volumes and play around again. I tried SCSIDISC against our big volumes on a 2107, which are of varying sizes between 500GB and 1TB, and didn't notice any negative values. Weird, but I'll mess around with it and see what I can find. Thanks for the heads up. Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY Romanowski, John (OFT) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/26/2007 09:41 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Questions about LUN DASD volumes Eric, large LUN that I referred to was a 957GB LUN in an IBM SVC 2145. reported LUN size (bytes) was correct, but prefixed with a minus sign. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Eric R Farman Sent: Monday, November 26, 2007 9:06 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes How large is large? I can't put my hands on one larger than 70GB at the moment, and it looks fine. Will look for the huge disks tomorrow to try them. As for the fields reported as X, that's due to some kind of I/O error when trying to get a LUN to decribe itself. This sometimes occurs because of an ACL restriction, as some DASD controllers will gladly tell us a LUN exists, but reject any I/O directed at it. In those cases, description I/O such as the SCSI Inquiry or Read Capacity commands will fail, and we cannot fill in that information. Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY Romanowski, John (OFT) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/21/2007 03:49 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Questions about LUN DASD volumes 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 X?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)__ B098 5005076300CA04DA 5100 IBM 2105 F20 10013262 .1785127617216 3900014592 B098 5005076300CA04DA 5101 IBM 2105 F20 10113262 .1785127617216 3900014592 B098 5005076300CA04DA 5102 IBM 2105 F20 10213262 .1785127617216 3900014592 B098 5005076300CA04DA 5103 IBM 2105 F20 10313262 .1785127617216 3900014592 B098 5005076300CA04DA 5104 IBM 2105 F20 10413262 .178512 19532817936 B098 5005076300CA04DA 5105 IBM 2105 F20 10513262 .178512 19532817936 B098 5005076300CA04DA 5106 IBM 2105 F20 10613262 .178512 19532817936 B098 5005076300CA04DA 5107 IBM 2105 F20 10713262 .1785121953152 113824 B098 5005076300CA04DA 5108 IBM 2105 F20 10813262 .1785121953152 113824 B098 5005076300CA04DA 5109 IBM 2105 F20 10913262 .1785121953152 113824 B098 5005076300CA04DA 510A IBM 2105 F20 10A13262 .1785121953152 113824 B098 5005076300CA04DA 510B IBM 2105 F20 10B13262 .1785121953152 113824 Regards, Steve. Steve Wilkins IBM z/VM Development
Re: Questions about LUN DASD volumes
Eric, I found an old SCSDISC report that shows the negative LUN size; here it is, I've omitted some middle columns: These are 8 paths to the same LUN _FCP_CH_ __WWPN__ _LUN_ID_ _VENDOR_ PROD SIZE_(bytes)__ 0200 5005076801102C4C 0010 IBM 2145 -1027570925568 0200 5005076801302C78 0010 IBM 2145 -1027570925568 0201 5005076801202C4C 0010 IBM 2145 -1027570925568 0201 5005076801402C78 0010 IBM 2145 -1027570925568 0202 5005076801202C78 0010 IBM 2145 -1027570925568 0202 5005076801402C4C 0010 IBM 2145 -1027570925568 0203 5005076801102C78 0010 IBM 2145 -1027570925568 0203 5005076801302C4C 0010 IBM 2145 -1027570925568 From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Eric R Farman Sent: Monday, November 26, 2007 10:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes Thanks, John. I guess I'll have to get some larger 2145 volumes and play around again. I tried SCSIDISC against our big volumes on a 2107, which are of varying sizes between 500GB and 1TB, and didn't notice any negative values. Weird, but I'll mess around with it and see what I can find. Thanks for the heads up. Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY Romanowski, John (OFT) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/26/2007 09:41 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Questions about LUN DASD volumes Eric, large LUN that I referred to was a 957GB LUN in an IBM SVC 2145. reported LUN size (bytes) was correct, but prefixed with a minus sign. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Eric R Farman Sent: Monday, November 26, 2007 9:06 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes How large is large? I can't put my hands on one larger than 70GB at the moment, and it looks fine. Will look for the huge disks tomorrow to try them. As for the fields reported as X, that's due to some kind of I/O error when trying to get a LUN to decribe itself. This sometimes occurs because of an ACL restriction, as some DASD controllers will gladly tell us a LUN exists, but reject any I/O directed at it. In those cases, description I/O such as the SCSI Inquiry or Read Capacity commands will fail, and we cannot fill in that information. Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY Romanowski, John (OFT) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/21/2007 03:49 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Questions about LUN DASD volumes 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 X'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)__ B098 5005076300CA04DA 5100 IBM 2105 F20 10013262 .1785127617216 3900014592 B098 5005076300CA04DA 5101 IBM 2105 F20 10113262 .1785127617216 3900014592 B098 5005076300CA04DA 5102 IBM 2105 F20 10213262 .1785127617216 3900014592 B098 5005076300CA04DA 5103 IBM 2105 F20 10313262 .1785127617216 3900014592 B098 5005076300CA04DA 5104 IBM 2105 F20 10413262 .178512 19532817936 B098 5005076300CA04DA 5105 IBM 2105 F20 10513262 .178512 19532817936 B098 5005076300CA04DA 5106 IBM 2105 F20 10613262 .178512 195328
Re: Questions about LUN DASD volumes
I sent the wrong url earlier. This is the correct link about IBM's performance comparison of dasd, fba, scsi on fcp, emulated fba at http://www.vm.ibm.com/perf/reports/zvm/html/520lxd.html -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Gerard Graham Sent: Monday, November 26, 2007 9:57 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes We are now dealing with file in excess of 54 gig since they can not be contained on a single mod54 minidisk we have been writing to sharefile but have found the perforamce to be dreadfull. Does anyone have performance numbers using SCSI devices on native z/VM, compared to sharefile. If the prefomance of SCSI on a lun was superior to that of sharefile it would solve a major problem here. Romanowski, John (OFT) John.Romanowski@ To oft.state.ny.us IBMVM@LISTSERV.UARK.EDU Sent by: The cc IBM z/VM Operating System Subject [EMAIL PROTECTED] Re: Questions about LUN DASD ARK.EDU volumes 11/26/2007 09:47 AM Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU You probably need to find RXSCSIFN SAMPMOD and copy it as RXUSERFN MODULE; SCSIDISC uses it. From SCSIDISC HELPCMS: SETUP - Located on MAINT 194 or 2C2 disk Find SCSIDISC SAMPEXEC - Copy to SCSIDISC EXEC Find RXSCSIFN SAMPMOD - Copy to RXUSERFN MODULE ATTACH FCP Subchannel (CH ID) to CMS machine 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 Mark Pace Sent: Monday, November 26, 2007 9:35 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes On Nov 21, 2007 10:48 AM, Steve Wilkins [EMAIL PROTECTED] wrote: SCSIDISC (the SCSI Discovery Tool) is a sample exec which provides target port and LUN information so one can discover the LUN topology which hangs off a System z FCP Subchannel. The help file for the tool (SCSIDISC SAMPHELP) indicates that it is Located on MAINT 194 or 2C2 disk. Regards, Steve. I copied SCSIDISC SAMPEXEC to SCSIDISC EXEC, but when I run it I get - DMSRTL2103E Error in compiled CMS system Rexx file; additional information: 4300 43 SCSIDISC EXEC 587 -- Mark Pace Mainline Information Systems Visit our website at http://www.nyse.com Note: The information contained in this message and any attachment to it is privileged, confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to the message, and please delete it from your system. Thank you. NYSE Group, Inc.
Re: Questions about LUN DASD volumes
During our TSM Linux POC test, we used SCSIDISC but regretted that it only reports DASD, no TAPEs. So, at this time it is the name could be SCSIDISK as well ;-) 2007/11/21, Romanowski, John (OFT) [EMAIL PROTECTED]: 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 X's -- Kris Buelens, IBM Belgium, VM customer support
Re: Questions about LUN DASD volumes
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 X¹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)__ B098 5005076300CA04DA 5100 IBM 2105 F20 10013262 .178 5127617216 3900014592 B098 5005076300CA04DA 5101 IBM 2105 F20 10113262 .178 5127617216 3900014592 B098 5005076300CA04DA 5102 IBM 2105 F20 10213262 .178 5127617216 3900014592 B098 5005076300CA04DA 5103 IBM 2105 F20 10313262 .178 5127617216 3900014592 B098 5005076300CA04DA 5104 IBM 2105 F20 10413262 .178 512 195328 17936 B098 5005076300CA04DA 5105 IBM 2105 F20 10513262 .178 512 195328 17936 B098 5005076300CA04DA 5106 IBM 2105 F20 10613262 .178 512 195328 17936 B098 5005076300CA04DA 5107 IBM 2105 F20 10713262 .178 5121953152 113824 B098 5005076300CA04DA 5108 IBM 2105 F20 10813262 .178 5121953152 113824 B098 5005076300CA04DA 5109 IBM 2105 F20 10913262 .178 5121953152 113824 B098 5005076300CA04DA 510A IBM 2105 F20 10A13262 .178 5121953152 113824 B098 5005076300CA04DA 510B IBM 2105 F20 10B13262 .178 5121953152 113824 Regards, Steve. Steve Wilkins IBM z/VM Development
Re: Questions about LUN DASD volumes
Speaking with the OPEN guys, the major problem say have when they restore on a D/R site is to exactly map their requirements to what they find in t he new DASD array. So the problem appears when they want to restore a group of LUNs (meta volume) to preserve data coherence. Does a CP cmd exist to get this info. I presume the query edev is for LUN only ? Alain Benveniste
Re: Questions about LUN DASD volumes
Alain, There is: CP QUERY EDEVICE But I'm not sure that will give you what you are looking for ... Especially since you would have first had to have done a SET EDEVICE for the LUN ... which would mean the devices are attached and active on z/VM. JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alain Benveniste Sent: Wednesday, November 21, 2007 10:08 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes Speaking with the OPEN guys, the major problem say have when they restore= on a D/R site is to exactly map their requirements to what they find in t= he new DASD array. So the problem appears when they want to restore a group = of LUNs (meta volume) to preserve data coherence. Does a CP cmd exist to get this info. I presume the query edev is for LUN= only ? Alain Benveniste
Re: Questions about LUN DASD volumes
SCSIDISC (the SCSI Discovery Tool) is a sample exec which provides target port and LUN information so one can discover the LUN topology which hangs off a System z FCP Subchannel.The help file for the tool (SCSIDISC SAMPHELP) indicates that it is Located on MAINT 194 or 2C2 disk. Regards, Steve. Steve Wilkins IBM z/VM Development Alain Benveniste [EMAIL PROTECTED] E.FR To Sent by: The IBM IBMVM@LISTSERV.UARK.EDU z/VM Operating cc System [EMAIL PROTECTED] Subject ARK.EDU Re: Questions about LUN DASD volumes 11/21/2007 10:07 AM Please respond to The IBM z/VM Operating System [EMAIL PROTECTED] ARK.EDU Speaking with the OPEN guys, the major problem say have when they restore on a D/R site is to exactly map their requirements to what they find in the new DASD array. So the problem appears when they want to restore a group of LUNs (meta volume) to preserve data coherence. Does a CP cmd exist to get this info. I presume the query edev is for LUN only ? Alain Benveniste
Re: Questions about LUN DASD volumes
Ahh ... yes ... I forgot about the SCSI sniffer :-) JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Steve Wilkins Sent: Wednesday, November 21, 2007 10:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes SCSIDISC (the SCSI Discovery Tool) is a sample exec which provides target port and LUN information so one can discover the LUN topology which hangs off a System z FCP Subchannel. The help file for the tool (SCSIDISC SAMPHELP) indicates that it is Located on MAINT 194 or 2C2 disk. Regards, Steve. Steve Wilkins IBM z/VM Development Inactive hide details for Alain Benveniste [EMAIL PROTECTED]Alain Benveniste [EMAIL PROTECTED] Alain Benveniste [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/21/2007 10:07 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Questions about LUN DASD volumes Speaking with the OPEN guys, the major problem say have when they restore on a D/R site is to exactly map their requirements to what they find in the new DASD array. So the problem appears when they want to restore a group of LUNs (meta volume) to preserve data coherence. Does a CP cmd exist to get this info. I presume the query edev is for LUN only ? Alain Benveniste
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)__ B098 5005076300CA04DA 5100 IBM 2105 F20 10013262 .178 5127617216 3900014592 B098 5005076300CA04DA 5101 IBM 2105 F20 10113262 .178 5127617216 3900014592 B098 5005076300CA04DA 5102 IBM 2105 F20 10213262 .178 5127617216 3900014592 B098 5005076300CA04DA 5103 IBM 2105 F20 10313262 .178 5127617216 3900014592 B098 5005076300CA04DA 5104 IBM 2105 F20 10413262 .178 512 19532817936 B098 5005076300CA04DA 5105 IBM 2105 F20 10513262 .178 512 19532817936 B098 5005076300CA04DA 5106 IBM 2105 F20 10613262 .178 512 19532817936 B098 5005076300CA04DA 5107 IBM 2105 F20 10713262 .178 5121953152 113824 B098 5005076300CA04DA 5108 IBM 2105 F20 10813262 .178 5121953152 113824 B098 5005076300CA04DA 5109 IBM 2105 F20 10913262 .178 5121953152 113824 B098 5005076300CA04DA 510A IBM 2105 F20 10A13262 .178 5121953152 113824 B098 5005076300CA04DA 510B IBM 2105 F20 10B13262 .178 5121953152 113824 Regards, Steve. Steve Wilkins IBM z/VM Development
Re: Questions about LUN DASD volumes
FYI, SCSIDISC requires a LUN zero exist and be accessible in each storage controller to be scanned. Assuming non-NPIV, If one's using IBM San Volume Controller then consider having the very first LUN (LUN ) that each of its I/O Groups maps to your host (mainframe) be a minimal size LUN that will exist but not normally be used. That way its always free for SCSIDISC's need. Otherwise if LUN zero's in use by z/VM CP or a linux guest, SCSIDISC can't use it to scan the LUN's storage controller (SVC I/O Group). 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 10:49 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Questions about LUN DASD volumes SCSIDISC (the SCSI Discovery Tool) is a sample exec which provides target port and LUN information so one can discover the LUN topology which hangs off a System z FCP Subchannel. The help file for the tool (SCSIDISC SAMPHELP) indicates that it is Located on MAINT 194 or 2C2 disk. Regards, Steve. Steve Wilkins IBM z/VM Development Inactive hide details for Alain Benveniste [EMAIL PROTECTED]Alain Benveniste [EMAIL PROTECTED] Alain Benveniste [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 11/21/2007 10:07 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: Questions about LUN DASD volumes Speaking with the OPEN guys, the major problem say have when they restore on a D/R site is to exactly map their requirements to what they find in the new DASD array. So the problem appears when they want to restore a group of LUNs (meta volume) to preserve data coherence. Does a CP cmd exist to get this info. I presume the query edev is for LUN only ? Alain Benveniste
Re: Questions about LUN DASD volumes
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 X'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)__ B098 5005076300CA04DA 5100 IBM 2105 F20 10013262 .1785127617216 3900014592 B098 5005076300CA04DA 5101 IBM 2105 F20 10113262 .1785127617216 3900014592 B098 5005076300CA04DA 5102 IBM 2105 F20 10213262 .1785127617216 3900014592 B098 5005076300CA04DA 5103 IBM 2105 F20 10313262 .1785127617216 3900014592 B098 5005076300CA04DA 5104 IBM 2105 F20 10413262 .178512 19532817936 B098 5005076300CA04DA 5105 IBM 2105 F20 10513262 .178512 19532817936 B098 5005076300CA04DA 5106 IBM 2105 F20 10613262 .178512 19532817936 B098 5005076300CA04DA 5107 IBM 2105 F20 10713262 .1785121953152 113824 B098 5005076300CA04DA 5108 IBM 2105 F20 10813262 .1785121953152 113824 B098 5005076300CA04DA 5109 IBM 2105 F20 10913262 .1785121953152 113824 B098 5005076300CA04DA 510A IBM 2105 F20 10A13262 .1785121953152 113824 B098 5005076300CA04DA 510B IBM 2105 F20 10B13262 .1785121953152 113824 Regards, Steve. Steve Wilkins IBM z/VM Development
Questions about LUN DASD volumes
Hi all, We have a new requirement where we would like to be able to backup/restor e LUN DASD from open for a test. OPEN is an other world for me. So I would like to know how I should code LUN DASD (METALUN ?) into IOCP and how a MDISK would look like too. A copy/paste would be great. And what q da xxx details would show ? Thanks Alain Benveniste Paris, France
Re: Questions about LUN DASD volumes
Alain, Mini disks are defined in your IOCDS/IODF as though they were real DASD devices. Mini disks will appear as 3390's to your operating system running in a virtual machine. Of course, their size/capacity will be that of the mini disk definition. If by LUN DASD you are referring to iSCSI devices, please review the attachment to this e-mail. It covers all of the topics relating to z/VM EDEV support. Good luck. HITACHI DATA SYSTEMS Raymond E. Noal Senior Technical Engineer Office: (408) 970 - 7978 -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alain Benveniste Sent: Friday, November 09, 2007 11:27 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Questions about LUN DASD volumes Hi all, We have a new requirement where we would like to be able to backup/restore LUN DASD from open for a test. OPEN is an other world for me. So I would like to know how I should code LUN DASD (METALUN ?) into IOCP and how a MDISK would look like too. A copy/paste would be great. And what q da xxx details would show ? Thanks Alain Benveniste Paris, France
Re: Questions about LUN DASD volumes
Alain, I think the only way you could do this from z/VM (the mainframe) is if the LUN DASD was configured as FBA devices ... if it's native Linux, I think the only way it can be accessed on the mainframe is by dedicating it to a z/Linux system. JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Alain Benveniste Sent: Friday, November 09, 2007 02:27 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Questions about LUN DASD volumes Hi all, We have a new requirement where we would like to be able to backup/restor= e LUN DASD from open for a test. OPEN is an other world for me. So I would like to know how I should code LUN DASD (METALUN ?) into IOCP and how a MDISK would look like too. A copy/paste would be great. And what q da xxx details would show ? Thanks Alain Benveniste Paris, France
