Does FILE CONTROL thus have the same exposure to a file being changed 'under the
covers' as a minidisk has, possibly causing an error for the other users?
Is there something similar to the minidisk trick of:
copyfile new1 version a pseudo1 name k (noupdir
copyfile new2 version a pseudo2 name k (noupdir
rename old1 version k save1 version k (noupdir
rename old2 version k save2 version k (noupdir
rename pseudo1 name k old1 version k (noupdir
rename pseudo2 name k old2 version k
(hope I got that right!) to avoid impacting other users?
Les
Alan Altmark wrote:
On Monday, 03/21/2011 at 05:50 EDT, clifford jackson
<cliffordjackson...@msn.com> wrote:
What are the major differences between filecontrol and directorycontrol
in a
SFS structure
DIRECTORY CONTROL directories have two important attributes:
1. You don't seen any changes to any files until you re-ACCESS the
directory.
2. Authority for the files resides at the directory level (DIRREAD,
DIRWRITE). That is, all files have the same access rights, matching the
access rights of the directory. You just grant access to the directory
and the person has those rights to all the files. If there are new files,
they automatically get access, but only after they re-access the
directory.
The above is called "Access-to-Release Consistency" and mimics the way a
minidisk works.
FILE CONTROL directories have separate file and directory access rights,
and any changes to a file are visible to others as soon as the file is
closed.
Alan Altmark
z/VM and Linux on System z Consultant
IBM System Lab Services and Training
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott
