Example Of Temporary Upgrade Activation Sequence - IBM z13s Technical Manual

Temporary upgrades are represented in the z13s server by a
records, downloaded from the RSF or installed from portable media, are resident on the SE
hard disk drive (HDD). At the time of activation, the customer can control everything locally.
Figure 8-1 shows a representation of the provisioning architecture.
The authorization layer enables administrative control over the temporary offerings. The
activation and deactivation can be driven either manually or under the control of an
application through a documented application programming interface (API).
By using the API approach, you can customize, at activation time, the resources necessary to
respond to the current situation, up to the maximum specified in the order record. If the
situation changes, you can add more, or remove resources, without having to go back to the
base configuration. This capability eliminates the need for temporary upgrade specifications
for all possible scenarios. However, for CPE, the specific ordered configuration is the only
possible activation.
In addition, this approach enables you to update and replenish temporary upgrades, even in
situations where the upgrades are already active. Likewise, depending on the configuration,
permanent upgrades can be performed while temporary upgrades are active. Figure 8-2
shows examples of activation sequences of multiple temporary upgrades.
R1 R1 R2 R2
CPE OOCoD CBU
R4 R4
CBU
R2 R2
R2 R2
OOCoD OOCoD
Activation and usage of dormant resources over time
Time
Figure 8-2 Example of temporary upgrade activation sequence
If R2, R3, and R1 are active at the same time, only parts of R1 can be activated because not
enough resources are available to fulfill all of R1. When R2 is then deactivated, the remaining
parts of R1 can be activated as shown.
Temporary capacity can be billable as On/Off CoD, or replacement as CBU or CPE:
On/Off CoD is a function that enables
server.
can
On/Off CoD be used for customer peak workload requirements, for any length of time,
and has a daily hardware and maintenance charge.
R3 R3 R4 R4
Record and associated authorization
CBU
R3 R3
CBU
R4 R4
CBU
R2 R2
OOCoD
concurrent
record
. All temporary upgrade
R1 R1
CPE
R3 R3
R3 R3
CBU
CBU
R2 R2 R2 R2
OOCoD
OOCoD
temporary
and capacity growth of the
Chapter 8. System upgrades
R1 R1
CPE
R3 R3
CBU
321