c5

Revised: November 25, 2003.

Revised: August 10, 2004.

9a30

63,164c164,165
replacement to the Turbo Processor. The Turbo II Processor offers up
to a 30% improvement for high-hit ratio and high operations per second
replacement to the Turbo Processor. The Turbo II Processor offers up to
a 30% improvement for high-hit ratio and high operations per second

82,183c183,184
for high-hit ratios and high operations per second workloads compared
to the Standard Processor.
for high-hit ratios and high operations per second workloads compared to
the Standard Processor.

59,264c260,287

Rich Set of Business Continuance Solutions

The Model 800 supports the rich set of previously introduced ESS copy
services functions and management tools that can be used to build
solutions to help meet business continuance requirements.

FlashCopy - Is designed to provide a point-in-time copy
capability for logical volumes. FlashCopy creates a physical

IBM TotalStorage Resiliency Family

The IBM Total Storage Resiliency Family is comprised of IBM
TotalStorage Resiliency Core Technology, an extensive set of hardware and
software features and products, and IBM TotalStorage Resiliency
Automation, integrated software and services packages. The IBM
TotalStorage Resiliency Family is designed to help you implement storage
infrastructures to help keep your business running 24 hours a day, 7 days
a week.

The following ESS Model 800 functions are key components of the IBM
TotalStorage Resiliency Core Technology:

FlashCopy

PPRC:

PPRC Metro Mirror (Synchronous PPRC)

PPRC Global Mirror (Asynchronous PPRC)

PPRC Metro/Global Copy (Asynchronous Cascading PPRC)

PPRC Global Copy (PPRC Extended Distance)

Extended Remote Copy (XRC)

zSeries Global Mirror (XRC)

zSeries Metro/Global Mirror (three-site solution using Synchronous
PPRC and XRC)

FlashCopy: FlashCopy is designed to provide a point-in-time
copy capability for logical volumes. FlashCopy creates a physical

67,328c290,444
copies immediately. FlashCopy is an optional feature on the ESS.

FlashCopy Version 2 - Enables business continuance
solutions with the delivery of new FlashCopy functions and enhancements
designed to help improve business efficiency, along with FlashCopy
performance improvements designed to help minimize operational
disruption. FlashCopy Version 2 includes support for all previous
FlashCopy functions, plus the following:

Data Set FlashCopy, providing a new level of granularity for IBM
eServer zSeries and S/390 environments.

Multiple Relationship FlashCopy, allowing a source to have multiple
targets.

Incremental FlashCopy, providing the capability to "refresh" a
FlashCopy relationship.

Elimination of the LSS constraint - A source and target relationship
can span logical subsystems (LSS).

Establish time improvement, designed to provide up to a 10 times
reduction.

Peer-to-Peer Remote Copy (PPRC) - A hardware-based
disaster recovery solution designed to provide real-time mirroring of
logical volumes within an ESS or between two ESSs that can be located
up to 103 km from each other. PPRC is a synchronous copy solution
where write operations are completed on both copies (primary and
secondary ESS) before they are considered to be done. PPRC is an
optional feature on the ESS.

PPRC Extended Distance (PPRC-XD) offers a non-synchronous
long-distance copy option whereby write operations to the primary ESS are
considered complete before they are transmitted to the secondary ESS.
The non-synchronous operation can result in a "fuzzy copy" at the
secondary site; however, through operational procedures, a point-in-time
consistent copy at the remote site can be created which is suitable for
data migration, backup, and disaster recovery purposes. PPRC-XD can
operate at very long distances -- distances well beyond the 103 km
supported with PPRC synchronous transmissions -- with the distance
typically limited only by the capabilities of the network and channel
extension technologies. PPRC-XD support is included at no additional
charge when PPRC is purchased for the Model 800.

PPRC Version 2 - Provides new options for long-distance
remote copy solutions with the introduction of Asynchronous Cascading
PPRC. Asynchronous Cascading PPRC provides a long-distance remote copy
solution for zSeries and open systems environments by allowing a PPRC
secondary volume (involved in a PPRC synchronous relationship) to also
simultaneously serve as a PPRC primary volume in a PPRC Extended Distance
(PPRC-XD) relationship to the remote site. This new capability enables
the creation of three-site or two-site Asynchronous Cascading PPRC
configurations.

PPRC Version 2 is also designed to provide Fibre Channel as the
communications link between the PPRC primary and PPRC secondary
machines. Compared to PPRC over ESCON links, PPRC over Fibre Channel
allows a reduction in PPRC link infrastructure by a 4 to 1 ratio, while
delivering equivalent or better performance. PPRC communication to
the secondary control unit, via Fibre Channel, provides for a much
faster interface compared to ESCON, particularly at long distances.

Extended Remote Copy (XRC) - A combined hardware and
software business continuance solution for the zSeries and S/390
environments providing asynchronous mirroring between two ESSs at global
distances. XRC is an optional feature on the ESS.

Concurrent Copy - Offers another method for creating a
point-in-time copy in zSeries and S/390 environments, with the source
data fully available for access and update after initiation of the copy
operation.
copies immediately. FlashCopy is an optional feature for the ESS
(feature numbers 83xx).

FlashCopy Version 2 further supports business continuance solutions
with the following additional functions:

Data Set FlashCopy

Multiple Relationship FlashCopy

Incremental FlashCopy

FlashCopy to a PPRC primary

Additional enhancements:

Elimination of the Logical Subsystem (LSS) constraint

Establish time improvement

Consistency group commands

Inband commands over PPRC link

Data Set FlashCopy allows you to perform a FlashCopy of a data set in
zSeries and S/390 environments. This level of granularity allows for
more efficient use of your ESS capacity and can also help reduce the
background copy completion time since a FlashCopy no longer needs to be
performed at a volume level when a copy of selected data sets within a
volume is required. As with FlashCopy at the volume level, Data Set
FlashCopy is fully supported by z/OS Data Facility Storage Management
Subsystem (DFSMS).

With Multiple Relationship FlashCopy, a source can have FlashCopy
relationships with multiple targets simultaneously. This flexibility
allows you to initiate up to 12 FlashCopy establishes on a given logical
unit number (LUN), volume, or data set, without needing to first wait for
or cause previous relationships to end.

Incremental FlashCopy provides the capability to "refresh" a LUN or
volume involved in a FlashCopy relationship. When a subsequent FlashCopy
establish is initiated, only the data required to bring the target
current to the source's newly established point-in-time is copied. The
direction of the "refresh" can also be reversed, in which case the LUN or
volume previously defined as the target becomes the source for the LUN or
volume previously defined as the source (and is now the target).
Incremental FlashCopy can help reduce the background copy completion time
when only a subset of data on either the source or target has changed,
giving you the option to perform a FlashCopy on a more frequent basis.
Additionally, if no updates were made to the target since the last
"refresh", the direction change could be used to "restore" the source
back to the previous point-in-time state.

FlashCopy to a PPRC primary lets you establish a FlashCopy
relationship where the FlashCopy target is also a PPRC primary volume.
This enables you to create full or incremental point-in-time copies at a
local site and then use PPRC to copy the data to the remote site.

Additional enhancements:

Elimination of the LSS constraint: A FlashCopy source and target
relationship can span logical subsystems within an ESS. This flexibility
can help simplify administration and capacity planning for FlashCopy.

Establish time improvement: Performance improvements in FlashCopy
Version 2 are designed to provide up to a 10 times reduction in the time
required to complete a FlashCopy establish command (as compared to
FlashCopy). With this significant reduction in establish time,
operational interruption can be further minimized and the benefits of
FlashCopy can be extended into new application environments.

Consistency group commands: Commands are available to facilitate the
creation of FlashCopy consistency groups. With the FlashCopy Consistency
Group command, the ESS will hold off I/O activity to a LUN or volume
until the Flash Copy Consistency Group Created command is issued.
Consistency groups can be used to help create a consistent point-in-time
copy across multiple LUNs or volumes, and even across multiple ESSs.

Inband commands over PPRC link: In a PPRC environment, commands to
manage FlashCopy at the remote site can be issued from the local or
intermediate site and transmitted over the PPRC links. This eliminates
the need for a network connection to the remote site solely for the
management of FlashCopy.

FlashCopy Version 2 is an optional feature to the ESS (feature numbers
86xx). In addition to supporting the functions listed above, FlashCopy
Version 2 includes support for all functions offered with FlashCopy
(feature numbers 83xx).

Peer to Peer Remote Copy (PPRC): PPRC is designed to offer
hardware-based remote copy solutions. Synchronous PPRC (PPRC Metro
Mirror) is designed to provide real-time mirroring of logical volumes
between two ESSs that can be located up to 103 km from each other when
using ESCON communication links and up to 300 km when using Fibre Channel
communication links. It is a synchronous copy solution where write
operations are completed on both copies (local and remote site) before
they are considered to be done. PPRC also includes PPRC Extended
Distance (PPRC Global Copy), a non-synchronous long-distance copy option
for data migration and backup. PPRC is an optional feature to the ESS
(feature numbers 82xx).

PPRC Version 2 further supports business continuance solutions with
following additional functions:

PPRC over Fibre Channel links

Asynchronous PPRC (PPRC Global Mirror)

Asynchronous Cascading PPRC (PPRC Metro/Global Copy)

PPRC over Fibre Channel links enables the use of Fibre Channel as the
communications link between the PPRC primary and PPRC secondary machines.
Compared to PPRC over ESCON links, PPRC over Fibre Channel allows a
reduction in PPRC link infrastructure, while delivering equivalent or
better performance. PPRC communication to the secondary control unit,
via Fibre Channel, provides for a much faster interface compared to
ESCON, particularly at long distances. Within a single machine, you can
run PPRC over both Fibre Channel and ESCON links, although the link type
cannot be mixed within the same LSS. The Fibre Channel ports used for
PPRC can be configured as either a dedicated PPRC link or as a shared
port between PPRC and Fibre Channel Protocol (FCP) data traffic.

PPRC Global Mirror is designed to provides a long-distance remote copy
solution across two sites using asynchronous technology. It operates
over high-speed, Fibre Channel communication links and is designed to
provide the following:

Support for virtually unlimited distance between the local and remote
sites, with the distance typically limited only by the capabilities of
the network and channel extension technologies. This can better enable
you to choose your remote site location based on business needs and
enables site separation to add protection from localized disasters.

A consistent and restartable copy of the data at the remote site,
created with minimal impact to applications at the local site. Compared
to Asynchronous Cascading PPRC (PPRC Metro/Global Copy), PPRC Global
Mirror eliminates the requirement to do a manual and periodic suspend at
the local site order to create a consistent and restartable copy at the
remote site.

Data currency where, for many environments, the remote site lags
behind the local site an average of 3 to 5 seconds, minimizing the amount
of data exposure in the event of an unplanned outage. Data currency is
also known as the recovery point objective (RPO). The actual lag in data
currency experienced will depend upon a number of factors, including
specific workload characteristics and bandwidth between the local and
remote sites.

Dynamic selection of the desired RPO based upon business requirements
and optimization of available bandwidth.

Session support whereby data consistency at the remote site is
internally managed across up to eight ESS machines located among the
local and remote sites.

Efficient synchronization of the local and remote sites with support
for PPRC failover and failback modes, helping to reduce the time required
to switch back to the local site after a planned or unplanned outage.

PPRC Metro/Global Copy is designed to provide a long-distance remote
copy solution across three sites using a combination of PPRC Metro Mirror
and PPRC Global Copy. In a three-site configuration, the PPRC Metro
Mirror is maintained between an ESS at the local site and an ESS at an
intermediate site, while a PPRC Global Copy relationship is
simultaneously maintained between the ESS at the intermediate site and an
ESS at the remote site. When used with specific operational procedures,
this can be designed to provide a data protection solution in the event
of an unplanned outage at any one of the three sites. Alternatively,
operational procedures, including the creation of a "safety copy" at the
remote site using FlashCopy, can be used to design a solution that
provides a consistent copy of the data at the remote site in the event of
a regional outage affecting both the local and intermediate site.

PPRC Version 2 is an optional feature to the ESS (feature numbers
85xx). In addition to supporting the functions listed above, PPRC
Version 2 also includes support for all functions offered with PPRC
(feature numbers 82xx).

Extended Remote Copy (XRC): XRC (zSeries Global Mirror) is
a combined hardware and software business continuance solution for the
zSeries and S/390 environments providing asynchronous mirroring between
two ESSs at global distances. XRC is an optional feature on the ESS
(feature numbers 81xx).

17,419c533,535

An ESS can have up to six Standby CoD Disk Eight-Packs.

Standby CoD Disk Eight-Packs can be installed as a field upgrade into

An ESS can have up to six Standby CoD Disk Eight-Packs.

Standby CoD Disk Eight-Packs can be installed as a field upgrade into

21c537

The Standby CoD Disk Eight-Pack convenience charge and annual renewal

32,434c548,550

Management Tools and Utilities Improve Administrator
Productivity

The Model 800 supports the following management tools and utilities.

Management tools and utilities improve administrator
productivity: The Model 800 supports the following management tools
and utilities.

36,444c552,559
Master Console) Provides Single Point of Control

