The short form - only DIRC directories may be made eligible for
dataspaces; File control directories may not. You have to enable
specific directories for dataspaces. The dataspace is created when the
first user accesses an enabled directory. As long as at least one user
has access to the directory, the dataspace lives. It is deleted when
there are no users accessing it. There is a 2G limit on the amount of
data that may reside in a dataspace. Finally, the SFS server must be
running in an XC mode machine.
Regards,
Richard Schuh
________________________________
From: The IBM z/VM Operating System
[mailto:[EMAIL PROTECTED] On Behalf Of Gentry, Stephen
Sent: Wednesday, September 17, 2008 6:42 AM
To: [email protected]
Subject: SFS and DATASPACE
Whilst looking through a recent version of the VM Quick
Reference manual, I came across a QUERY DATASPACE command. We use DB2
and SFS pools so the dataspace part got my attention. I know both use
DATASPACE's so, I paused to check out the command. In this case, the
command applies to SFS related stuff. I issued a Q DATASPACE on our
existing pools and was a little surprised to find out that none of our
pools were using DATASPACE's. So, this got me more curious, and I did
some reading in the SFS manual. I have all the correct entries in the
user directory for my SFS servers.
One of my assumptions is/was that VM and/or SFS will
automatically load "stuff" into dataspaces. After doing some reading, I
don't think it does, I have to tell SFS to put directories into a
DATASPACE. The manual recommends that SFS pools/sub-pools that are
rarely updated, are good candidates.
So, could someone clarify a little on this subject?
Thanks,
Steve
