Thanks Kris. I don't think I asked the question you answered. _______________________ Jim Hughes 603-271-5586 "Mainframes. We're back and we're lean, mean, processing machines."
=>-----Original Message----- =>From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On =>Behalf Of Kris Buelens =>Sent: Saturday, January 28, 2006 7:44 AM =>To: [email protected] =>Subject: Re: VM:Secure DASD report VMRSDA => =>DMK was the module prefix for CP in the VM/SP days. DMKRIO contained the =>real device configuration (you can compare it well with an IOCP), you =>assembled it and included it in the CP nucleus. In the VM/XA and first =>VM/ESA releases DMKRIO became HCPRIO. With some VM/ESA release (oh my =>rusty memory - I forgot the release number), HCPRIO became optional, =>SYSTEM CONFIG is now the way to go. => =>Kris, =>IBM Belgium, VM customer support => =>> I am testing out some of the VM:Secure DASD utilities and one of them is =>> behaving oddly. => =>> I issue command VMRSDA ( PRINT NOOVP => =>> I get a report full of warnings like this: =>> VMRSDA023W Minidisk VMSERVU 306 devtype '3390' conflicts with DMKRIO =>> specification: FB-512 (for volume SFS101). => =>> =>> I do not use a DMKRIO, There isn't a DMKRIO on any disk I can find, and =>> I've not used the DMKSRC so I don't think it should care about DMKRIO. =>> All the dasd is 3390. => =>> Then again, maybe I don't understand the report either. => =>> Any advice or assistance is appreciated. => =>> Regards, =>> _______________________ =>> Jim Hughes =>> 603-271-5586 =>> "Mainframes. We're back and we're pissed."
