Family 9672+02 IBM System/390 Parallel Enterprise Server

IBM U.S. Sales Manual
Revised:  October 13, 2003.

Table of contents  Document options 
IBM U.S. Product Life Cycle Dates Publications
Abstract Features -- Specify/Special/Exchange
Highlights Accessories
Description Machine Elements
Models Supplies
Technical Description  
 
Printable version
 

 
IBM U.S. Product Life Cycle Dates
Type ModelAnnounced AvailableMarketing Withdrawn Service DiscontinuedReplaced By
9672-R11 1994/09/131994/09/13 1998/12/292003/12/31 None
9672-R21 1994/09/131994/09/13 1998/12/292003/12/31 None
9672-R31 1994/09/131994/09/13 1998/12/292003/12/31 None
9672-R41 1994/09/131994/09/13 1998/12/292003/12/31 None
9672-R51 1994/09/131994/09/13 1998/12/292003/12/31 None
9672-R61 1994/09/131994/09/13 1998/12/292003/12/31 None

Back to top
 
Abstract

The System/390* Parallel Enterprise Server general purpose models are a continuation of the Complementary Metal Oxide Semiconductor (CMOS) product family. These processors can participate in business computing in a standalone environment and are the building blocks for a Parallel Sysplex. These models in a Parallel Sysplex configuration enable single image growth well beyond single processor solutions.

Model Abstract 9672-R11

(For IBM US, No Longer Available as of December 29, 1998)

The 9672 Model R11 is a Parallel Enterprise Server that contains one CEC (one-way central processor). The CEC capacity includes: storage ranging from 128 MB to 2 GB and ESCON and/or Parallel channels up to 48 in increments of three.

Model Abstract 9672-R21

(For IBM US, No Longer Available as of December 29, 1998)

The 9672 Model R21 is a Parallel Enterprise Server that contains one CEC (two-way central processor). The CEC capacity includes: storage ranging from 128 MB to 2 GB and ESCON and/or Parallel channels up to 48 in increments of three.

Model Abstract 9672-R31

(For IBM US, No Longer Available as of December 29, 1998)

The 9672 Model R31 is a Parallel Enterprise Server that contains one CEC (three-way central processor). The CEC capacity includes: storage ranging from 128 MB to 2 GB and ESCON and/or Parallel channels up to 48 in increments of three.

Model Abstract 9672-R41

(For IBM US, No Longer Available as of December 29, 1998)

The 9672 Model R41 is a Parallel Enterprise Server that contains one CEC (four-way central processor). The CEC capacity includes: storage ranging from 128 MB to 2 GB and ESCON and/or Parallel channels up to 48 in increments of three.

Model Abstract 9672-R51

(For IBM US, No Longer Available as of December 29, 1998)

The 9672 Model R51 is a Parallel Enterprise Server that contains one CEC (five-way central processor). The CEC capacity includes: storage ranging from 128 MB to 2 GB and ESCON and/or Parallel channels up to 48 in increments of three.

Model Abstract 9672-R61

(For IBM US, No Longer Available as of December 29, 1998)

The 9672 Model R61 is a Parallel Enterprise Server that contains one CEC (six-way central processor). The CEC capacity includes: storage ranging from 128 MB to 2 GB and ESCON and/or Parallel channels up to 48 in increments of three.
Back to top
 

Highlights
  • ESA/390* architecture
  • Large-system capacity
  • Microprocessor price/performance
  • Horizontal growth
  • Air-cooled CMOS environmentals
  • Automated operations
  • Concurrent maintenance by CEC
  • ICMF for simulation of coupling without Coupling Links for migration
  • Support for 128 MB, 256 MB, 512 MB, 1024 MB, and 2048 MB memory

Back to top
 
Description

System/390* Parallel Enterprise Server 9672 R models are general- purpose CMOS-based technology processors. This CMOS technology packages circuitry in a manner that allows for high-density chips and thus allowing for smaller packaging of the entire system. This has several benefits. First, is the manufacturing costs to build CMOS is cheaper. Second, CMOS uses much less power and thus requires much less to keep it cool. Third, CMOS delivers what used to take a roomful of space in a very compact footprint. Fourth, the cost on maintaining is reduced.

The System/390 Parallel Enterprise Server includes six models (R11 thru R61). The middle digit represents the number of Processors (1 to 6-way processors). A 1-way processor (R11 model) is roughly equivalent to a 3090-180 processor up to a 6-way processor (R61 model) capacity roughly equivalent to a ES/3090-300S system.

System/390 Parallel Enterprise Server 9672 R models come with a minimum of 128-MB storage and a maximum of 2048-MB storage. All storage is customer configurable for splitting between central and expanded storage. In other words, you decide, in increments of 16 MB, how much memory should be used as central (minimum 64 MB) and how much should be used as expanded storage (minimum zero).

The 9672 R models will continue to have parallel channels available and/or ESCON/ESCON XDF channels. You can configure a total of 48 channels in increments of three.

Within the 9672 R models, you can upgrade throughout and take a model R11 up thru and to the R61 model. This provides a great way of dealing with increased capacity requirements and protecting the investment you make in your initial purchase. Also, the 9672 R models are upgradable to the 9672 E and P models. This gives you growth and investment protection into the future.

Model Description

  • Single CEC general-purpose server
  • Cost-effective replacement for equivalent-performance 4381, 308x, and selected 3090 and Plug-compatible systems
  • Performance growth within family of up to approximately 4.5 times
  • Field-installable upgrade paths
    • Within the 9672 R family (R11 through R61 models)
    • To 9672 Exx and Pxx models
  • Hardware Management Console (HMC)

Prerequisites

Each 9672 Model Rx1 requires:

    The Hardware Management Console (HMC) is attached via token-ring LAN. A 75-ft token-ring cable is shipped with the machine. If additional length is needed, customer must order it. Please see the "9672 S/390 Installation Manual-Physical Planning," GC22-7101, for information on ordering LAN cables.

    A Remote Support Facility (RSF) modem is shipped with the system.

    When ordering parallel channels, two types of cables can be used to attached the channel to the I/O. Either the OEMI bus and tag cables or the 78D cables. In either case, the customer must order these cables, they DO NOT come with the system. Please see the "9672 S/390 Installation Manual-Physical Planning," GC22-7101, for information on ordering these cables.

Processor Storage

The minimum processor storage is 128MB (Two 64MB cards). The storage will always be plugged with two equal size cards. The maximum processor storage is 2048 MB (Two 1028-MB cards). The storage cards removed or replaced become the property of IBM and must be returned.

Customer can configure the storage between central and expanded. A minimum of 64 MB is required for central, then the remainder, in increments of 16 MB, can be configured either in central or expanded.

The following Tables show every possible order combination for processor storage. You tell the configurator the amount of storage you want and the configurator plugs in the feature numbers required. The tables illustrate Initial Order and MES Orders.

 Storage Orders - Initial
===========================
  TOTAL       ON
 STORAGE     ORDER  FEATURE
 DESIRED    FEATURE   QTY
--------------------------
   128MB     0064      2
--------------------------
   256MB     0128      2
--------------------------
   512MB     0256      2
--------------------------
  1024MB     0512      2
--------------------------
  2048MB     1024      2
--------------------------
 
 
Storage upgrades for MESs =========================== | | | | INSTALLED | DESIRED | MES ORDER | MFG WILL | MUST BE RETURNED TOTAL | TOTAL | FEATURES | SHIP | TO MFG STORAGE | STORAGE | # |Qty | CARD |QTY | CARD |QTY -----------|---------|-------|----|-------|----|------|---------- 128MB | 256MB | 0128 | 2 | 0128 | 2 | 0064 | 2 -----------|---------|-------|----|-------|----|------|---------- 128MB | 512MB | 0256 | 2 | 0256 | 2 | 0064 | 2 -----------|---------|-------|----|-------|----|------|---------- 128MB | 1024MB | 0512 | 2 | 0512 | 2 | 0064 | 2 -----------|---------|-------|----|-------|----|------|---------- 128MB | 2048MB | 1024 | 2 | 1024 | 2 | 0064 | 2 -----------|---------|-------|----|-------|----|------|---------- 256MB | 512MB | 0256 | 2 | 0256 | 2 | 0128 | 2 -----------|---------|-------|----|-------|----|------|---------- 256MB | 1024MB | 0512 | 2 | 0512 | 2 | 0128 | 2 -----------|---------|-------|----|-------|----|------|---------- 256MB | 2048MB | 1024 | 2 | 1024 | 2 | 0128 | 2 -----------|---------|-------|----|-------|----|------|---------- 512MB | 1024MB | 0512 | 2 | 0512 | 2 | 0256 | 2 -----------|---------|-------|----|-------|----|------|---------- 512MB | 2048MB | 1024 | 2 | 1024 | 2 | 0256 | 2 -----------|---------|-------|----|-------|----|------|---------- 1024MB | 2048MB | 1024 | 2 | 1024 | 2 | 0512 | 2 -----------|---------|-------|----|-------|----|------|---------- 2048MB | n/a | n/a | | n/a | | n/a | -----------|---------|-------|----|-------|----|------|----------  

Processor Resource/Systems Manager (PR/SM)

PR/SM is standard.

Two modes of operation are available: ESA/390 mode (which supports 370-XA and ESA/370* operating systems), and Logically Partitioned (LPAR) mode. When operating in LPAR mode the following enhancements are available:

  • Capability to define up to ten logical PR/SM partitions

  • PR/SM dynamic storage reconfiguration capability allows central and expanded storage to be dynamically added or removed from a logical partition.

  • PR/SM resource capping capability is included.

  • The PR/SM security functions include a display frame that strengthens the separation between operating systems running in logical partitions by controlling access to certain system facilities, allowing a higher level of security control.

  • Software supported in LPAR mode:
    • MVS/ESA* 5.2, 5.1, 4.3, 4.2, 3.1.3
    • MVS/XA* 2.2.3, 2.2.0
    • VM/ESA* 1.2.2, 1.2.1, 1.2.0, 1.1.1
    • VM/ESA (370) 1.1.5
    • VSE/ESA 1.2, 1.3

PR/SM also provides the enhancement support for Multiple Preferred Guests.

Channels

The 9672 R11 model support up to 48 ESCON and/or parallel channels. When more than 24 channels are required, an expansion cage (#1000) is installed.

Three channels, either ESCON or parallel, are the minimum channel requirement. Additional channels are added in increments of three (one card).

The channels supported are:

  • ESCON channel group (#6113) provides three ESCON channels
  • ESCON XDF channel group (#6114) provides three ESCON XDF channels
  • Parallel channel group (#6103) provides three parallel channels

Frame considerations: If all of the channels in the CEC are ESCON (no parallel, then the space below the CEC in the frame can be used for an additional I/O Expansion Cage (#1000). The I/O expansion cage is only required when more than 24 channels are installed.

If there is at least one parallel channel in the CEC, then the space below the CEC is dedicated to the bus and tag tailgate assembly (#6109) If an additional I/O expansion cage is required, an additional frame is installed.

Channels - Parallel

Parallel channels allow for the attachment of one to eight control units per channel to the System/390 Parallel servers. Each channel can address as many as 256 I/O devices. Each parallel channel card contains three channels.

The parallel channels will use the existing OEMI bus and tag cables or the new 78D cables to connect to I/O control units.

The OEMI bus and tag cables connect to the parallel channel two ways. You can order the tailgate feature which will allow the bus and tag cables to attach inside the frame to the tailgate. Or you can request no tailgate in which case you will be shipped a 2.1 meter 78D cables that run from the parallel channel card underneath the frame and butt with the OEMI bus and tag cables. One 78D cable will be shipped for each parallel channel ordered without a tailgate. The OEMI bus and tag channel cables are not provided with the parallel channel features and are the customer's responsibility to order.

Also 78D cables, part number 55G8739, are available in variable lengths up to 400 feet. It has the bus and tag connectors on the control unit end and a 78D connector on the channel end. The variable length 78D cables are not provided with the parallel channel features and are the customer's responsibility to order.

Use the "I/O Equipment Installation Manual--Physical Planning" GC22-7064 and the "S/390 9672 Installation Manual--Physical Planning" GC22-7101 for information on planning the channel cabling.

Modes of Operation

Parallel Channels operate in ESA/390 mode. Parallel channels can be configured for operation in block multiplex mode or for byte multiplex mode.

  • Block-Multiplex Mode of Operation

    Block-multiplex mode of operation is used for faster devices (disk and tape devices, printers, display stations, and more) such as the IBM 3490 Tape, the 3174 Terminal Controller, and the 6098 Graphics System.

    Block multiplex mode lets several I/O devices operate concurrently with high speed. Both `direct coupled (DC) interlock mode' and `data streaming mode' are supported. DC interlock mode permits a data rate of up to 1.5 megabytes/sec. Data streaming permits a maximum aggregate data rate of 4.5 megabytes/sec, and cable lengths of up to 122 meters (400 ft) between the System/390 Parallel Enterprise Server and the last control unit. The channel subsystem permits the intermixed attachment of data streaming and non-data-streaming devices on the same channel.

  • Byte-Multiplex Mode of Operation

    Byte-multiplex mode of operation is used for slower-speed I/O devices (card readers, punches, TP control units) such as the 2540 Card Reader/Punch or the 2701 Data Adapter Unit.

    Byte-multiplex mode lets several relatively slow-speed devices operate concurrently. The data transfer rate in byte multiplex mode ranges from 40 kilobytes/sec in single-byte mode to 590-1000 kilobytes/sec in burst mode. Cable lengths may be up to 122 meters (400 ft) between the System/390 Parallel Enterprise Server and the last control unit.

Channels - ESCON

The ESCON Channel allows for attachment of I/O control units using a fiber optic (glass) cable, with higher speed and over longer distances compared to attachment via the Parallel Channel. The I/O devices attach through control units equipped for ESCON attachment. One control unit can be attached directly, point to point, to an ESCON Channel; several control units can be attached via an ESCON Director (IBM 9032-2 or IBM 9033-1). The ESCON Channel allows the addressing of up to 256 I/O devices per channel to the System/390 Parallel Enterprise Server. These channels are only available on ESA capable machines.

The ESCON Channel consists of one card in the System/390 Parallel Enterprise Server and contains three channels plus the necessary Licensed Internal Code.

The ESCON XDF Channel consists of one card in the System/390 Parallel Enterprise Server that contains three channels plus the necessary Licensed Internal Code.

The System/390 Parallel Enterprise Server allows 32 control units per ESCON or ESCON XDF channel. All ESCON channels are capable of operating at a data rate of up to 17 MB per second. (See "Special Features.")

ESCON Multiple Image Facility enables ESCON channel sharing among PR/SM logical partitions, lowering the total cost of computing as well as migration to an ESCON environment by reducing the number of channels, director ports, and control unit adapters required to support connectivity to a single machine.

The connectivity distances possible with the Enterprise Systems Connection (ESCON)* Architecture is being expanded by the ESCON Extended Distance Feature (XDF*). This allows customers to further utilize the benefits of ESCON, IBM's ESA/390* I/O and interconnection architecture.

ESCON products work together to provide solutions in the areas of:

  • Simplified device connectivity and sharing
  • Efficient use of channels and adapters
  • Increased connectivity distances
  • Configuration management under program control
  • High availability
  • Basis for growth and I/O performance
  • Reduced cable bulk and weight

By utilizing Laser/single mode fiber optic technology connectivity distances can significantly exceed those offered by LED/multimode fiber technology. While ESCON LED/multi-mode technology is the preferred cabling implementation for campus-wide interconnection, ESCON XDF offers a solution when unrepeated link distances up to 20 kilometers are required. The following maximum device attachment distances are possible when using ESCON XDF with ESCON Directors and ESCON I/O:

  • 3990 Storage Control Models 2 and 3 at up to 9 kilometers using just one ESCON Director that could be located in close proximity to attached 3990s.
  • 9343 Storage Controller Model D04 at up to 9 kilometers using just one ESCON Director that could be located in close proximity to attached 3990s.
  • 3490 Magnetic Tape Subsystems at up to 23 kilometers. In those configurations where 3490 models A01, A02, A10, A20, D31 D32, D41, or D42 are required to be attached at a distance greater than 9 kilometers from the host processor, with ESCON XDF, then EC# C14154 must be ordered and installed on the 3490s.
  • ESCON 3174 and 3172 distances at up to 43 kilometers.

The ESCON Extended Distance Feature (XDF) is available on all System/390 Parallel Enterprise Server models. The ESCON XDF is available as a new feature or field upgrade.

In ESA/390 mode, any processor may initiate an operation with any I/O device and process any I/O interrupt, using any of the channel paths in single-image mode or any of the channel paths when physically partitioned. The Model R11 can use up to a maximum of eight different logical paths to a single device. For additional information, see "Introducing Enterprise Systems Connection," GA23-0383.

Note: ESCON Channels do not support System/370* Mode.

The 9034 ESCON converter Model 001 is supported. Additional selected byte devices will be available via the 9034 ESCON converter Model 001. This includes the 3720, 3725 and 3745. RPQs will be accepted against the 9034-001 for support of other byte devices. The sales manual pages for the 9034-001 will be updated at General Availability with a complete description of supported devices and the other requirements associated with byte device support.

S/390 Open Systems Adapter

(For IBM US, No Longer Available as of May 24, 1998)

The S/390 Open Systems Adapter feature is an integrated hardware feature that has been implemented as a new channel type on the supported S/390 processors/servers. It appears to the application software as a channel-attached control unit and supports the industry standard LAN protocols for Ethernet, Token Ring, and Fiber Distributed Data Interface (FDDI).

The S/390 Open Systems Adapter provides TCP/IP for MVS and VM passthru support (protocol processing of TCP/IP is performed on the S/390 processor/server), as well as TCP/IP for MVS offload support (protocol processing is offloaded to the S/390 Open Systems Adapter).

Along with the S/390 Open Systems Adapter, the S/390 Open Systems Adapter Support Facility for MVS/ESA is being introduced. It offers an efficient method of managing the S/390 Open Systems Adapter features when performing configuration and operations management, and downloading supported software and related patches and updates. The S/390 Open Systems Adapter Support Facility for MVS/ESA also supports sharing of the S/390 Open Systems Adapter applications and/or LAN ports among logical partitions (LPAR support).

The S/390 Open Systems Adapter offers integrated industry standard LAN connectivity in a heterogeneous, multi-vendor environment, in a more seamless manner, helping to reduce the total cost of computing, and enhancing investments in Local Area Networks.

The S/390 Open Systems Adapter feature delivers client/server computing solutions by providing an additional network connectivity option; a direct connection between the S/390 processor/server and the Local Area Network using Ethernet, Token Ring, or FDDI LAN adapters. The Ethernet and Token Ring features each contain five LAN ports per feature, and the FDDI feature contains one dual-attach LAN port.

The S/390 Open Systems Adapter feature enables the S/390 processor/server to deliver a multipurpose and integrated open systems platform. Workstation clients and networks benefit from the performance, enterprise connectivity, security, availability and growth opportunities of the Enterprise Systems Architecture (TM)/390 (ESA/390)(TM).

The S/390 Open Systems Adapter can be managed from network and systems management products (e.g., NetView for MVS/ESA, AIX NetView/6000).

Ethernet, Token Ring, and FDDI LAN media information can be retrieved through a variety of LAN management products (e.g., the S/390 Open Systems Adapter will respond to Station Management (SMT) frames when supporting FDDI).

The S/390 Open Systems Adapter will also respond to requests to gather information about the network protocols that are executing (e.g., SNMP requests when supporting TCP/IP traffic and NetView for MVS/ESA alerts when supporting SNA/APPN traffic).

The S/390 Open Systems Adapter has been implemented as a new channel type on the supported S/390 processors/servers, an integrated hardware feature to provide a direct connection between the S/390 processor/server and the LAN. The S/390 Open Systems Adapter provides direct connectivity to LANs, LAN backbones, hubs, bridges, and routers that conform to industry standards.

Consulting, design, installation, and operational services are available to provide industry standard solutions that integrate the client/server capability of the S/390 Open Systems Adapter into premise, campus and wide-area networks.

Hardware Requirements

The S/390 Open Systems Adapter feature is supported on the following S/390 processors/servers:

  • S/390 Parallel Enterprise Server Models R11, R21, R31, R41, R51, R61. These models must have Engineering Change D79541 or above installed.

S/390 Open Systems Adapter Support Facility for MVS/ESA Hardware Requirements

The following hardware is required to run the S/390 Open Systems Adapter Support Facility:

  • One of the supported S/390 processors/servers

  • 100 MB of S/390 DASD for each S/390 Open Systems Adapter feature when the application running on the S/390 Open Systems Adapter is LANRES/MVS.

  • 30 MB of S/390 DASD for each S/390 Open Systems Adapter feature when the application running on the S/390 Open Systems Adapter is LFS/ESA for MVS or TCP/IP offload (TCP/IP protocol processing performed on the S/390 Open Systems Adapter).

  • A 9-track/6250 bpi magnetic tape drive or an 18-track/34K 3480 tape cartridge drive

The S/390 Open Systems Adapter Support Facility is required for all MVS/ESA environments, with the exception of TCP/IP for MVS passthru (TCP/IP protocol processing performed on the host). The S/390 Open Systems Adapter Support Facility for MVS/ESA application can co-exist with other applications on the workstation. A dedicated workstation is not required.

Note: The S/390 Open Systems Adapter Support Facility for MVS/ESA is required when sharing of S/390 Open Systems Adapter applications and/or LAN ports among logical partitions is desired. The S/390 Open Systems Adapter Support Facility for MVS/ESA is highly recommended for the TCP/IP for MVS passthru environment.

The following hardware is required to run the workstation for the S/390 Open Systems Adapter Support Facility for MVS/ESA.

  • A workstation with an 80386SX, 16MHz or better microprocessor

  • Sufficient memory to support IBM Operating System/2* (OS/2*) (8 MB or more of memory is recommended)

  • A communications adapter that supports the CPIC or TCP/IP communications protocol and is supported by OS/2 and the 80386

  • A node supporting LU 6.2 (if CPIC)

S/390 Open Systems Adapter Cable Planning Information:

Note: The cables used to attach the S/390 Open Systems Adapters to the Local Area Network (LAN) are a customer responsibility.

S/390 Open Systems Adapter Ethernet Feature:

This feature supports attachment to a 10 Mbit/second Ethernet LAN that conforms to either the IEEE 802.3 or the Ethernet V2.0 specifications.

The customer interface for each of the Ethernet features is a tailgate panel containing five standard Attachment Unit Interface (AUI) connections or ports. Each is a female 15-pin subminiature "D" Shell connector with a slide latch for cable retention.

Each of the five Ethernet ports can be connected to an external transceiver referred to as a MAU (Medium Attachment Unit) via an AUI cable. AUI cables are a customer responsibility.

The tailgate panel will accept either an IEEE 802.3 AUI cable or an Ethernet V2.0 AUI cable. The maximum length cable that can be supported from the S/390 Open Systems Adapter Ethernet feature to a MAU, Hub (e.g. IBM 8250 or equivalent), or repeater is 50 meters (164 feet).

Note: There is up to a 1.5 meter (4.9 feet) internal AUI cable between the S/390 Open Systems Adapter Ethernet feature and the tailgate panel, so the maximum supported length of the external AUI cable is 48.5 meters (159 feet).

The actual length of the AUI cable from the tailgate panel to the MAU depends upon the customer's installation.

The type of MAU chosen is based upon the customer's installation. Using the appropriate MAU, the AUI interface supports the following connections:

  1. 10BASE5 - "thick" Ethernet
  2. 10BASE2 - "thin" Ethernet
  3. 10BASET - twisted pair Ethernet
  4. Fiber optic ST or SMA connection
S/390 Open Systems Adapter Token Ring 4/16 Feature:

This feature supports attachment to either a 4 Mbit/second or 16 Mbit/second Token Ring network that conforms to the IEEE 802.5 architecture.

When entering the token ring, the adapter will sense and conform to the speed of the ring. If no carrier is sensed on the ring the adapter will enter the ring at the speed it had last entered at successfully.

The customer interface for each of the Token Ring features is a tailgate panel containing five connectors or ports. Each is a female 9-pin subminiature "D" Shell connector supporting 4-40 screw locks for cable retention. This design supports a shielded twisted pair (STP) interface.

An attachment cable (IBM P/N 6339098 or equivalent) is required for each of the five Token Ring ports and must be ordered separately, with length based on the installation requirements. This attachment cable is a customer responsibility. Standard cabling is used as needed from the tailgate panel to a Token Ring MAU (Medium Attachment Unit or Multistation Access Unit), (e.g. IBM 8228 or equivalent).

Note: There is up to a 1.2 meter (3.9 feet) internal shielded twisted pair cable between the S/390 Open Systems Adapter Token Ring feature and the tailgate panel. The maximum supported length of the external cable is dependent upon the type of cable and/or the gauge of the wire.

For Type 1 cable, the maximum distance from the tailgate panel to the MAU is 97.5 meters (320 feet). For Type 2 cable, the maximum distance from the tailgate panel to the MAU is 97.5 meters (320 feet) for 22 gauge wire and 64 meters (210 feet) for 26 gauge wire. S/390 Open Systems Adapter FDDI Feature:

This feature supports attachment to a 100 Mbit/second Fiber Distributed Data Interface (FDDI) Local Area Network (LAN) that conforms to the American National Standard Institute (ANSI) X3T9.5 specification and the International Standards Organization 9314 (ISO) specification. Both dual ring and single ring attachments are supported. In addition, the S/390 Open Systems Adapter FDDI feature supports optical bypass when used with an externally connected optical bypass switch. The optical bypass switch is not included with this feature, and is a customer responsibility.

Multimode fiber optic FDDI jumper cables are required to connect the S/390 Open Systems Adapter FDDI feature into the FDDI ring. Two FDDI jumper cables are required for dual ring configurations and one FDDI jumper cable is required for single ring configurations. The recommended fiber cross section is 62.5/125 micron fiber. The FDDI jumper cables connect directly to the transmitter and receiver of the S/390 Open Systems Adapter FDDI feature. Each FDDI connector is a standard Media Interface Connector (MIC). The FDDI jumper cables are not included with this feature, and are a customer responsibility.

When an optical bypass switch is used, the S/390 Open Systems Adapter FDDI feature provides the necessary 5 volts to power the switch. The connection is made at the tailgate panel via a female 9-pin subminiature "D" shell connector supporting 4-40 screw locks for cable retention. The optical connections are made directly to the transmitter and receiver of the S/390 Open Systems Adapter FDDI feature to maximize the optical power budget available. The 5 volt power connection is made at the tailgate panel to minimize Electromagnetic interference (EMI). The "D" shell connector has the following pin assignments:

 D01       +5V to secondary switch
 D02       +5V to primary switch
 D03-D05   Ground
 D06       Sense switch presence
 D07-D09   Sense no connection
 

If the cables coming off the optical bypass switch are of insufficient length, extensions cables must be ordered from the supplier. For the 5 volt power cable, a 9 pin "D" shell male to female extension cable should be used.

Note: To assure proper voltage at the optical bypass switch, the external cable length from the S/390 Open Systems Adapter FDDI feature tailgate panel to the optical bypass switch should not exceed 12.2 meters (40 feet).

Refer to the "IBM Cabling System Optical Fiber Planning and Installation Guide," (GA27-3943), and "IBM FDDI Network Introduction and Planning Guide," (GA27-3892), for more information about the jumper cables, and planning, design and installation of optical fiber cabling systems. Jumper cables are the responsibility of the customer and may be ordered from your local authorized IBM cabling distributor or by calling 1-800-IBM-2468 in the United States and 1-800-465-1234 in Canada. For EMEA customers, cables are available from Montpellier through CE offerings (Cablex ordering).

Software Requirements

The S/390 Open Systems Adapter Feature and the S/390 Open Systems Adapter Support Facility for MVS/ESA is supported by the following operating systems:

  • MVS/ESA* SP Version 5 Release 2 (5655-068 or 5655-069)

  • MVS/ESA SP Version 5 Release 1 (5655-068 or 5655-069)

  • MVS/ESA SP Version 4 Release 3 (5695-047 or 5695-048)

Contact your IBM Support Center for the PTFs required on these releases.

For HCD users on MVS/ESA Version 4 Release 3, HCD 5.1 is required. Install one of the following Feature Codes: 5890, 5891, or 5892.

The S/390 Open Systems Adapter Feature is supported by the following operating system:

  • VM/ESA Version 2 Release 1.0 (5654-030)

The following software provides enhanced support for the S/390 Open Systems Adapter Feature:

  • RMF* Version 5 Release 1 (5655-084)

  • ESCON* Manager Version 1 Release 3 with PTFs. Contact your IBM Support Center (5688-008)

    ESCON Manager can:

    • Recognize and display a S/390 Open Systems Adapter channel type, the devices, and the I/O paths between them

    • Provide control and status displays of the logical S/390 Open Systems Adapter I/O configuration, similar to those provided for ESCON channels.

The following application programs are supported by the S/390 Open Systems Adapter Feature:

Refer to the application documentation for application-specific requirements.

  • TCP/IP Version 2 Release 2 for MVS (5735-HAL) or above

  • TCP/IP for VM Version 2 Release 3 (5735-FAL)

  • ACF/VTAM Version 4 Release 2 for MVS/ESA with PTF (5695-117)

  • LAN File Services/ ESA for MVS Version 1 Release 1.2 with PTFs (5648-039).

    Note: A PTF is required to be installed to support this program product if MVS/ESA SP Version 5 Release 2 is not installed. Contact your IBM Support Center.

  • LAN Resource Extension and Services/MVS (LANRES/MVS) Version 1 Release 3.0 (5695-123)

    Note: A PTF is required to be installed to support this program product if MVS/ESA SP Version 5 Release 2 is not installed. Contact your IBM Support Center.

    LANRES/MVS requires one of the following:

    • NetWare** Version 3.12 from IBM, Multiuser Version

    • Novell** NetWare Version 3.12, Multiuser Version

    If SNA support is required, select one of the following:

    • NetWare for SAA Version 1.3B from IBM

    • Novell NetWare for SAA Version 1.3B

    A DOS-capable workstation for running RCONSOLE (Can be the same workstation used by the S/390 Open Systems Adapter Support Facility for MVS/ESA)

S/390 Open Systems Adapter Support Facility for MVS/ESA Software Requirement

The following additional software must be installed:

  • Time Sharing Options Extensions (TSO/E) Version 2 Release 4 (5685-025)

  • C/370* Library Version 2 Release 2 for MVS (5688-188)

  • Host Editor to edit MVS/ESA datasets (e.g., Interactive System Productivity Facility (ISPF) Version 3 Release 5 (5685-054))

The following products are optional and may be helpful additions in running the S/390 Open Systems Adapter Support Facility for MVS/ESA:

  • RACF* Version 1 Release 9.2 (5740-XXH) with PTFs

    • Provides access control for the S/390 Open Systems Adapter Support Facility for MVS/ESA commands. (An equivalent external security manager can also be used).

  • NetView for MVS/ESA Version 1 Release 3 with PTFs (5685-152)

    • Provides the ability to issue S/390 Open Systems Adapter Support Facility for MVS/ESA commands from NetView.

  • Appropriate support for communications (if workstation installed)

    • For TCP/IP protocol: TCP/IP Version 2 Release 2 for MVS (5735-HAL) or above

    • For APPC Common Programming Interface for Communications (CPI-C) or EHLLAPI (3270) protocol: ACF/VTAM Version 4 Release 2 for MVS/ESA with PTF

The following software is required to run the workstation interface for the S/390 Open Systems Adapter Support Facility for MVS/ESA:

  • OS/2 2.1 or above

The following support on the workstation for communication is required:

  • For TCP/IP protocol: TCP/IP Version 2.0 for OS/2 (65G1220) or above

  • For APPC (CPI-C) or EHLLAPI (3270) protocol: Communications Manager/2 1.1 or above.

Back to top
 
Models

Model Summary Matrix

                              Optional
                              Expansion  ESCON or           Processor
                               Box for   Parallel  Storage  Unit Card
          Frame QTY  CEC QTY  Chan Crds  Channels   Range   Range/CEC
Models    Min - Max   Total    Maximum     MAX      (MB)     (X-Way)
--------  ---- ----  -------  ---------  --------  -------  ---------
9672-R11   1     1      1         0         48     128-2GB      1
9672-R21   1     1      1         0         48     128-2GB      2
9672-R31   1     1      1         0         48     128-2GB      3
9672-R41   1     1      1         0         48     128-2GB      4
9672-R51   1     1      1         0         48     128-2GB      5
9672-R61   1     1      1         0         48     128-2GB      6
 

9672 Model Rx1 Configurations:

*_______________________________________________*
|                                               |
|              MODELS R11 THRU R61              |
*-------*-------*-------*-------*-------*-------*
|  R11  |  R21  |  R31  |  R41  |  R51  |  R61  |
*_______________________________________________*
|                                               |
|          CENTRAL PROCESSORS PER MODEL         |
|                                               |
*-------*-------*-------*-------*-------*-------*
|   1   |   2   |   3   |   4   |   5   |   6   |
*_______________________________________________*
|           CENTRAL STORAGE PER MODEL           |
|      Minimum  /  Maximum  / (Increments)      |
*-----------------------------------------------*
|  128MB  /  2 GB  /  (128MB/256MB/512MB/1GB)   |
*_______________________________________________*
|              CHANNELS PER MODEL               |
|   Minimum / Maximum / Increments (see Note 1) |
*-----------------------------------------------*
|              3  /  48    /  3                 |
*_______________________________________________*
 

Notes:

  1. Parallel Channels on the R models can be cabled using standard bus and tag cables or the new 78D cables.

Maximum

Not applicable.

Customer Setup (CSU)

Not applicable.

Devices Supported

System/390 Parallel Enterprise Server Supported I/O Devices

The following I/O devices and control units are supported for attachment to System/390 Parallel Enterprise Server Parallel and ESCON channels as specified. It does not include devices and control units approved for attachment via the ESCON Converter, Model 1. These devices and control units can operate in ESA/390 mode and S/370* mode operating in a PR/SM partition in LPAR mode.

This list is updated periodically. Devices supported exclusively through a communications controller are not included.

SUPPORTED OEMI/PARALLEL I/O DEVICES

The following I/O devices and control units are supported for attachment to the IBM OEMI/parallel channel interface.

DIRECT ACCESS STORAGE DEVICE (DASD) CONTROLLERS             BLOCK  BYTE
 
3880 - 001,002,003            Storage Controller              X
3880 - 011,013,021,023        Storage Controller              X
3990 - 001,002,003,006        Storage Controller              X
3995 - 131,132,151,153        Optical Library Dataserver      X
3995 - 133,153                Optical Library Dataserver      X
9341 - A02                    Storage Controller              X
9343 - C02,C04,CC2,CC4        Storage Controller              X
9394 - 001,002,003            RAMAC Array Subsystem           X
 
MAGNETIC TAPE UNITS                                         BLOCK  BYTE
 
3480 - A11,A22                Magnetic Tape Subsystem         X
3490 - A01,A02,A10,A20        Magnetic Tape Subsystem         X
3490 - C1A,C2A,C10,C11,C22    Magnetic Tape Subsystem         X
3490 - D31,D32,D41,D42        Magnetic Tape Subsystem         X
3494 - L10                    Tape Library Dataserver         X
 
PRINTERS                                                    BLOCK  BYTE
 
3800 - 001,003,006            Printing Subsystem              X
3820 - 001                    Page Printer                    X
3825 - 001                    Page Printer                    X
3827 - 001                    Page Printer                    X
3828 - 001                    Page Printer                    X
3835 - 001,002                Page Printer                    X
3900 - DW1,DW2,D01,D02,       Duplex Printing System          X
       0W1,0W3,001
 
MISCELLANEOUS                                               BLOCK  BYTE
 
3088 - 0A1,001,002            Multisys. Channel Comm. Unit    X
3172 - 001,003                Interconnect Controller         X
3174 - 11L,21L                Establishment Controller        X     X
3745 - 130,150,170            Communications Controller       X     X
3814 - A01,A02,A03,A04        Switching Management System     X     X
6098 - 001                    Control Unit                    X
7013 - All Models             RS/6000                         X
 
MODELS: J01, J30, 52E, 52H, 520, 53E, 53H, 530, 540, 55E,
55L, 55S, 550, 56F, 560, 57F, 57L, 570, 571, 58F, 58H, 580,
581, 59H, 590
 
7015 - All Models             RS/6000                         X
MODELS R00, R10, R20, R24, R3U, R30, 930, 95E, 950, 951, 97B,
97E, 97F, 970, 98B, 98E, 98F, 980, 99E, 99F, 99J, 99K, 990.
 
9035 - 002                    ESCON Converter Model 2         X
9076 SP1, SP2 - All Models *   Power Parallel Systems         X
 
*MODELS: A01, 001, 002, 003, 004, 101, 201, 202, 203, 204,
3A2, 3A3, 3A4, 3B2, 3B3, 3B4, 301, 302, 303, 304, 401, 402,
403, 404,
 
SUPPORTED ESCON I/O DEVICES
 
The following I/O devices and control units are supported for
attachment to the ESCON channel.
 
DIRECT ACCESS STORAGE DEVICE (DASD) CONTROLLERS
 
3990 - 002,003,006            Storage Controller
3995 - 133                    Optical Library Dataserver
9341 - A02                    Storage Controller
9343 - D04,DC4                Storage Controller
9394 - 001,002,003            RAMAC Array Subsystem
 
MAGNETIC TAPE UNITS
 
3490 - A01,A02,A10,A20        Magnetic Tape Subsystem
3490 - C1A,C2A,C10,C11,C22    Magnetic Tape Subsystem
3490 - D31,D32,D41,D42        Magnetic Tape Subsystem
3494 - L10                    Tape Library Dataserver
 
MISCELLANEOUS
 
3172 - 001,003                Interconnect Controller
3174 - 12L, 22L               Establishment Controller
3745 - 17A,21A,31A,41A,61A    Communications Controller
3900 - DW1,DW2,D01,D02,       Duplex Printing System
       0W1,0W3
 
7013 - All Models             RS/6000
7015 - All Models             RS/6000
9032 - 002,003                ESCON Director
9033 - 001                    ESCON Director
9034 - 001                    ESCON Converter
9036 - 001,002                ESCON Remote Channel Extender
9076 SP1, SP2, All Models     Power Parallel Systems
 

Model Conversions

(For IBM US, some model conversions are no longer available as of May 24, 1998. See announcement letters for details.)

All model upgrades, as well as memory and feature upgrades, can be field installed by IBM Service representatives.

Upgrades may involve the replacement or removal of parts which become the property of IBM and must be returned to IBM. Parts returned must be unaltered.

The installation of additional features such as channels, or the installation of required microcode levels, affects the total installation time.

Model and memory downgrades are not available.

Vertical upgrades:
     FROM                   TO
---------------        --------------
9672 Model  R11        9672 Model R21
9672 Model  R11        9672 Model R31
9672 Model  R11        9672 Model R41
9672 Model  R11        9672 Model R51
9672 Model  R11        9672 Model R61
 
Horizontal upgrades: FROM TO --------------- -------------- 9672 Model R11 9672 Model E01 9672 Model R11 9672 Model E02 9672 Model R11 9672 Model P01 9672 Model R11 9672 Model P02  

Horizontal/Diagonal Upgrades: FROM TO --------------- -------------- 9672 Model R11 9672 Model R12 9672 Model R11 9672 Model R22 9672 Model R11 9672 Model R32 9672 Model R11 9672 Model R42 9672 Model R11 9672 Model R52 9672 Model R11 9672 Model R72 9672 Model R11 9672 Model R53 9672 Model R11 9672 Model R63 9672 Model R11 9672 Model R73 9672 Model R11 9672 Model R83 9672 Model R11 9672 Model RX3  

     From                  To
--------------       --------------
 
9672 Model R11       9672 Model RA4
9672 Model R11       9672 Model R14
9672 Model R11       9672 Model RB4
9672 Model R11       9672 Model R24
9672 Model R11       9672 Model RC4
9672 Model R11       9672 Model R34
9672 Model R11       9672 Model R44
 
9672 Model R11       9672 Model R54
9672 Model R11       9672 Model R64
9672 Model R11       9672 Model R74
9672 Model R11       9672 Model R84
9672 Model R11       9672 Model R94
9672 Model R11       9672 Model RX4
 
Vertical upgrades:
     FROM                   TO
---------------        --------------
9672 Model  R21        9672 Model R31
9672 Model  R21        9672 Model R41
9672 Model  R21        9672 Model R51
9672 Model  R21        9672 Model R61
 
Horizontal upgrades: FROM TO --------------- -------------- 9672 Model R21 9672 Model E01 9672 Model R21 9672 Model E02 9672 Model R21 9672 Model P01 9672 Model R21 9672 Model P02  

Horizontal/Diagonal Upgrades: FROM TO --------------- -------------- 9672 Model R21 9672 Model R22 9672 Model R21 9672 Model R32 9672 Model R21 9672 Model R42 9672 Model R21 9672 Model R52 9672 Model R21 9672 Model R72 9672 Model R21 9672 Model R53 9672 Model R21 9672 Model R63 9672 Model R21 9672 Model R73 9672 Model R21 9672 Model R83 9672 Model R21 9672 Model RX3  

     From                 To
--------------       --------------
 
9672 Model R21       9672 Model R14
9672 Model R21       9672 Model RB4
9672 Model R21       9672 Model R24
9672 Model R21       9672 Model RC4
9672 Model R21       9672 Model R34
9672 Model R21       9672 Model R44
 
9672 Model R21       9672 Model R54
9672 Model R21       9672 Model R64
9672 Model R21       9672 Model R74
9672 Model R21       9672 Model R84
9672 Model R21       9672 Model R94
9672 Model R21       9672 Model RX4
 
Vertical upgrades:
     FROM                   TO
---------------        --------------
9672 Model  R31        9672 Model R41
9672 Model  R31        9672 Model R51
9672 Model  R31        9672 Model R61
 
Horizontal upgrades: FROM TO --------------- -------------- 9672 Model R31 9672 Model E01 9672 Model R31 9672 Model E02 9672 Model R31 9672 Model P01 9672 Model R31 9672 Model P02  

Horizontal/Diagonal Upgrades: FROM TO --------------- -------------- 9672 Model R31 9672 Model R32 9672 Model R31 9672 Model R42 9672 Model R31 9672 Model R52 9672 Model R31 9672 Model R72 9672 Model R31 9672 Model R53 9672 Model R31 9672 Model R63 9672 Model R31 9672 Model R73 9672 Model R31 9672 Model R83 9672 Model R31 9672 Model RX3  

     From                  To
--------------       --------------
 
9672 Model R31       9672 Model RB4
9672 Model R31       9672 Model R24
9672 Model R31       9672 Model RC4
9672 Model R31       9672 Model R34
9672 Model R31       9672 Model R44
 
9672 Model R31       9672 Model R54
9672 Model R31       9672 Model R64
9672 Model R31       9672 Model R74
9672 Model R31       9672 Model R84
9672 Model R31       9672 Model R94
9672 Model R31       9672 Model RX4
 
Vertical upgrades:
     FROM                   TO
---------------        --------------
9672 Model  R41        9672 Model R51
9672 Model  R41        9672 Model R61
 
Horizontal upgrades: FROM TO --------------- -------------- 9672 Model R41 9672 Model E01 9672 Model R41 9672 Model E02 9672 Model R41 9672 Model P01 9672 Model R41 9672 Model P02  

Horizontal/Diagonal Upgrades: FROM TO --------------- -------------- 9672 Model R41 9672 Model R32 9672 Model R41 9672 Model R42 9672 Model R41 9672 Model R52 9672 Model R41 9672 Model R72 9672 Model R41 9672 Model R53 9672 Model R41 9672 Model R63 9672 Model R41 9672 Model R73 9672 Model R41 9672 Model R83 9672 Model R41 9672 Model RX3  

     From                 To
--------------       --------------
 
9672 Model R41       9672 Model R24
9672 Model R41       9672 Model RC4
9672 Model R41       9672 Model R34
9672 Model R41       9672 Model R44
 
9672 Model R41       9672 Model R54
9672 Model R41       9672 Model R64
9672 Model R41       9672 Model R74
9672 Model R41       9672 Model R84
9672 Model R41       9672 Model R94
9672 Model R41       9672 Model RX4
 
Vertical upgrades:
     FROM                   TO
---------------        --------------
9672 Model  R51        9672 Model R61
 
Horizontal upgrades: FROM TO --------------- -------------- 9672 Model R51 9672 Model E01 9672 Model R51 9672 Model E02 9672 Model R51 9672 Model P01 9672 Model R51 9672 Model P02  

Horizontal/Diagonal Upgrades: FROM TO --------------- -------------- 9672 Model R51 9672 Model R42 9672 Model R51 9672 Model R52 9672 Model R51 9672 Model R72 9672 Model R51 9672 Model R53 9672 Model R51 9672 Model R63 9672 Model R51 9672 Model R73 9672 Model R51 9672 Model R83 9672 Model R51 9672 Model RX3  

     From                 To
--------------       --------------
 
9672 Model R51       9672 Model RC4
9672 Model R51       9672 Model R34
9672 Model R51       9672 Model R44
 
9672 Model R51       9672 Model R54
9672 Model R51       9672 Model R64
9672 Model R51       9672 Model R74
9672 Model R51       9672 Model R84
9672 Model R51       9672 Model R94
9672 Model R51       9672 Model RX4
 
Horizontal upgrades:
     FROM                   TO
---------------        --------------
9672 Model  R61        9672 Model E01
9672 Model  R61        9672 Model E02
9672 Model  R61        9672 Model P01
9672 Model  R61        9672 Model P02
 

Horizontal/Diagonal Upgrades: FROM TO --------------- -------------- 9672 Model R61 9672 Model R42 9672 Model R61 9672 Model R52 9672 Model R61 9672 Model R72 9672 Model R61 9672 Model R53 9672 Model R61 9672 Model R63 9672 Model R61 9672 Model R73 9672 Model R61 9672 Model R83 9672 Model R61 9672 Model RX3  

     From                 To
--------------       --------------
 
9672 Model R61       9672 Model RC4
9672 Model R61       9672 Model R34
9672 Model R61       9672 Model R44
 
9672 Model R61       9672 Model R54
9672 Model R61       9672 Model R64
9672 Model R61       9672 Model R74
9672 Model R61       9672 Model R84
9672 Model R61       9672 Model R94
9672 Model R61       9672 Model RX4
 

Note: When vertical upgrades are processed, CFSYSTEM will generate a feature exchange to remove the 'from' PU Card feature code and add the 'to' PU Card feature code.

The primary difference between the R models and E/P models is the addition of coupling links on the E/P models. Also, tailgates will be added or deleted depending on the upgrade.

The R11 upgrade to a 9672 E or P model requires you to also upgrade your processor card since the 1-way is not available on the E and P models. The upgrade can be to a 2-way through 6-way processor card.

Note: The following scenarios depict model conversions from R*1 to R*2 or R*3. It is a representation of certain parts that remain or get replaced/exchanged when converting from the R*1 to the R*2 or R*3 models.

 
MODEL UPGRADE R*1 TO R*2 OR R*3 R*1 HARDWARE R*1 HARDWARE A Frame ------> B Frame *-------------------------* *--------------------------* | | | | | | | | | 9672 | | 9672 | | | | | | CEC | | EXPANSION CAGE | | | ------> | | | FC 0010 | | FC 1000 | | | | | | | | | | | | | |-------------------------| |--------------------------| | | | | | | | | | 9672 | | 9672 | | | | | | EXPANSION CAGE | ------> | EXPANSION CAGE | | | | | | FC 1000 | | FC 1000 | | | | | | | | | | | | | *-------------------------* *--------------------------*  

Notes:

  1. The R*1 Hardware (including its frame) will be moved from the "A" Frame position to the "B" Frame position. The R*2/R*3 Hardware will assume the "A" Frame position. It is not NECESSARY to move the FRAME unless its location prevents the R2/3 from being placed before the "B" Frame.

  2. Except for the ISC Adapter and Links, all of the R*1 hardware that is used on the R*2/R*3 models must remain in the R*1 "B" Frame (Details and Examples to follow).

Parts That are affected by the Upgrade

  • Items that will be REMOVED:
    1. STORM MAU
    2. STORM SE
    3. EPO
    4. TAILGATE
    5. PU (Processing Unit)
    6. Memory
    7. TORNADO - Feature Code 2000
    8. ETR - Feature Code 6151 (Feature Code 6152 and 6150 will be MOVED)
    9. Extra STORM Frames.
    10. IF there are MORE then TWO 6101/2. Three and above will be removed.

  • Items that will be MOVED:

    1. ETR - Feature Code 6150 and 6152 (Feature Code 6151 will be REMOVED)

  • Items that will be Kept in the Expansion Cage or the Converted CEC:
    1. CEC (STORM) is converted from F/C 0010 to Expansion Cage F/C 1000
    2. ESCON Channels (STORM) Feature Code 6113
    3. XDF Channels (STORM) Feature Code 6114
    4. Parallel Channels (STORM) Feature Code 6103
    5. OSA-1 (STORM) Feature Code 5001
    6. ISC Cards - Quantity of TWO or LESS will be kept and placed in Slots 19 and 17.

  • Items that need to ADDED to the Expansion Cage/s:
    1. Redrive Card
    2. Air Flow Card
    3. UEPO Cable
    4. UPC Cables
MODEL UPGRADE R*1 TO R*2
 
The following is an example of R*1 to R*2 Conversions:
 
 
    Example 1:  R*1 CEC Only Upgrade to an R*2
 
                          Feature Exchange
            *-----------------------------------------------*
            |                                               |
            |                                               |
       R*1 CEC ONLY                  R*2 CEC ONLY      R*1 Hardware
         A Frame                       A Frame           B Frame
    |----------------|           |-----------------||-----------------|
    |                |           |                 ||                 |
    |      CEC       |           |       CEC       ||    EXPANSION    |
    |    FEATURE     |           |     FEATURE     ||      CAGE       |
    |     CODE       |           |      CODE       ||     FEATURE     |
    |                |           |                 ||                 |
    |     0010       |           |      0020       ||      1000       |
    |    (STORM)     |           |    (CYCLONE)    ||     (STORM)     |
    |----------------|           |-----------------||-----------------|
    |                |           |  Optional       ||                 |
    |                |           |     I/O Cage    ||                 |
    |    Empty       |           |     OSA-1       ||     Empty       |
    |                |           |                 ||                 |
    |                |           |                 ||                 |
    |                |           |                 ||                 |
    |                |           |                 ||                 |
    |----------------|           |-----------------||-----------------|
 
The following is an example of R*1 to R*2 Conversion with
Expansion Cage:
 
 
    Example 2:  R*1 CEC with Expansion Upgrade to an R*2
 
                          Feature Exchange
            *-----------------------------------------------*
            |                                               |
            |                                               |
       R*1 CEC ONLY                  R*2 CEC ONLY      R*1 Hardware
         A Frame                       A Frame           B Frame
    |----------------|           |-----------------||-----------------|
    |                |           |                 ||                 |
    |      CEC       |           |       CEC       ||    EXPANSION    |
    |    FEATURE     |           |     FEATURE     ||      CAGE       |
    |     CODE       |           |      CODE       ||     FEATURE     |
    |                |           |                 ||                 |
    |     0010       |           |      0020       ||      1000       |
    |    (STORM)     |           |    (CYCLONE)    ||     (STORM)     |
    |----------------|           |-----------------||-----------------|
    |                |           |  Optional       ||                 |
    |    EXPANSION   |           |                 ||    EXPANSION    |
    |      CAGE      |           |     OSA-1       ||      CAGE       |
    |     FEATURE    |           |                 ||     FEATURE     |
    |                |           |                 ||                 |
    |      1000      |           |                 ||      1000       |
    |     (STORM)    |           |                 ||     (STORM)     |
    |----------------|           |-----------------||-----------------|
 
The following is an examples of R*1 with OSA-1 to R*2
Conversions:
 
 
    Example 3:  R*1 CEC with Expansion and OSA-1 Upgrade to an R*2
 
                          Feature Exchange
              *------------------------------------------*
              |                                          |
              |                                          |
        R*1 Hardware                 R*2 CEC       R*1 Hardware
     Z Frame   A Frame               A Frame    B Frame    C Frame
   |---------||---------|          |---------||---------||---------|
   | Optional||   CEC   |          |   CEC   ||EXPANSION|| Optional|
   | OSA-1   || FEATURE |          | FEATURE ||  CAGE   || OSA-1   |
   |         ||  CODE   |          |   CODE  || FEATURE ||         |
   |         ||         |          |         ||         ||         |
   |         ||  0010   |          |  0020   ||  1000   ||         |
   |         || (STORM) |          |(CYCLONE)|| (STORM) ||         |
   |---------||---------|          |---------||---------||---------|
   | Optional||         |          |         ||         || Optional|
   | OSA-1   ||EXPANSION|          |         ||EXPANSION|| OSA-1   |
   |         ||  CAGE   |          |  Empty  ||  CAGE   ||         |
   |         || FEATURE |          |         || FEATURE ||         |
   |         ||         |          |         ||         ||         |
   |         ||  1000   |          |         ||  1000   ||         |
   |         || (STORM) |          |         || (STORM) ||         |
   |---------||---------|          |---------||---------||---------|
 
   Note:  OSA-1 is limited to one (1) per CEC.
 
The following is an examples of R*1/P01 with Tailgate and
OSA-1 to R*2 Conversions:
 
 
    Example 4:  R*1/P01 CEC with Expansion, Tailgate and OSA-1 Upgraded
                to an R*2.
 
                          Feature Exchange
               *--------------------------------------*
               |                                      |
               |                                      |
          R*1 Hardware              R*2 CEC       R*1 Hardware
  Y Frame    Z Frame   A Frame      A Frame    B Frame    C Frame
|----------|----------|--------|  |----------||---------|----------|
| Optional |EXPANSION |  CEC   |  |          ||  PSC (2)|  Optional|
| OSA-1    |  CAGE    |FEATURE |  |          ||---------|  OSA-1   |
|          |          | CODE   |  |    CEC   ||EXPANSION|          |
|          |          |        |  |  FEATURE ||  CAGE   |          |
|          |  1000    | 0010   |  |   0020   ||  1000   |          |
|          | (STORM)  |(STORM) |  | (CYCLONE)|| (STORM) |          |
|----------+----------+--------|  |----------||---------+----------|
|          |Optional  |Optional|  |          ||         |  Optional|
|          |PSC       |PSC     |  |          ||EXPANSION|  OSA-1   |
| Empty    |----------+--------|  |  Empty   ||  CAGE   |          |
|          |TAILGATE  |TAILGATE|  |          || FEATURE |          |
|          |----------+--------|  |          ||         |          |
|          |          |        |  |          ||  1000   |          |
|          |          |        |  |          || (STORM) |          |
|----------|----------|--------|  |----------||---------|----------|
 

Notes:

  1. The "A" Frame and the Tailgates from the "A" and the "Z" Frames will be removed from the system and returned to MFG via FEATURE EXCHANGE.

  2. The CEC (Feature Code 0010) in the "A" Frame will be converted to an Expansion Cage (Feature Code 1000) via FEATURE EXCHANGE and moved to the bottom of the "Z" Frame.

  3. PSC boxes will be removed and reinstalled as pictured. There is room for one set (2 PSC boxes) to be placed above the converted CEC (top half of "B" Frame). If there are more then one set (2) 6101/2 they will be discarded. If more PSCs are required, Feature Code 6201/2 MUST and installed in the "A" and "Z" and connected to the PASSAT or the CYCLONE as required.

  4. The Expansion Cage in the LOWER half of the STORM Frames will NEVER have a PSC box above it (this is an exception to the PSC placement RULES).
MODEL UPGRADE R*1 TO R*3
 
The following is an examples of R*1 to R*3 Conversions:
 
 
    Example 5:  R*1 CEC Only Upgrade to an R*3
 
                          Feature Exchange
            *-------------------------------------------------*
            |                                                 |
            |                                                 |
       R*1 CEC ONLY                          R*3 CEC ONLY R*1 Hardware
         A Frame                  Z Frame      A Frame     B Frame
      |-----------|            |-----------||-----------||-----------|
      |    CEC    |            | Optional  ||    CEC    ||EXPANSION  |
      |  FEATURE  |            | I/O Cage  ||  FEATURE  ||  CAGE     |
      |   CODE    |            |           ||   CODE    || FEATURE   |
      |           |            |           ||           ||           |
      |   0010    |            |           ||   0030    ||  1000     |
      |  (STORM)  |            |           ||(HURRICANE)|| (STORM)   |
      |-----------|            |-----------||-----------||-----------|
      |           |            | Optional  || Optional  ||           |
      |           |            | I/O Cage  ||  I/O Cage ||           |
      |  Empty    |            | OSA-1     ||           ||  Empty    |
      |           |            |           ||           ||           |
      |           |            |           ||           ||           |
      |           |            |           ||           ||           |
      |           |            |           ||           ||           |
      |-----------|            |-----------||-----------||-----------|
 
The following is an examples of R*1 with Expansion Cage to
R*3 Conversions:
 
 
    Example 6:  R*1 CEC with Expansion Upgrade to an R*3
 
                          Feature Exchange
            *-------------------------------------------------*
            |                                                 |
            |                                                 |
       R*1 Hardware                   R*3 Hardware        R*1 Hardware
         A Frame                  Z Frame      A Frame     B Frame
      |-----------|            |-----------||-----------||-----------|
      |    CEC    |            | Optional  ||    CEC    ||EXPANSION  |
      |  FEATURE  |            | I/O Cage  ||  FEATURE  ||  CAGE     |
      |   CODE    |            |           ||   CODE    || FEATURE   |
      |           |            |           ||           ||           |
      |   0010    |            |           ||   0030    ||  1000     |
      |  (STORM)  |            |           ||(HURRICANE)|| (STORM)   |
      |-----------|            |-----------||-----------||-----------|
      | EXPANSION |            | Optional  || Optional  ||EXPANSION  |
      |   CAGE    |            | I/O Cage  ||  I/O Cage ||  CAGE     |
      |  FEATURE  |            | OSA-1     ||           || FEATURE   |
      |           |            |           ||           ||           |
      |   1000    |            |           ||           ||  1000     |
      |  (STORM)  |            |           ||           || (STORM)   |
      |           |            |           ||           ||           |
      |-----------|            |-----------||-----------||-----------|
 
The following is an examples of R*1 with OSA-1 to R*3
Conversions:
 
 
    Example 7:  R*1 CEC with Expansion and OSA-1 Upgrade to an R*3
 
                          Feature Exchange
         *-----------------------------------------------------*
         |                                                     |
         |                                                     |
    R*1 Hardware                  R*3 Hardware          R*1 Hardware
 Z Frame   A Frame            Z Frame     A Frame    B Frame    C Frame
|--------||---------|        |---------||---------||---------||---------|
|Optional||   CEC   |        |         ||   CEC   ||EXPANSION|| Optional|
|OSA-1   || FEATURE |        |         || FEATURE ||  CAGE   || OSA-1   |
|        ||  CODE   |        | Empty   ||  CODE   ||FEATURE  ||         |
|        ||         |        |         ||         ||         ||         |
|        ||  0010   |        |         ||  0030   ||  1000   ||         |
|        || (STORM) |        |         ||HURRICANE|| (STORM) ||         |
|--------||---------|        |---------||---------||---------||---------|
|Optional||         |        |Optional ||Optional ||         || Optional|
|OSA-1   ||EXPANSION|        |I/O Cage ||I/O Cage ||EXPANSION|| OSA-1   |
|        ||  CAGE   |        |         ||         ||  CAGE   ||         |
|        || FEATURE |        |         ||         || FEATURE ||         |
|        ||         |        |         ||         ||         ||         |
|        ||  1000   |        |         ||         ||  1000   ||         |
|        || (STORM) |        |         ||         || (STORM) ||         |
|--------||---------|        |---------||---------||---------||---------|
 
Note:  OSA-1 is limited to one (1) per CEC.
 
The following is an examples of R*1/P01 with Tailgate,
Expansion, and OSA-1 to R*3 Conversions:
 
 
    Example 8:  R*1 CEC with Expansion, Tailgate and OSA-1 Upgraded
                to an R*3.
 
                            Feature Exchange
               *------------------------------------------------*
               |                                                |
               |                                                |
          R*1 Hardware                        R*3 CEC       R*1 Hardware
  Y Frame   Z Frame   A Frame      Z Frame   A Frame    B Frame   C Frame
|---------|---------|--------|   |---------|---------||---------|---------|
| Optional|EXPANSION|  CEC   |   |         |   CEC   ||  PSC (2)| Optional|
| OSA-1   |  CAGE   |FEATURE |   |         | FEATURE ||---------| OSA-1   |
|         |         | CODE   |   | Empty   |  CODE   ||EXPANSION|         |
|         |         |        |   |         |         ||  CAGE   |         |
|         |  1000   | 0010   |   |         |  0020   ||  1000   |         |
|         | (STORM) |(STORM) |   |         |HURRICANE|| (STORM) |         |
|---------|---------|--------|   |---------|---------||---------|---------|
|         |Optional |Optional|   |Optional | PSC (2) ||         | Optional|
|         |PSC  (2) |PSC (2) |   |  PSC (2)|         ||EXPANSION| OSA-1   |
| Empty   |---------|--------|   |---------|---------||  CAGE   |         |
|         |TAILGATE |TAILGATE|   |Optional |Optional || FEATURE |         |
|         |---------|--------|   |I/O Cage |I/O Cage ||         |         |
|         |         |        |   |         |         ||  1000   |         |
|         |         |        |   |         |         || (STORM) |         |
|---------|---------|--------|   |---------|---------||---------|---------|
 

Notes:

  1. The "A" Frame and the Tailgates from the "A" and the "Z" Frames will be removed from the system and returned to MFG via FEATURE EXCHANGE.

  2. The CEC (Feature Code 0010) in the "A" Frame will be converted to an Expansion Cage (Feature Code 1000) via FEATURE EXCHANGE and moved to the bottom of the "Z" Frame.

  3. PSC boxes will be removed and reinstalled as pictured. There is room for one set (2 PSC boxes) to be placed above the converted CEC (top half of "B" Frame). If there are more then one set (2) 6101/2, they will be discarded. If more PSCs are required, Feature Code 6201/2 MUST and installed in the "A" and "Z" and connected to the PASSAT or the CYCLONE as required.

  4. The Expansion Cage in the LOWER half of the STORM Frames will NEVER have a PSC box above it (this is an exception to the PSC placement RULES).

Parts removed as a result of a model change become the property of IBM.
Back to top
 

Technical Description
Physical Specifications Operating Environment Limitations
Hardware Requirements Software Requirements


Highlights

System/390 Parallel Enterprise Server processors provide high performance and flexibility due to its improved design and use of technology advances. The design of these models supports:

  • ESA/390 architectural mode of operation
  • Logically partitioned (LPAR) operating mode. up to ten logical partitions for each CEC can be defined.
  • Integrated Coupling Migration Facility (ICMF)
  • Enterprise Systems Connection Architecture* (ESCON Architecture) and technology for the ESCON channels
  • ESCON Multiple Image Facility (EMIF)
  • Data compression
  • Dynamic I/O configuration
  • Optional IBM Sysplex Timer* attachment
  • CICS* group subspace facility
  • Asynchronous data mover facility (ADMF)
  • Logical string assist
  • Asynchronous pageout facility
  • High levels of reliability, availability, and serviceability
  • Online information

ESA/390 Architectural Mode of Operation

System/390 Parallel Enterprise Server provide the Enterprise Systems Architecture/390* (ESA/390) mode in three ways:

  • Basic mode
  • Mode of a logical partition in the LPAR mode
  • Mode of a guest virtual machine

In ESA/390 mode (which includes the functions of ESA/370* mode), these models have problem-program compatibility with System/360*, System/370, and 4300 processors. They can access virtual storage in multiple address spaces and data spaces. This extends addressability for system, subsystem, and application functions that use ESA/390.

ESA/390 mode provides:

  • 31-bit addressing with a virtual address range of 2GB (2,147,483,648 bytes).

  • ESCON and parallel channels.

  • Channel path selection and I/O-busy-condition management as hardware functions (rather than control program functions) that provide:

    • As many as eight channel paths available to each I/O device.

    • Increased I/O device accessibility by allowing each central processor to initiate operations with any of the I/O devices and to handle any I/O interruption conditions.

  • A significantly extended addressability through access to multiple address spaces and data spaces while maintaining compatibility with existing 24-bit and 31-bit subsystems and user applications. Each address space can contain as many as 2GB of programs and data. Each data space can contain as many as 2GB of data.

  • Support for the Start Interpretive Execution (SIE) instruction, allowing support of guest ESA/390 and System/370 virtual machines.

  • Support for the VM data space facility which makes the ESA/390 access-register architecture more useful in virtual machine applications. For more information, see "VM/ESA CP Programming Services," SC24-5520.

Logically Partitioned (LPAR) Operating Mode

The operating mode is set during system initialization (power-on reset). The operating mode can be basic mode (ESA/390 or ESA/390 TPF) or LPAR mode. When LPAR mode is selected the following must be specified:

  • Architectural mode (ESA/390 or ESA/390 TPF mode) for each logical partition
  • Resources for each logical partition
    • Central processors (CPs)
    • Storage (central storage and optional expanded storage)
    • Channels

Up to ten logical partitions can be defined.

Central Processors (CPs)

The System/390 Parallel Enterprise Server Model R11 has one Processor Unit (PU). The Processor Unit can be upgraded to either a 2-way, 3-Way, 4-way, 5-Way, or 6-way 9672 R model. This provides great performance granularity and a large number of flexible configurations to meet customers needs.

CPs can be dedicated to a single logical partition or shared among multiple logical partitions. The allocation of CPs to a logical partition is made when the logical partition is activated. The use of CP resources shared between logical partitions can be limited and modified by operator commands while the logical partitions are active. CPs that are dedicated to a logical partition are available only to that logical partition.

Storage

The System/390 Parallel Enterprise Server Model R11 has 128 MB of storage standard that can be increased to 256 MB, 512 MB, 1024 MB, or 2048 MB.

Before activation of logical partitions, central storage and optional expanded storage must be defined to the logical partitions. When a logical partition is activated, the storage resources are allocated in contiguous blocks. System/390 Parallel Enterprise Server models support a 16 MB storage granularity for both central and expanded storage. A minimum of 64-MB central storage is required. You can dynamically reallocate storage resources for ESA/390 mode and ESA/390 TPF mode logical partitions using dynamic storage reconfiguration. After you define and activate an ESA/390 logical partition, you can load a supporting operating system into that logical partition.

Note: Allocated central storage or expanded storage can not be shared among multiple logical partitions.

Channels

Model R11 has a maximum of 48 ESCON and/or Parallel channels which are installed in increments of 3.

Channels can be allocated to logical partitions as follows:

  • Dedicated channels
  • Reconfigurable channels
  • Shared channels (for EMIF-capable processor complexes only).

Dedicated Channels: Individual parallel channels (byte or block multiplexer), ESCON channels that attach to an ESCON Converter Model 1, ESCON channels, or coupling facility channels (both sender and receiver) can be allocated to each logical defined partition. Dedicated channels are unshared channels and can only be used by those logical partitions to which they are allocated.

Reconfigurable Channels: Parallel channels, ESCON channels that attach to an ESCON Converter Model 1, ESCON channels, or coupling facility sender channels as reconfigurable among allocated logical, defined partitions. Reconfigurable channels are unshared channels that can be dynamically moved among logical partitions but can only belong to one logical partition at a given time.

Shared Channels: ESCON channels and coupling facility sender channels can be allocated to be shared among multiple logical partitions so that the shared channels can be accessed by more than one logical partition at the same time.

Device Sharing: Device can be shared among logical partitions by:

  • Using a separate channel for each logical partition.

  • Using a shared ESCON channel if your processor complex is EMIF-capable.

Preferred Path: Preferred channel paths can be specified for devices in LPAR mode as well as basic mode. Use IOCP to define a preferred path for a device by coding the PATH parameter in the IODEVICE macro instruction.

For more information, see "Input/Output Configuration Program User's Guide" and "ESCON Channel-to-Channel Reference," GC38-0401.

Integrated Coupling Migration Facility (ICMF)

The Integrated Coupling Migration Facility (ICMF) runs in a PR/SM LPAR environment, with PR/SM providing the necessary emulation of physical coupling links to allow interconnected communications between MVS/ESA systems in logical partitions and a logical partition which the LPAR coupling facility is running.

ICMF provides a cost effective alternative for testing and migration of workloads to a coupled systems environment. ICMF provides an environment for migration activities which includes the coupling Facility functions and simulation of coupling links. Using this facility the installation, development and testing of software needed for coupling systems can be completed prior to the installation of or migration to 9672 E or P models and 9674 Coupling Facilities. One or two integrated coupling facility logical partitions can be defined to connect to other integrated logical partitions (or LPARs) running MVS/ESA on the same Central Electronics Complex (CEC) to assist in the test and development of data sharing applications designed for future coupling growth.

Remember, the ICMF coupling capability runs without coupling links which are not available on the 9672 R models. The 9672 R models running ICMF gives you a entry test and migration vehicle into the coupling environment. Then ready to implement coupling, the 9672 R model is upgradable to a 9672 E or P model with coupling links.

ESCON Architecture and Technology

ESCON combines technology, architecture, and a set of interrelated hardware and software products and services that provide:

  • ESCON Architecture
  • ESCON channels, including the ESCON extended distance feature (ESCON XDF*)
  • Fiber optic cabling, transmission, and reception
  • Dynamic connectivity through switched point-to-point topology and data flow
  • Interconnectivity with other networks

For detailed information about the basic concepts of ESCON technology and architecture, see "Introducing Enterprise Systems Connection," and "ESA/390 Principles of Operation."

ESCON Architecture

ESCON Architecture, a channel architecture, is designed to support the fiber optic environment and dynamic connectivity.

ESCON Architecture uses link-level and device-level protocols for the transfer of information. Link-level protocols establish and maintain the physical and logical path for the transmission and reception of information. Device-level protocols establish and maintain the transfer of information between a channel and control units that use device-level protocols.

For detailed information about the ESCON interface protocol, see "IBM Enterprise Systems Architecture/390: ESCON I/O Interface."

ESCON Channels

ESCON Channels transfer information on a link in a serially transmitted synchronous bit stream (serial transmission) through fiber optic channel cables and:

  • Operate using link-level protocols and device-level protocols, or

  • Attach to an IBM 9034 ESCON Converter to attach to control units with parallel interfaces, using bus and tag cable.

For detailed information about the I/O commands used to operate the new ESCON interface protocols in the fiber optic environment, see "IBM Enterprise Systems Architecture/390: Common I/O Device Commands."

Fiber Optic Cabling, Transmission, and Reception

ESCON LED multimode fiber optic technology providing a direct channel attachment range of up to 3 kilometers (1.9 miles); and control units can be attached to a range of up to 9 kilometers (5.6 miles) from a channel through two optional ESCON Directors.

ESCON XDF uses single-mode fiber optic technology providing a direct channel attachment range of up to 60 kilometers (37.3 miles); and control unit attachment range of up 43 kilometers (26.7 miles) from a channel through two optional ESCON Directors.

Dynamic Connectivity (Switched Point-to-Point Topology)

Using switched point-to-point topology and ESCON Directors, many channel and control unit connections can be handled simultaneously. The path between each point-to-point interconnection is called a link. With dynamic connectivity:

  • Many control units can share a single link to a channel through an ESCON Director.
  • Many channels can share a single link to a control unit through an ESCON Director.
  • I/O configuration management is simplified through the use of dynamic I/O configuration.
  • Alternate paths can be used if a failure occurs.

Interconnectivity with Other Networks

Using the IBM 3172 Interconnect Controller and ESCON interface can send large amounts of data at wideband speeds to remote processor complexes, or a parallel (bus and tag) interface to an IBM 9034 ESCON Converter to use existing hardware and I/O interfaces that access commonly used local area networks.

ESCON Multiple Image Facility (EMIF)

The ESCON Multiple Image Facility (EMIF) allows multiple logical partitions to directly share channels (CNC, CTC, and CFS channel paths) and to optionally share any of the control units and associated I/O devices configured to these shared channels. Enhancements to the channel subsystem (CSS) allow the CSS to be operated as multiple logical CSSs when the processor complex is operating in LPAR mode so that one logical CSS is automatically configured to each logical partition. EMIF also provides a way to limit the logical partitions that can access a reconfigurable channel (parallel, ESCON or coupling facility sender) or shared channel to enhance security.

EMIF Hardware and Software Corequisites: EMIF is available on System/390 Parallel Enterprise Server. Any operating system that supports the ESCON architecture can use EMIF. Additionally, non-ESCON operating systems can still operate on EMIF-capable processor complexes.

MVS/ESA SP Version 5 Release 1 (MVS/ESA SP 5.1) or MVS/ESA SP Version 4 Release 2 (MVS/ESA SP 4.2) or MVS/ESA SP 4.2.2 with APAR support provide the capability to make dynamic I/O configuration changes to configurations without shared channels.

MVS/ESA SP 4.3 provides full support for dynamic I/O configuration and EMIF, allowing dynamic I/O configuration changes for I/O configurations that have both shared and unshared channels.

Additionally, there is a new stand-alone input/output configuration program (IOCP) for EMIF-capable processor complexes, IZP IOCP. Operating system program temporary fixes (PTFs) will introduce the corresponding batch versions of IZP IOCP for MVS, VM, and VSE/ESA*.

Data Compression

System/390 Parallel Enterprise Server includes hardware-assisted data compression for DB2 and IMS running under MVS/ESA. (VTAM* and DFSMS/MVS* have issued statements of direction to take advantage of hardware- assisted data compression at a future date.)

New hardware facilities allow the compression and expansion of data which can provide significant reductions in the total cost of computing by significantly reducing:

  • DASD and tape storage requirements
  • The number of communication lines or required line speeds for network data transmission
  • Central processor (CP) cycles needed to perform data compression and expansion (when compared to software-only data compression)

Data compression, along with the increased data rate of ESCON channels and sequential data striping, may provide further enhancements to the effective bandwidth of System/390 Parallel Enterprise Server systems. When combined, these attributes may improve channel utilization and enhance system level performance in situations where I/O bandwidth has been a limiting factor.

Software Corequisites

Hardware-assisted compression requires the following minimum levels of software support:

  • For DB2:
    • DB2 Version 3
    • MVS/ESA SP Version 4 Release 2.2 (4.2.2)
  • For IMS:
    • IMS Version 4 Version 1 (4.1)
    • MVS/ESA SP Version 4 Release 3 (4.3)

Dynamic I/O Configuration

Dynamic I/O configuration allows you to modify the I/O configuration without performing:

  • Power-on reset (POR) of the processor complex
  • Initial program load (IPL) of the system control program (SCP)

Dynamic I/O configuration allows you to add, delete, or modify the I/O definitions of channel paths, control units, and I/O devices in the processor complex. It also allows you to save the changes you made to the I/O configuration definitions and apply them to the active I/O configuration data set (IOCDS).

Initiate these changes by using MVS/ESA SP Version 4 Release 2 and the Hardware Configuration Definition (HCD). It is operational in basic and LPAR modes.

Note: Dynamic I/O configuration requires MVS/ESA SP Version 4 Release 2

To use dynamic I/O configuration on an EMIF-capable processor complex, you need:

  • MVS/ESA* SP Version 5 Release 1 (MVS/ESA SP 5.1) or MVS/ESA SP Version 4 Release 2 (MVS/ESA SP 4.2) or MVS/ESA SP 4.2.2 with APAR support provide the capability to make dynamic I/O configuration changes to configurations without shared channels.

  • MVS/ESA SP 4.3 provides full support for dynamic I/O configuration and EMIF, allowing dynamic I/O configuration changes for I/O configurations that have both shared and unshared channels.

Sysplex Timer Attachment

The optional Sysplex Timer, supported by MVS/ESA SP Version 4.1 or subsequent releases, synchronizes the processor's time-of-day clock in multiple systems.

Asynchronous Data Mover Facility (ADMF)

System/390 Parallel Enterprise Server includes support for the asynchronous data mover (ADM) facility. ADM allows DB2 users in an MVS/ESA environment to more efficiently move large amounts of data between central and expanded storage. ADM can be used with data stored in a compressed format.

ADM offloads the movement of data between central and expanded storage to the CEC I/O subsystem allowing CPs to accomplish additional work.

PR/SM LPAR Mode Considerations

In PR/SM LPAR mode, logical partitions (LPs) enabled to use ADM share the facility. LP requests to use the facility are serviced on a first come, first served basis. You must deactivate an LP to enable or disable LP use of ADM.

Asynchronous Pageout Facility

The asynchronous pageout facility allows the processor complex to more efficiently move pages of data from central storage to expanded storage. This can be valuable to processing environments where a large volume of block paging takes place (for example, numerically intensive computing, NIC).

With the asynchronous pageout facility, a processor complex can move a page of data from central storage to expanded storage without delaying the processing of subsequent instructions by the central processor (CP). The CP can continue to process instructions as soon as data movement begins.

This facility contrasts with the synchronous movement of data from central storage to expanded storage which caused the CP to delay processing of instructions until data movement completed.

Note: The asynchronous pageout facility requires the following software corequisites:

  • MVS/ESA SP Version 5 Release 1
  • MVS/ESA SP Version 4 Release 3
  • VM/ESA Version 4 Release 2

    VM/ESA 1.2 guest support is for MVS/ESA SP 4.3 preferred guests only. If you run MVS as a V=V guest under VM/ESA 1.2, MVS will use the synchronous expanded storage access facility to avoid performance degradation.

Online information

All System/390 Parallel Enterprise Server customer publications are available and displayable softcopy form. All unlicensed manuals are included. The Displayable manuals are shipped on CD-ROM and available from Mechanicsburg Distribution Center.

These displayable manuals use the BookManager* Read Licensed program in any of the supported environments. Terms and Conditions for use of the machine-readable files are shipped with the files.

For further detail, refer to IBM publication GK2T-6685, "The VM/ESA and ES/9000 Softcopy Libraries on CD-ROM."

Physical Specifications

Package Description

System/390 Parallel Enterprise Server uses the packaging concept of 9309 Packaging Architecture for rack mounted devices. The mechanical packages are designed along the Electronic Industry Association (EIA) guidelines for racks and associated equipment. Refer to EIA standard RS-310-B.

For this architecture, the frames are built as EIA-Frames which offer flexibility for mounting various heights of rack mounted units, called modules. The height of one EIA unit is 44.45 mm (1.75 inches).

Serviceability is from the front and rear of each module. In some cases, the module must be pulled out or removed from the EIA-Frame for servicing.

System Configuration

The System/390 Parallel Enterprise Server base system configuration is a EIA-Frame containing one CEC. System performance is increased by upgrading the 9672-R11 model to a R21 thru R61 model.

The maximum system configuration is two EIA-Frames bolted together with one CEC in the first frame and an expansion cage, for additional I/O, in the second frame.

Power

Each frame has two line cords for AC distribution. Each cord is connected to a separate AC box in the frame. Each AC box powers a cage in the frame. There is an Emergency Power Off (EPO) circuit. This circuit will remove AC power from the frame.

Input Power Requirements:

The system is designed to operate in a voltage range of 180-264 Volts AC at a frequency of 47-63 Hertz. The total harmonic distortion of the AC source must be less than 5%. The minimum configuration (one frame with only a CEC assembly) requires a maximum of 1.4 kVA from a utility source and has one power cable. The maximum configuration (two frames with a CEC assembly and I/O Subsystem) requires a maximum of 2.3 kVA input power and has two power cables, one for the CEC assembly and one for the I/O Subsystem.

Battery Backup Unit:

The Battery Backup Unit will provide battery power (24V DC) to the CEC under periods where the AC utility power is lost. The batteries will last up to 3.5 minutes while the CEC continues to run. The Battery Backup Unit also has a 24-volt DC external connection. EXIDE Electronics has developed an Auxiliary DC Power Module (ADMOD) that can attach to the external 24-Volt DC supply. The ADMOD extends the battery backup capability up to 48 hours. Refer to availability package on market tools for more detail on ADMOD.

Cooling

System/390 Parallel Enterprise Server are cooled by forced airflow. Air enters the frame through louvers in the front and exhausts out the top.

System/390 Parallel Enterprise Server operates from 10 C to 32 C and from sea level to an elevation of 2133 m.

Acoustics

Each System/390 Parallel Enterprise Server frame emits 6.9 Bels.

Operating Environment

Programming Compatibility

This information applies to System/390 Parallel Enterprise Server running in basic mode and to operation in a logical partition.

Any program written for ESA/390 mode can operate on System/390 Parallel Enterprise Server operating in ESA/390 mode, provided that the program:

  • Is not time-dependent.

  • Does not depend on the presence of system facilities (such as storage capacity, I/O equipment, or optional features) when the facilities are not included in the configuration.

  • Does not depend on the absence of system facilities when the facilities are included in the configuration.

  • Does not depend on results or functions that are defined as unpredictable or model dependent in the "IBM Enterprise Systems Architecture/390: Principles of Operation."

  • Does not depend on results or functions that are defined in this publication (or, for logically partitioned operation, as being differences or deviations from the appropriate "Principles of Operation" publication.

  • Does not depend on the contents of instruction parameter fields B and C on interception of the SIE instruction. See IBM System/370 Extended Architecture Interpretive Execution for additional information.

Any problem state program written for System/370 operates in ESA/390 mode and any problem state or control program written for 370-XA or ESA/370 operates in ESA/390 mode, provided that in each case the program:

  • Observes the limitations in the preceding statements.

  • Does not depend on any programming support facilities that are not provided or that have been modified.

  • Takes into account other changes made that affect compatibility between modes. These changes are described in the "IBM Enterprise Systems Architecture/390 Principles of Operation."

Any program, including its programming support, that complies with the programming compatibility statements described above will operate in a logical partition with the following exceptions:

  • VM/XA* Migration Aid, VM/XA Systems Facility, and VM/XA System Product Release 1 are not supported in a logical partition.

  • When operating in a logical partition, the CPU ID presented to that logical partition is not the same as when operating in basic mode. This may impact operation of software products that use the CPU ID field.

For more information, see the "IBM Processor Resource/Systems Manager Planning Guide."

Programming Support

The control program you use depends on the mode in which the processor complex is operating. For example, an ES/9000 operating in ESA/390 mode (basic mode) requires a control program for ESA/390 mode.

The term basic mode refers to the mode the processor complex is operating in when it is not operating in LPAR mode.

Control Programs for Basic and LPAR modes

The following IBM control programs operate in basic and LPAR mode:

  • MVS/ESA SP Version 5 Release 1 and 2
  • MVS/ESA SP Version 4 Release 3.0
  • MVS/ESA SP Version 4 Releases 2.0 and 2.2
  • MVS/ESA SP Version 3 Release 1.3
  • VM/ESA Version 2 Release 1.0
  • VM/ESA Version 1 Releases 1.1, 2.0, 2.1 and 2.2
  • VM/ESA (370) Version 1 Release 1.5
  • VSE/ESA Version 1 Releases 2 and 3
  • Transaction Processing Facility (TPF) Version 3 Release 1
  • Transaction Processing Facility (TPF) Version 4 Release 1

Limitations

Not applicable.

Hardware Requirements

System/390 Parallel Enterprise Server is a self-contained system and require no additional components.

An option Auxiliary DC Power Module is available as an accessory for additional availability and power input options. Refer to the Accessories section for additional information on the Auxiliary DC Power Module.

Software Requirements

Not applicable.
Back to top
 

Publications

The following publications are available.

  • GC22-7101 Installation Manual-Physical Planning
  • GA22-7148 System Overview
  • GA22-7123 Processor Resource/Systems Manager Planning Guide

The following publications are shipped with the product.

  • GC38-0452 Managing Your Processor
  • GC38-0453 Hardware System Console Operations
  • GC38-0454 Operations Guide
  • GC38-0455 IOCP User's Guide
  • GC38-0401 Input/Output Configuration Program User's Guide
  • GA22-7123 Processor Resource/Systems Manager Planning Guide
  • GC38-3100 Pre-Installation Configuration Workbook
  • SC28-8141 Hardware Management Console Application Programming Interfaces
  • SY22-9862 Problem Analysis (PA) guide (Customer service doc)
  • SK2T-1196 Hardware Management Console Tutorial (diskette-kit)

Back to top
 
Features -- Specify/Special/Exchange
No Charge Specify Codes Special Feature Codes -- Chargeable Feature Exchanges


No Charge Specify Codes

One of the following Specify Codes for Frame Power Cables must be selected on Initial Order only:

Must select one 998X minimum:

  • #9986 1.8 Meter U.S., Chicago Watertight
  • #9987 4.8 Meter U.S., Non-Chicago Watertight
  • #9988 4.8 Meter Non-U.S., Watertight

Available on Initial Order Only. Prerequisite: None. Corequisite: None. Maximum: One. Field Installation: No.

(#0012) CEC AirFlow Card

The CEC requires one airflow card per empty socket. Will be added by the configurator as required. This Feature is NOT orderable. Available on Initial Order or MES, but determined by the configurator. Prerequisite: None. Corequisite: None. Maximum: 5 per CEC; 15 per expansion cage #1000. Field Installation: Yes.

(#0010) CEC Board Definition

Will be added to all orders by the Configurator. Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Maximum: 1 per CEC and 1 per expansion cage. Field Installation: Yes.

(#0011) Service Cart

The service cart is required to service machines shipped before 10/20/95. For machines shipped after 10/20/95, the Service Element (SE) replaces the service cart function.

The same service cart is used for 9672-R11 thru R61, E01 thru E08, P01 thru P03 and 9674-C01 models. If you already have a service cart from a previous order, answer 'N' to prevent your customer from getting an additional service cart.

Available on MES orders only. Maximum: One per machine. Prerequisite: None. Corequisite: None. Field Installation: Yes.

(#0319) Customized Solutions

(For IBM US, No Longer Available as of April 19, 1999)

S/390 Customized Solutions is an IBM factory service that loads, configures, customizes and tests system/application software for your 9672 R models for immediate use upon installation.

The Customized Solution Feature (#0319) indicates that you have requested Customized Solution services. The S/390 Customized Solution team will be available to work with the IBM marketing specialists to develop customer proposals. IBM marketing personnel can call S/390 Customized Solutions on (914) 433-3551 or 293-3551 (IBM dial network) or send a note to PKEDVM(JUSTASK) for proposal assistance.

(#5007) Open Systems Adapter Air Flow Card

The Open Systems Adapter Module requires one airflow card per empty Open Systems Adapter socket. Will be added by the configurator as required on Model R11. Available on Initial Order or MES, but determined by the configurator. Prerequisite: None. Corequisite: None. Maximum: 9. Field Installation: Yes.

(#5555) OSA1 Located in lower region of a frame

If OSA1 is installed in the lower region of any frame the configurator will assign Specify Code #5555. This code establishes OSA1 cage (#5000) placement for cabling. Available on Initial Order or MES, but determined by the configurator. Prerequisite: #5000. Corequisite: None. Maximum: One per OSA1 cage. Field Installation: Yes.

(#5556) OSA1 location in 'A' Frame

If OSA1 is installed in frame A the configurator will assign Specify Code #5556. This code establishes OSA1 cage (#5000) placement. Available on Initial Order or MES, but determined by the configurator. Prerequisite: #5000. Corequisite: None. Maximum: One per OSA1 cage. Field Installation: Yes.

(#5557) OSA1 location in any Secondary Frame

If OSA1 is installed in any secondary frame the configurator will assign Specify Code #5557. This code establishes OSA1 cage (#5000) placement. Available on Initial Order or MES, but determined by the configurator. Prerequisite: #5000. Corequisite: None. Maximum: One per OSA1 cage. Field Installation: Yes.

(#5558) OSA1 attached to I/O cage

If OSA1 is attached to an I/O cage (#1000 or #2000) the configurator will assign Specify Code #5558. This code establishes OSA1 cage (#5000) attachment. Available on Initial Order or MES, but determined by the configurator. Prerequisite: #5000. Corequisite: None. Maximum: One per OSA1 cage. Field Installation: Yes.

(#5563) 78D cable attachment

If parallel channel features are ordered without a tailgate the configurator will assign Specify Code #5563. There will be one Specify Code #5563 for each parallel channel feature (#6103). This code provides the 78D cables required without the tailgate. Available on Initial Order or MES, but determined by the configurator. Prerequisite: None. Corequisite: None. Maximum: One per parallel channel feature. Field Installation: Yes.

(#5564) CEC or I/O cage attached to OSA1 location

If OSA1 is attached to either a CEC or I/O cage with is located in the lower region of a frame the configurator will assign Specify Code #5564. This code establishes the CEC or I/O cage location. Available on Initial Order or MES, but determined by the configurator. Prerequisite: #5000. Corequisite: None. Maximum: One per OSA1 cage. Field Installation: Yes.

(#9930) Northern Hemisphere

This feature identifies where the system is being installed. Available on initial order or MES when a new display (FC 6090 or 6091) is being ordered. Prerequisite: 6090 or 6091 order. Corequisite: 6090 or 6091 order. Maximum: One. Field Installation: Yes.

(#9931) Southern Hemisphere

This feature identifies where the system is being installed. Available on initial order or MES when a new display (FC 6090 or 6091) is being ordered. Prerequisite: 6090 or 6091 order. Corequisite: 6090 or 6091 order. Maximum: One. Field Installation: Yes.

Special Feature Codes -- Chargeable

Hardware Management Console (HMC)

The console through commands via LAN communications is the single control point for the System/390 Parallel Enterprise Server. The console provides functions through a new object oriented design which allows customers to directly manipulate the objects that make up the system and be aware of changes to the system status immediately.

  • Console with RSF (#0009)
  • 17" Console Display (#6090)
  • 21" Console Display (#6091)

Prerequisite: None. Corequisite: None. Maximum: Four consoles. Field Installation: Yes.

Note: A Maximum of four consoles can be supported and the quantities of #609X must equal the Quantities of Feature #0009.

Note: Orders for Feature #0009 or Feature #0021 will be satisfied by Feature #0031/#0041, which is an equivalent feature. Feature #0031/#0041 will also be automatically shipped with any upgrade or MES order to a system with Feature #0009 or #0021 installed. The reason for migration to Feature #0031/#0041 is to ensure that customers can exploit the latest HMC code levels.

(#0009, #0021, #0031, #0041) Hardware Management Console (HMC) with RSF

(For IBM US, #0041 No Longer Available as of November 19, 2002)

On new build orders, HMC feature #0031 has been replaced by #0041 on all 2003, 9672, & 9674 machine types. All MES orders effective will include either replacement of existing HMC by #0041 or an upgrade to #0031, depending upon the level of system HMC. HONE AID (CFSYSTEM) will determine the appropriate shipment content. When upgrading a system which has #0009 installed, that HMC will be upgraded to either a #0031 or #0041, depending upon the type of PC that has been included in the original or installed HMC configuration (PS/2 based #0009 will be exchanged for #0041; Model 6885 based #0009 will be upgraded to #0031). All upgrades from 9672 G3, 9674 C04, or earlier models, or 2003 1xx models presently using #0021 HMC should confirm order of #0031, as a no- charge feature. All upgrades from 9672 R1, R2, and R3 as well as 9674 C01, C02, C03 models presently using #0009 HMC should confirm feature exchange for either #0031 or #0041, depending upon the original or installed HMC configuration as a no-charge feature exchange (NOTE: #0009 is not applicable to any 2003 or 3000 models; #0021 is not applicable to 2003 2xx models, or 3000 models). #0041 is also available as an optional feature for customers who desire additional HMC performance and flexibility, especially in multi-system environments. No upgrade path from #0031 to #0041 is available; #0031 and #0041 are fully compatible and may coexist on the system LAN. #0023 should only be ordered if the HMC will be connected to a token-ring LAN.

The technical differences between #0031 and #0041 are as follows:

#0031 includes the HMC Token-Ring support and HMC 3270 Emulation support, as standard function.

#0041 includes the HMC Ethernet support as standard function. HMC Token-Ring support is optional as #0023; HMC 3270 emulation support is optional as #0026. #0041 allows two of three options to be installed as follows:

  • HMC/SE ISDN (Integrated Services Digital Network) Feature (#0022)
  • HMC/Standalone SE Token-Ring Feature (#0023)
  • HMC/Standalone SE 3270 Emulation Feature (#0026)

9672 or 9674 installations require at least one local token-ring attached HMC for LIC updates (either #0031 or #0041) at this time; the HMC code senses installation of the token-ring hardware and assumes that token-ring is the protocol to be used. 2003 installations do not have this dependency.

The optional Hardware Management Console(s) allow the management of one or more (up to 100) local or remote servers from a single console. The HMC(s) communicate with the server(s) using either SNA protocol flowing over a Token-Ring LAN or using a TCP/IP protocol flowing over either a Token-Ring LAN or over an Ethernet LAN. The HMC employs a state-of-the-art direct-manipulation object-oriented graphical user interface supporting exception based real-time system status reporting, consolidated hardware messages, consolidated operating system messages, and consolidated service support (including modems and phone lines), and full operation of the managed systems. This is the suggested option for continuous remote operation of a 9672/74. See the section "Remote Operations" under the Support Element (#0015) description for more information. Minimum - 0; Maximum - (on 9672/74 - 4); (on 2003/3000 - 3).

(#0022) HMC/SE ISDN (Integrated Services Digital Network) Feature

The HMC/Standalone Service Element ISDN feature allows high-speed (64 Kbps) remote operation of the Support Element or HMC over digital ISDN lines. This feature is mutually exclusive with the Ethernet feature (#0024) and is only available in US, Canada, Austria, Belgium, Denmark, Finland, France, Germany, Italy, Japan, Netherlands, New Zealand, Norway, Portugal, Spain, Switzerland, Sweden, United Kingdom, and Ireland. Minimum - 0; Maximum - 1 per SE or HMC.

(#0023) HMC/Standalone SE Token-Ring Feature

(For IBM US, No Longer Available as of November 19, 2002)

This card is an option to be used with HMC feature (#0041) on 9672 or 9674 models; on 2003 models feature #0023 may also be used with #0045, Standalone Support Element (SASE), #0023 should only be ordered if the HMC will be connected to a token-ring LAN.

If #0041 is the first HMC or the only HMC at a 9672 or 9674 system installation, #0023 must be ordered to perform LIC code loads to the Support Element; this requirement does not apply to 2003 or 3000 systems that are configured with feature #0045. Minimum - 0; Maximum - 1 per Standalone SE or HMC. Default in CFSYSTEM is one, recommended for any installation that needs token-ring support, as described above.

(#0024) HMC/Standalone SE Ethernet Feature

(For IBM US, No Longer Available as of November 19, 2002)

The Ethernet feature allows the use of existing Ethernet LANs to provide connectivity between the Standalone Support Element (SASE) or HMC systems. It also allows high-speed (10 Mbps) remote operation of the SE or HMC over existing Ethernet LANs. This feature is mutually exclusive with the ISDN feature (#0022) on features (#0031) and (#0015), and is not available on HMC feature (#0041 for 9672 or 9674 models), nor on HMC feature (#0041) or SASE feature (#0045), for 2003 models. NOTE: Ethernet support on (#0041) and (#0045) is a standard function. Minimum - 0; Maximum - 1 per SE or HMC.

(#0026) HMC/Standalone SE 3270 Emulation Feature

(For IBM US, No Longer Available as of September 30, 2002)

This feature is an option to be used with HMC feature (#0041 on 9672 or 9674 models) and the SASE feature (#0045 on 2003 models) Note: Support for 3270 Emulation has been standard on Features #0009, #0021 and #0031 but is now an option on #0041. Minimum - 0; Maximum - 1 per Standalone SE or HMC.

(#0047) - DVD Driver

(For IBM US, No Longer Available as of August 31, 2001)

The DVD Driver is used on HMC (#0061). This feature is required to support the 2064 server. Feature 0047 is available with installation of feature 0061 (HMC Console) on all 9672 models R1, R2, R3, and G3 MES orders; 9674 C02, C03, C04 MES orders; all 9672 G4, G5, and G6 orders; all 9674 model C05 orders.

  • Minimum - 1 per HMC; Maximum - 1 per HMC

(#6152) Sysplex Timer Attachment

Provides the attachment of a centralized time source to set the Time-Of-Day clocks in a multiprocessor environment and maintain synchronization. The sysplex timer attachment has dual port capability to allow you to attach two sysplex timers providing high availability. Prerequisite: None. Corequisite: None. Maximum: One. Field Installation: Yes.

9672/9674 Pre-Installation Configuration Service

Pre-Installation Configuration service is a no charge optional manufacturing-based service which reduces system installation time for factory ordered S/390 Parallel Transaction Servers, S/390 Parallel Enterprise Servers and 9674 Coupling Facilities. This service, available now, allows customers to receive their processor with the Hardware Management Console (HMC) and Service Element (SE) customized to their specifications prior to shipment.

The Pre-Installation Configuration service works as follows:

  • A Pre-Installation Configuration Workbook, the Worksheet, and a memorandum explaining how to use the service are sent to both the HONE and PROFS node/userIDs specified when configuring your system on HONE.

    The Respective files are called WORKBOOK LIST38PP and "ORDERNO" WKSHEET. "ORDERNO" is the actual purchase order number. For convenience, the same files are also available by entering the following REQUEST command on the VM command line:

     
    REQUEST PREICFG PACKAGE FROM S390CS AT KGNVMC  

    The Pre-Installation Configuration Workbook is also available through Mechanicsburg (GC38-3100). Information on the Pre-Installation Configuration service is in the latest version of the 9674 Coupling Facility SAPR guide (SA94-007) and the two 9672 SAPR guides (SA94-006 and SA94-018).

  • Print out the WORKBOOK LIST38PP file. Then with the customer complete the Workbook. Edit the file "ORDERNO" WKSHEET and fill in the information from the WORKBOOK. Make sure the WKSHEET filename ("ORDERNO") equals your six digit purchase order number.

  • The completed Worksheet file is returned to S390CS at KGNVMC.

    The completed Worksheet file must be returned at least ten working days prior to the scheduled processor ship date from manufacturing. If the worksheet is received less than ten days prior to shipment, a file will be returned that the IBM service representative can use during the installation. The turn around time for this file will be ten working days.

Use your support structure for technical questions. For any questions about the service, please send a note to JUSTASK at PKEDVM9 or call S/390 Customized Solutions at 914-433-3552 or 8-293-3551 (IBM dial network).

Processor Storage Features

  • The minimum storage for the 9672 R11 Model is 128 MB (two 64-MB cards feature #0064).

  • Each CEC requires two equally sized storage cards to be plugged at all times. All storage features are mutually exclusive.

  • These storage features are net priced.

  • You tell the configurator the amount of storage you want and the configurator plugs the right storage features.
        Total    |  Order    |
        Storage  |  Feature  | Order
        Desired  |  number   |  QTY
       ----------|-----------|---------
         128MB   |  #0064    |   2
         256MB   |  #0128    |   2
         512MB   |  #0256    |   2
        1024MB   |  #0512    |   2
        2048MB   |  #1024    |   2
 

(#0064) (QTY 2) Storage, 128 MB

Minimum 128-MB Storage on the CEC. Cannot be ordered with #0128, #0256, #0512, or #1024. Prerequisite: None. Corequisite: None. Maximum: Two Mandatory. Field Installation: No, Initial Order ONLY.

Note: This Feature is Mutually Exclusive with #0128, #0256, #0512, or #1024.

(#0128) (QTY 2) Storage, 256 MB

Provides 256 MB of System Storage. Cannot be ordered with #0064, #0256, #0512, or #1024. Prerequisite: None. Corequisite: None. Maximum: Two Mandatory. Field Installation: Yes.

Note: This Feature is Mutually Exclusive with #0064, #0256, #0512, or #1024.

(#0256) (QTY 2) Storage, 512 MB

Provides 512 MB of System Storage. Cannot be ordered with #0064, #0128, #0512, or #1024. Prerequisite: None. Corequisite: None. Maximum: Two Mandatory. Field Installation: Yes.

Note: This Feature is Mutually Exclusive with #0064, #0128, #0512, or #1024.

(#0512) (QTY 2) Storage, 1024 MB

Provides 1024 MB of System Storage. Cannot be ordered with #0064, #0128, #0256, or #1024. Prerequisite: None. Corequisite: None. Maximum: Two Mandatory. Field Installation: Yes.

Note: This Feature is Mutually Exclusive with #0064, #0128, #0256, or #1024.

(#1024) (QTY 2) Storage, 2048 MB

Provides 2048 MB of System Storage. Cannot be ordered with #0064, #0128, #0256, or #0512. Prerequisite: None. Corequisite: None. Maximum: Two Mandatory. Field Installation: Yes.

Note: This Feature is Mutually Exclusive with #0064, #0128, #0256, or #0512.

(#0017) Channel Driver Card

The ESCON and parallel channel cards require channel driver cards to be plugged. Each channel driver card supports up to 12 channels (any fix). Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Maximum: 2 in CEC cage and two in expansion cage. Field Installation: Yes.

Channel Features

The System/390 Parallel Enterprise Server support up to 48 ESCON and/or parallel channels. When more than 24 channels are required, an expansion cage (#1000) is installed bringing the maximum per CEC to 48 Channels.

Three parallel or ESCON channels are standard. Additional channels can be added in increments of three.

Parallel channel devices can be attached through the 9034-001 converter.

The channels supported are:

  • 3-port parallel (#6103)
  • 3-port ESCON LED (#6113)
  • 3-port ESCON Extended Distance (#6114)

(#6103) Parallel Channel Card

Provides an additional three Parallel channels. OEMI bus and tag cable or new 78D cable required to attach to I/O device. Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Minimum: 0. Maximum: 8 in CEC cage and 8 in expansion cage total 16 Field Installation: Yes.

(#6113) ESCON Channel Card

Provides an additional three ESCON channels. Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Minimum: 0. Maximum: 8 in CEC cage and 8 in expansion cage total 16 Field Installation: Yes.

(#6114) ESCON Extended Distance Feature Channel Card

(For IBM US, No Longer Available as of May 30, 1995)

Provides an additional three ESCON Extended Distance Feature Channels Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Minimum: 0. Maximum: 8 in CEC cage and 8 in expansion cage total 16. Field Installation: Yes.

(#6109) Tailgate

The 9672-R models provides parallel channel attachment either with a tailgate assembly or with 78D cables both utilizing Bus/Tag connections. The tailgate is frame mounted below the CEC or I/O expansion cage in which the parallel channel cards are installed. The 78D cables eliminates the need for the tailgate by allowing you to plug your Bus/Tag cables under the frame. The 78D cables allows more efficient use of the frame space and in most configurations reduces the number of frames required.

You will be given the option to order the tailgate or not when configurating your system. If you do not order at least one tailgate, you will not be able to order the Power Sequence control (PSC) features (#6101 or #6102). The I/O or OSA cage which will use the tailgate space leaves no space for the PSC features.

Up to 24 parallel channels are supported with a tailgate feature or the 78D cables. If NO parallel channels are ordered, the tailgate feature or 78D cables are not shipped. Tailgate removal will be available for MES orders.

Available on initial orders and MES. Maximum number: One in CEC frame and one is expansion cage frame. Prerequisite: None. Corequisite: Parallel channel card feature #6103. Field Installation: Yes. Field removable: Yes.

(#1000) Expansion Cage

This cage allows for the plugging of additional Channel Cards. The cage does not support PU nor Memory Cards.

This feature allows for the plugging of additional Channel Cards.

  • Up to 24 additional ESCON and/or Parallel Channels
Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Maximum: One. Field Installation: Yes.

(#2011) Battery Backup Unit

This feature provides a function similar to that of an uninterruptible power source. When utility power is interrupted, the Battery Backup Unit automatically supplies the power for the CEC cage and the I/O expansion cage (#1000) for approximately 3.5 minutes.

In addition, the Battery Backup Unit provides an external 24 volt DC supply connection. EXIDE Electronics has developed an Auxiliary DC power module (ADMOD) that can attach to the external 24 volt DC connection. For detailed information call 1-800-925-4426 (US and Canada) or 1-919-870-3150 (International number) and ask for ADMOD.

Provides Battery Backup (24V) capabilities for System/390 Parallel Enterprise Server to remain active through brief power outages. Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Maximum: One. Field Installation: Yes.

Note: This feature is mandatory for upgrades to G3, if feature code #1000 has been carried over on the upgrade. Customers may remove feature code #1000 via RPQ.

(#3000) Additional Frame

The Additional Frame would be required if the Expansion Cage is present and the tailgate feature is installed for parallel channels in the frame with the CEC. Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Maximum: One. Field Installation: Yes.

(#6101, #6102) Power Sequence Control

Provides power sequencing for attachment of up to 32 I/O controllers per frame. Feature #6101 and #6102 are mutually exclusive in a frame. Feature #6101 provides a Power Sequence Control (PSC) box which provides 16 I/O controller attachments. Feature #6102 provides two PSC boxes which provides 32 I/O controller attachments. An upgrade from #6101 to #6102 is available and only the delta parts are shipped. Prerequisite: #6109. Corequisite: None. Maximum: One or either feature (#6101 or #6102) per frame.

Open Systems Adapter Channels

(#5000) Open Systems Adapter Cage

Provides for the installation of FDDI, Token Ring or Ethernet channels. Number of Open Systems Adapter channels is as follows: FDDI = 9, Token Ring = 4 and Ethernet = 4. Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Maximum: 1. Field Installation: Yes.

(#5001) Open Systems Adapter Extender Card

Provides the Extender Card that can support a maximum of 3 Open Systems Adapter card features (#5002 or #5003) in the Open Systems Adapter Cage. An Open Systems Adapter feature is an FDDI card, or a Token Ring/Ethernet 2 card package. Thus the Extender to Open Systems Adapter relationship, per Open Systems Adapter cage is:

     Extender              QTY of Open Systems Adapter Features
     Card Qty                    supported/module
     --------                   -------------------
        1                             1-3
        2                             4-6
        3                             7-9
 
Available on Initial Order or MES. Prerequisite: None. Corequisite: None. Maximum: 3 per Feature #5000. Field Installation: Yes.

(#5002) Open Systems Adapter Token Ring Feature

Provides Token Ring channel card(s), Tailgate and Cables.

This is a two card package consisting of a BASE LAN card (controller) and a five port Token Ring/Ethernet card, referred to as the Combo Card. All 5 ports must be configured either totally Token Ring. Available on Initial Order or MES. Prerequisite: None. Corequisite: #5000 on initial install of Open Systems Adapter. Maximum: 4 per Feature #5000 if without #5003 or #5005. Field Installation: Yes.

(#5003) Open Systems Adapter FDDI Feature

Provides FDDI channel card(s) on Models E01, E02, E03, E04, E05, E06, E07, E08, P01, P02, P03, R11, R21, R31, R41, R51 and R61. Available on Initial Order or MES. Prerequisite: None. Corequisite: #5000 on initial install of Open Systems Adapter. Maximum: 9 per Feature #5000 if without #5002 or #5005. Field Installation: Yes.

(#5005) Open Systems Adapter Ethernet Feature

Provides Ethernet channel card(s), Tailgate and Cables.

This is a two card package consisting of a BASE LAN card (controller) and a five port Ethernet card, referred to as the Combo Card. All 5 ports must be configured totally Ethernet. Available on Initial Order or MES. Prerequisite: None. Corequisite: #5000 on initial install of Open Systems Adapter. Maximum: 4 per Feature #5000 if without #5002 or #5003. Field Installation: Yes.

Coupling Links

The Coupling Links connect the S/390 Parallel Enterprise Servers to a Coupling Facility. There are two types of coupling links that provide attachment at different distance and support two different transfer rates.

The S/390 Parallel Enterprise Servers holds a maximum of eight Coupling Links per CEC. The fifth and sixth Coupling Links reduce the ESCON channel maximum by three channels; as does the seventh and eighth Coupling Links (with 8 coupling links, the maximum ESCON channels would be reduced from 48 to 42).

Should more than eight (8) Coupling Links be required per CEC, an Expansion Cage can be added to the frame. The Expansion Cage can contain up to an additional 8 Coupling Links for a maximum per CEC of 16 Coupling Links.

(#0007) Coupling Links

(For IBM US, No Longer Available as of September 11, 1998)

Provides one Coupling Links card which can be plugged onto an adapter card #0014. The Coupling Links (#0007) has the following characteristics:

  • Multimode Fiber

  • 1 Km distance
Available on Initial Order or MES.
For all 9672-R models.
Prerequisite:  EC# D57262
Corequisite:   6152 (Sysplex Dual Port ETR)
Maximum:  8 within each CEC and 8 more with a Expansion Cage
          w/Feature Codes #0010  #1000.
Maximum:  16 with the Expansion Cage
Field Installation:   Yes.
 

(#0008) Coupling Links Extended Distance Feature

(For IBM US, No Longer Available as of August 31, 2001)

Provides one Coupling Links Extended Distance Feature card which can be plugged onto an adapter card #0014. The Coupling Links (#0008) has the following characteristics:

  • Single-Mode Fiber

  • 10 Km distance
Available on Initial Order or MES.
For all 9672-R models.
Prerequisite:  EC# D57262
Corequisite:   6152 (Sysplex Dual Port ETR)
Maximum:  8 within each CEC and 8 more with a Expansion Cage
          w/Feature Codes #0010  #1000.
Maximum:  16 with a Expansion Cage.
Field Installation:   Yes.
 

(#0014) Coupling Links Adapter Card

Provides one adapter card which accepts up to two pluggable Coupling Links. Available on Initial Order or MES.

For all 9672-R models.
Prerequisite:  EC# D57262
Corequisite:   6152 (Sysplex Dual Port ETR)
Maximum:  4 within each CEC/4 more within the Expansion Cage
          w/Feature Codes #0010  #1000.
Maximum:  16 with the Expansion Cage.
Field Installation:   Yes.
 

Fiber Optic Jumper Cables

Channel-to-Channel multimode and single-mode fiber optic jumper cables are not provided with the processor ESCON Channel features. To order jumper cables for channel-to-channel connection when an ESCON Director is not in the connection, two alternatives can be used: AAS MSORDER and IBM Authorized Cable Distributors.

When using AAS MSORDER, the IBM Duplex-to-Duplex multimode fiber optic jumper cable part number is 14F3797, and the length must be specified. Eleven standard lengths are available from inventory, 4 meters (12 feet), 7 meters (20 feet), 13 meters (40 feet), 22 meters (70 feet), 31 meters (100 feet), 46 meters (150 feet), 61 meters (200 feet), 77 meters (250 feet), 92 meters (300 feet), 107 meters (350 feet) and 122 meters (400 feet). Custom lengths between 4 meters (12 feet) and 500 meters (1640 feet) will have longer delivery schedules. IBM Duplex-to-Duplex multimode fiber optic jumper cables are also available from IBM Authorized Cable Distributors in seven standard lengths and custom lengths. For the name of the nearest distributor call 1-800-IBM-2468. The part numbers of the IBM Duplex-to-Duplex multimode jumper cables purchased through the IBM Authorized Distributors are:

  • 4 meters (12 feet) (P/N 74F5412)
  • 7 meters (20 feet) (P/N 74F5413)
  • 13 meters (40 feet) (P/N 74F5414)
  • 22 meters ( 70 feet) (P/N 74F5415)
  • 31 meters (100 feet) (P/N 74F5416)
  • 61 meters (200 feet) (P/N 74F5417)
  • 122 meters (400 feet) (P/N 74F5418)
  • Custom-Specify length, Minimum 4 meters (12 feet), Maximum 500 meters (1640 feet) (P/N 74F5436)

When using AAS MSORDER, the IBM Duplex-to-Duplex single-mode fiber optic jumper cable part number is 42F8253, and the length must be specified. Seven standard lengths are available from inventory, 4 meters (12 feet), 13 meters (40 feet), 22 meters (70 feet), 31 meters (100 fee), 61 meters (200 feet), 92 meters (300 feet) and 122 meters (400 feet). Custom lengths between 4 meters (12 feet) and 500 meters (1640 feet) will have longer delivery schedules. IBM Duplex-to-Duplex single-mode fiber optic jumper cables are also available from IBM Authorized Cable Distributors in seven standard lengths and custom lengths. The part numbers of the IBM Duplex to Duplex single-mode jumper cables purchased through the IBM Authorized Distributors are:

  • 4 meters (12 feet) (P/N 02G4982)
  • 13 meters (40 feet) (P/N 02G4983)
  • 22 meters (70 feet) (P/N 02G4984)
  • 31 meters (100 feet) (P/N 02G4985)
  • 61 meters (200 feet) (P/N 02G4986)
  • 92 meters (300 feet) (P/N 02G4987)
  • 122 meters (400 feet) (P/N 02G4988)
  • Custom-Specify length, Minimum 4 meters (12 feet), Maximum 500 meters (1640 feet) (P/N 02G4989)

For additional fiber optic components and connectivity solutions, contact your local branch office installation planning representative or your local Customized Operational Services cabling specialist.

78D Parallel Jumper Cables

A standard length 2.1 meters, IBM Parallel channel 78D pin jumper cable will be provided with the processor Parallel Channel features. To order additional standard length or custom length jumper cables for 78D pin connection two alternatives can be used, AAS MSORDER and IBM Authorized Cable Distributors.

When using AAS MSORDER, there are three types of cables that are available for use with 78D parallel channels:

  1. 2.1 meters standard length (78D to Bus and Tag) P/N 6473053
  2. Custom lengths up to 122 meters (400 feet) (78D to Bus and Tag) P/N 55G8739.
  3. Custom lengths up to 122 meters (400 feet) (78D to 78D) P/N 55G8735.

Custom cable lengths in one foot increments, chargeable to the customer, are available between 4 meters (12 feet) and 122 meters (400 feet). Custom lengths will have longer delivery schedules.

IBM 78D Parallel channel jumper cables are also available from IBM Authorized Cable Distributors. For the name of the nearest distributor call 1-800-IBM-2468.

For additional connectivity solutions, contact your local branch office installation planning representative, your local Customized Operational Services cabling specialist, or your Installation Manual Physical Planning (IMPP) document.

Feature Exchanges

When upgrading an 9672 Rxx Model to a 9672 P01 or P02 model, feature #6109 is changed to a standard feature and feature #3000 is feature exchanged for feature #3001.
Back to top
 

Accessories

System/390 Parallel Enterprise Server has an optional Auxiliary DC Power Module that is available for any model. The Auxiliary DC Power Module is an additional power source for the processor that contains a battery reserve and a direct current (DC) power source to continually charge the battery. The DC power source is connected to an alternating current (AC) power source. In the event of a power interruption the Auxiliary DC Power Module will provide power to the System/390 Parallel Enterprise Server to allow continuous availability by riding through the power interruption. The System/390 Parallel Enterprise Server can be configured for high availability with the Auxiliary DC Power Module by installing the AC input of the processor and Auxiliary DC Power Module to different line feeds.

Customer Replacement Parts

Not applicable.
Back to top
 

Machine Elements

System/390 Parallel Enterprise Server are self-contained elements and require no additional components.

An option Auxiliary DC Power Module is available as an accessory for additional availability and power input options. Refer to the Accessories section for additional information on the Auxiliary DC Power Module
Back to top
 

Supplies

None.

Diskettes

None.

Trademarks

(R), (TM), * Trademark or registered trademark of International Business Machines Corporation.

** Company, product, or service name may be a trademark or service mark of others.
 © IBM Corporation 2003.

Contact IBM

Considering a purchase?