Hello Kris,
Would you send that newsletter to me too, please? Ed Martin Aultman Health Foundation 330-363-5050 ext 35050 From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Kris Buelens Sent: Tuesday, October 05, 2010 9:55 AM To: [email protected] Subject: Re: SFS - misunderstanding That's something left over from the early SFS days in 1988: one wanted to make SFS as transparently as possible to old programs: old programs check a bit in CMS' disk table (ADT), and if that bit tells "R/W" they suppose they can write to it. Not always so with SFS, maybe you can write to file 1 on a directory, but not to file 2. Therefore: ACCESS of some one else's directory turned the R/W flag off in the ADT. To make usage at all possible: - XEDIT and COPYFILE were changed to check the SFS authority, and not the ADT bit - ERASE and RENAME: if you code a filemode: they continue to check the ADT bit; if you code a dirid: they check the SFS authority of the file. Later was added ACCESS xxx (FORCERW and FORCERW, makes it possible to set the ADT bit they way you want FILELIST and DIRLIST got a READWRITE option. Even later: people (like Rob?) complained that XEDIT and COPYFILE could still overwrite files in a directory accessed as R/O. So was the SET RORESPECT born. I'll send you "VM Newsletter 4" that we sent to the Belgian VM community back in 1995. SFS Auhtorities was the main subject of nr 4. 2010/10/5 Mark Pace <[email protected]> Yes, I am an administrator for the file pool. On Tue, Oct 5, 2010 at 8:13 AM, Frank M. Ramaekers <[email protected]> wrote: Are you the administrator for the file pool? Frank M. Ramaekers Jr. ________________________________ From: The IBM z/VM Operating System [mailto:[email protected]] On Behalf Of Mark Pace Sent: Tuesday, October 05, 2010 7:10 AM To: [email protected] Subject: SFS - misunderstanding I admit that I've always stayed away from SFS. But recently I've decided to use it to share files between VM systems. Here is something I don't understand. I access a SFS, it shows as R/O, yet I can edit and save a file, but then can't erase it?! What am I missing that allows me to edit a file on a R/O accessed SFS? acc vmuser:ddisk. d DMSACR723I D (VMUSER:DDISK.) R/O Ready; T=0.01/0.01 08:09:27 q disk d LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL - DIR D R/O - - 4096 281 - - - xedit test data d I changed and saved the file. Ready; T=0.01/0.01 08:06:08 erase test data d DMSERS037E Filemode D is accessed as read/only Ready(00036); T=0.01/0.01 08:07:33 -- Mark D Pace Senior Systems Engineer Mainline Information Systems _____________________________________________________ This message contains information which is privileged and confidential and is solely for the use of the intended recipient. If you are not the intended recipient, be aware that any review, disclosure, copying, distribution, or use of the contents of this message is strictly prohibited. If you have received this in error, please destroy it immediately and notify us at [email protected]. -- Mark D Pace Senior Systems Engineer Mainline Information Systems -- Kris Buelens, IBM Belgium, VM customer support
