IBM z/OS - Manual (Page 76)

76
Installation Considerations
CustomPac is a suite of services designed to help you
effi ciently install, migrate and maintain a z/OS system. It
can also help with migrating and maintaining z/OS system-
related products and/or third parties’ software vendor
products. Options include:
• RefreshPac ® , which includes preventative software
services
• ProductPac ® for custom-built products
• SystemPac ® for installation or system replacement
Highlights
• Customized services and products to help meet cus-
tomer specifi c needs
• Effi cient and effective exploitation of new z/OS functions
• A solution for businesses that lack skilled system pro-
grammers
• Installation of IBM and selected third-party software
vendor products in one package
For more information visit: ibm.com/ca/custompac.
ServerPac is a software package, available free of charge
with a z/OS license, that creates or replaces a z/OS,
OS/390, or z/OS.e system.
CBPDO is a no-charge software package for adding or
upgrading products or service or both on an existing z/OS
systems.
z/OS 1.4 and 1.5 are supported on the following IBM servers:
• S/390 Parallel Enterprise Server ™ G5/G6 (or compatible
server) (ESA/390 mode)
• Multiprise ® 3000 Enterprise Server (or compatible
server) (ESA/390 mode)
• IBM ^ zSeries 800, 890, 900 and 990 servers (or
compatible servers in z/Architecture mode)
z/OS 1.6 is supported on the following IBM servers:
• IBM ^ zSeries 800, 890, 900 and 990 servers (or
compatible servers in z/Architecture mode)
Migration/Coexistence
General coexistence, release migrations, and fallback:
z/OS continues to deliver compatibility and fl exibility as
the user migrates systems in a multisystem confi guration
by allowing several releases of z/OS, OS/390, and z/OS.e
to coexist. This includes Parallel Sysplex and non-Parallel
Sysplex multisystem confi gurations.
Coexistence allows systems within a multisystem confi gu-
ration to be upgraded to a new release level of the operat-
ing system one system at a time. This is contingent on the
fact that the release the user is migrating to can coexist
with the lowest release running in the user’s multisystem
confi guration.
IBM has a consistent coexistence, migration, and fallback
policy. Migration forward as well as backward should be
made within the same releases supported by the coexis-
tence policy.