I assume that by system zFS you intend to distinguish from user or vendor zFS the same way system dataset distinguishes from user or vendor dataset.
1 - I have put non-system zFS datasets on SMS volumes without problems. I don't think I used indirect support but I don't see why it should make a difference. But if you are going to have multiple copies and different systems sharing the catalog but each with a unique symbol resolving to a different volume, I'm not sure how the BCS and VVDS which point to each other will work when the BCS can be pointing here or there. 2 - In my opinion, the system zFS should be catalogued in the same catalog as the other system datasets it relates to. I think of the root zFS in the same class as LINKLIB and place it in the same catalog. 3 - A minimal SMS usually doesn't have any volumes in the storage groups so you will need to either go beyond minimal or reside on a non-SMS volume. 4 - It may be just me but I never put any "important" system dataset (one that would prevent an IPL from proceeding to the point where I could log in) on an SMS volume. :>: -----Original Message----- :>: From: IBM Mainframe Discussion List [mailto:[email protected]] On :>: Behalf Of Mark Jacobs :>: Sent: Wednesday, January 16, 2013 10:20 AM :>: To: [email protected] :>: Subject: ZFS Questions - Indirect volser support :>: :>: I'm looking to implement indirect volser support for system zFS's and I :>: have a few questions. :>: :>: 1) Am I going to have any heartburn with these datasets residing on an :>: SMS volume (they're extended format)? :>: 2) Should they be cataloged in the master catalog or a user catalog? :>: 3) During our DR activities we start off with a very minimal SMS :>: configuration (or so I'm told), will that be a problem? :>: 4) Is there anything else I should be thinking about/ ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
