Re: Hardware upgrade z13 to z14....Yikes

[fred glenlake]

Hi Jesse,

From what I understand the current plan to be as of typing of this response, 
the plan is to merge/move the lpars from the z13's to the z14.   There is no 
plan to collapse lpars into smaller number of lpars so no need to break out the 
abacus and slide rules to figure out workloads that need to merge and all that 
mess.   Those are my current marching orders and I am working towards that.   
Having said that a couple of weeks ago the marching orders were build a new 
sysplex, then last week it was upgrade from a single z13 to a z14 and this week 
it has morphed into merge/move all lpars from the two z13's into one z14.   The 
beauty of management directions and the right to change their minds 

Fred G.


From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Jesse 1 Robinson <jesse1.robin...@sce.com>
Sent: March 1, 2018 12:32 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Hardware upgrade z13 to z14Yikes

I'm not clear on the scope of 'merging'. If you are just moving LPARs wholesale 
from two CECs to one CEC, it should not be too complicated. In particular, if 
you're careful, there should be minimal impact on users.

If you're consolidating LPARs, then you're in a whole new ballgame. That 
requires a great deal of planning and preparation.

In either case, you have to choose between push-pull and 'incorporation'. In 
the latter case, you add the new CEC into your configuration and move things 
gradually, then remove the old CEC. In the former case, you have to deal with a 
big bang event. Keep in mind a back-out plan in case the new configuration 
falls horribly flat. I've come over the years to prefer a 'fix forward' 
strategy that determines to correct problems and move on. Nevertheless you 
could encounter a problem so severe that the business would not put up the 
ensuing outage.

So many variables.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of fred glenlake
Sent: Thursday, March 01, 2018 6:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Hardware upgrade z13 to z14Yikes

Hi Chuck and list members,

I would be interested in knowing once you figure out the cause.   My upgrade is 
actually much more complicated that first presented.   We are going from two 
z13's with about 6 lpars on each to one z14 so not only are we upgrading we are 
merging as well just to make things more interesting.

We are going to run into duplicate definitions for channels, devices, etc. that 
we will need to rectify when we do the odd 30 minutes of planningHa.   The 
new z14 came with of course other new hardware HMC, routers, etc.   I 
personally have not had the experience of gluing two into one, all of the 
upgrades I have worked on have been one for oneup until now.

I would be interested in hearing if anyone else has merged two to one or three 
to one and their experiences.

FredG.


From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Chuck Kreiter <kreiter_ibm-m...@twc.com>
Sent: March 1, 2018 8:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Hardware upgrade z13 to z14Yikes

We recently did an upgrade to z14's and have seen some unexplained problems.
It appears (unconfirmed as of yet, but should be soon) to be related to some CA 
products.  We should have confirmation later today or tomorrow.  Our upgrade 
was z12's to z14's and we are running z/OS 2.2.  If I get confirmation, I'll 
pass along more details.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of fred glenlake
Sent: Monday, February 26, 2018 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Hardware upgrade z13 to z14Yikes

Hi List,

My management must be in line to cash in on performance bonuses because they
have decreed we will upgrade our z13's to z14's in 90 days.   This was a
total out of left field surprise, perhaps our hardware vendor had a sale on for 
"Presidents Day", right next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots
to consider and read which I do not mind.   Wondered if any list members had
already moved to z14's and could share any land mines they encountered 
upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware
wise we drop the new CEC's next to the existing ones.   Hook them up to
power, HMC's, etc.  Then grab a couple of cables from existing CEC's for
DASD and Tape, swing them over.   Use the existing IOCP and IOCDS as the
basis of the new IOCP/IOCDS, update serial numbers, models, etc.  Then bring up 
our sysprog lpar on the new CEC, get that 

Re: Hardware upgrade z13 to z14....Yikes

[Jesse 1 Robinson]

I'm not clear on the scope of 'merging'. If you are just moving LPARs wholesale 
from two CECs to one CEC, it should not be too complicated. In particular, if 
you're careful, there should be minimal impact on users. 

If you're consolidating LPARs, then you're in a whole new ballgame. That 
requires a great deal of planning and preparation. 

In either case, you have to choose between push-pull and 'incorporation'. In 
the latter case, you add the new CEC into your configuration and move things 
gradually, then remove the old CEC. In the former case, you have to deal with a 
big bang event. Keep in mind a back-out plan in case the new configuration 
falls horribly flat. I've come over the years to prefer a 'fix forward' 
strategy that determines to correct problems and move on. Nevertheless you 
could encounter a problem so severe that the business would not put up the 
ensuing outage.

