You no longer need a separate MCAT for each system. You need to ensure that
system specific datasets are unique (e.g. using &SYSNAME in the DSN for
logrec). As for indirect volume reference for shared files, that too is allowed
and very useful (E.g. SYS1.LINKLIB) In the old days, I had to rename
I agree that one would not use indirect volume reference for any file that is
shared across LPARs. This would only be for files that are unique for each LPAR.
Jon… I thought being SYS1 removed the catalog ownership restriction. Each LPAR
has its own master catalog.
-
http://pic.dhe.ibm.com/infocenter/zos/v1r12/index.jsp?topic=%2Fcom.ibm.zos.r12.idac100%2Fdefzfs.htm
http://www-01.ibm.com/support/docview.wss?uid=isg1OA34695
Specific references in Define Cluster Required and Optional parameters in z/OS
DFSMS Access Method Services for Catalogs > DEFINE CLUSTER
It's not a requirement that it be a SYS1 dataset. There are advantages to it
being SYS1 such as you know immediately it is in the mastercat and is covered
by SYS1 RACF rules.
Jon Perryman
- Original Message -
> From: Donald Likens
>
> So it must be a SYS1 dataset... Thanks
---
So it must be a SYS1 dataset... Thanks
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
On Wed, 15 Jan 2014 04:18:42 -0600, Donald Likens
wrote:
>Note: The zFS would have been created with a different master catalog. I was
>assuming that SYS1 statement in the entry in the manual meant that it was
>cataloged in the master catalog. Has anyone put the OMVS root ion the SYSRES?
>IF
I have not experimented with this much, since we use SYSRES volser as part of
the filesystem datasetname. But, I'm still trying to fathom if ZFS indirect
volser support would even work in a multisystem sysplex with Sysplex
filesharing? If I have LPAR A on SYSRESA, and LPAR B runni
Note: The zFS would have been created with a different master catalog. I was
assuming that SYS1 statement in the entry in the manual meant that it was
cataloged in the master catalog. Has anyone put the OMVS root ion the SYSRES?
IF so, how did you do it?
Right now the root is read write but someday I plan to make it read-only.
I guess I didn't ask the right question... Let me try again.
If I put a zFS on the SYSRES and recatalog it to use a indirect volume
reference, what needs to be done to IPL from a different SYSRES?
---
EDU
Subject: Re: zFS Indirect volser support
Wouldn't the DELETE NOSCRATCH mark the VVCR as not in a catalog and available
for RECATALOG? Otherwise we couldn't RECATALOG to another UCAT or must it
always be recataloged to the original catalog?
Jon Perryman.
- Original Message
Wouldn't the DELETE NOSCRATCH mark the VVCR as not in a catalog and available
for RECATALOG? Otherwise we couldn't RECATALOG to another UCAT or must it
always be recataloged to the original catalog?
Jon Perryman.
- Original Message -
> From: "Pearce, Colin E"
>
>T he VVDS keeps the n
The VVDS keeps the name of each BCS, that has datasets cataloged on the volume,
in its VSAM Volume Control Record - VVCR. So the DEFINE RECATALOG, will use
the BCS information in the VVDS VVCR, plus the information in the associated
VVR, in order to recatalog the dataset to the correct User Cat
It just dawned on me what you were asking. The VVDS definition should occur
automatically unless you are using some really old MVS version. When you do the
DELETE NOSCRATCH, the data still resides on disk. I suspect that RECATALOG will
use the VVDS data to help recatalog the dataset.
Jon Perrym
I don't understand the quest "How does this really help". I assume you just
want to catalog the zFS datasets with symbolic volume.
I'm guessing you did not define ZFS.ROOT because you say there isn't a VVDS. I
thought that defining a VSAM dataset on a volume would cause the VVDS to be
created.
Is the roof RO or is it RW?
Lizette
-Original Message-
>From: Donald Likens
>Sent: Jan 14, 2014 3:11 PM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: zFS Indirect volser support
>
>OK I already figured out that the following command allows a shop to use
>indirect volser
OK I already figured out that the following command allows a shop to use
indirect volser support for zFS files.
DEFINE CLUSTER (NAME(ZFS.ROOT) LINEAR VOLUMES(&SYSR1) RECATALOG)
I also figured out that (at least on z/OS R12) that you cannot use a 6
character symbolic and you cannot use **.
16 matches
Mail list logo
