content_image/979946.jpg
Consider the following points regarding upgrades: 

GLYPH<SM590000> Upgrade from a z14 LR1 to a z14 ZR1 is  supported 

GLYPH<SM590000> Upgrade from z14 ZR1 to z14 LR1 is not  supported 

GLYPH<SM590000> Upgrade from z14 ZR1 to z14 M0x is  supported 

GLYPH<SM590000> Upgrade from z14 LR1 to z14 LM1 is not  supported 

You can upgrade a z13s (2965) server and preserve the CPC serial number (S/N). The I/O cards can also be carried forward (with certain restrictions) to the z14 ZR1 server. For frame roll MES from z13s to z14 ZR1, new frames are shipped. New PCIe+ I/O drawers are supplied with the MES for z13s to replace the PCIe I/O drawers. 

## 2.7.4 Concurrent PU conversions 

Important:  Upgrades from IBM z13s are always disruptive. 

Assigned CPs, assigned IFLs, and unassigned IFLs, ICFs, zIIPs, and SAPs can be converted to other assigned or unassigned PU feature codes. 

Most conversions are nondisruptive. In exceptional cases, the conversion might be disruptive; for example, when a model ZR1  with 6 CPs is converted to an all IFL system. In addition, an LPAR might be disrupted when PUs must be freed before they can be converted. Conversion information is listed in Table 2-9. 

<img src='content_image/979946.jpg'>

## 2.7.5 Model capacity identifier 

To recognize how many PUs are characterized as CPs, the Store System Information (STSI) instruction returns a Model Capacity Identifier (MCI). The MCI determines the number and speed of characterized CPs. Characterization of a PU as an IFL, ICF, or zIIP is not reflected in the output of the STSI instruction because characterization has no effect on software charging. For more information about STSI output, see “Processor identification” on page 321. 

Capacity identifiers:  Within a z14 ZR1 server, all CPs feature the same capacity identifier. Specialty engines (IFLs, zIIPs, and ICFs) operate at full speed. 

## Model capacity identifiers 

All model capacity identifiers feature a related MSU value that is used to determine the software license charge for MLC software, as listed in Table 2-10 on page 54. 

