The real problem is that the third-party vendors do not all comply with the standard.
Regards, Richard Schuh > -----Original Message----- > From: The IBM z/VM Operating System > [mailto:ib...@listserv.uark.edu] On Behalf Of Phil Smith III > Sent: Friday, March 05, 2010 5:12 PM > To: IBMVM@LISTSERV.UARK.EDU > Subject: Re: CP's Parm Disks > > Chuckie wrote: > >All CP mods are supposed to be identified via the LOCALMOD > command. If > >SERVICE finds that there are CP local mods, then SERVICE > will rebuild > >the nuc with those mods. If the modules to which local mods > apply are > >hit by IBM service, then SERVICE will warn you and stop. After you > >have resolved any issues [obtained new mods to match the > service level, > >rebuilt them yourself, or ignored it], you mark the mods as > "serviced" > >and restart SERVICE. SERVICE will rebuild the nuc with your > text decks. > > >If you have CP mods that are not managed via LOCALMOD, then SERVICE > >won't know about them, won't monitor the RSU/COR service stream for > >potential conflicts, and won't pull in the text decks. > > Ah...VMVIS lives. > > ...phsiii (ducking quickly, *really* just kidding!) >