So many variables.  

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of fred glenlake
Sent: Thursday, March 01, 2018 6:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Hardware upgrade z13 to z14Yikes

Hi Chuck and list members,

I would be interested in knowing once you figure out the cause.   My upgrade is 
actually much more complicated that first presented.   We are going from two 
z13's with about 6 lpars on each to one z14 so not only are we upgrading we are 
merging as well just to make things more interesting.

We are going to run into duplicate definitions for channels, devices, etc. that 
we will need to rectify when we do the odd 30 minutes of planningHa.   The 
new z14 came with of course other new hardware HMC, routers, etc.   I 
personally have not had the experience of gluing two into one, all of the 
upgrades I have worked on have been one for oneup until now.

I would be interested in hearing if anyone else has merged two to one or three 
to one and their experiences.

FredG.


From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Chuck Kreiter <kreiter_ibm-m...@twc.com>
Sent: March 1, 2018 8:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Hardware upgrade z13 to z14Yikes

We recently did an upgrade to z14's and have seen some unexplained problems.
It appears (unconfirmed as of yet, but should be soon) to be related to some CA 
products.  We should have confirmation later today or tomorrow.  Our upgrade 
was z12's to z14's and we are running z/OS 2.2.  If I get confirmation, I'll 
pass along more details.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of fred glenlake
Sent: Monday, February 26, 2018 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Hardware upgrade z13 to z14Yikes

Hi List,

My management must be in line to cash in on performance bonuses because they
have decreed we will upgrade our z13's to z14's in 90 days.   This was a
total out of left field surprise, perhaps our hardware vendor had a sale on for 
"Presidents Day", right next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots
to consider and read which I do not mind.   Wondered if any list members had
already moved to z14's and could share any land mines they encountered 
upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware
wise we drop the new CEC's next to the existing ones.   Hook them up to
power, HMC's, etc.  Then grab a couple of cables from existing CEC's for
DASD and Tape, swing them over.   Use the existing IOCP and IOCDS as the
basis of the new IOCP/IOCDS, update serial numbers, models, etc.  Then bring up 
our sysprog lpar on the new CEC, get that one going, update and fix
software keys/licenses, issues with first IPL's on new CEC, etc.   Once all
the work is done in terms of getting ready for the rest of the lpars, then go 
for the big bang one weekend.  Bring down the rest of the lpars, drop the
cables, swing over to new CEC, hook up and IPL remaining lpars.   Assuming
no phat thumb checks it should work.  Of course there are a ton of 
considerations to review and check, coupling facility stuff, software stuff,
compatibility maintenance, etc.   However all things being equal I am
thinking this approach is likely the safest in terms of risk avoidance and
getting this done with the 90 days.   We could go the move one lpar at a
time route but that would mean more work and it would take longer especially 
with our change management processes (bless their little hearts).

Any alternate suggestions or comments would be appreciated as I am sure there 
will still be a few land mines with my name on them waitin

Re: Hardware upgrade z13 to z14....Yikes

[Feller, Paul]

Well we did 2 zEC12s to one z13 last summer.  In our case we did not have to 
move all the lpars over in one weekend.  Also both CECs had been in the same 
sysplex so no duplicate datasets, devices or other stuff.  Our big issue was 
software contracts.  The one zEC12 was small and we had to fight with vendors 
over MSU pricing for the software that was on the small box that now ran on a 
big box.  We put all the lpars that had been on the small box into a capacity 
group so we could cap them.  We also took the time to actually eliminate a few 
lpars in the process.

The main thing is we worked it out that we did not have to do everything in one 
weekend.  We had a about a two week time frame to get everything done.

Thanks..

Paul Feller
AGT Mainframe Technical Support

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of fred glenlake
Sent: Thursday, March 01, 2018 08:36
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Hardware upgrade z13 to z14Yikes

Hi Chuck and list members,

I would be interested in knowing once you figure out the cause.   My upgrade is 
actually much more complicated that first presented.   We are going from two 
z13's with about 6 lpars on each to one z14 so not only are we upgrading we are 
merging as well just to make things more interesting.

We are going to run into duplicate definitions for channels, devices, etc. that 
we will need to rectify when we do the odd 30 minutes of planningHa.   The 
new z14 came with of course other new hardware HMC, routers, etc.   I 
personally have not had the experience of gluing two into one, all of the 
upgrades I have worked on have been one for oneup until now.

