Hardware requirements for running z/OS V2R1

Hardware requirements for a target system are discussed in Identifying hardware requirements for the target system. Beyond these basic requirements, certain elements and features have additional hardware requirements. This topic describes the additional requirements.

Note: For general information about requirements for a Parallel Sysplex® configuration, see the Parallel Sysplex Web site: http://www.ibm.com/systems/z/pso/.

Table 1. Hardware requirements for z/OS V2R1 elements and features
z/OS® element or feature	Additional hardware required beyond the basic hardware requirements for z/OS V2R1
Alternate Library for REXX	None
BCP	Automatic tape switching requirements for 3480, 3490, or 3590 tape drives: A single I/O device should have a single device number (defined through HCD) across the entire sysplex, and that number should not be reused for any other device. For ease of management, you should use the same device number on all systems to represent an automatically switchable device. If an automatically switchable device is a 3480 without the 'Read Configuration Data Capable' function, you must use the same device number on all systems. Note that, if you have not already applied C05566E, device numbers must be the same. Automatic IPL (autoIPL) requirement: Use of the autoIPL function on a System z9® server requires the no-charge SCSI IPL hardware feature (#9904) and hardware driver 67 or later. (Both are required.) Note the following: For the z9 EC and z9 BC, the minimum driver and MCL level required is Driver-67, Bundle #6b, MCL053 in the G40965 (System) stream. Although this level is the minimum, IBM® recommends that you install the latest driver and MCL. The hardware feature is integrated on the zEnterprise® servers and System z10™ servers (that is, no features are required on the zEC12, zBC12, z196 and z114 servers, or a System z10 server). AutoIPL is not supported on servers prior to the System z9 server. z/OS must be IPLed in order to detect the support. Enablement of autoIPL in multisystem-capable sysplexes with SFM active: The use of autoIPL in multisystem-capable sysplex configurations where a sysplex failure management (SFM) policy is active was previously disabled by PTF UA43911 (APARs OA26371 and OA26574) because the IPL actions performed by autoIPL could prevent or delay the successful completion of system isolation (fencing) and system removal actions performed by SFM. This restriction has now been removed. The PTF for APARs OA26993 and OA26995, along with underlying LPAR firmware support (identified in this section), now enables autoIPL to be used in configurations where an SFM policy is active. With this support, requested autoIPL actions will be performed in accordance with the DIAGxx parmlib member, even when an SFM policy is active in the sysplex. Use of autoIPL on a system in a multisystem-capable sysplex configuration where an SFM policy is active requires the following licensed internal code (LIC) levels to be installed: For System z10 systems at driver 73: MCL009 in EC stream (LPAR) F85901 (bundle 45b) For System z10 systems at driver 76: MCL003 in EC stream (LPAR) N10965 (bundle 8) For System z9 systems at driver 67: MCL006 in EC stream (LPAR) G40954 (bundle 38) Flash Express®, which supports storage-class memory (SCM) on Flash Express cards as optional auxiliary storage, is available only on the zEC12 or zBC12 server and requires FC #0402. Global resource serialization: If any systems are in a global resource serialization ring complex but not in the sysplex, global resource serialization requires basic mode CTCs to communicate with those systems.
BCP (continued)	XCF (cross-system coupling facility) requirements in a sysplex configuration with one central processor complex (CPC): Sysplex timing capability is not required. However, to provide timing for all members of the sysplex, one of the following must be true: The sysplex is a single-system sysplex on one processor. The sysplex runs in multiple logical partitions on a single CPC. The sysplex runs as a set of VM guests on the same VM image. Unless your system is running in XCF-local mode, a sysplex couple data set is required. If you have more than one system image in the sysplex, XCF signaling connectivity is required between each system in the sysplex. In a sysplex configuration with two or more central processor complexes (CPCs), XCF requires all of the following: Sysplex timing capability that extends to all of the processors that contain any of the z/OS or coupling facility images in the sysplex. The sysplex timing capability can be provided by either or both of the following: The Server Time Protocol (STP) feature of a zEC12, zBC12, z196, z114, z10 EC, z10 BC, z9 EC, or z9 BC servers A Sysplex Timer (9037) Shared DASD for the sysplex couple data set. Certain functions require multiple couple data sets. For more information, see z/OS MVS Setting Up a Sysplex. XCF signaling connectivity between each system in the sysplex and every other system in the sysplex. This signaling connectivity may be established using several different hardware means. The signaling mechanisms that are supported are: FICON® or ESCON® channels that are used as extended mode CTCs Coupling facility channels connected to a coupling facility with the use of XCF signaling structures System z® Application Assist Processors (zAAPs) are specialized processing units that provide an economical Java™ execution environment. Use of a zAAP requires one of the following: A zEC12, zBC12, z196, z114, z10 EC, z10 BC, z9 EC, or z9 BC server A Hardware Management Console (HMC) for defining and configuring the zAAP The zEC12, zBC12, z196, z114, System z10, or System z9 Integrated Information Processor (zIIP) is a specialty engine for running database workloads. Use of a zIIP requires a zEC12, zBV12, z196, z114, z10 EC, z10 BC, or a z9 EC with the 26 May 2006 or later update for SE Driver 63j and HMC Driver 64x, or a z9 BC. In order for z/OS to be a z/OS System z Advanced Workload Analysis Reporter (IBM zAware) monitored client, the system logger z/OS IBM zAware log stream client requires the following: IBM zAware must be installed in a PR/SM™ logical partition (LPAR) on an zEC12 or zBC12 central processor complex (CPC). IBM zAware must be accessible through Communication Server. Enablement of z/OS IBM zAware log stream client requires system logger IXGCNFxx parmlib member and log stream attribute specifications. For more information see
BCP (continued)	Enablement of z/OS zAware log stream client requires the PTF for APAR OA38747, along with the underlying LPAR firmware support (identified in the list). With this support, requested system logger actions are performed in accordance with the IXGCNFxx parmlib member and log stream attribute specifications. For more information see, z/OS MVS Setting Up a Sysplex.
BDT	None
BDT File-to-File	None
BDT SNA NJE	None
BookManager® BUILD	None
BookManager READ	None
CIM	For CIM support of the SMI-S Host Discovered Resources and Storage HBA profiles, a z196, z114, or System z10® GA2 server is required.
Communications Server	See Hardware Requirements for Communications Server.
Communications Server Security Level 3	If hardware cryptography is available, it is used by Communications Server Security Level 3. The use of hardware cryptography by Communications Server Security Level 3 requires the Cryptographic Coprocessor hardware feature on the server.
Cryptographic Services	For ICSF to provide cryptographic services on z196, z114, z10 EC, z10 BC, z9 EC, and z9 BC servers, the Crypto Express2 feature is required. For acceleration of cryptographic requests on z196, z114, z10 EC, z10 BC, z9 EC, and z9 BC servers, the Crypto Express2 feature must be configured as an accelerator. For secure key processing on z196, z114, z10 EC, z10 BC, z9 EC, and z9 BC servers, the Crypto Express2 feature must be configured as a coprocessor. The Crypto Express2 Coprocessor is the default configuration. To enable clear key DES and TDES instructions on z196, z114, z10 EC, z10 BC, z9 EC, or z9 BC the CP Assist for Cryptographic Functions (CPACF) feature is required. To enable clear key AES-128 instructions on z196, z114, z10 EC, z10 BC, z9 EC, and z9 BC servers, the CP Assist for Cryptographic Functions (CPACF) feature is required. To enable clear key AES-192 and AES-256, along with SHA-224, SHA-384 and SHA-512 instructions on a z196, z114, z10 EC or z10 BC server, the CP Assist for Cryptographic Functions (CPACF) feature is required.
DFSMSdfp	Catalog sharing enhancements (ECS) for Parallel Sysplex environments: To use this function, a coupling facility is required. Data compression: For optimal performance, this support uses the data compression feature that is available on some system processors. If the hardware is not available, it uses the software compression facility to compress data. Defining and accessing extended format sequential data sets: Extended format data sets must reside on DASD attached through cached storage controls and an ESCON or FICON channel adapter. Extended address volumes (EAVs): To use this function, an IBM System Storage® DS8000® with Licensed Machine Code (LMC) level 5.4.0xx.xx (bundle version 64.0.xx.xx) or later is required. Extended remote copy (XRC): When migrating data with XRC, the primary storage device must be attached to an XRC-capable storage subsystem, such as an Enterprise Storage Server® with applicable feature licenses enabled. Peer-to-peer remote copy (PPRC): When migrating data with PPRC, the primary and secondary storage devices must be attached to a PPRC-capable storage subsystem, such as an Enterprise Storage Server with applicable feature licenses enabled. OAM File System support: To use a file system sublevel configured with an NFS file system mounted in the z/OS UNIX hierarchy, an NFS server compatible with the z/OS NFS client is required. OAM Parallel Sysplex support: To use this OAM object support capability, coupling facility hardware or a supported simulated environment is required. OAM virtual tape server support: To use this support in an automated tape library environment, an IBM automated tape library or an IBM Virtual Tape Server is required. To use this support in a manual tape library environment, stand-alone tape drives are required. PDSE cross-system sharing support: If sharing PDSEs in a Parallel Sysplex environment, coupling facility hardware is required. Storage management subsystem 32-name support: When defining more than 16 systems in an SMS complex, you must allocate the ACDS and the COMMDS on DASD volumes that are capable of attaching to more than 16 systems. Storage management subsystem system groups: Some SMS complex configurations might require DASD with enhanced connectivity. Because all systems in an SMS complex share the same configuration data sets, the ACDS and the COMMDS must reside on DASD devices that are accessible to the system activating the configuration. VSAM record level sharing (RLS): A coupling facility (at least one) must be connected to all systems capable of VSAM RLS. For multiple coupling facilities, select one facility with global connectivity to contain the master lock structure. The coupling facility must be at control level 2. It must be large enough to contain either a lock or a cache structure, or both, and have enough surplus space to allow the structures to be modified. The cache structures must be defined to SMS to enable it for VSAM RLS. WORM Tape Support: Requires the IBM 3592 Enterprise Tape System and WORM tape media.
DFSMSdss	Concurrent copy: To use this function, data must reside on DASD volumes attached through a concurrent copy-capable storage subsystem. Defining and accessing extended format sequential data sets through BSAM and QSAM: Extended format data sets must reside on DASD attached through cached storage controls and an ESCON or FICON channel adapter. FlashCopy®: To use this function you need DASD attached to a FlashCopy capable storage subsystem such as DS8000. Storage management subsystem 32-name support: When defining more than 16 systems in an SMS complex, you must allocate the ACDS and the COMMDS on volumes that are capable of attaching to more than 16 systems.
DFSMShsm	Control data set (CDS) record level sharing (RLS) serialization: To use this function, a coupling facility is required. Defining and accessing extended format sequential data sets through BSAM and QSAM: Extended format data sets must reside on DASD attached through cached storage controls and an ESCON or FICON channel adapter. FlashCopy: To use this function you need DASD attached to a FlashCopy capable storage subsystem such as DS8000. Storage management subsystem 32 name support: When defining more than 16 systems in an SMS complex, you must allocate the ACDS and the COMMDS on volumes that are capable of attaching to more than 16 systems. Common Recall Queue (CRQ): To use this function, a coupling facility is required
DFSMSrmm	None
DFSMStvs	A coupling facility is required.
DFSORT	None
Distributed File Service	None
EREP	None
ESCON Director Support	None
FFST™	None
GDDM®	GDDM supports devices that use the 3270 Extended Data Stream, the architected extensions to SNA character string (SCS), or IPDS. GDDM supports any other terminal or terminal-attached printer and provides graphics and image functions if it is upwardly compatible with the supported device. Certain non-IBM ASCII displays are supported through the 3174 Controller or on an upgraded older model 3174 Controller. GDDM host graphics are supported for viewing, printing, and plotting on OS/2 through CM/2 1.11 solely, IBM Personal Communications/3270 for OS/2 V4, or GDDM/MVS V3 download for GDDM-OS/2 Link in addition to CM/2. For Microsoft Windows, use either IBM Personal Communications/3270 V3 or V4, the latter providing a native graphics emulator. GDDM host graphics are supported on DOS for viewing and printing/plotting to GDDM-PCLK supported devices through IBM Personal Communications/3270 V2 or later, and download of GDDM-PCLK from GDDM/MVS V3 GDDM host graphics are supported for viewing on AIX® terminals through the X3270 emulator or the TCP/IP GDDMXD facility.
GDDM-PGF	None
GDDM-REXX	None
HCD	None
HCM	Hardware that can be used to establish a TCP/IP connection from the workstation to the z/OS host is required. Workstation requirements: Disk space: about 200 MB Color display with 1024 x 768 resolution Network adapter Processing very large configurations may require additional disk space and may benefit from additional memory.
HLASM	To display or enter double-byte data, any of the following are required: DBCS 3270 emulation on RS/6000® or PS/55 DBCS nonprogrammable terminal To print double-byte data, any of the following are required: AFP printers 3270 remote printing on RS/6000 or PS/55
HLASM Toolkit	None
IBM HTTP Server	A networked workstation with a web browser is required. If hardware encryption is desired, cryptographic hardware is required.
IBM TDS	None.
ICKDSF	None.
Infoprint Server	Printer and connectivity requirements depend on the function to be performed: To print output using IP PrintWay™, a printer connected by way of the z/OS Communications Server base element (either IP Services or SNA Services) is required. An IP connection requires a printer that supports the LPR protocol, the IPP protocol, or TCP/IP direct sockets. A SNA connection requires a printer that supports the SCS or DSC/DSE data streams. To print AFP data streams, an IPDS (Intelligent Printer Data Stream) printer supported by PSF is required, with the appropriate hardware attachment (channel, SNA, or TCP/IP) for the printer. Line data can be printed on any printer supported by JES2 or JES3. To receive LPR print requests from a remote host, a TCP/IP connection is required from the remote host to the z/OS host. A workstation capable of running Windows Server 2003, Windows Server 2008, Windows Vista (Business Edition or Enterprise Edition), Windows XP, or Windows 7 is required to use the Infoprint Port Monitor. The Infoprint Port Monitor also requires a TCP/IP connection from the workstation to the z/OS host.
Integrated Security Services	None.
ISPF	The ISPF base implementation requires a full-screen display terminal that supports 3270 data stream and provides a minimum interactive screen of 24 lines by 80 characters and a maximum interactive screen of 62 lines by 160 characters. On the host, the ISPF Client/Server (ISPF C/S) implementation requires the following: A TCP/IP or APPC network connection from the workstation to the z/OS host On the programmable workstation, the ISPF C/S implementation requires one of the following: Any personal computer capable of running Windows 2000. Any RS/6000 machine capable of running AIX Version 5.2 with a display device or X-station capable of running Motif 1.2. Any HP machine capable of running HP-UX Version 11 with a display device or X-station capable of running Motif 1.2. Any SPARC machine capable of running Solaris Version 7 with a display device or X-station capable of running Motif 1.2 or OpenLook.
JES2	A JES2 MAS with multiple z/OS images using multiple central processors requires a Sysplex Timer to synchronize time across the processors.
JES3	A JES3 complex with multiple z/OS images using multiple central processors requires a Sysplex Timer to synchronize time across the processors.
Language Environment®	None
Library Server	None
Metal C Runtime Library	None
MICR/OCR	None
NFS	None
OSA/SF	OSA/SF requires an OSA. For information about the requirements for an OSA, see and zEnterprise System and System z10 OSA-Express Customer's Guide and Reference. Consider the following for levels of OSA/SF. OSA-1 is not supported on any zEnterprise or System z server. OSA-2 is not supported on zEC12, zBC12, z196, z114, z10 EC, z10 BC, z9 EC, or z9 BC zservers. The only OSA-2 features supported on z900 and z800 servers are the token ring and FDDI features. OSA-Express features are not supported on zEC12, zBC12, z196 , z114,z10 EC, and z10 BC servers. OSA-Express features: The Gigabit Ethernet, Fast Ethernet, and 1000Base-T Ethernet features are supported on z9 EC, or z9 BC OSA-Express2 features: The 1000Base-T Ethernet feature is only supported on zEC12, z196, z114, z10 EC, z10 BC, z9 EC, or z9 BC servers. The Gigabit Ethernet SX, Gigabit Ethernet LX, and 10 Gigabit Ethernet LR features are only supported on zEC12, z196, z114, z10 EC, z10 BC, z9 EC, z9 BC, VERIFYING THAT THESE SERVER REFERENCES SHOULD BE DELETED FOR V2R1: z990, and z890 servers. None of the OSA-Express2 features are supported on z900 and z800 servers. OSA-Express3 features: The Gigabit Ethernet SX, Gigiabit Ethernet LX, and 10 Gigabit Ethernet LR features are only supported on zEC12, zBC12, z196, z114, z10 EC and z10 BC servers. The 1000Base-T Ethernet feature is only supported on the z196, z114, and z10 EC servers. None of the OSA-Express3 features are supported on the z9 EC, or z9 BC, z servers. OSA-Express4S features: The Gigabit Ethernet SX, Gigabit Ethernet LX, and 10 Gigabit Ethernet LR features are only supported on zEC12, z196, z114, z10 EC and z10 BC servers. The 1000Base-T Ethernet feature is only supported on the zEC12 servers. None of the OSA-Express4S features are supported on the z10 EC, z10 BC, z9 EC, or z9 BC servers. The 1000Base-T Ethernet feature is only supported on the zEC12 or zBC12 servers. None of the OSA-Express4 features are supported on the z9 EC, or z9 BC servers.
OSA/SF (con't)	Any OSA can be run in the TCP/IP Passthru and SNA modes except OSA-Express Gigabit Ethernet, OSA-Express2 Gigabit, OSA-Express2 10 Gigabit Ethernet, OSA-Express3 Gigabit, and OSA-Express3 10 Gigabit Ethernet. Only the OSA-Express features support IP traffic using QDIO architecture working with the IP Services component of z/OS Communications Server. Only an Asynchronous Transfer Mode (ATM) OSA-2 or an ATM OSA-Express feature can be run in ATM Native mode. Only ATM OSA-2 can be run in ATM IP Forwarding mode. For zEC12, zBC12, z196, z114, z10 EC, z10 BC, z9 EC, or z9 BC servers, an OSA-Express2 1000Base-T Ethernet feature is available as a replacement for the Fast Ethernet feature. For zEC12, zBC12, z196, z114, z10 EC and z10 BC servers, an OSA-Express3 1000Base-T Ethernet feature is available as a replacement for the Fast Ethernet feature. If the Windows (GUI) interface to OSA/SF is to be used, OSA/SF requires: A workstation with a Pentium 200 MHz (or equivalent) processor, 128 MB RAM, and an SVGA display with a resolution of 1024x768x16 colors is recommended. You might be satisfied with OSA/SF GUI performance on the minimum processor required by your Windows operating system, but the GUI might not display correctly at a lesser resolution. TCP/IP connectivity to the host system where OSA/SF is running.
RMF™	For all RMF workstation functions: A workstation with a Pentium II or later processor A graphics adapter and monitor with a configured resolution of at least 1024x768 pixels At least 96 MB RAM and 150 MB free disk space
Run-Time Library Extensions	None
SDSF	None
Security Server	If you run in data sharing mode in a Parallel Sysplex configuration, a coupling facility must be configured for use by RACF®.
SMP/E	Installing software products and service directly from a network source (such as the Internet) on the z900 and z800 servers is not supported for z/OS V2R1.
TIOC	None
TSO/E	These requirements apply to interactive use of TSO/E, not to batch use. Any terminal supported by base element Communications Server is required. The full-screen LOGON, TRANSMIT and RECEIVE commands, the Session Manager, and the Information Center Facility, which need a minimum screen size of 24 by 80, require one of the following terminals: IBM 3270 Information Display System Terminals 3275 Models 2 and 12 3276 Models 2, 3, 4, 12, 13, and 14 3277 Model 2 3278 Models 2, 3, 4, and 5 (monochrome) 3279 Models 2A, 2B, 2X, 3A, 3B, 3X, S2A, S2B, and S3G (base color mode) IBM 3472 Family IBM 3178 Display Terminal Models C1, C2, C3, and C4 IBM 3179 Display Terminal Model 1 and Model G (alphanumeric mode) IBM 3180 Display Terminal Models 100 and 110 IBM 3191 Display Terminal Models A30, A40, B30, B40, D, E, and L IBM 3192 Color Display Terminal Models A, B, C, D, F, G, L, and W IBM 3194 Display Terminal IBM 3290 Information Panel IBM PS/2 family (configured for 3270 support) IBM Personal Computer (configured for 3278/79 support) IBM PS/55 family (configured for 3270 support) IBM 5550 family (configured for 3270 support) Any other terminal that functions in compatibility mode with the terminals in the list. The VM/PC servers (spool, disk, and file) available with the MVSSERV command processor require the IBM Personal Computer Models XT/370 or AT/370 with an IBM 3278/79 Device Emulation Adapter.
XL C/C++	None
z/OS Font Collection	None
z/OS UNIX	The extended user interface support allows existing hardware (such as terminals and workstations) and existing telecommunications software (such as VTAM® and TCP/IP) that run on z/OS to be used. For 3270 support, most 3270 type terminals or 3270 emulators in a z/OS network from which a user can interactively log on to TSO/E are supported by z/OS UNIX services and include: Real and emulated 3270s in a VTAM SNA network which satisfy the following. The minimum screen size is 24x80. The terminal must be known to TSO/E and VTAM as a full-screen device. z/OS UNIX services use full-screen mode. The terminal must support uppercase and lowercase characters. A minimum of 12 PF keys are required. UNIX workstations and other workstations in a TCP/IP network that supports the TELNET 3270 (TN3270) client function. The OMVS command supports customized PF keys to scroll backward/forward, display HELP, hide input typed into the command line, refresh the screen, retrieve previous commands, and enter TSO/E commands. For ASCII control sequence support from 3270 displays, the OMVS command, with the pseudoterminal functions, maps and transforms a 3270 TSO/E terminal interface and user externals to the POSIX 1003.1 defined terminal interface expected by POSIX compliant user processes, including the POSIX 1003.2 Shell. This mapping consists of: Use of 3270 key sequences to emulate ASCII terminal control is supported. A set of system-defined 3270 default key sequences that map to ASCII escape control values is supplied. The user can tailor the system defaults. Execution in canonical (line-oriented) mode only. Conversion tables that map the 3270 data stream to a pseudoterminal device driver for both control and data are provided. Users can customize these tables. For ASCII terminal interface, UNIX workstations and other workstations in a TCP/IP network that support the telnet or rlogin virtual terminal protocols can directly login to the z/OS shell through Communications Server. The supported ASCII terminal interface conforms to X/OPEN Issue 4, Version 2.
3270 PC File Transfer Program	An IBM or compatible PC with appropriate communications device, such as a LAN adapter or modem, is required.