ame Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Mike Cairns
> Sent: 17 February, 2017 16:24
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: maintaining PARMLIBs over several sysplexes
>
> Hi all - it's been a long time since I posted a question here, look
TCPIP, JES,
SA, etc).
And then there's Omegamon... Who knows what's what there...
Bart
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mike Cairns
Sent: Friday, February 17, 2017 10:24 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject:
Hey there mate,
As you already know my current customer's process, I will talk about a
previous experience that applies to the scenario mentioned.
Customer had 3 Parallel Sysplexes:
- SYSPLEX A w/ 4 LPARs (3 prod/1 test) => 3 production systems used shared
SYS1.PARMLIB. Test system had its own PA
One shop I was at we only had 2 parmlibs. One shipped by IBM and the other
maintained by the MVS group.
The one maintained by the MVS Group managed 36 images and 16 plexes at the
time. So the suffixes were very important.
XX all plexes
X1 Specific to LPAR1 in a plex
X2 Specific to LPAR2
bruary 17, 2017 10:59 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: EXTERNAL: Re: maintaining PARMLIBs over several sysplexes
We have a Sandbox system in it's own sysplex and a primary sysplex with two
LPARS. Each LPAR has it's own SYS1.PARMLIB, it used to share and they used the
LPAR # as part of
98
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mike Cairns
Sent: Friday, February 17, 2017 10:24 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: maintaining PARMLIBs over several sysplexes
Hi all - it's been a long time since I p
only one sysplex here sorry, but almost the same setup as Allan
SYS1.plexname.PARMLIB - for all members, common and LPAR specific using
&SYSCLONE members for each lpar part of migration - user modified parms of
IBM's parms
SYS1.PARMLIB - EMPTY on the SYSRES automatically concatinated at IPL time
SYS1.LPAR.PARMLIB (unique to this LPAR in plex. Never moves).
SYS1.PARMLIB (common to all LPARS in plex. Never moves).
SYS1.IBM.PARMLIB (on sysres for all LPARS in plex. Changes w/IBM maint.
Always moves)
Synchronization/promotion between Plexes is an exercise in change control.
Behalf Of Mike Cairns
> Sent: Friday, February 17, 2017 8:24 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: maintaining PARMLIBs over several sysplexes
>
> Hi all - it's been a long time since I posted a question here, looking
> forward to
> hearing from you all.
>
> Qu
Hi all - it's been a long time since I posted a question here, looking forward
to hearing from you all.
Question about your local policy/practice:
When faced with the task of maintaining multiple PARMLIBS over a few related
sysplexes (sandpit, development, production), do you:
Prefer to try an
10 matches
Mail list logo
