Our high level of OMVS has been in a user catalog for quite awhile with no issues. I always rename the OMVS.ROOT and other OMVS datasets that come with a Serverpac to be something like OMVS.ZOS180.ROOT (for z/OS 1.8), so this keeps me out of a duplicate dataset situation. Otherwise, I have run into no issues with this, and it actually makes it easier to not have to MERGECAT datasets to upgrade, etc... A simple CONNECT of the usercatalog and then a DEFALIAS is all you need for an upgrade.
C. Todd Burrell Senior z/OS Systems Programmer ITSO (404) 498-3299 (404) 723-2017 (cell) -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock Sent: Friday, September 07, 2007 11:37 AM To: [email protected] Subject: HFS in master catalog Our HFS datasets are all currently SMS-managed and cataloged in the master catalog. I'm thinking of moving them to a usercat to facilitate OS upgrades. To judge by the IBM-MAIN archives, this seems like a reasonable thing to do. Are there any particular things I need to keep in mind when I do this? Any nasty gotchas to beware of? Thanks, Jon ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