I would be interested in hearing if anyone else has merged two to one or three 
to one and their experiences.

FredG.


From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Chuck Kreiter <kreiter_ibm-m...@twc.com>
Sent: March 1, 2018 8:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Hardware upgrade z13 to z14Yikes

We recently did an upgrade to z14's and have seen some unexplained problems.
It appears (unconfirmed as of yet, but should be soon) to be related to some
CA products.  We should have confirmation later today or tomorrow.  Our
upgrade was z12's to z14's and we are running z/OS 2.2.  If I get
confirmation, I'll pass along more details.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of fred glenlake
Sent: Monday, February 26, 2018 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Hardware upgrade z13 to z14Yikes

Hi List,

My management must be in line to cash in on performance bonuses because they
have decreed we will upgrade our z13's to z14's in 90 days.   This was a
total out of left field surprise, perhaps our hardware vendor had a sale on
for "Presidents Day", right next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots
to consider and read which I do not mind.   Wondered if any list members had
already moved to z14's and could share any land mines they encountered
upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware
wise we drop the new CEC's next to the existing ones.   Hook them up to
power, HMC's, etc.  Then grab a couple of cables from existing CEC's for
DASD and Tape, swing them over.   Use the existing IOCP and IOCDS as the
basis of the new IOCP/IOCDS, update serial numbers, models, etc.  Then bring
up our sysprog lpar on the new CEC, get that one going, update and fix
software keys/licenses, issues with first IPL's on new CEC, etc.   Once all
the work is done in terms of getting ready for the rest of the lpars, then
go for the big bang one weekend.  Bring down the rest of the lpars, drop the
cables, swing over to new CEC, hook up and IPL remaining lpars.   Assuming
no phat thumb checks it should work.  Of course there are a ton of
considerations to review and check, coupling facility stuff, software stuff,
compatibility maintenance, etc.   However all things being equal I am
thinking this approach is likely the safest in terms of risk avoidance and
getting this done with the 90 days.   We could go the move one lpar at a
time route but that would mean more work and it would take longer especially
with our change management processes (bless their little hearts).

Any alternate suggestions or comments would be appreciated as I am sure
there will still be a few land mines with my name on them waiting in the
woods.

FredG.




--
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 instruction

Re: Hardware upgrade z13 to z14....Yikes

[fred glenlake]

Hi Chuck and list members,

I would be interested in knowing once you figure out the cause.   My upgrade is 
actually much more complicated that first presented.   We are going from two 
z13's with about 6 lpars on each to one z14 so not only are we upgrading we are 
merging as well just to make things more interesting.

We are going to run into duplicate definitions for channels, devices, etc. that 
we will need to rectify when we do the odd 30 minutes of planningHa.   The 
new z14 came with of course other new hardware HMC, routers, etc.   I 
personally have not had the experience of gluing two into one, all of the 
upgrades I have worked on have been one for oneup until now.

I would be interested in hearing if anyone else has merged two to one or three 
to one and their experiences.

FredG.


From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of 
Chuck Kreiter <kreiter_ibm-m...@twc.com>
Sent: March 1, 2018 8:39 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Hardware upgrade z13 to z14Yikes

We recently did an upgrade to z14's and have seen some unexplained problems.
It appears (unconfirmed as of yet, but should be soon) to be related to some
CA products.  We should have confirmation later today or tomorrow.  Our
upgrade was z12's to z14's and we are running z/OS 2.2.  If I get
confirmation, I'll pass along more details.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of fred glenlake
Sent: Monday, February 26, 2018 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Hardware upgrade z13 to z14Yikes

Hi List,

My management must be in line to cash in on performance bonuses because they
have decreed we will upgrade our z13's to z14's in 90 days.   This was a
total out of left field surprise, perhaps our hardware vendor had a sale on
for "Presidents Day", right next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots
to consider and read which I do not mind.   Wondered if any list members had
already moved to z14's and could share any land mines they encountered
upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware
wise we drop the new CEC's next to the existing ones.   Hook them up to
power, HMC's, etc.  Then grab a couple of cables from existing CEC's for
DASD and Tape, swing them over.   Use the existing IOCP and IOCDS as the
basis of the new IOCP/IOCDS, update serial numbers, models, etc.  Then bring
up our sysprog lpar on the new CEC, get that one going, update and fix
software keys/licenses, issues with first IPL's on new CEC, etc.   Once all
the work is done in terms of getting ready for the rest of the lpars, then
go for the big bang one weekend.  Bring down the rest of the lpars, drop the
cables, swing over to new CEC, hook up and IPL remaining lpars.   Assuming
no phat thumb checks it should work.  Of course there are a ton of
considerations to review and check, coupling facility stuff, software stuff,
compatibility maintenance, etc.   However all things being equal I am
thinking this approach is likely the safest in terms of risk avoidance and
getting this done with the 90 days.   We could go the move one lpar at a
time route but that would mean more work and it would take longer especially
with our change management processes (bless their little hearts).