The Model 800 utilizes the Enterprise Storage Server Network (ESSNet),
a dedicated LAN, to support configuration, copy services communications
between machines, call home, and remote support capabilities. At the
center of the ESSNet is the ESS Master Console, which serves as a single
point of control for up to seven ESSs. Multiple ESSNets can also be
interconnected and even connected into an enterprise WAN to enable
control of the ESSs from a central location, regardless of where the
machines may be located.
Master Console) Provides Single Point of Control: The Model 800
utilizes the Enterprise Storage Server Network (ESSNet), a dedicated LAN,
to support configuration, copy services communications between machines,
call home, and remote support capabilities. At the center of the ESSNet
is the ESS Master Console, which serves as a single point of control for
up to seven ESSs. Multiple ESSNets can also be interconnected and even
connected into an enterprise WAN to enable control of the ESSs from a
central location, regardless of where the machines may be located.

46,448c561,562
Specialist)

The ESS Specialist is a Web-based tool for performing logical
configuration and copy services (PPRC and FlashCopy) management
Specialist): The ESS Specialist is a Web-based tool for performing
logical configuration and copy services (PPRC and FlashCopy) management

52,453c566,570
network. The ESS Specialist is provided with the Model 800, at no
additional charge.
network. The ESS Specialist is provided with the ESS, at no additional
charge.

IBM TotalStorage Multiple Device Manager (MDM): MDM
provides centralized volume management, performance management, and
replication management for the ESS. MDM is an optional software product.

55,542c572,615
Expert)

The ESS Expert provides comprehensive asset, capacity, and performance
management information for the ESS. The ESS Expert is an optional
software product.

ESS Application Program Interface (API) Simplifies ESS
Administration

The ESS API presents yet another option for ESS management,
complementing the IBM TotalStorage Enterprise Storage Server Specialist
web-based interface and the ESS CLI to provide the flexibility for
building efficiency and continuity into storage management processes.
The ESS API helps to simplify ESS administration and reduce total cost of
ownership by enabling ESS LUN management activities through the use of
the Storage Management Initiative Specification (SMI-S) as defined
by the Storage Networking Industry Association (SNIA).

The API helps enable the integration of ESS configuration management
support into industry-leading storage resource management (SRM)
applications, allowing customers to leverage and exploit their investment
in existing SRM applications and infrastructures. The API can also help
enable configuration management automation through their integration into
customer-written applications.

SMI-S, which is based on the Distributed Management Task Force (DMTF)
Common Information Model (CIM) and Web Based Enterprise Management (WBEM)
technology, defines a common interface for the discovery and management
of resources in a multi-vendor storage area network (SAN). With the
SMI-S interface, customers and vendors can develop applications to a
single standard interface, eliminating the current requirement for
developing to device unique, proprietary interfaces.

The ESS API supports routine LUN management
activities, such as LUN creation, mapping, and masking. It is
implemented through the IBM TotalStorage Common Information Model Agent
(CIM Agent) for the ESS, a middleware application that provides a
CIM-compliant interface.

The ESS API also supports two Copy Services functions, FlashCopy and
PPRC. It supports these activities through the use of the interface
as defined by the SNIA SMI-S.

The ESS API and CIM Agent are provided with the ESS at no additional
charge. The CIM Agent is available for the AIX, Linux, and Windows 2000
operating system environments.

ESS Command Line Interface (CLI) Simplifies Storage
Administration

The ESS CLI provides an alternate method to perform ESS logical
configuration and storage management functions. With the ESS CLI,
routine configuration and management tasks can now be automated through
their incorporation into scripts and applications,helping to simplify ESS
administration and thereby reducing the total cost of ownership.

The ESS CLI supports the following functions:

Asset Management: Obtain information about ESS volumes,
I/O ports, volume spaces, disk groups, and connected hosts.

LUN Masking: Expose/unexpose volumes to fibre
channel-based initiators and obtain volume access information, including
a list of volumes not exposed to any initiator.

Space Management: Query available free space and create
new volumes.

Volume Identification: Assign a user-specified label to a
volume.

Host Connections: Define, undefine, and modify host
connections and obtain host type information, including host port
world-wide name.

Audit Log: Obtain a log of configuration activity by
userid.

Parallel Access Volumes (PAV): List and create new PAVs.

Copy Services: Query functions to view tasks in the copy
services task repository, obtain PPRC path status, and determine
completion of the FlashCopy background copy.

The ESS CLI is provided with the ESS at no additional charge. The ESS
CLI client is available for the AIX, HP-UX, Linux, Solaris, and Windows
2000 operating system environments.

Command Line Interface (CLI) for PPRC and FlashCopy

The CLI enables open systems hosts to invoke and manage FlashCopy and
PPRC functions through batch processes and scripts. It provides commands
to query the status of ESS volumes and to execute copy services tasks
that were previously created using the ESS Specialist. The CLI is
provided with the ESS, with the Model 800, at no additional charge, and
is supported in the AIX, Dynix/ptx, HP-UX, NetWare, Solaris, Tru64 UNIX,
Windows NT, and Windows 2000 environments.

Subsystem Device Driver (SDD)

SDD provides load balancing and enhanced data availability capability
in configurations with more than one I/O path between the host server and
the ESS. Load balancing can reduce or eliminate I/O bottlenecks that
occur when many I/O operations are directed to common devices via the
same I/O path. SDD also helps eliminate a potential single point of
failure by automatically rerouting I/O operations when a path failure
occurs, thereby supporting enhanced data availability capability. SDD is
provided with the Model 800, at no additional charge, and selected
configurations are supported in the AIX, HP-UX, Linux, NetWare, Windows
NT, Windows 2000, and Solaris environments.
Expert): The ESS Expert provides comprehensive asset, capacity, and
performance management information for the ESS. The ESS Expert is an
optional software product.

ESS Command Line Interface (ESS CLI): The ESS CLI provides
an alternate method to perform ESS logical configuration and storage
management functions. With the ESS CLI, routine configuration and
management tasks can be automated through their incorporation into
scripts and applications, helping to simplify ESS administration and
thereby reducing the total cost of ownership. The ESS CLI is provided
with the ESS at no additional charge. The ESS CLI client is available
for the AIX, HP-UX, Linux, Solaris, and Windows 2000 operating system
environments.

Copy Services Command Line Interface (Copy Services CLI):
The Copy Services CLI enables open systems hosts to invoke and manage
FlashCopy and PPRC functions through batch processes and scripts. It
provides commands to query the status of ESS volumes and to execute copy
services tasks that were previously created using the ESS Specialist.
The Copy Services CLI is provided with the ESS at no additional charge.
The Copy Services CLI client is available for the AIX, Dynix/ptx, HP-UX,
NetWare, Solaris, Tru64 UNIX, Windows NT, and Windows 2000 environments.

ESS Application Programming Interface (ESS API): The ESS
API supports routine LUN management activities, such as LUN creation,
mapping, masking, and the management of FlashCopy and PPRC. It supports
these activities through the use of a standard interface as defined by
the Storage Networking Industry Association (SNIA) Storage Management
Initiative Specification (SMI-S). The ESS API is implemented through the
IBM TotalStorage Common Information Model Agent (CIM Agent) for the ESS,
a middleware application designed to provide a CIM-compliant interface.
The interface allows Tivoli and third-party software management tools to
discover, monitor, and control the ESS. The ESS API and CIM Agent are
provided with the ESS at no additional charge. The CIM Agent is
available for the AIX, Linux, and Windows 2000 operating system
environments.

