How I would do it:
are you sharing the same master catalog?
if no, then simply recatalog the datasets in the new master using either
VOL(&SYSR1) or VOL(******)
if YES, you are sharing the same master catalog, then
Make the two systems either use a different IEASYMnn member in PARMLIB.
There are at least 3 methods:
1) Create a system unique PARMLIB, specified in the LOADnn member,
2) if you don't have a system unique PARMLIB, then select a different
LOADnn member on
on the HMC IPL screen or,
3) use the same LOADnn parm, but select a different set of parameters
(especially a
different IEASYMnn value) based on the LPARNAME. This only works if you
have separate LPARs
for each system and are consistent in IPLing each system in its own,
unique, LPAR.
In any case, in the IEASYMnn member used by the source SYSRES, set
&SYSRS2='&SYSRS1(1:5).2'
in the IEASYMnn member used by the target SYSRES, set
&SYSRS2='&SYSRS1'
This makes the datasets catalogued to &SYSRS2 use the correct volser. Yes,
&SYSRS1 and &SYSRS2 can have the same value. It may be confusing to some, so
clearly document why &SYSRS2 is what it is. I would do that as a comment in the
IEASYMnn member.
--
John McKown
Systems Engineer IV
IT
Administrative Services Group
HealthMarkets(r)
9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mck...@healthmarkets.com * www.HealthMarkets.com
Confidentiality Notice: This e-mail message may contain confidential or
proprietary information. If you are not the intended recipient, please contact
the sender by reply e-mail and destroy all copies of the original message.
HealthMarkets(r) is the brand name for products underwritten and issued by the
insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance
Company(r), Mid-West National Life Insurance Company of TennesseeSM and The
MEGA Life and Health Insurance Company.SM
> -----Original Message-----
> From: IBM Mainframe Discussion List
> [mailto:IBM-MAIN@bama.ua.edu] On Behalf Of Jake anderson
> Sent: Monday, April 09, 2012 10:40 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: Coding IEASYMxx
>
> Hi,
>
> Apology for not being precise. Here I am trying to understand
> about SYSRES
> cloning, so I have referred the Currently Running SYSRES as
> source SYSRES
> and Target Volume specifies as the Volume Which Would be used during
> DFSMSdss SYSRES cloning.
>
> This volumes are not SMS managed.
>
> On Tue, Apr 10, 2012 at 9:05 AM, retired mainframer <
> retired-mainfra...@q.com> wrote:
>
> > We need to get the terminology straight first. What do you
> mean by source
> > SYSRES and target SYSRES? Is source the IPL volumes and
> target the volume
> > holding the SMPE target datasets? Or are you using
> ServerPac terminology?
> >
> > BTW, are any of these volumes SMS managed?
> >
> > :>: -----Original Message-----
> > :>: From: IBM Mainframe Discussion List
> [mailto:IBM-MAIN@bama.ua.edu] On
> > :>: Behalf Of Jake anderson
> > :>: Sent: Monday, April 09, 2012 8:20 PM
> > :>: To: IBM-MAIN@bama.ua.edu
> > :>: Subject: Re: Coding IEASYMxx
> > :>:
> > :>: Hi,
> > :>:
> > :>: Seasons Greeting !!
> > :>:
> > :>: One curious question is that if the Two source SYSRES
> volumes are in
> > :>: seperate MOD-3 volumes, but the Target SYSRES Volume is
> initialized
> > :>: using
> > :>: MOD-9. In this scenario how do make use of the SYMBOLIC
> parameter when
> > :>: two
> > :>: Source SYSRES volumes(MOD-3) are copied to Single
> SYSRES volume(mod-9).
> >
> >
> ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
> >
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
>
>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