Any alternate suggestions or comments would be appreciated as I am sure
there will still be a few land mines with my name on them waiting in the
woods.

FredG.




--
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

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

Re: Hardware upgrade z13 to z14....Yikes

[Chuck Kreiter]

We recently did an upgrade to z14's and have seen some unexplained problems.
It appears (unconfirmed as of yet, but should be soon) to be related to some
CA products.  We should have confirmation later today or tomorrow.  Our
upgrade was z12's to z14's and we are running z/OS 2.2.  If I get
confirmation, I'll pass along more details.  

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of fred glenlake
Sent: Monday, February 26, 2018 11:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Hardware upgrade z13 to z14Yikes

Hi List,

My management must be in line to cash in on performance bonuses because they
have decreed we will upgrade our z13's to z14's in 90 days.   This was a
total out of left field surprise, perhaps our hardware vendor had a sale on
for "Presidents Day", right next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots
to consider and read which I do not mind.   Wondered if any list members had
already moved to z14's and could share any land mines they encountered
upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware
wise we drop the new CEC's next to the existing ones.   Hook them up to
power, HMC's, etc.  Then grab a couple of cables from existing CEC's for
DASD and Tape, swing them over.   Use the existing IOCP and IOCDS as the
basis of the new IOCP/IOCDS, update serial numbers, models, etc.  Then bring
up our sysprog lpar on the new CEC, get that one going, update and fix
software keys/licenses, issues with first IPL's on new CEC, etc.   Once all
the work is done in terms of getting ready for the rest of the lpars, then
go for the big bang one weekend.  Bring down the rest of the lpars, drop the
cables, swing over to new CEC, hook up and IPL remaining lpars.   Assuming
no phat thumb checks it should work.  Of course there are a ton of
considerations to review and check, coupling facility stuff, software stuff,
compatibility maintenance, etc.   However all things being equal I am
thinking this approach is likely the safest in terms of risk avoidance and
getting this done with the 90 days.   We could go the move one lpar at a
time route but that would mean more work and it would take longer especially
with our change management processes (bless their little hearts).

Any alternate suggestions or comments would be appreciated as I am sure
there will still be a few land mines with my name on them waiting in the
woods.

FredG.




--
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

Re: Hardware upgrade z13 to z14....Yikes

[Tim Deller]

In my experience; an upgrade with the same serial number means they upgrade the 
box you already have. This requires hours of downtime and no time to test on 
the upgraded box. (also; no fallback)

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

Re: Hardware upgrade z13 to z14....Yikes

[Jesse 1 Robinson]

It's been a while since we in a position do a straight upgrade. If your 
(re)seller tells you that you'll have the same serial number, that should be 
the case. But if so, the original box should have been transformed into a new 
one, so I don't see how there would be any opportunity to connect them 
together. Seller will need to explain that. 

HMC is technically a part number of a CEC complex, so if new HMC hardware is 
needed, it should be included in the upgrade. You ought to be able to have a 
fully capable HMC with software already in place before the CEC upgrade.

Again, I don't think you can have two boxes side by side with the same serial 
number. Please get your seller to clarify that.  

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Alan(GMAIL)Watthey
Sent: Monday, February 26, 2018 10:19 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Hardware upgrade z13 to z14Yikes

We are in the early stages of doing an 'upgrade' and we have been told that 
this means the serial number does not change (obviously the model number does). 
 An 'upgrade' is much cheaper allegedly.

Same serial number CPCs must apparently never see each other so I've set up a 
VLAN on the HMCLAN just for this new CPC and it's HMC.  We've put one of the 
new HMCs on the prod LAN and one on the segregated LAN.  We'll switch them both 
to the prod LAN when the old CPC is disconnected.

Also your existing HMCs (if you keep any) may not be able to see the new CPC 
without a software upgrade which their hardware may not be able to support.
The new HMCs will see the old CPCs (if you have any) without issue (once on the 
same LAN).

