On Tue, 19 Jan 2016 08:33:55 -0600, Bruce Hewson
wrote:
>You do not need to use /Service to perform mainmtenance.
>
>You can mount your maintenance target HFS/ZFS files at ANY mountpoint, just so
>long as your DDDEF PATH statements match.
>
>You could even create mount
I vote for Bruce's method also. This will allow multiple versions (a
maintenance version of current and the next Version release) to be mounted at
the same time. Allows two people or parallel work on both systems.
I even went so far as to write a REXX routine which would create the mount
Hi James
You do not need to use /Service to perform mainmtenance.
You can mount your maintenance target HFS/ZFS files at ANY mountpoint, just so
long as your DDDEF PATH statements match.
You could even create mount points as /IPLVOL - same names as your IPL volume
VOLSER.
Hope that helps
On Mon, 18 Jan 2016 18:32:28 -0500, John Eells wrote:
>the abilities to use SYMBOLICRELATE to point to a user catalog
>... were there
>from its inception many releases ago (well before z/OS V1.13).
Thanks, John. I never noticed the ability to use SYMBOLICRELATE
to point to a user catalog. I see
Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of van der Grijn, Bart (B)
Sent: 18 January 2016 12:35
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cloning a Sysres and ZFS
Hi James,
We clone our sysres (maintained in sandbox) every month to generate IPL volumes
for the Dev and Prod LPARs
-MAIN@LISTSERV.UA.EDU
Subject: Re: Cloning a Sysres and ZFS
To expand on that thought a bit:
- You can name the usercatalog using the volume name.
- You can use SYMBOLICRELATE on DEFINE ALIAS to point to the catalog thusly
named in the master catalog on the production system.
- If you have more
To expand on that thought a bit:
- You can name the usercatalog using the volume name.
- You can use SYMBOLICRELATE on DEFINE ALIAS to point to the catalog
thusly named in the master catalog on the production system.
- If you have more than one volume in your target volume set, you can
On Mon, 18 Jan 2016 09:04:53 -0500, John Eells wrote:
>- You can use SYMBOLICRELATE on DEFINE ALIAS to point to the catalog
>thusly named in the master catalog on the production system.
There used to be a requirement that the alias and the data set name be in
the same catalog. I see in Managing
On Mon, 18 Jan 2016 14:41:32 +, Chambers, James wrote:
>Is there a better way to deal with the HFS or ZFS DDDEFs?
Include the SYSRES VOLSER as part of the dsname. When you
mount it, you can use in the mount specification.
--
Tom Marchant
Hi,
We use a process of cloning on our Dev lpar to create new Sysres before we
apply maintenance, it has worked fine for Zos 1r13 but we only used HFS. We
have started to use ZFS for 2r1 which is fine if the Sysres is for the same
Lpar the clone process is run on but I am now cloning a Sysres
Sent: Monday, January 18, 2016 9:28 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cloning a Sysres and ZFS
Most posts in this thread seem to support the strategy of 'cloning a running
system in order to do maintenance'. For as long as I can remember, we have
pursued the opposite strategy: the ser
t; To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [Bulk] Re: Cloning a Sysres and ZFS
>
> Hi Tom,
>
> We already include it like OMVS.RESPR1.ROOT but the DDDEF only has the
> path. The below shows a DDDEF taken from the apply, it still means I need to
> make sure I got the mount right
, 2016 5:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Cloning a Sysres and ZFS
Hi,
We use a process of cloning on our Dev lpar to create new Sysres before we
apply maintenance, it has worked fine for Zos 1r13 but we only used HFS. We
have started to use ZFS for 2r1 which is fine if the Sysres
a Sysres and ZFS
On Mon, 18 Jan 2016 14:41:32 +, Chambers, James wrote:
>Is there a better way to deal with the HFS or ZFS DDDEFs?
Include the SYSRES VOLSER as part of the dsname. When you mount it, you can use
in the mount specification.
--
Tom March
Tom Marchant wrote:
On Mon, 18 Jan 2016 09:04:53 -0500, John Eells wrote:
- You can use SYMBOLICRELATE on DEFINE ALIAS to point to the catalog
thusly named in the master catalog on the production system.
There used to be a requirement that the alias and the data set name be in
the same
On Mon, 18 Jan 2016 16:03:39 +, Chambers, James
wrote:
>We already include it like OMVS.RESPR1.ROOT but the DDDEF only has the path.
>The below shows a DDDEF taken from the >apply, it still means I need to make
>sure I got the mount right and the ZONEEDIT
16 matches
Mail list logo