Thank you all for your response, but it looks as though this one was the winner!!! Special thanks to Mr. Romanowski and yes, the mystery lies within the SCSI_id and just converting that number to hex. Thanks again,
Mark Wiggins University of Connecticut -----Original Message----- From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of Romanowski, John (OFT) Sent: Tuesday, May 25, 2010 10:32 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Mapping an Emulated DASD device to an SVC LUN number The SVC command line command svcinfo lshostvdiskmap might list the information you're looking for. Look online for the manual "IBM TotalStorage SAN Volume ControllerCommand-Line Interface User's Guide" Here's sample output (probably folded across two lines); the SCSI_id column is the LUN's hex id in decimal (decimal 102 below is hex LUN id 0066) svcinfo lshostvdiskmap Z10_P1-T1Linux id name SCSI_id vdisk_id vdisk_name wwpn vdisk_UID 240 Z10_P1-T1Linux 102 186 Z_TZ2BF152_V2 5005076401E2893A 6005076801818076280000000000062F 240 Z10_P1-T1Linux 103 667 Z_TZ2BF152_V3 5005076401E2893A 60050768018180762800000000000633 (the SVC's SCSI_id column is not to be confused with the value given by linux's scsi_id command. I found that prefixing 3 to the SVC's vdisk_UID is the same value returned by linux's scsi_id command)