Some software checks the model number when doing a serial number check so even 
when the serial number stays the same they will need a new code.

We plan to test the new box and then change over to it in its entirety in one 
go.  We have a few spare ports on our Ficon Directors but nowhere near enough 
to connect new and old in their entirety so I'm connecting a few CHPIDs up 
front to give access and then moving the rest over during the changeover.  
They'll already all be in the IO defs everywhere as I'll change the port 
address (old to new) on the Ficon Director as I swap the cables.

Regards,
Alan Watthey

-Original Message-
From: Ward, Mike S [mailto:mw...@ssfcu.org]
Sent: 26 February 2018 7:28 pm
Subject: Re: Hardware upgrade z13 to z14Yikes

What also comes to mind, if you have 3rd party software make sure to contact 
them about the new CPU. Even if it's a 1 to 1 swap they may want to charge an 
upgrade fee. You also have a new CPU serial number so make sure any 3rd party 
software that requires a specific cpu serial number is updated.

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

Re: Hardware upgrade z13 to z14....Yikes

[Parwez Hamid]

This Redbook should be a good starting point:

http://www.redbooks.ibm.com/abstracts/sg248460.html?Open

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

Re: Hardware upgrade z13 to z14....Yikes

[Alan(GMAIL)Watthey]

We are in the early stages of doing an 'upgrade' and we have been told that
this means the serial number does not change (obviously the model number
does).  An 'upgrade' is much cheaper allegedly.

Same serial number CPCs must apparently never see each other so I've set up
a VLAN on the HMCLAN just for this new CPC and it's HMC.  We've put one of
the new HMCs on the prod LAN and one on the segregated LAN.  We'll switch
them both to the prod LAN when the old CPC is disconnected.

Also your existing HMCs (if you keep any) may not be able to see the new CPC
without a software upgrade which their hardware may not be able to support.
The new HMCs will see the old CPCs (if you have any) without issue (once on
the same LAN).

Some software checks the model number when doing a serial number check so
even when the serial number stays the same they will need a new code.

We plan to test the new box and then change over to it in its entirety in
one go.  We have a few spare ports on our Ficon Directors but nowhere near
enough to connect new and old in their entirety so I'm connecting a few
CHPIDs up front to give access and then moving the rest over during the
changeover.  They'll already all be in the IO defs everywhere as I'll change
the port address (old to new) on the Ficon Director as I swap the cables.

Regards,
Alan Watthey

-Original Message-
From: Ward, Mike S [mailto:mw...@ssfcu.org] 
Sent: 26 February 2018 7:28 pm
Subject: Re: Hardware upgrade z13 to z14Yikes

What also comes to mind, if you have 3rd party software make sure to contact
them about the new CPU. Even if it's a 1 to 1 swap they may want to charge
an upgrade fee. You also have a new CPU serial number so make sure any 3rd
party software that requires a specific cpu serial number is updated.

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

Re: Hardware upgrade z13 to z14....Yikes

[Mike Schwab]

z13 FICON is 2/4/8G.  z14 FICON is 4/8/16G, so be sure you don't have
2G or less or have a switch to convert.

On Mon, Feb 26, 2018 at 10:10 AM, fred glenlake
 wrote:
> Hi List,
>
> My management must be in line to cash in on performance bonuses because they 
> have decreed we will upgrade our z13's to z14's in 90 days.   This was a 
> total out of left field surprise, perhaps our hardware vendor had a sale on 
> for "Presidents Day", right next to the slacks and shirts and CEC's??
>
> I am just starting to review the IBM considerations of going to z14's, lots 
> to consider and read which I do not mind.   Wondered if any list members had 
> already moved to z14's and could share any land mines they encountered 
> upgrading.
>
> At the 10,000 foot level I am thinking to get this done quickly hardware wise 
> we drop the new CEC's next to the existing ones.   Hook them up to power, 
> HMC's, etc.  Then grab a couple of cables from existing CEC's for DASD and 
> Tape, swing them over.   Use the existing IOCP and IOCDS as the basis of the 
> new IOCP/IOCDS, update serial numbers, models, etc.  Then bring up our 
> sysprog lpar on the new CEC, get that one going, update and fix software 
> keys/licenses, issues with first IPL's on new CEC, etc.   Once all the work 
> is done in terms of getting ready for the rest of the lpars, then go for the 
> big bang one weekend.  Bring down the rest of the lpars, drop the cables, 
> swing over to new CEC, hook up and IPL remaining lpars.   Assuming no phat 
> thumb checks it should work.  Of course there are a ton of considerations to 
> review and check, coupling facility stuff, software stuff, compatibility 
> maintenance, etc.   However all things being equal I am thinking this 
> approach is likely the safest in terms of risk avoidance and getting this 
> done with the 90 days.   We could go the move one lpar at a time route but 
> that would mean more work and it would take longer especially with our change 
> management processes (bless their little hearts).
>
> Any alternate suggestions or comments would be appreciated as I am sure there 
> will still be a few land mines with my name on them waiting in the woods.
>
> FredG.
>
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



-- 
Mike A Schwab, Springfield IL USA
Where do Forest Rangers go to get away from it all?

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

Re: Hardware upgrade z13 to z14....Yikes

[R.S.]

In a few words: Did you ever replaced a CPC with a new one?
If yes, it's piece of cake. z13->z14 migration has no gotchas.
If no, then you have to learn it. What to consider? A lot of things, 
most of them are not a headache for experienced user.



To name a few:
ICSF - every crypto change require new MK's. Every crypto generation 
upgrade means something new is coming, something obsolete is fading.

HMC - only new, UGLY user interface is left.
FICON - some FUD about the switches, so if you want to be supported, 
take care about FOS levels, etc. It could end up with switch change.


Software - in order to start using new hardware, you existing z/OS (and 
other OSes too) should be aware of new hardware. Means new functions 
PTFs. for example for HCD.


--
Radoslaw Skorupka
Lodz, Poland






W dniu 2018-02-26 o 17:10, fred glenlake pisze:

Hi List,

My management must be in line to cash in on performance bonuses because they have decreed 
we will upgrade our z13's to z14's in 90 days.   This was a total out of left field 
surprise, perhaps our hardware vendor had a sale on for "Presidents Day", right 
next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots to 
consider and read which I do not mind.   Wondered if any list members had 
already moved to z14's and could share any land mines they encountered 
upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware wise 
we drop the new CEC's next to the existing ones.   Hook them up to power, 
HMC's, etc.  Then grab a couple of cables from existing CEC's for DASD and 
Tape, swing them over.   Use the existing IOCP and IOCDS as the basis of the 
new IOCP/IOCDS, update serial numbers, models, etc.  Then bring up our sysprog 
lpar on the new CEC, get that one going, update and fix software keys/licenses, 
issues with first IPL's on new CEC, etc.   Once all the work is done in terms 
of getting ready for the rest of the lpars, then go for the big bang one 
weekend.  Bring down the rest of the lpars, drop the cables, swing over to new 
CEC, hook up and IPL remaining lpars.   Assuming no phat thumb checks it should 
work.  Of course there are a ton of considerations to review and check, 
coupling facility stuff, software stuff, compatibility maintenance, etc.   
However all things being equal I am thinking this approach is likely the safest 
in terms of risk avoidance and getting this done with the 90 days.   We could 
go the move one lpar at a time route but that would mean more work and it would 
take longer especially with our change management processes (bless their little 
hearts).

Any alternate suggestions or comments would be appreciated as I am sure there 
will still be a few land mines with my name on them waiting in the woods.

FredG.




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






==


   --
Treść tej wiadomości może zawierać informacje prawnie chronione Banku 
przeznaczone wyłącznie do użytku służbowego adresata. Odbiorcą może być jedynie 
jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś adresatem 
niniejszej wiadomości lub pracownikiem upoważnionym do jej przekazania 
adresatowi, informujemy, że jej rozpowszechnianie, kopiowanie, rozprowadzanie 
lub inne działanie o podobnym charakterze jest prawnie zabronione i może być 
karalne. Jeżeli otrzymałeś tę wiadomość omyłkowo, prosimy niezwłocznie 
zawiadomić nadawcę wysyłając odpowiedź oraz trwale usunąć tę wiadomość 
włączając w to wszelkie jej kopie wydrukowane lub zapisane na dysku.

This e-mail may contain legally privileged information of the Bank and is 
intended solely for business use of the addressee. This e-mail may only be 
received by the addressee and may not be disclosed to any third parties. If you 
are not the intended addressee of this e-mail or the employee authorized to 
forward it to the addressee, be advised that any dissemination, copying, 
distribution or any other similar activity is legally prohibited and may be 
punishable. If you received this e-mail by mistake please advise the sender 
immediately by using the reply facility in your e-mail software and delete 
permanently this e-mail including any copies of it either printed or saved to 
hard drive.

