OnDemand Users Group

Support Forums => CMOD for z/OS Server => Topic started by: Exit16W on April 11, 2014, 07:16:16 PM

Title: zFS Allocation
Post by: Exit16W on April 11, 2014, 07:16:16 PM
We're starting a POC for CMOD.  Our zOS OAM configuration does not yet access disk.  All our zFS and HFS filesystems are modestly sized and grow via AGGR modestly if required.
After a zFS filesystem is created, is it possible to add a volume and expand the filesystem to the new volume if the filesystem needs more space?  Our POC will use a fraction of the reports in our other repository.  We know there will be a need to size for real produciton, but I'm thinking in advance in order to build the real envornment as best as possible.
Title: Re: zFS Allocation
Post by: Greg Ira on April 14, 2014, 05:05:27 PM
I would suggest identifying the directories you expect to grow and have a separate mount for those.  We have a zFS mount for the OnDemand libraries, mounted as read-only.  Then we have a read-write mount for directories containing configuration files.  Lastly we have separate mounts for directories like TEMP and CACHE so we can unmount/mount larger volumes if need be, especially for temp. For cache, which we don't use a lot, you can specify multiple cache filesystems.  We half heartedly tried enlarging our temp space by adding a volume but couldn't get the mount to span volumes and just ended up defining a single MOD27.