FWIW, I try to keep both the 190 and 19E pretty much as shipped by IBM. All "public" programs and files (i.e. other vendor products, locally developed programs and files, etc. etc.) all go on a disk accessed by all users via an exit in the SYSPROF EXEC (i.e. in my case they live on PUBLIC 191). This way you don't have to worry about trivial file changes making a LOT more work for you. Don't forget, in order to change a file on either the 190 or 19E you are SUPPOSED to make the changes to the 490 or 49E, test them, and then promote the changes to the 190 or 19E. If you skip this and make your changes directly to the 190/19E they could be OVERLAID (or lost) the next time you do any kind of service that does PUT2PROD and copies the 490/49E to 190/19E.
Consider a local PUBLIC disk and save your self the grief of resizing CMS system minidisks, keeping test/prod CMS disks in synch, and constantly resaving the CMS minidisk FST's in NSS. -Mike -----Original Message----- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rob van der Heij Sent: Monday, May 19, 2008 9:17 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Extension of MAINT 190 (S-DISK) On Mon, May 19, 2008 at 2:47 PM, Fox Blue <[EMAIL PROTECTED]> wrote: > OK thank you, correct. But then I would like to extend the question > with regard of the Y-Disk. Is a simple CMS copy enough or is special > attention Since the Y-disk FST's are also kept in the CMS NSS, you need to save CMS again when you modify the 19E disk. PS I believe other installations have also concluded that flexibility with the 19E is more important than saving a few bytes on FST's and modified SYSPROF not to complain about the non-shared YSTAT. When you frequently change things on the 19E and have to save CMS often as well, you end up with more "pending purge" copies of the NSS and that cost is not justified by the savings. Rob