mBank S.A. z siedzibą w Warszawie, ul. Senatorska 18, 00-950 Warszawa, 
www.mBank.pl, e-mail: kont...@mbank.plsąd Rejonowy dla m. st. Warszawy XII 
Wydział Gospodarczy Krajowego Rejestru Sądowego, nr rejestru przedsiębiorców 
KRS 025237, NIP: 526-021-50-88. Według stanu na dzień 01.01.2018 r. kapitał 
zakładowy mBanku S.A. (w całości wpłacony) wynosi 169.248.488 złotych.
   


--
For IBM-MAIN subscribe / signoff / 

Re: Hardware upgrade z13 to z14....Yikes

[Ward, Mike S]

What also comes to mind, if you have 3rd party software make sure to contact 
them about the new CPU. Even if it's a 1 to 1 swap they may want to charge an 
upgrade fee. You also have a new CPU serial number so make sure any 3rd party 
software that requires a specific cpu serial number is updated.

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of fred glenlake
Sent: Monday, February 26, 2018 10:11 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Hardware upgrade z13 to z14Yikes

Hi List,

My management must be in line to cash in on performance bonuses because they 
have decreed we will upgrade our z13's to z14's in 90 days.   This was a total 
out of left field surprise, perhaps our hardware vendor had a sale on for 
"Presidents Day", right next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots to 
consider and read which I do not mind.   Wondered if any list members had 
already moved to z14's and could share any land mines they encountered 
upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware wise 
we drop the new CEC's next to the existing ones.   Hook them up to power, 
HMC's, etc.  Then grab a couple of cables from existing CEC's for DASD and 
Tape, swing them over.   Use the existing IOCP and IOCDS as the basis of the 
new IOCP/IOCDS, update serial numbers, models, etc.  Then bring up our sysprog 
lpar on the new CEC, get that one going, update and fix software keys/licenses, 
issues with first IPL's on new CEC, etc.   Once all the work is done in terms 
of getting ready for the rest of the lpars, then go for the big bang one 
weekend.  Bring down the rest of the lpars, drop the cables, swing over to new 
CEC, hook up and IPL remaining lpars.   Assuming no phat thumb checks it should 
work.  Of course there are a ton of considerations to review and check, 
coupling facility stuff, software stuff, compatibility maintenance, etc.   
However all things being equal I am thinking this approach is likely the safest 
in terms of risk avoidance and getting this done with the 90 days.   We could 
go the move one lpar at a time route but that would mean more work and it would 
take longer especially with our change management processes (bless their little 
hearts).

Any alternate suggestions or comments would be appreciated as I am sure there 
will still be a few land mines with my name on them waiting in the woods.

FredG.




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

==
This email, and any files transmitted with it, is confidential and intended 
solely for the use of the individual or entity to which it is addressed. If you 
have received this email in error, please notify the system manager. This 
message contains confidential information and is intended only for the 
individual named. If you are not the named addressee, you should not 
disseminate, distribute or copy this e-mail. Please notify the sender 
immediately by e-mail if you have received this message by mistake and delete 
this e-mail from your system. If you are not the intended recipient, you are 
notified that disclosing, copying, distributing or taking any action in 
reliance on the contents of this information is strictly prohibited.

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

Re: Hardware upgrade z13 to z14....Yikes

[Mark Jacobs - Listserv]

If you have CryptoExpress cards on the z13's and will have on the z14's, and 
using ICSF with protected keys, you'll need to reinstall your current ICSF 
master keys (and maybe the previous ones too), into the new CryptoExpress cards.

Mark Jacobs

fred glenlake
February 26, 2018 at 11:10 AM
Hi List,

