On Thu, 5 Jun 2008 08:17:23 -0400, Lizette Koehler <[EMAIL PROTECTED]> wrote:
>I want to thank Mark Jacobs and Mark Zelden and everyone else for their help >both on and off list while I got my hands around the zFS functions in z/OS > You're welcome. >I was able to successfully IPL my z/OS V1.9 Serverpac yesterday with all zFS >files for USS. So I went from all HFS to all zFS without issue so far. > >What I learned from this is that I need to address the naming convention for >these files. Since they are now vsam I need to look at a better way of >naming then other than SYS1.&SYSNAME.OMVS.ETC.NEW and >SYS1.&SYSNAME.OMVS.ETC.OLD. I really liked Mark Jacobs convention of adding >the SYSRES volser to the name to keep them unique and in alignment with the >Sysres volume being IPLd. > That (or similar) was also a requirement for shared HFS (now called shared file system), so I was already doing that. Prior to non-SMS HFS and PDSE it was also a requirement since you can't indirectly catalog SMS controlled data sets. You can't indirectly catalog VSAM (someday?), so you have to do the same thing for zFS now. So I've gone from keeping the OMVS files off the sysres and SMS controlling them with the matching sysres as part of the name, to indirectly cataloging them and putting them on the sysres (set) to once again adding in the sysres name - but at least they are still on the sysres (set). >I next have to understand some other basic concepts like copying them from >one volume to another. Currently I am using FDR with NEWNAME, but I would >like to use something more like copytree or pax. But that will take a bit >more reading and playing on my part. > Why? That would be a logical copy and slow. DASD utility programs like FDR, DFSMSdss and CA-DISK would all be much quicker to move an entire file system. >I will also need to understand how growing the aggregate for a USS file >affects the z/OS USS environment. > I'm not sure what your concern is. It obviously is not an issue for read only file systems (like your sysres zFS files). Many other product "root" files are read only also. For others, if you don't want it to grow, don't specify secondary extents or don't set aggrgrow on. Were you concerned about the same thing with HFS? The difference is that growing with zFS is a little more auto-magic. >The z/OS V1.9 Serverpac USS files took up a bit more than ½ of a 3390 Mod9. >I was hoping to lay two sets down on the same mod9. > Why two? Would you use one for maintenance and another one for a running system? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