Subsystem Device Driver (SDD): SDD provides load balancing
and enhanced data availability capability in configurations with more
than one I/O path between the host server and the ESS. Load balancing
can help reduce or eliminate I/O bottlenecks that occur when many I/O
operations are directed to common devices via the same I/O path. SDD
also helps eliminate a potential single point of failure by automatically
rerouting I/O operations when a path failure occurs, thereby supporting
enhanced data availability capability. SDD is provided with the ESS at
no additional charge. Fibre Channel (SCSI-FCP) attachment configurations
are supported in the AIX, HP-UX, Windows NT, Windows 2000, and Solaris
environments.

82c655,666

None.

            From                        To

         Type    Model              Type    Model

         ----    -----              ----    -----

         2105     750               2105     800

Note: Parts removed or replaced become the property of IBM and must be
returned.

Note: When ordering the model conversion, the Standard Processor feature
(#3604) must be selected. Additionally, if the ESS Model 750 has only
two disk eight-pack features (#212x), a minimum of two additional disk
eight-pack features must be ordered.

96,776c780,785

Calculating Physical and Effective Capacity

Table 1 - Disk Eight-Pack Capacity Chart(1)

                                     Effective Capacity(2)

                        ------------------------------------------------

                                 RAID 10                    RAID 5(3)

                        ----------------------    ----------------------

 Disk       Physical       3x2          4x2          6+P          7+P

 Size       Capacity    Array(4)     Array(5)     Array(6)     Array(7)

 --------  ----------   ---------    ---------    ---------    ---------

  18.2 GB    145.6 GB    52.50 GB     70.00 GB    105.20 GB    122.74 GB

  36.4 GB    291.2 GB   105.12 GB    140.16 GB    210.45 GB    245.53 GB

  72.8 GB    582.4 GB   210.39 GB    280.52 GB    420.92 GB    491.08 GB

 145.6 GB  1,164.8 GB   420.78 GB    561.04 GB    841.84 GB    982.16 GB

Notes:

A gigabyte (GB) equals one billion bytes when referring to disk
capacity.

Effective capacity represents the approximate portion of the Disk
Eight-Pack that is usable for customer data. All available capacity may
not get fully utilized due to overheads on logical devices and/or a loss
of capacity due to a configured set of logical devices. Also note that
while this table assumes that arrays map directly to Disk Eight-Packs,
arrays are actually created using eight (8) drives of the same type and
the drives are not necessarily contained within the same Disk Eight-Pack.

In RAID 5 configurations, the parity information utilizes the
capacity of one disk, but is actually distributed across all the disks
within a given Disk Eight-Pack.

Array consists of three data drives mirrored to three copy drives.
The remaining drives are used as spares.

Array consists of four data drives mirrored to four copy drives.

Array consists of six data drives and one parity drive. The
remaining drive is used as a spare.

Array consists of seven data drives and one parity drive.

Physical Capacity: Physical capacity is calculated by
multiplying each Disk Eight-Pack feature by its respective "physical
capacity" value shown in Table 1 and then summing the values.

Effective Capacity: The ESS supports the intermix of the
following within an Serial Storage Architecture (SSA) loop:

18.2 GB, 36.4 GB, 72.8 GB, and 145.6 GB Disk Eight-Pack features

RAID 5 and RAID 10

The combination and sequence in which Disk Eight-Pack features are
purchased, installed, and logically configured will determine the
effective capacity of the ESS. The following information can be used to
calculate the effective capacity of a given ESS configuration:

Disk Eight-Pack installation sequence:

Disk Eight-Packs are installed on an SSA loop in pairs, with the
first pair of eight-packs installed on the A loop in device adapter (DA)
pair number 1, the second pair of eight-packs installed on the A loop in
DA pair number 2, and so on.

A given set of Disk Eight-Packs are installed in order of the largest
capacity to the lowest capacity. A set comprises the group of eight-pack
features installed on a new machine during the initial order or a group
of eight-pack features ordered on a capacity upgrade.

Creation of spares:

A unique spare pool is established for each drive capacity on an SSA
loop.

A spare pool must contain at least two drives.

If an SSA loop contains both RAID 5 and RAID 10 arrays, the spare
pool may have three drives, depending upon the sequence in which arrays
are configured.

Spares are always created when the first array on an SSA loop is
configured.

If the array is configured as RAID 5, one spare is created (6+P
array).

If the array is configured as RAID 10, two spares are created (3x2
array).

Spares will be created when the second array on the SSA loop is
configured only if there is not already two spares on the SSA loop.

Calculating Physical and Effective Capacity Refer to the
IBM TotalStorage Enterprise Storage Server Introduction and Planning
Guide (GC26-7444) for capacity calculation guidelines.

ESS Advanced Functions

Advanced functions are enabled and authorized based upon the physical
capacity of the ESS:

78,779c787

If the first array was configured as RAID 5, additional spare(s) will
be created.

FlashCopy and FlashCopy Version 2

81,790c789,790

If the second array is configured as RAID 5, one spare is created
(6+P array).

If the second array is configured as RAID 10, two spares are created
(3x2 array).

If the first array was configured as RAID 10, no additional spares
are created.

The effective capacity for each array type is shown in Table 1.

Enablement and authorization must be equal to or greater than the
total physical capacity of the ESS.

92,794c792

ESS Advanced Functions

ESS advanced functions are enabled and authorized based upon the
physical capacity of the ESS:

PPRC and PPRC Version 2

96c794,797

PAV and XRC:

Enablement and authorization must be equal to or greater than the
total physical capacity of the ESS.

PAV:

02c803

PPRC and FlashCopy:

XRC:

05,882c806,807
total physical capacity of the ESS.

Upgrades from PPRC and FlashCopy Version 1 to PPRC and FlashCopy
Version 2 should be processed using the "Feature Exchange" option of the
MSORDER transaction. The feature exchange to Version 2 can be made to
either the same or a higher capacity level.

The initial enablement of an ESS advanced function is a concurrent
activity (assuming the appropriate level of microcode is installed on the
machine for the given function). The removal of an ESS advanced function
to deactivate the function is a disruptive activity and requires a
machine IML

Ordering Instructions:

Advanced functions require the selection of IBM 2105 Model 800 feature
numbers and the purchase of the matching IBM 2240 ESS Function
Authorization feature numbers:

The ESS Model 800 feature number enables a given function on the ESS
at a given capacity level.

The ESS Function Authorization feature number authorizes use of the
given advanced function at the given capacity level on the ESS machine
for which it was purchased.

The ESS Model 800 8xxx feature numbers and the ESS Function
Authorization 8xxx feature numbers are corequisites and must always
correspond to one another.

                                                          ESS Function

                                       Model 800           Authorization

      ESS Advanced Function            Feature Numbers     Feature Numbers

      -------------------------------  ------------------  ---------------

      Parallel Access Volumes (PAV)    2105-800 #80xx      2240-PAV #80xx

      Extended Remote Copy (XRC)       2105-800 #81xx      2240-XRC #81xx

      Peer-to-Peer Remote Copy (PPRC)  2105-800 #82xx      2240-PRC #82xx

      FlashCopy                        2105-800 #83xx      2240-FLC #83xx

      PPRC Version 2                   2105-800 #85xx      2240-PRC #85xx

      FlashCopy Version 2              2105-800 #86xx      2240-FLC #86xx

The following ordering process must be used for the advanced
functions. This process must be used for all advanced function orders
(initial orders or upgrades).

The 2240 Function Authorizations must be included in the same order
as the Model 800.

The 2240 Function Authorizations (an I/O component) must be linked to
the Model 800 (a CPU/SIU) during order entry.

The Model 800 and the 2240 Function Authorizations must all have a
System Type of 2105.

The Model 800 and the 2240 Function Authorizations must all have the
same System Number. The 2240 Function Authorizations must have the
unique System Number of the Model 800 for which they are being ordered.

All machine types on the order have the same Scheduling Link Number.

All machine types on the order must have the same CRAD.

                      Machine            CPU     Product    System

        System          Type     Model   or I/O   Identity    Type

        ------------   -------   -----   ------   --------   ------

        ESS 2105-800     2105     800     CPU        0        2105

                         2240     FLC     I/O        2        2105

                         2240     PAV     I/O        2        2105

                         2240     PRC     I/O        2        2105

                         2240     XRC     I/O        2        2105

Failure to follow this process will result in an ordering error;
incorrectly placed orders will not be processed by the plant. Incorrect
orders include:

Failure to link the ESS Function Authorization order(s) to the Model
800 order.

Purchase of an ESS Function Authorization feature number without an
order for the corequisite #8xxx advanced function feature on the Model
800.

Specification of a #8xxx advanced function feature on the Model 800
without an order for the corequisite ESS Function Authorization feature
number.
physical capacity within the ESS that will be logically configured as
Count Key Data (CKD) volumes for use with zSeries and S/390 servers.

84,897d808

Upgrades to higher enablement and authorization levels should be
processed using the "Feature Exchange" option of the MSORDER transaction.
The upgrade will be priced as the delta between the current purchase
price of the ESS Function Authorization feature numbers added and
removed. The feature exchange must be processed against both the ESS
Model 800 8xxx feature number(s) and ESS Function Authorization 8xxx
feature number(s).

A feature exchange to a lower capacity level (a numerically lower
feature number) is not supported, with the following exception:

Within a given advanced function type, #8x99 (0 TB (disable)) feature
can be exchanged for any #8xxx feature. The feature exchange must be
processed against both the ESS Model 800 8xxx feature number and ESS
Function Authorization 8xxx feature number.

98a810,817

Refer to the IBM TotalStorage Enterprise Storage Server Introduction
and Planning Guide (GC26-7444) for physical capacity calculation
guidelines.

Standby CoD Disk Eight-Packs can be excluded from the physical
capacity calculation when the Standby CoD Indicator (feature number 9510)
is present on the machine.

Refer to "Ordering ESS Advanced Functions" at the end of the Special
Features section for ordering instructions.

07,913c826,831

Disk Eight-Pack features of the same capacity but different rpm can
be intermixed not only within an ESS, but also within an SSA loop.
When 15,000 rpm Disk Eight-Packs will be installed onto an SSA loop
with logically configured Disk Eight-Packs of the same capacity but
lower rpm, IBM recommends the purchase of the appropriate 15,000 rpm
Spare Upgrade as a corequisite to the purchase of the 15,000 rpm Disk
Eight-Packs.

Disk Eight-Pack features of the same capacity but different rpm can be
intermixed not only within an ESS, but also within an SSA loop. When
15,000 rpm Disk Eight-Packs will be installed onto an SSA loop with
logically configured Disk Eight-Packs of the same capacity but lower rpm,
IBM recommends the purchase of the appropriate 15,000 rpm Spare Upgrade
as a corequisite to the purchase of the 15,000 rpm Disk Eight-Packs.

16,921c834,838
assigned to the spare pool on that SSA loop. Upgrading the spares
to 15,000 rpm is necessary to help maintain the performance benefits
offered by the 15,000 rpm drives. Failure to upgrade the spares
when an intermix situation is first created can leave the machine
vulnerable to performance degradation in the event of a 15,000 rpm
drive failure.
assigned to the spare pool on that SSA loop. Upgrading the spares to
15,000 rpm is necessary to help maintain the performance benefits offered
by the 15,000 rpm drives. Failure to upgrade the spares when an intermix
situation is first created can leave the machine vulnerable to
performance degradation in the event of a 15,000 rpm drive failure.

23,940c840,857
intermix within an SSA loop. Even for those models with an
Expansion Enclosure, intermix within an SSA loop may not always
occur. Your disk marketing specialist can help you determine
whether your configuration is subject to rpm intermix within an
SSA loop and can help you plan accordingly.

Support for rpm intermix among same-capacity disks is available
only as field install. New ESS machine orders continue to be
subject to the following limitation:

For a given capacity, the 15,000 rpm Disk Eight-Pack features
(#214x and #215x) cannot be intermixed with lower rpm Disk Eight-Pack
features (#212x and #213x) of the same capacity.

#2142 and #2152 (18.2 GB, 15,000 rpm) cannot be intermixed with
#2122 or #2132.

#2143 and #2153 (36.4 GB, 15,000 rpm) cannot be intermixed with
#2123 or #2133.

#2144 and #2154 (72.8 GB, 15,000 rpm) cannot be intermixed with
#2124 or #2134.
intermix within an SSA loop. Even for those models with an Expansion
Enclosure, intermix within an SSA loop may not always occur. Your disk
marketing specialist can help you determine whether your configuration is
subject to rpm intermix within an SSA loop and can help you plan
accordingly.

Support for rpm intermix among same-capacity disks is available only
as field install. New ESS machine orders continue to be subject to the
following limitation:

For a given capacity, the 15,000 rpm Disk Eight-Pack features (#214x
and #215x) cannot be intermixed with lower rpm Disk Eight-Pack features
(#212x and #213x) of the same capacity.

#2142 and #2152 (18.2 GB, 15,000 rpm) cannot be intermixed with #2122
or #2132.

#2143 and #2153 (36.4 GB, 15,000 rpm) cannot be intermixed with #2123
or #2133.

#2144 and #2154 (72.8 GB, 15,000 rpm) cannot be intermixed with #2124
or #2134.

43,944c860,861
the IBM TotalStorage Enterprise Storage Server Introduction and
Planning Guide (GC26-7444).
the IBM TotalStorage Enterprise Storage Server Introduction and Planning
Guide (GC26-7444).

47,949d863

See Software Requirements.

Software Requirements

54,1021c868

Model 800: The Model 800 requires ESS LIC level 2.0.0, or
later. Selected features and functions have LIC level prerequisites,
including:

ESS LIC level 2.1.0, or later:

145.6 GB Disk Eight-Pack features (#21xx)

64-bit ESCON Host Adapter feature (#3013)

Advanced function features (#8x13 - #8x15)

ESS CLI.

FlashCopy and PPRC enhancements:

Initiate a FlashCopy background copy task for active relationship
established with "NOCOPY" parameter.

Persistent FlashCopy relationship.

PPRC Failover Mode and PPRC FailBack Mode.

Fibre channel attachment for Compaq AlphaServers with OpenVMS.

Copy Services CLI for Compaq AlphaServers with OpenVMS.

SDD for Novell NetWare.

ESS LIC level 2.1.1, or later:

ESS API

Linux support enhancements for zSeries and S/390 environments:

FICON connectivity.

FlashCopy and PPRC support.

Linux distributions.

Fibre Channel attachment for SGI Origin servers with IRIX

72.8 GB (15,000 rpm) Disk Eight-Pack features (#2144/#2154)

Turbo II Processor option (feature #3607)

ESS LIC level 2.2.0, or later:

FlashCopy Version 2, with support for all previous FlashCopy
functions, plus these new enhancements:

Data Set FlashCopy

Multiple Relationship FlashCopy

Incremental FlashCopy

Elimination of the LSS constraint

FlashCopy establish time reduction

PPRC Version 2, with support for all previous PPRC functions, plus
Asynchronous Cascading PPRC for long-distance remote copy solutions.

IBM Standby Capacity On Demand for ESS (Standby CoD), offering
capacity on demand.

Interoperability enhancements:

Fibre Channel attachment support for Microsoft Windows Server 2003

Sun Cluster 3.0

UnitedLinux running in the Intel environments

ESS LIC level 2.3.0, or later:

PPRC over Fibre Channel, enabling the use of FCP as a communications
link between the ESS PPRC primary and secondary machines

ESS Application Programming Interface (ESS API) support for Copy
Services configuration and use

Arrays Across Loops (AAL) feature, offering improved single array
sequential bandwidth performance (feature #9903)

Asynchronous Cascading PPRC enhancements, exploiting Failover and
Failback modes

rpm intermix support among same-capacity disks, including Spare
Upgrades (feature #219x)

The ESS Model 800 requires ESS LIC level 2.0.0, or later.

028,1069c875,886

Current information on zSeries, S/390, and open systems servers,
operating systems, host adapters, and connectivity products supported by
the ESS is available at:

http://www.ibm.com/storage/hardsoft/products/ess/supserver.htm

PPRC and PPRC Extended Distance (PPRC-XD)

PPRC must be purchased for both the primary and secondary ESS.

PPRC requires the installation of at least one ESCON Host Adapter
(feature number 3012 or 3013) on each ESS to provide the communications
link between the ESS primary and ESS secondary server. For highest
availability offered by the ESS, IBM recommends that more than one ESCON
adapter per ESS be used for the PPRC connectivity.

PPRC is supported with the use of ESCON Directors, DWDMs, and channel
extenders. A current list of supported environments, configurations,
networks, and products is available at:

http://www.ibm.com/storage/hardsoft/products/ess/supserver.htm

Vendors should be consulted regarding hardware and software
prerequisites when using their products in an ESS PPRC configuration.
IBM is not responsible for third-party products.

When using channel extender products with PPRC, the channel extender
vendor will determine the maximum distance supported between the primary
and secondary ESS. The vendors should be contacted for their distance
capability, line quality requirements, and WAN attachment capabilities.

PPRC Version 2

PPRC Version 2 must be purchased for both the primary and secondary
ESS. In three-machine Asynchronous Cascading PPRC configurations, PPRC
Version 2 must also be purchased for the intermediate ESS.

FlashCopy is not required when using PPRC Version 2. However,
FlashCopy can provide additional value and flexibility when used in
Asynchronous Cascading PPRC configurations. Only FlashCopy Version 2 is
supported with PPRC Version 2.

PPRC requires the installation of at least one ESCON Host Adapter
(feature number 3011, 3012, or 3013) on each ESS in the PPRC
configuration to provide the PPRC communications link. For highest
availability offered by the ESS, IBM recommends that more than one ESCON
adapter per ESS be used for the PPRC connectivity.

PPRC is supported with the use of ESCON Directors, DWDMs, and channel
extenders. A current list of supported environments, configurations,
networks, and products is available at:
PPRC

PPRC must be purchased for both the primary and secondary ESS. In
three-machine Asynchronous Cascading PPRC (PPRC Metro/Global Copy)
configurations, PPRC must also be purchased for the intermediate ESS.

PPRC requires the installation of at least one Fibre Channel/FICON or
ESCON host adapter on each ESS in the PPRC configuration to serve as the
PPRC communications link. For higher availability, IBM recommends that
more than one host adapter per ESS be used for the PPRC connectivity.

PPRC is supported with the use of SAN fabric products, ESCON
directors, Dense Wavelength Division Multiplexing (DWDM) products, and
channel extenders. A current list of supported environments,
configurations, networks, and products is available at:

073,1075c890,892

Vendors should be consulted regarding hardware and software
prerequisites when using their products in an ESS PPRC configuration.
IBM is not responsible for third-party products.
Vendors should be consulted regarding hardware and software prerequisites
when using their products in an ESS PPRC configuration. IBM is not
responsible for third-party products.

080,1104c897,930

PPRC Over Fibre Channel

PPRC over Fibre Channel requires PPRC Version 2 (feature #85xx),
and is supported on the ESS Model 800 with Fibre Channel/FICON host
adapters (feature #3024 and #3025).

PPRC Version 2 must be purchased for both the primary and
secondary ESS. In three-machine Asynchronous Cascading PPRC
configurations, PPRC Version 2 must also be purchased for the
intermediate ESS.

PPRC over Fibre Channel requires the installation of at least one
Fibre Channel/FICON host adapter on each ESS in the PPRC configuration.
For highest availability, IBM recommends that more than one Fibre
Channel/FICON host adapter per ESS be used for the PPRC connectivity.

PPRC over Fibre Channel is supported with the use of SAN fabric
products, DWDMs, and channel extenders. A current list of supported
environments, configurations, networks, and products is available at:

http://www.ibm.com/storage/hardsoft/products/ess/supserver.htm

DFSMS Support

DFSMS support for the FlashCopy and PPRC Version 2 enhancements will
vary depending upon the enhancement. z/OS and OS/390 PTFs are required
to provide DFSMS support for Data Set FlashCopy, Multiple Relationship
FlashCopy, and elimination of the LSS constraint. The IBM Support Center
should be contacted for the current PTF information.

Extended Remote Copy (XRC)

PPRC over Fibre Channel: PPRC over Fibre Channel
communication links has the following additional prerequisites:

ESS LIC level 2.3.0, or later

PPRC Version 2

Fibre Channel/FICON Host Adapter (feature #3024 or #3025)

Asynchronous PPRC (PPRC Global Mirror): PPRC Global Mirror has
the following additional prerequisites:

ESS LIC level 2.4.0, or later

PPRC Version 2

Fibre Channel communications link

FlashCopy Version 2 on the secondary ESS. If PPRC Global Mirror will
be used during failback from the secondary ESS machine(s), FlashCopy
Version 2 must also be enabled on the primary machine(s).

In the event of a planned or unplanned outage, recovery procedures are
required to achieve a consistent and restartable copy of the data at the
remote site. Scripts and software can be used to help automate these
procedures.

PPRC Global Mirror is not supported in Asynchronous Cascading PPRC
(PPRC Metro/Global Copy) configurations as an alternative to the PPRC-XD
(PPRC Global Copy) relationship to the remote site.

Asynchronous Cascading PPRC (PPRC Metro/Global Copy): PPRC
Metro/Global Copy has the following additional prerequisites:

ESS LIC level 2.2.0, or later

PPRC Version 2

PPRC Global Mirror is not supported in Asynchronous Cascading PPRC
(PPRC Metro/Global Copy) configurations as an alternative to the PPRC-XD
(PPRC Global Copy) relationship to the remote site.

XRC

107,1108c933,934
XRC must be purchased for both ESSs and if the the secondary ESS is a
Model 800, it also requires a minimum of 16 GB of cache. Not applicable.
XRC must be purchased for both ESS machines. If the secondary ESS is a
Model 800, it also requires a minimum of 16 GB of cache.

112,1113c938,939
services server, the ESS API can also be used to configure and use
Copy Services on ESS Models 800, F20, and F10 residing within the copy
services server, the ESS API can also be used to configure and use Copy
Services on ESS Models 800, F20, and F10 residing within the copy

115,1137c941,959
LIC level 2.1.1, or later.

IBM Standby Capacity on Demand for ESS (Standby CoD)

Standby CoD Disk Eight-Packs (#213x and #215x) must be ordered in
pairs of the same type (quantity of two). Up to six Standby CoD Disk
Eight-Pack features are supported on the Models 800 and F20, subject to
the following:

Four Standby CoD Disk Eight-Packs require a minimum of eight Disk
Eight-Pack features (#212x and #214x).

Six Standby CoD Disk Eight-Packs require a minimum of ten Disk
Eight-Pack features (#212x and #214x).

Arrays Across Loops (AAL)

For machines with the AAL feature enabled (feature #9903), Disk
Eight-Packs must always be ordered in a quantity of four features of
the same type.

When AAL is used in configurations with the Expansion Enclosure,
Disk Eight-Pack Mounting Kits (feature #2102 and #9102) must be
ordered in pairs within the Expansion Enclosure.

AAL is not supported on machines with the Standby Capacity On
Demand program. The IBM TotalStorage Enterprise Storage Server
Expert (ESS Expert) is not supported on the ESS Model 800 with
the AAL feature.
LIC level 2.2.0, or later.

Software Requirements

Current information on servers, operating systems, host adapters, and
connectivity products supported by the ESS is available at:

http://www.ibm.com/storage/hardsoft/products/ess/supserver.htm

The ESS Expert requires a PTF to support the ESS Model 800 with AAL.
Refer to the IBM TotalStorage Expert V2.1 fixes entries at:

http://www-1.ibm.com/support/search.wss?rs=563&tc=STFLM3+STCVQ5N+STCVQ5P1

 dc=D400

DFSMS support for the FlashCopy Version 2 and PPRC Version 2
enhancements will vary depending upon the enhancement. z/OS and OS/390
PTFs are required to provide DFSMS support for Data Set FlashCopy,
Multiple Relationship FlashCopy, and elimination of the LSS constraint.
The IBM Support Center

329c1151
Flexible Capacity Option:
Capacity Options and Indicators:

330a1153
- Standby CoD Indicator 9510

331a1155
- Flexible Capacity Indicator 9610

368a1193
PPRC Global Mirror Indicator 9912

542,1543c1367,1368

If the result is not a whole number or an even number, round up
to the next even, whole number.

If the result is not a whole number or an even number, round up to
the next even, whole number.

556,1558c1381,1383
of features #9102 and #2102 exceeds two. For machines with Arrays
Across Loops (#9903) with feature #2110, feature #2102 must always
be ordered in pairs.
of features #9102 and #2102 exceeds two. For machines with Arrays Across
Loops (#9903) with feature #2110, feature #2102 must always be ordered in
pairs.

642,1646c1467,1475

When a machine exits the Standby CoD program (all Standby CoD Disk
Eight-Pack features (#213x or #215x) are converted to Disk Eight-Pack
features (#212x or #214x), the Standby CoD Flexible Capacity Option
feature must be replaced with the Flexible Capacity Option feature
(#9600) using the feature removal and add option.

When a machine exits the Standby CoD program, the Standby CoD Flexible
Capacity Option feature must be replaced with the Flexible Capacity
Option feature (#9600) using the feature removal and add option. A
machine exits the Standby CoD program when all Standby CoD Disk
Eight-Pack features (#213x) are converted to Disk Eight-Pack features
(#212x).

When purchasing Standby CoD, agreements must be signed by the client
prior to the acquisition of their first ESS configured with any of the
Standby CoD features.

652c1481

http://w3-1.ibm.com/sales/systems/ibmsm.nsf

http://w3.ibm.com/sales/systems

656c1485

http://partners.boulder.ibm.com

http://www.ibm.com/partnerworld/sales/systems/ibmsm.nsf

667c1496,1531

Plant Install / Field Install: Plant only.

Plant Install / Field Install: Both.

(#9510) Standby CoD Indicator

This feature is used to identify machines participating in the ESS
Standby CoD program. It is for administrative purposes only.

When this feature is present, advanced function licenses can be
purchased based upon the machine's physical capacity excluding Standby
CoD Disk Eight-Pack features (#213x and #215x).

When the machine exits the Standby CoD program, the Standby CoD
Indicator feature must be replaced with the Flexible Capacity Indicator
feature (#9610) using the feature removal and add option. A machine
exits the Standby CoD program when all Standby CoD Disk Eight-Pack
features (#213x and #215x) are converted to Disk Eight-Pack features
(#212x and #214x).

Current Standby CoD customers that add the Standby CoD Indicator
feature to the machine are required to sign new versions of the
agreements if their current agreements are dated prior to April 2004.
Additional information on requirement agreements is available on the
following sites (search the site on "Standby CoD"):

IBM System Sales site

http://w3.ibm.com/sales/systems

PartnerWorld site:

http://www.ibm.com/partnerworld/sales/systems/ibmsm.nsf

Minimum: None.

Maximum: One.

Prerequisites: Standby CoD Flexible Capacity Option (#9500).
Corequisites: None.

Compatibility Conflicts: Not compatible with Flexible Capacity
Option (#9600) or Flexible Capacity Indicator (#9610).

Limitations: None.

Plant Install / Field Install: Both.

682a1547,1566

(#9610) Flexible Capacity Indicator

This feature designates a machine that previously ordered the Standby
CoD Indicator feature (#9510) and is no longer participating in the
Standby CoD program. This feature is for administrative and tracking
purposes only.

If the machine re-enters the Standby CoD program, the Flexible
Capacity Indicator feature must be replaced with the Standby CoD
Indicator feature (#9510) using the feature removal and add option. A
machine re-enters the Standby CoD program when Standby CoD Disk
Eight-Pack features (#213x and #215x) are ordered.

Minimum: None.

Maximum: One.

Prerequisites: Flexible Capacity Option (#9600).

Corequisites: None.

Compatibility Conflicts: Not compatible with Standby CoD Flexible
Capacity Option (#9500) or Standby CoD Indicator (#9510).

Limitations: None.

Plant Install / Field Install: Both.

732c1616
------- --------------------------------------------------------------
------- -------------------------------------------------------------

872,1873c1756,1757

This feature is used to request an Arrays Across Loops configuration.
With Arrays Across Loops, disk arrays are spread across the loops of an

This feature is used to request an Arrays Across Loops (AAL).
configuration. With AAL, disk arrays are spread across the loops of an

875,1915c1759,1762

To understand the benefits of AAL, refer to the Arrays Across Loops
White Paper.

For machines with the AAL feature enabled, the following rules apply:

A given set of disk eight-packs are installed in sequence of highest
capacity, highest speed to the lowest capacity, lowest speed. As a
result, 72.8 GB, 15,000 rpm drives are installed before 72.8 GB,
10,000 rpm drives or 36.4 GB, 15,000 rpm drives. A set is defined
as a group of disk eight-pack features installed on a new machine
during the initial order or a group of disk eight-pack features ordered
on a capacity upgrade.

Disk eight-packs are installed in pairs on the Serial Storage
Architecture (SSA) loops. The installation is rotated through the SSA
loops in the following sequence:

1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B.

Disk eight-packs are installed in the Disk Eight-Pack Mounting Kit
as follows:

Disk eight-pack numbers 1 - 16 are installed (evenly distributed)
in the first and second Disk Eight-Pack Mounting Kits.

Disk eight-pack numbers 17 - 32 are installed (evenly distributed)
in the third and fourth Disk Eight-Pack Mounting Kits.

Disk eight-pack numbers 33 - 48 are installed (evenly distributed)
in the fifth and sixth Disk Eight-Pack Mounting Kits.

A unique spare pool is established for each drive capacity on an
SSA loop.

A spare pool must contain at least two drives.

If an SSA loop contains both RAID 5 and RAID 10 arrays, the spare
pool might have three drives. The number of drives depends upon the
sequence in which the arrays are configured.

Spares are not shared between SSA loops.

AAL is a plant install only feature. Requests to convert existing
machines to an AAL configuration or to remove an AAL configuration
will be processed through a priced ITS services contract. The
conversion process is disruptive and data will not be preserved.

Requests to convert existing machines to an AAL configuration or to
remove an AAL configuration will be processed through a priced ITS
services contract. The conversion process is disruptive and data will
not be preserved.

921,1924c1768,1771

Compatibility Conflicts: This feature is not compatible with
Standby CoD Flexible Capacity Option (#9500).

Limitations: Disk Eight-Pack features #212x and #214x must always
be ordered in a quantity of four features of the same type.

Compatibility Conflicts: This feature is not compatible with Standby
CoD Flexible Capacity Option (#9500).

Limitations: Disk Eight-Pack features #212x and #214x must always be
ordered in a quantity of four features of the same type.

968,2015c1815,1817
Alliance (Eagle) agreement. It is for administrative purposes only.

The IBM/Openwave Alliance agreement pertains to all IBM sales activity
for products that will be used by a Wireless or Wireline Service Provider
to deploy revenue generating wireless or mobile services (i.e., Wireless
Internet Mobile Data Services, Wireless Services, Provisioning and Device
Management, Internet Mail, Mobil Messaging, etc.). IBM is contractually
obligated to identify the activity listed above and pay a finders fee (%
of revenue) to Openwave.

Below is a list of the customers that are being targeted by the
IBM/Openwave joint sales effort. Please specify this feature on all ESS
orders (new machine and MES) associated with revenue generating wireless
or mobile services deployed by any of the customers listed below. Also,
an Eagle ISA code has been designated for the purposes of identifying the
Eagle opportunities in OMSYS. The ISA code is "ANC". Questions
regarding the customer list below or the eligibility of any other
customer that appears to come under the jurisdiction of this agreement
should be directed to the Eagle Project Office.

Country           Customer Name

 ----------------  -------------------------------------------------------

 Belgium           Belgacom Mobile

 France            Bouygues Telecom

 Germany           Deutsche Telekom

 Germany           MobilCom

 Holland           UPC (including Chello)

 Israel            Bezeq

 Italy             Telecom Italia Mobile

 Italy             Tiscali Group

 Italy             Wind

 Netherlands       KPN (including Eplus)

 Norway            Telecom Norway (Telenor)

 Portugal          Portugal Telecom

 Portugal          Telepac

 South Africa      MTN

 Spain             Amena (Retevisiln Mlvil)

 Spain             Telefonica (Mobiles, Lycos)

 Sweden            Telia (incl Sonera)

 Turkey            Telsim

 Turkey            Turkcell

 UK                BT (mmO2)

 UK                Freeserve

 UK                LineOne

 UK                Orange (France Telecom, NTL)

 UK                Vodafone (Omnitel, Mannesmann D2, SFR/Cegetel, Airtel

                   Movil)

 UK                WorldOnline

Minimum: None.
strategic alliance. It is for administrative purposes only.

Software Requirements

Software Requirements

(#9510) Standby CoD Indicator

(#9610) Flexible Capacity Indicator

(#9912) PPRC Global Mirror Indicator

(#80xx) Parallel Access Volumes (PAV)

(#80xx) PAV

(#81xx) Extended Remote Copy (XRC)

(#81xx) XRC

(#82xx) Peer-to-Peer Remote Copy (PPRC)

(#82xx) PPRC

(#85xx) Peer-to-Peer Remote Copy Version 2 (PPRC V2):

(#85xx) PPRC Version 2

(#86xx) FlashCopy Version 2 (V2):

(#86xx) FlashCopy Version 2

(#8xxx) - ESS Advanced Functions (PAV, XRC, PPRC, and FlashCopy)