On Wed, 23 May 2007 10:08:56 -0500, Matthew Stitt <[EMAIL PROTECTED]> wrote:
>ZFS is not the issue. HFS has the same restriction. What same restriction? >Hence many shops use a >specific dataset name for them, probably with variable substitution, like >the matching sysres volser in the name. Of course this is assuming the >HFS/ZFS reside on different volumes than the target library set. I've not >tried placing these datasets together on one volume yet. Would be nice to >know if indirect volser cataloging would work. > It works fine for HFS. I used a name like "SYS1.OMVS.ROOT" cataloged to VOLSER(******) or VOLSER(&SYSR2) for years (since non-sms HFS was allowed). See this from my web site / CBT file 434: Setting Up a Shared UNIX Root File HFS http://home.flash.net/~mzelden/mvsfiles/$rootshr.txt I had to change the way we were doing things here when I implemented shared HFS. The root name (and other sysres set HFS files) must be unique for that. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ 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
