IBM OS/390 User Manual
25.2 Install and Configure Required Hardware
VSE and OS/390 operating systems both use the same basic S/390 hardware
platform, although you will find that OS/390 may require more processor power,
storage and DASD resources. On the other hand, OS/390 also provides more
function, supports more devices, and is easier to manage as your applications
and workload grow.
platform, although you will find that OS/390 may require more processor power,
storage and DASD resources. On the other hand, OS/390 also provides more
function, supports more devices, and is easier to manage as your applications
and workload grow.
25.2.1 Processor Requirements
You will need a separate S/390 system such as a Multiprise 2000, or add another
LPAR and supporting hardware to your existing processor. Customers with
VM/ESA might want to add a virtual machine instead. If you add a migration and
test load to your existing processor, you should add additional engines and
memory to support the extra work.
LPAR and supporting hardware to your existing processor. Customers with
VM/ESA might want to add a virtual machine instead. If you add a migration and
test load to your existing processor, you should add additional engines and
memory to support the extra work.
Contact your IBM Representative to use one of the following capacity planning
tools to size the processor requirements for your workload:
tools to size the processor requirements for your workload:
•
LPAR/CE
•
CP2000
Appendix B in
OS/390 Planning for Installation describes the minimum processor
requirements.
25.2.2 Devices Supported by OS/390
In general, all devices supported by VSE are supported by OS/390, except Fixed
Block Architecture (FBA) DASD and most integrated communications adapters.
See
Block Architecture (FBA) DASD and most integrated communications adapters.
See
FBA to ECKD Migration Aid - Internal Disk for the Multiprise 2000 which is a
S/390 White Paper in the SG242000 PACKAGE on MKTTOOLS. Contact your local
IBM representative for a copy.
IBM representative for a copy.
See Appendix B in
OS/390 MVS Hardware Configuration Definition (HCD)
Planning, GC28-1750 for a complete list of supported devices.
25.2.3 DASD Requirements
Direct Access Storage Devices (DASD) are required for your OS/390 System
Libraries, Page, Spool, Programs, Data, and Work/Public/Storage volumes. If
you are configuring your own system, see Chapter 4 and Appendix E in
Libraries, Page, Spool, Programs, Data, and Work/Public/Storage volumes. If
you are configuring your own system, see Chapter 4 and Appendix E in
OS/390
Planning for Installation for a thorough description and recommended pack
layout. If you are using SystemPac or SIE to build your system, the volumes will
be configured slightly differently for you.
layout. If you are using SystemPac or SIE to build your system, the volumes will
be configured slightly differently for you.
While it is technically possible to create a one or two-pack OS/390 system, you
will need a lot more DASD for productive use. The initial number of volumes
required for system data sets with a SystemPac may be two RES, two DLIB, one
SMP, and one CAT volume. Even though these contain paging and spool data
sets, you will very quickly run out of space if you try to do any work.
will need a lot more DASD for productive use. The initial number of volumes
required for system data sets with a SystemPac may be two RES, two DLIB, one
SMP, and one CAT volume. Even though these contain paging and spool data
sets, you will very quickly run out of space if you try to do any work.
Most installations require more spool space on OS/390 than they did with
POWER because of the allocation units (track-groups) and space reclamation
differences. (You will want to automate some method for purging old spool data
sets.)
POWER because of the allocation units (track-groups) and space reclamation
differences. (You will want to automate some method for purging old spool data
sets.)
402
VSE to OS/390 Migration Workbook