Re: Sharing ZFS file b/w two systems [not sysplex]

2013-07-27 Thread Shameem .K .Shoukath
Thanks john,
 I also read about RECATALOG parm. The restriction is if the HLQ is not SYS1 
then the catalog name must match for RECATALOGing.

I made a plan based on this.

1)make the ZFS filesystem as READONLY in SYS1  AUTOMOVE=YES
2)Define a UCAT in SYS1 same name as the MCAT of SYS2 (since my HLQ for ZFS is 
not SYS1)
3)Define cluster with same name of original ZFS in SYS1 with RECATALOG.
4)MOUNT ZFS FS as R/W in SYS1
5)APPLY maintenance, then unmount.
6)delete Cluster with noscratch. Delete the UCAT (or keep it for future)
7)Make the FS R/W in SYS1

Going to try this on a sample ZFS on Monday


 



Thanks and Regards
Shameem K Shoukath
 
 




 From: John McKown john.archie.mck...@gmail.com
To: IBM-MAIN@LISTSERV.UA.EDU 
Sent: Friday, July 26, 2013 6:00 PM
Subject: Re: Sharing ZFS file b/w two systems [not sysplex]
 

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 
shameemkshouk...@yahoo.com 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 lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Sharing ZFS file b/w two systems [not sysplex]

2013-07-26 Thread Shameem .K .Shoukath
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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Re: Sharing ZFS file b/w two systems [not sysplex]

2013-07-26 Thread Don Williams
It's been fair number of years ago, but I've ran into difficulties even when
the zFS was mounted readonly on all other systems.  I was told by IBM
support that any zFS mounted READ/WRITE in one sysplex, must not be mounted
at all in any other sysplex.  IIRC, it had something to do with being a
journaled file system.

Don

 -Original Message-
 From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
 On Behalf Of John McKown
 Sent: Friday, July 26, 2013 12:01 PM
 To: IBM-MAIN@LISTSERV.UA.EDU
 Subject: Re: Sharing ZFS file b/w two systems [not sysplex]
 
 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 
 shameemkshouk...@yahoo.com 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 lists...@listserv.ua.edu 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN