I can't answer the question directly, but I'm a big fan of experimenting with "new" VMSES/E commands on a 2nd level test system -- and following the command by entering: FileList * * * (TODAY and looking into every file that changed. (For 100% accuracy, that may require a accessing all of MAINT' s disksn and those in the affected PPF).
It won't show erased files (that could be done with a little pre-cmd and post-cmd inventory of all files on all MAINT's disks, and the affected PPF) . Doing this could even lead to some post-cmd source code analysis to see _why_ things changed. With normal disk backups before the command you'll know EXACTLY what changed, and be able to figure out why, _in a safe environment_. Anything someone replies on the list is subject to their experience, and their understanding of your environment, and their understanding of the question. Empirical proof on a 2nd level system is king! :-) Mike Walter Hewitt Associates ----- Original Message ----- From: "Schuh, Richard" [rsc...@visa.com] Sent: 12/19/2008 09:45 AM PST To: IBMVM@LISTSERV.UARK.EDU Subject: VMFINS DELETE I am getting ready to delete a couple of seldom or never used products from the system. It appears to be straight-forward. A simple 'VMFINS DELETE PPF ppfname' command appears to be all it will take. I cannot let VMFINS attempt to delete the resources as the directory is not, and cannot be, accessible to it. I have a couple of questions: 1. Is it really that simple? 2. What are the gotchas, if any? 3. Will VMFINS try to save a new CMS when it is done? If so, is there some way to prevent it? Regards, Richard Schuh The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
