You forget the VMSES PARTCAT: I've got entries in VMSES PARTCAT for all the things I store on 19E, even y own code gets a dummy prodid. VMFCOPY can then be used to copy all files of a "prodid". And, I wouldn't be me if I hadn't coded an exec to help with the task: my SESCOMP first compares VMSES PARTCAT with LISTFILE and helps you to add missing entries in VMSES PARTCAT. You do that for the old and new disk. The you can tell SESCOMP to compare the PARTCATs of two minidisks; it produces a list prodids and number of files; PF-keys allow to copy or FILELIST files of a prodid. This way, merging two minidisks is quickly done. Ask and you shall be given.
But, indeed: most products live on a separate minidisk (like GDDM 191, DITTO 191, ...), only stuff that needs to be available to everyone lives on our 19E. Examples: RAC, VMBACKUP, VMTAPE, some local helpfiles. 2008/5/19 David Boyes <[EMAIL PROTECTED]>: >> Thank you for this hint. Well I am also much more in favour to do the >> installation on a separate disks, however in my case IBM install >> instructions of the SDO (Semi-VMSES/E Licenced Products) tell to > install >> it >> on MAINT 19E. > > Save yourself a lot of pain. Don't. Mixing stuff up on the 19E is just a > recipe for a lot of heartache when you have to upgrade. > > We recommend using a separate minidisk for each product and using VMLINK > with a shared NAMES file to access them as needed. Lets you do > indirection and gets you a way to easily catalog who is using which > product and how often it's used. At this point, the small real storage > savings is unlikely to outweigh the amount of time it takes to sort out > what files you need when you do an upgrade. > >> Therefore I do it in the recommended way but only for IBM >> products ;-) > > If there's a feedback form, submit it with the comment that this is a > REALLY bad idea. > -- Kris Buelens, IBM Belgium, VM customer support
