Hi Eric, When I do a display of the an alias I receive the following q 7000 HCPQDV040E Device 7000 does not exist Ready(00040); T=0.01/0.01 08:11:59
To me it appears that these devices are not being detected for some reason. The question is why. I will work closely with the HCD people to try to determine this. One thing he has told me is that the base is on MSS 0 while the aliases are on MSS 1. I do not know if that would have any impact or not. We are running on a z196. Regards, Mike -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Eric R Farman Sent: Wednesday, March 30, 2011 3:28 PM To: [email protected] Subject: Re: HyperPAV Alias definitions on DS8700 Alan said: > Instead of querying the control unit, you need to QUERY PAV ALL. HyperPAVs > are not associated with a base device until an I/O is performed, and that > association only lasts for the duration of that I/O. Hence the > failure of > QUERY CU DASD ALIAS to give you anything useful. Instead, HyperPAVs > are in "pools" that are selected by CP for association with a base > device in the same pool. While it is true that the association between base-and-alias only occurs for the duration of an I/O, the Q CU ALIAS command will show the HyperPAV aliases just fine: q dasd details 1580 1580 CUTYPE = 2107-E8, DEVTYPE = 3390-0E, VOLSER = JS1580, CYLS = 71232 CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY -SUBSYSTEM Y Y Y - N N -DEVICE Y - - Y N N DEVICE DETAILS: CCA = 00, DDC = -- DUPLEX DETAILS: -- HYPERPAV DETAILS: BASE VOLUME IN POOL 26 CU DETAILS: SSID = 0227, CUNUM = 1580 q cu 0227 dev DASD CU 0227 DEVICES: 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 158A 158B 158C 158D 158E q cu 0227 al DASD CU 0227 ALIASES: 1586 1587 1588 1589 158A 158B 158C 158D 158E q dasd details 1586 1586 CUTYPE = 2107-E8, DEVTYPE = 3390-0A, VOLSER =, CYLS = 0 CACHE DETAILS: CACHE NVS CFW DFW PINNED CONCOPY -SUBSYSTEM Y Y Y - N N -DEVICE N - - N N N DEVICE DETAILS: CCA = 00, DDC = -- DUPLEX DETAILS: -- HYPERPAV DETAILS: ALIAS VOLUME IN POOL 26 CU DETAILS: SSID = 0227, CUNUM = 1580 Mark mentioned... > The Q DASD DETAILS does not contain the HYPERPAV DETAILS ...snip... > Looks like the device is not even detecting HyperPAV status. This appears to be the case to me as well. A base device is only marked as a base when we find at least one alias that is associated with either the base subchannel (PAV) or the base subchannel's pool (HyperPAV). Until then, the responses you see for Q PAV, Q CU, Q DASD DETAILS, etc., can look like you have described here. If you have the device string defined to HCD, what happens if you query one of the supposed alias subchannels? Perhaps they still need to be varied online? Regards, Eric Eric Farman z/VM I/O Development IBM Endicott, NY ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/ This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