My management must be in line to cash in on performance bonuses because they 
have decreed we will upgrade our z13's to z14's in 90 days. This was a total 
out of left field surprise, perhaps our hardware vendor had a sale on for 
"Presidents Day", right next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots to 
consider and read which I do not mind. Wondered if any list members had already 
moved to z14's and could share any land mines they encountered upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware wise 
we drop the new CEC's next to the existing ones. Hook them up to power, HMC's, 
etc. Then grab a couple of cables from existing CEC's for DASD and Tape, swing 
them over. Use the existing IOCP and IOCDS as the basis of the new IOCP/IOCDS, 
update serial numbers, models, etc. Then bring up our sysprog lpar on the new 
CEC, get that one going, update and fix software keys/licenses, issues with 
first IPL's on new CEC, etc. Once all the work is done in terms of getting 
ready for the rest of the lpars, then go for the big bang one weekend. Bring 
down the rest of the lpars, drop the cables, swing over to new CEC, hook up and 
IPL remaining lpars. Assuming no phat thumb checks it should work. Of course 
there are a ton of considerations to review and check, coupling facility stuff, 
software stuff, compatibility maintenance, etc. However all things being equal 
I am thinking this approach is likely the safest in terms of risk avoidance and 
getting this done with the 90 days. We could go the move one lpar at a time 
route but that would mean more work and it would take longer especially with 
our change management processes (bless their little hearts).

Any alternate suggestions or comments would be appreciated as I am sure there 
will still be a few land mines with my name on them waiting in the woods.

FredG.




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



Please be alert for any emails that may ask you for login information or 
directs you to login via a link. If you believe this message is a phish or 
aren't sure whether this message is trustworthy, please send the original 
message as an attachment to 
'phish...@meredith.com'.

Jesse 1 Robinson
February 7, 2018 at 3:53 PM
I know this is not OP's first bronco ride in a sysplex rodeo, but I have a few 
more suggestions.

-- Create a new unique name for the combined sysplex.

-- Pick one (least critical) system and start there as the first member of the 
new sysplex.

-- Once the new sysplex is running with this one member, add in a second member.

-- Continue until all desired members have joined the new sysplex.

-- All along the way make extensive use of symbolics in names. One suggestion 
for DSN is the suffix '$SYS'. '$SYS' (or whatever you choose) is a 
kind of marker that several similar data sets exist in the sysplex with 
 identifying the owning member.

.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
robin...@sce.com


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of fred glenlake
Sent: Tuesday, February 06, 2018 8:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: Setting up a new parallel sysplex

Hi Kees and Allan,

Thank you both for your suggestions. I greatly appreciate all the input I am 
receiving as I get through the "Insomnia Cure"I mean the IBM Red Book on 
Setting up a Sysplex. I will definitely include your input in my notes I am 
making as I read through the book.

Fred G.


From: IBM Mainframe Discussion List 
 on behalf of 
Vernooij, Kees (ITOPT1) - KLM 

Sent: February 6, 2018 8:56 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Setting up a new parallel sysplex

In addition to that, if you are implementing LOGGER CF Logstreams: beware if 
you read about putting more than 1 Logstream in a CF structure. As I 
understand, these are old recommendations and it is often difficult to convert 
them to 1 Logstream per CF structure.

Hardware upgrade z13 to z14....Yikes

[fred glenlake]

Hi List,

My management must be in line to cash in on performance bonuses because they 
have decreed we will upgrade our z13's to z14's in 90 days.   This was a total 
out of left field surprise, perhaps our hardware vendor had a sale on for 
"Presidents Day", right next to the slacks and shirts and CEC's??

I am just starting to review the IBM considerations of going to z14's, lots to 
consider and read which I do not mind.   Wondered if any list members had 
already moved to z14's and could share any land mines they encountered 
upgrading.

At the 10,000 foot level I am thinking to get this done quickly hardware wise 
we drop the new CEC's next to the existing ones.   Hook them up to power, 
HMC's, etc.  Then grab a couple of cables from existing CEC's for DASD and 
Tape, swing them over.   Use the existing IOCP and IOCDS as the basis of the 
new IOCP/IOCDS, update serial numbers, models, etc.  Then bring up our sysprog 
lpar on the new CEC, get that one going, update and fix software keys/licenses, 
issues with first IPL's on new CEC, etc.   Once all the work is done in terms 
of getting ready for the rest of the lpars, then go for the big bang one 
weekend.  Bring down the rest of the lpars, drop the cables, swing over to new 
CEC, hook up and IPL remaining lpars.   Assuming no phat thumb checks it should 
work.  Of course there are a ton of considerations to review and check, 
coupling facility stuff, software stuff, compatibility maintenance, etc.   
However all things being equal I am thinking this approach is likely the safest 
in terms of risk avoidance and getting this done with the 90 days.   We could 
go the move one lpar at a time route but that would mean more work and it would 
take longer especially with our change management processes (bless their little 
hearts).

Any alternate suggestions or comments would be appreciated as I am sure there 
will still be a few land mines with my name on them waiting in the woods.

FredG.




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