That may have been the original intent; however, customers always find ways to use features that may not have been considered by the designer. If we didn't, VM would have been a conversion tool with a 2 year life span.
If a device is sensed and there is a device present, a VMDBK is built for it regardless of its online/offline status. There may be other blocks created for it as well. Making the device Not_Accepted prevents the sensing of the device and the building of the blocks. It is possible to dynamically add the device later using the DEFINE and SET commands, just as you would a device dynamically added to the LPAR. Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Gregg > Sent: Wednesday, July 14, 2010 9:52 AM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: Devices OFFLINE at IPL > > Isn't Not_accepted/Not_Sensed(unsupported) more to do with > how CP handles devices Dynamically defined/added by a > different LPar(Not_Accepted, specifically)? > > On Wed, Jul 14, 2010 at 12:41 PM, Schuh, Richard > <rsc...@visa.com> wrote: > > Sorry, but there are the intermittent times when we need to > see some of them. When needed, that can be accomplished via > command, without requiring an update to the IOCP or LPAR > Profile. The MVS security people want us to not even be able > to vary them online except in special circumstances; thus, > the Not_Accepted status. More proof that, "All generalities > are wrong, including this one." > > > > Regards, > > Richard Schuh > -- > Gregg Reed > "No Plan, survives execution" >
