Hi Chris, A nice argument for SFS is that you don’t need to pre-allocate diskspace when a user is created. For minidisks you need to assign a certain amount of space, regardless of the user actually using it. The allowed space can be extended in-flight with the MODIFY command. When a minidisk needs to be extended you need to create a new minidisk. And you can overallocate the SFS space. When users aren't using all of their allowed space it can be used by other users.
You don't need a user in the VM directory in order to create an SFS filespace. Though it might be common practice to enroll a corresponding user in VM anyway, that's up to you if you want or need that. We often enroll a user anyway just to make sure the userid used in the SFS filespace is actually allocated in the VM directory. Once an SFS filespace is created the top level directory is created. So once VMWW2 is created (in this case the user is enrolled in VMPSFS with 5000 blocks space) you can access the directory "VMPSFS:VMWW2." (note the point at the end to denote you are accessing a directory). The FORCERW option is to ensure you get the filespace in write mode. Met vriendelijke groet/With kind regards/Mit freundlichen Grüßen, Berry van Sleeuwen -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Will, Chris Sent: Friday, November 06, 2015 2:30 PM To: [email protected] Subject: Re: Change common service filepool name from POOL1 to VMPSFS - New z/VM cookbook questions SFS is new for us. I have been happy using regular minidisks in the past but if there is a good reason to start looking at SFS (better for SSI, LGR, DR, etc.), we will try to get up to speed on it. Another question about the redbook is creation of the files under VMWW2. Would you not have to define a userid VMWW2 and create a directory prior to accessing the directory? Here is the portion of the redbook in question. ===> enroll user vmww2 vmpsfs ( blocks 5000 << there is no step in the book to create a user. ===> access vmpsfs:vmww2 z (forcerw << shouldn't there be a step to create the directory? ===> copy VMWW2 VMARC M = = Z ===> erase VMWW2 VMARC M Chris Will This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, Atos’ liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. On all offers and agreements under which Atos Nederland B.V. supplies goods and/or services of whatever nature, the Terms of Delivery from Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly submitted to you on your request.
