You can only do this if the ZFS file is NOT, NOT, NOT currently mount in Read/Write mode on System1.
You cannot access a VSAM file (and a zFS container dataset is a VSAM LINEAR data set) which is not catalogued. If the zFS DSN has a high level node of SYS1, then you _CAN_ simply catalog it in System2's master catalog using a RECATALOG parameter on the DEFINE for it. If it is not SYS1, you can't do this. I don't know why IBM allows this, but they do. Another, strange, possibility is to NFS export the mount point from System1 and then MOUNT the exported filesystem somewhere on System2. But this requires that you have NFS running on both systems. Well, NFS server running on System1 and NFS client running on System2. No, don't ask me how. I know it is possible, but I have some sort of mental block about it because I've never gotten it to work properly. On Fri, Jul 26, 2013 at 9:04 AM, Shameem .K .Shoukath < [email protected]> wrote: > hi, > There are two different systems LPARs on the same box and volumes can be > made online on both sides. > > I have a ZFS file on System1 on VOLUM1 cataloged in master cat and it > belong there. I need the same ZFS file on SYStem 2 temporarily to apply > some maintenance (SMPE). > > What would be the best way to do this? I am trying to avoid import connect > SYS2 mcat catalog to SYS1 master catalog > > any ideas ? > > Thanks > Shameem > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > -- This is a test of the Emergency Broadcast System. If this had been an actual emergency, do you really think we'd stick around to tell you? Maranatha! <>< John McKown ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
