I've been trying to find this myself. One thing I read is to run "/sbin/dasd_configure 0.0.298 1 0" to bring it online. This is a script that does all the magic in the sysfs file system to enable it. The "1" after the address is to bring it online and the "0" is to not use the diag driver. I haven't yet tried this command, though...
On Fri, 18 Mar 2005 09:09:38 -0800, Wolfe, Gordon W <[EMAIL PROTECTED]> wrote: > I have a different, but related question: > > in SLES8, if I have in my zipl.conf dasd=292-2AF, > and I "hcp link linux5 292 298 mr" > the link is performed (VMSECURE RULES allows the link), and if I immediately > look in /proc/dasd/devices, I show the new 298 disk as active at /dev/dasdg. > I can then mount dasdg and work with it. > > Now, in SLES9 with the same zipl.conf information, > If I do the link "hcp link linux5 292 298 mr" > the link is performed, but the 298 does not appear as active in > /proc/dasd/devices. > > Anyone know what the difference is? Am I missing something? > > "A statesman is a dead politician. Lord knows we need more statesmen!" > --Berkeley Breathed > Gordon Wolfe, Ph.D. Boeing Shared Services Group > Enterprise Servers VM Technical Services 425-865-5940 -- Bruce Hayden IBM Global Services zSeries Linux 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
