They are SYS1's but I wasn't sure if Recatalog would work for the linears. That won't be a problem. Thanks
Alan -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John McKown Sent: Thursday, September 02, 2010 8:16 PM To: [email protected] Subject: Re: Another zFS conversion question What is the DSN? If it starts with SYS1, then do a simple DEFINE CLUSTER( - NAME(SYS1.rest.of.the.dsn) - VOL(volser) LINEAR RECATALOG) VSAM datasets which start with SYS1 __can__ be catalogued in multiple catalogs! BTW - so can any PAGESPACE dataset, regardless of DSN high level. If the DSN does not start with SYS1, you might be able to use the catalog MLA (multilevel alias) to point the first two nodes of the DSN to the actual master catalog in which it is already catalogued. E.g. suppose the DSN is OMVS.SOME.ROOT.ZFS. Now, OMVS.SOME must be unique. I.e. you can't alread have OMVS.SOME.ROOT.HFS in your master catalog. DEF ALIAS(NAME(OMVS.SOME) - RELATE(new.master.catalog)) MLA can be from 1 to 4. You can set it with the z/OS operator command: F CATALOG,ALIASLEVEL(n) So you if the DSN is unique within the first 4 nodes, you are golden with this method. If the DSN is not unique, then you are out of luck. On Thu, 2010-09-02 at 18:27 -0500, Schwartz, Alan wrote: > I'm currently running z/OS 1.9 with all HFS files. Our corporate > center delivered my z/OS 1.11 system with all zFS format. Fine. We > can address staying zFS with the upgrade I was applying an SMP usermod > that copies IMS program DFAFMD0 from the RESLIB to one of our lpa > libraries. The apply failed with ALLOCATION FAILED FOR SMPJHOME - > IKJ56228I PATH /zs1bbase/usr/lpp/java/J5.0/ NOT IN CATALOG OR CATALOG > CAN NOT BE ACCESSED. The usermod has no OMVS interaction. I added an > explicit path in my apply job pointing to an alternate ROOT and the > apply worked with nothing in the ELEMENT SUMMARY REPORT showing any > reference to SMPJHOME. On to my real question. > > I tried mounting the 1.11 root on my 1.9 system. With TYPE(HFS) or > TYPE(ZFS) it failed with BPXF135E RETURN CODE 00000081, REASON CODE > EF096055 with is > Description: Error LOCATEing an HFS-compat aggregate. > Action: Ensure that the zFS file system named on the MOUNT command has > the same name as the VSAM Linear Data Set (and the HFS compatibility > mode > > aggregate) that contains the file system. > > > I found that the 1.11 ROOT is not cataloged in my 1.9 master, hence > the mount problem. In the discussions I've followed in IBMMain on zFS > I don't recall one indicating how to catalog one systems zFS linear > files in another systems master catalog. I'll continue looking in the > AMS manual or perhaps other DFSMS manuals but I thought I'd throw this > out there. Should be simple but I haven't found it yet. > > Thanks > > Alan Schwartz > > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- 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
