December 2002

IBM ^ zSeries 800 and z/OS, z/OS.e, z/VM and VSE/ESAReference Guide

2

zSeries Overview

The IBM ^™ zSeries™ is one of the fi rst enterprise-

class platform optimized to integrate business applications

and to help meet the critical transactions and demands

of the e-business world far into the twenty-fi rst century.

The IBM ^ zSeries servers are designed to provide

these capabilities through a totally new system design

based on z/Architecture™ announced in October 2000 with

the IBM ^ zSeries 900 (z900).

The IBM ^ zSeries 800 (z800) servers use the

functional characteristics of the z900 in a package that is

designed to deliver excellent price/performance for those

requiring zSeries functionality with a lower capacity entry

point than that offered by z900.

The z800 offers ten General Purpose models, from a sub-

uni to a four-way, which can operate independently or as

part of a Parallel Sysplex® cluster. There is a Coupling

Facility model and also a Dedicated Linux® model on which

one to four engines can be enabled for the deployment of

Linux solutions.

The z800 takes advantage of the robust zSeries I/O sub-

system. High speed interconnects for TCP/IP communi-

cation, known as HiperSockets™, let TCP/IP traffi c travel

between partitions at memory speed rather than network

speed. A high-performance Gigabit Ethernet feature is one

of the fi rst in the industry capable of achieving line speed:

1 Gb/sec. The availability of Native FICON™ devices, Fibre

Channels (FCP channels), 2 Gigabit per second links

and cascaded FICON directors can increase I/O perfor-

mance, simplify/consolidate channel confi gurations and

help reduce the cost of ownership.

The z800 benefi ts from the Intelligent Resource Director

(IRD) function, which directs resources to priority work. The

IRD function combines the strengths of key technologies:

z/OS™, Workload Manager, Logical Partitioning and Parallel

Sysplex clustering.

Unique to the z800 is z/OS.e™, a specially priced offering

for z/OS, providing select function at an exceptional price.

z/OS.e is intended to help customers exploit the fast growing

world of next generation e-business by making the deploy-

ment of new applications on the z800 very attractively

priced. z/OS.e uses the same code as z/OS, customized

with new system parameters, and invokes an operating

environment that is comparable to z/OS in service, man-

agement, reporting, and reliability. Also, z/OS.e invokes

key z800 hardware functionality that you would get from

z/OS. As a result, unless otherwise specifi ed, zSeries hard-

ware functionality described herein is applicable to both

z/OS and z/OS.e running on a z800 server.

While z/OS.e is unique to the z800, all existing zSeries

operating systems such as z/OS, z/VM™ and Linux are

supported and will be discussed later.

New Tools for Managing e-business

The IBM ^ product line is backed by a comprehen-

sive suite of offerings and resources that are designed to

provide value at every stage of IT implementation. These

tools can help customers test possible solutions, obtain

fi nancing, plan and implement applications and middle-

ware, manage capacity and availability, improve perfor-

mance and obtain technical support across the entire

infrastructure. The result is an easier way to handle the

complexities and rapid growth of e-business. In addition,

IBM Global Services experts and IBM Business Partners

can help with business and IT consulting, business trans-

formation, total systems management services, as well as

customized e-business solutions.

3

Ease of Use and Self-Management

To help organizations deal effectively with complexity, IBM

provides a blueprint for autonomic computing which will

help enable self-managing, self-optimizing, self-protecting

and self-healing functions for systems. The goal is to use

technology to manage technology, creating an intelligent,

self-managing IT infrastructure that minimizes complexity

and gives customers the ability to manage environments

that are hundreds of times more complex and more

broadly distributed than exist today. This enables

increased utilization of technology without the spiraling

pressure on critical skills, software and service/support

costs.

The IBM autonomic computing initiative represents a major

shift in the way the industry approaches reliability, avail-

ability and serviceability (RAS). It harnesses the strengths

of IBM and its partners to deliver open, standards-based

servers and operating systems that are self-confi guring,

self-protecting, self-healing and self-optimizing. The object

of autonomic computing technology is to help ensure that

critical operations continue without interruption and with

minimal need for operator intervention.

The goal of autonomic computing is to help customers

dramatically reduce the cost and complexity of their

e-business infrastructures, and overcome the challenges

of systems management. The zSeries product line plays a

major role in autonomic computing, since the self-manage-

ment capabilities available for the zSeries will function

as a model for other IBM ^ platforms, such

as IBM ^ xSeries™, IBM ^ iSeries™ and

IBM ^ pSeries™.

zSeries servers and z/OS provide the ability to confi gure,

connect, extend, operate and optimize the computing

resources to help effi ciently meet the “always-on”

demands of e-business.

One of the key functions of z/OS is the Intelligent Resource

Director (IRD), an exclusive IBM technology that makes

the z800/z900 servers capable of automatically reallocat-

ing processing power to a given application on the fl y,

based on the workload demands being experienced by

the system at that exact moment. This advanced tech-

nology, often described as the “living, breathing server,”

allows the z800/z900 with z/OS to provide nearly unlimited

capacity and nondisruptive scalability to z/OS and non-

z/OS partitions such as Linux, according to priorities deter-

mined by the customer.

Although z/VM does not specifi cally support the IRD,

capabilities are provided for managing guest performance

to help achieve customer-defi ned goals. A new service

virtual machine, the Virtual Machine Resource Manager

(VMRM), accepts workload defi nitions, goal specifi cations,

and associations between them. Virtual machine CPU and

I/O performance controls are adjusted based on actual

performance to attempt to achieve the goals associated

with each workload. Additionally, I/O management facilities

have been added that enable z/VM to exploit the hardware

I/O Priority Queuing facility to prioritize guest and host

I/O operations. A virtual equivalent of the hardware facility

is provided, allowing virtual machines running operating

systems such as z/OS that exploit I/O Priority Queuing to

determine the priority of their I/O operations within bounds

defi ned by a new SET IOPRIORITY command. z/VM will

automatically set a priority for I/O operations initiated by

virtual machines that do not exploit this function.

The zSeries is based on the z/Architecture, which is

designed to eliminate bottlenecks associated with the

lack of addressable memory and automatically directs

resources to priority work through Intelligent Resource

Director (IRD). The z/Architecture is a 64-bit superset of

ESA/390.

4

This architecture has been implemented on the zSeries

to allow full 64-bit real and virtual storage support. A maxi-

mum 32 GB of real storage is available on z800 servers.

zSeries can defi ne any LPAR as having 31-bit or 64-bit

addressability.

z/Architecture has:

• 64-bit general registers.

• New 64-bit integer instructions. Most ESA/390 architec-

ture instructions with 32-bit operands have new 64-bit

and 32- to 64-bit analogs.

• 64-bit addressing is supported for both operands and in-

structions for both real addressing and virtual addressing.

• 64-bit address generation. z/Architecture provides 64-bit

virtual addressing in an address space, and 64-bit real

addressing.

• 64-bit control registers. z/Architecture control registers

can specify regions, segments, or can force virtual

addresses to be treated as real addresses.

• The prefi x area is expanded from 4K to 8K bytes.

• New instructions provide quad-word storage consistency.

• The 64-bit I/O architecture allows CCW indirect data

addressing to designate data addresses above 2 GB for

both format-0 and format-1 CCWs.

• IEEE Floating Point architecture adds twelve new instruc-

tions for 64-bit integer conversion.

• The 64-bit SIE architecture allows a z/Architecture server

to support both ESA/390 (31-bit) and z/Architecture

(64-bit) guests. Zone Relocation is expanded to 64-bit

for LPAR and VM/ESA®.

• Use of 64-bit operands and general registers for all

Cryptographic Coprocessors instructions and Peripheral

Component Interconnect Cryptographic Coprocessors

(PCICC) instructions is added.

The implementation of 64-bit z/Architecture can help to

eliminate any bottlenecks associated with lack of address-

able memory by making the addressing capability virtually

unlimited (16 Exabytes from the current capability of 2 GB).

z/Architecture Operating System Support

The z/Architecture is a tri-modal architecture capable

of executing in 24-bit, 31-bit, or 64-bit addressing

modes. Operating systems and middleware products

have been modifi ed to exploit the new capabilities of

the z/Architecture. Immediate benefi t can be realized by

the elimination of the overhead of Central Storage to

Expanded Storage page movement and the relief provided

for those constrained by the 2 GB real storage limit of

ESA/390. Application programs will run unmodifi ed on the

zSeries.

Expanded Storage (ES) is still supported for operating sys-

tems running in ESA/390 mode (31-bit). For z/Architecture

mode (64-bit), ES is supported by z/VM. ES is not sup-

ported by z/OS in z/Architecture mode.

Although z/OS and z/OS.e do not support Expanded Stor-

age when running under the new architecture, all of the

Hiperspace™ and VIO APIs, as well as the Move Page

(MVPG) instruction, continue to operate in a compatible

manner. There is no need to change products that use

Hiperspaces

Some of the exploiters of z/Architecture for z/OS and

OS/390® Release 10 include:

• DB2 Universal Database™ Server for OS/390

• IMS™

• Hierarchical File System (HFS)

• Virtual Storage Access Method ( VSAM)

• Remote Dual Copy (XRC)

• Tape and DASD access methods

Operating System Support on z800 ESA/390 z/Arch. (31-bit) (64-bit)

z/OS.e Version 1 Release 3 and 4 No Yes

z/OS Version 1 Release 1, 2, 3 and 4 No1 Yes

OS/390 Version 2 Release 10 Yes Yes

OS/390 Version 2 Release 9 Yes No

Linux for zSeries No Yes

Linux for S/390® Yes No

z/VM Version 4 Release 1, 2 and 3 Yes Yes

z/VM Version 3 Release 1 Yes Yes

VM/ESA Version 2 Release 4 Yes No

VSE/ESA™ Version 2 Release 5, 6 and 7 Yes No(when available)

TPF Version 4 Release 1 (ESA mode only) Yes No1 ESA/390 mode permitted for migration purposes only for Release 2, 3 and 4

5

Intelligent Resource Director

Exclusive to the IBM z/Architecture is Intelligent Resource

Director (IRD), a function that optimizes processor and

channel resource utilization across Logical Partitions

(LPARs) based on workload priorities. IRD combines

the strengths of the z800/z900 LPARs, Parallel Sysplex

clustering, and z/OS Workload Manager.

Intelligent Resource Director uses the concept of an LPAR

cluster, the subset of z/OS systems in a Parallel Sysplex

cluster that are running as LPARs on the same z800/z900

server. In a Parallel Sysplex environment, Workload Manager

directs work to the appropriate resources based on busi-

ness policy. With IRD, resources are directed to the priority

work. Together, Parallel Sysplex technology and IRD pro-

vide the fl exibility and responsiveness to e-business work-

loads.

IRD has three major functions: LPAR CPU Management,

Dynamic Channel Path Management, and Channel Sub-

system Priority Queuing.

zSeries IRD Scope

LPAR Cluster

z/OS

z/OS

Linux

OS/390

ICF

LPAR CPU Management

LPAR CPU Management allows WLM working in goal mode

to manage the processor weighting and logical processors

across an LPAR cluster. With z/OS Version 1 Release 2,

WLM can even direct CPU resources outside a z/OS LPAR

cluster, to an LPAR running either z/VM or Linux. CPU

resources are designed to be automatically moved toward

LPARs with the greatest need by adjusting the partition’s

weight. WLM also manages the available processors by

adjusting the number of logical CPs in each LPAR. This

optimizes the processor speed and multiprogramming

level for each workload, reduces MP overhead, and gives

z/OS more control over how CP resources are distributed

to meet your business goals.

z/OS V1.2 enhances the LPAR CPU management capa-

bilities and will allow the dynamic assignment of CPU

resources to non-z/OS partitions such as Linux.

Dynamic Channel Path Management (DCM)

In the past, and on other architectures, I/O paths are

defi ned with a fi xed relationship between processors and

devices. With z/OS and the z800/z900, paths may be

dynamically assigned to control units to refl ect the I/O

load. For example, in an environment where an installation

normally requires four ESCON® channels to service several

control units, but occasionally needs as many as six,

system programmers must currently defi ne all six channels

to each control unit that may require them. With Dynamic

Channel Path Management, the system programmer need

only defi ne the four ESCON channels to the control units,

and indicate that DCM may add an additional two. As the

control unit becomes more heavily used, DCM may assign

additional ESCON channels from a pool of managed chan-

nels, identifi ed by the system programmer, to the control

unit. If the work shifts to other control units, DCM will

unassign them from lesser utilized control units and assign

them to what are now the more heavily used ones. This

helps reduce the requirement for greater than 256 ESCON

channels. DCM can also reduce the cost of the fi bre infra-

structure required for connectivity between multiple data

centers.

6

Channel Subsystem Priority Queuing

The notion of I/O Priority Queuing is not new; it has been

in place in OS/390 for many years. With IRD, this capability

is extended into the I/O channel subsystem. Now, when

higher priority workloads are running in an LPAR cluster,

their I/Os will be given higher priority, and will be sent to

the attached I/O devices (normally disk but also tape and

network devices) ahead of I/O for lower priority workloads.

LPAR priorities are managed by WLM in goal mode.

Channel Subsystem Priority Queuing provides two advan-

tages. First, customers who did not share I/O connectivity

via MIF (Multiple Image Facility) out of concern that a lower

priority I/O intensive workload might preempt the I/O of

higher priority workloads, can now share the channels and

reduce costs. Second, high-priority workloads may even

benefi t with improved performance if there were I/O con-

tention with lower priority workloads. Channel Subsystem

Priority Queuing is implemented for Parallel OEMI and

ESCON and FICON Bridge and native FICON channels.

Channel Subsystem Priority Queuing complements the

IBM Enterprise Storage Server™ capability to manage I/O

priority across CECs.

With IRD, the combination of z/OS and the z800/z900

working in synergy extends the industry-leading workload

management tradition of IBM S/390 and OS/390 to ensure

that the most important work on a server meets its goals,

to increase the effi ciency of existing hardware, and to

reduce the amount of intervention in a constantly changing

environment.

HiperSockets

HiperSockets, a feature unique to the zSeries, provides

a “TCP/IP network in the server” that allows high-speed

any-to-any connectivity among virtual servers (TCP/IP

images) within a z800/z900 without any physical cabling.

HiperSockets is designed to minimize network latency

and maximizes bandwidth between combinations of Linux,

z/OS and z/VM virtual servers. These OS images can be

fi rst level (directly under an LPAR), or second level images

(under z/VM).

With up to four HiperSockets per LPAR connection, one

could separate traffi c to different HiperSockets for security

(separation of LAN traffi c, no external wire-tapping, moni-

toring) and performance and management reasons (sepa-

rate sysplex traffi c Linux or non-sysplex LPAR traffi c).

Since HiperSockets does not use an external network, it

can free up system and network resources, eliminating

attachment cost while improving availability and perfor-

mance. HiperSockets can have signifi cant value in server

consolidation by connecting LPARs running multiple Linux

virtual servers under z/VM to z/OS images. Furthermore,

HiperSockets will be utilized by TCP/IP in place of XCF

for sysplex connectivity between images which exist in the

same server. Thus z/OS uses HiperSockets for connectivity

between sysplex images in the same server and uses XCF

for connectivity between images in different servers. Man-

agement and administration cost reductions over existing

confi gurations are possible.

z/OS z/OS

z900 or z800

HiperSockets A

Linux Linux

HiperSockets B

z900 or z800

Linux z/OS

HiperSockets C

z/VM

z/OS

7

HiperSockets acts like any other TCP/IP network interface,

so TCP/IP features like IP Security (IPSec) in Virtual Private

Networks (VPN) and Secure Sockets Layer (SSL) can be

used to provide heightened security for fl ows within the

same CHPID. HiperSockets supports multiple frame sizes,

which are confi gured on a per HiperSockets CHPID basis.

This support gives the user the fl exibility to optimize and

tune each HiperSockets to the predominant traffi c profi le,

for example, to distinguish between “high bandwidth”

workloads such as FTP versus lower bandwidth interactive

workloads.

The HiperSockets function provides many possibilities

for improved integration between workloads in different

LPARs, bounded only by the combinations of operating

systems and their respective applications. HiperSockets

is designed to provide the fastest z800/z900 connection

between e-business and ERP solutions sharing information

while running on the same server.

WebSphere® HTTP and Web Application Servers or

Apache HTTP servers can be running in a Linux LPAR or

z/VM guest machine, and will be able to use HiperSockets

for very fast TCP/IP traffi c transfer to a DB2® database

server LPAR which is running z/OS. System performance is

optimized because this allows you to keep your Web and

transaction application environments in close proximity to

your data and eliminates any exposure to network-related

outages, thus improving availability.

The z/OS HiperSockets Accelerator function can improve

performance and cost effi ciencies when attaching a high

number of TCP/IP images through HiperSockets to a

“front end” z/OS system for shared access to a set of

OSA-Express adapters.

z800 Support for Linux

Linux and zSeries make a great team. The fl exibility and

openness of Linux bring with it access to a very large

portfolio of applications. zSeries incorporates the qualities

of service that deliver an industrial strength environment for

these Linux applications. In addition zSeries enables mas-

sive scalability within a single server. Hundreds of Linux

images can run simultaneously, providing unique server

consolidation capabilities and reducing both cost and

complexity.

Linux for zSeries can address industry standard Fiber and

SCSI devices attached through FICON Express™ channel

features. These channel features can be defi ned, in the

I/O defi nitions, to enable them to communicate with native

FICON Devices, SCSI devices through a switch or act as

a FICON Channel.

Of course, no matter which Linux applications are brought

to the zSeries platform, they all benefi t from high-speed

access to the corporate data that typically resides on

zSeries.

Linux is Linux, independent of the platform on which it

runs. To run Linux on the S/390 and zSeries platform, IBM

has developed and provided a series of patches. IBM

continues to support the Open Source community.

Linux for zSeries supports the 64-bit architecture available

on zSeries processors. This architecture eliminates the

existing main storage limitation of 2 GB. Linux for zSeries

provides full exploitation of the architecture in both real and

virtual modes and is based on the Linux 2.4 kernel. Linux

for S/390 is also able to execute on zSeries and S/390

servers in 31-bit mode:

IBM Software

• Connectors

– DB2 Connect™, Version 7.1

– MQSeries® Client Version 5.2

– CICS® Transaction Gateway Version 4.0

– IMS Connect Version 7

8

• WebSphere Family

– WebSphere Application Server Advanced Edition 4.0

including Java™ Development Kit, Version 1.3.0 and

JIT

– WebSphere Commerce Suite, Version 5.1

– WebSphere Personalization Version 3.5

– WebSphere Host On-Demand Version 5.0.3

• Data Management

– DB2 Universal Database Version 7.2

– DB2 Connect Unlimited Edition Version 2

– DB2 Connect Web Starter Kit Version 7.2

– DB2 Intelligent Miner™ Scoring Version 7.2

– DB2 Net Search Extender Version 7.2

• Tivoli®

– Tivoli Storage Manager™ Client Version 4.2

– Tivoli Enterprise Console 3.7.1

– Tivoli Software Distribution 4.0

– Tivoli Distributed Monitoring 4.1

– Tivoli Workload Scheduler 8.1

Linux Distribution Partners

• SuSE Linux Enterprise Server 7 for S/390 and zSeries

Product Information at suse.de/en/produkte/susesoft/S390/.

• Turbolinux Server 6 for zSeries and S/390

Product Information at turbolinux.com/products/s390.

• Red Hat Linux 7.2 for S/390

Product Information at redhat.com/software/S390.

z/VM Version 4

z/VM enables large scale horizontal growth of Linux

images on zSeries. z/VM gives the capability of running

hundreds of Linux for zSeries or Linux for S/390 images.

This version of z/VM is priced on a per-engine basis (one-

time charge and annual maintenance fee) and will support

IBM Integrated Facility for Linux (IFL) processor features

for Linux based workloads and standard engines for all

other zSeries and S/390 workloads.

Integrated Facility for Linux (IFL)

This optional feature provides a way to add processing

capacity, exclusively for Linux workloads, with no effect on

the model designation. No traditional zSeries workload will

be able to run in this area. Consequently, these engines

will not affect the IBM S/390 and zSeries software charges

for workload running on the other engines in the system.

IFL engines can run in conjunction with Integrated

Coupling Facility engines and General Purpose engines

on the General Purpose z800 models. The Dedicated

Linux Model has 1–4 IFLs exclusively. The z800 model 0E1

has one IFL engine standard.

OSA-Express Gigabit Ethernet for Linux

Driver support is provided for the functions of the

OSA-Express Gigabit Ethernet feature. This driver supports

the IPv4 protocol, delivering the advantages of more rapid

communication across a network. This improvement may

be between virtual Linux instances on a single machine

(either in LPAR or virtual mode) communicating across a

network, or a Linux for zSeries or Linux for S/390 instance

communicating with another physical system across a net-

work.

OSA-Express Enhancements for Linux

Recent enhancements to OSA-Express for the Linux envi-

ronment include IPv6, Virtual LAN (VLAN), SNMP man-

agement, broadcast support and increased control of the

Address Resolution Protocol (ARP) cache. IPv6 is intended

to support the growth of network addresses required for

the explosion of new devices. VLAN support adds a new

dimension of security and cost savings permitting the

sharing of a physical network while logically maintaining

separation among unrelated users. New SNMP support

provides an ability to retrieve management data which

describes OSA-Express operational characteristics.

Broadcast is now supported on Gigabit Ethernet providing

a high bandwidth path for e-mail, print and fi le serving

applications. New query and purge ARP cache commands

can make network problem management easier.

9

HiperSockets for Linux

HiperSockets can be used for communication between

Linux images and z/OS images. Linux can run under z/VM,

natively, or in an LPAR, whether the engine is an IFL or a

standard engine.

Fibre Channel (FCP Channel) Support for Linux

FCP channels can connect to select Fibre Channel

Switches and FCP/SCSI devices under Linux for zSeries.

This expanded attachability provides more choice in stor-

age solutions for Linux implementations.

Cryptographic Support for Linux

Linux on zSeries running on standard z800/z900 engines

or IFLs is capable of exploiting the hardware cryptographic

feature provided by the PCICA card for SSL acceleration.

This enables customers implementing e-business applica-

tions on Linux on zSeries to utilize this enhanced security

of the hardware.

Linux Support

Environment

• zSeries or S/390 single image

• zSeries or S/390 LPAR

• VM/ESA or z/VM guest

Block devices

• VM minidisks

• ECKD 3380 or 3390 DASDs

• VM virtual disk in storage

Network devices

• Virtual CTC

• ESCON CTC

• OSA-Express (Gigabit Ethernet, Ethernet,

Fast Ethernet, Token-Ring)

• HiperSockets

• 3172

• IUCV

• Character devices

• 3215 console

• Integrated console

Additional information is available at ibm.com/linux/ and

ibm.com/zseries/linux/.

Parallel Sysplex Cluster Technology

Parallel Sysplex clustering was designed to bring the

power of parallel processing to business-critical zSeries

and S/390 applications. A Parallel Sysplex cluster consists

of up to 32 z/OS and/or OS/390 images coupled to one

or more Coupling Facilities (CFs or ICFs) using high-speed

specialized links for communication. The Coupling Facilities,

at the heart of the Parallel Sysplex cluster, enable high-

speed, read/write data sharing and resource sharing

among all the z/OS and OS/390 images in a cluster. All

images are also connected to a Sysplex Timer® to ensure

time synchronization.

Parallel Sysplex Resource Sharing enables multiple system

resources to be managed as a single logical resource

shared among all of the images. Some examples of

resource sharing include Automatic Tape Sharing, GRS

star, and Enhanced Catalog Sharing; all of which provide

simplifi ed systems management, increased performance

and/or scalability. For more detail, please see S/390

Value of Resource Sharing White Paper, GF22-5115

on the Parallel Sysplex home page at

ibm.com/servers/eserver/zseries/pso.

Although there is a signifi cant value in a single footprint

and multi-footprint environment with resource sharing,

those customers looking for high availability must move

on to a database data sharing confi guration. With the

Parallel Sysplex environment, combined with the Workload

Manager and CICS TS or IMS TM, incoming work can

be dynamically routed to the z/OS or the OS/390 image

CF

112

2

3

4567

8

9

10

11

10

most capable of handling the work. This dynamic workload

balancing, along with the capability to have read/write

access to data from anywhere in the Parallel Sysplex clus-

ter, helps provide the scalability and availability that busi-

nesses demand today. When confi gured properly, a Parallel

Sysplex cluster has no single point of failure and can

provide customers with near continuous application

availability over planned and unplanned outages. For

detailed information on the IBM Parallel Sysplex tech-

nology, visit our Parallel Sysplex home page at

ibm.com/servers/eserver/zseries/pso.

The IBM 9037 Sysplex Timer provides a common time

reference to all images that assist in managing the cluster

of multiple footprints as a single operational image. The

common time source also enables proper sequencing and

time stamping of updates to shared databases, a feature

critical to recoverability of the shared data.

Coupling Facility Confi guration Alternatives

IBM offers different options for confi guring a functioning

Coupling Facility:

• Standalone Coupling Facility: z800 Model 0CF, z900

Model 100, and 9672 Model R06 provide a physically

isolated, totally independent CF environment. There are

no software charges associated with standalone CF

models. An ICF or CF partition sharing a server with

z/OS, z/OS.e, or OS/390 images not in the sysplex acts

like a logical standalone CF.

• Internal Coupling Facility (ICF): Customers considering

clustering technology can get started with Parallel

Sysplex technology at a lower cost. An ICF feature is

a processor that can only run Parallel Sysplex coupling

code (CFCC) in a partition. Since CF LPARs on ICFs

are restricted to running only Parallel Sysplex coupling

code, there are no software charges associated with

ICFs. ICFs are ideal for Intelligent Resource Director

and resource sharing environments.

• Coupling Facility partition on a z800/z900 or 9672 server

using standard LPAR: A CF can be confi gured to run

in either a dedicated or shared CP partition. Software

charges apply. This may be a good alternative for

test confi gurations that require very little CF processing

resource or for providing hot-standby CF backup using

the Dynamic Coupling Facility Dispatching function.

A Coupling Facility can be confi gured to take advantage of

a combination of different Parallel Sysplex capabilities:

• Dynamic CF Dispatch: Prior to the availability of the

Dynamic CF Dispatch algorithm, shared CF partitions

could only use the “active wait” algorithm. With active

wait, a CF partition uses all of its allotted time-slice,

whether it has any requests to service or not. The

optional Dynamic CF Dispatch algorithm puts a CF parti-

tion to “sleep” when there are no requests to service and

the longer there are no requests, the longer the partition

sleeps. Although less responsive than the active wait

algorithm, Dynamic CF Dispatch will conserve CP or ICF

resources when a CF partition has no work to process

and will make the resources available to other partitions

sharing the resource. Dynamic CF Dispatch can be used

for test CFs and also for creating a hot-standby partition

to back up an active CF.

• Dynamic ICF Expansion. Dynamic ICF expansion pro-

vides value by providing extra CF capacity when there

are unexpected peaks in the workload or in case of loss

of CF capacity in the cluster.

– ICF Expansion into shared CPs. A CF partition running

with dedicated ICFs needing processing capacity

beyond what is available with the dedicated CP ICFs,

can “grow” into the shared pool of application CPs

being used to execute applications on the same

server.

– ICF Expansion into shared ICFs. A CF partition run-

ning with dedicated ICFs can “grow” into the shared

pool of ICFs in case the dedicated ICF capacity is

not suffi cient. The resulting partition, and “L-shaped”

LPAR, will be composed of both shared ICF and dedi-

cated ICF processors, enabling more effi cient utiliza-

tion of ICF resources across the various CF LPARs.

11

System-Managed CF Structure Duplexing

System-Managed Coupling Facility (CF) Structure Duplexing

provides a general-purpose, hardware-assisted, easy-to-

exploit mechanism for duplexing CF structure data. This

provides a robust recovery mechanism for failure such as

loss of a single structure or CF or loss of connectivity to

a single CF, through rapid failover to the other structure

instance of the duplex pair.

Intended Benefi ts of System-Managed CF Structure

Duplexing include:

• Availability

Faster recovery of structures by having the data already

there in the second CF. Furthermore, if a potential

IBM vendor or customer CF exploitation implementation

were being prevented by the effort of providing alter-

native recovery mechanism such as structure rebuild,

log recovery, etc., that constraint might be removed by

the much simpler exploitation requirements for system-

managed duplexing.

• Manageability and Usability

A consistent procedure to set up and manage structures

across multiple exploiters.

• Reliability

A common framework provides less effort on behalf

of the exploiters, resulting in more reliable subsystem

code.

• Cost Benefi ts

Enables the use of non-standalone CFs (e.g. ICFs) for all

resource sharing and data sharing environments.

• Flexibility

The diagram below represents creation of a duplexed

copy of the structure within a System-Managed CF

Duplexing Confi guration.

Note: An example of two systems in a Parallel Sysplex

environment with CF duplexing

To understand which of the options and capabilities

discussed above are suitable for your environment,

please review GF22-5042, Coupling Facility Confi guration

Options: A Positioning Paper at ibm.com/servers/eserver/

zseries/library/ whitepapers/gf225042.html.

Parallel Sysplex Coupling Connectivity

The Coupling Facilities communicate with z/OS and

OS/390 images in the Parallel Sysplex environment over

specialized high-speed links. For availability purposes, it

is recommended that there be at least two links connect-

ing each z/OS or OS/390 image to each CF in a Parallel

Sysplex cluster. As processor performance increases, it is

important to also use faster links so that link performance

does not become constrained. The performance, availabil-

ity and distance requirements of a Parallel Sysplex environ-

ment are the key factors that will identify the appropriate

connectivity option for a given confi guration.

Parallel Sysplex coupling links on the zSeries have been

enhanced with the introduction of Peer Mode. When con-

necting a zSeries server to a zSeries CF, the links can be

confi gured to operate in Peer Mode. This allows for higher

data transfer rates to and from the Coupling Facilities.

In Peer Mode, the fi ber-optic single mode coupling link

(ISC-3) provides 2 Gb/sec capacity, the ICB-3 link with 1

GB/sec peak capacity, and the IC-3 link with 1.25 GB/sec

capacity. Additional Peer Mode benefi ts are obtained by

using MIF to enable the link to be shared between z/OS

(or OS/390) and CF LPARs. The link acts simultaneously

z/OS ICF ICF z/OS

z800 z900

112

23

4567

8910

11

112

23

4567

8910

11

12

as both a CF Sender and CF Receiver link, reducing

the number of links required. Larger data buffers and

improved protocols also improve long distance perfor-

mance. For connectivity to 9672s, z800/z900 ICS-3 links

can be confi gured to run in Compatibility Mode with the

same characteristics as links on the 9672. All of these

above coupling link speeds are theoretical maximums.

Theoretical Maximum Coupling Link Speed

Connectivity z800/z900 z900 z800/z900Options ISC-3 ICB ICB-3

G3-G6 ISC 1 Gb/sec n/a n/a

z800/z900 2 Gb/sec n/a n/aISC-3 Peer Mode

G5-G6 ICB n/a 333 MB/3 n/a

z800/z900 n/a n/a 1 GB/secICB-3 Peer Mode

• SC-3. InterSystem Coupling Facility 3rd Generation

channels provide the connectivity required for data shar-

ing between the Coupling Facility and the systems

directly attached to it. ISC-3 channels are point-to-point

connections that require a unique channel defi nition

at each end of the channel.

ISC-3 channels operating in Peer Mode provide connec-

tion between z800/z900 general purpose models and

z800/z900 coupling facilities. ISC-3 channels operating

in Compatibility Mode provide a long-distance connec-

tion between z800/z900 systems and HiPerLink (ISC)

channels on 9672 Models. A four-port ISC-3 card struc-

ture is provided on the z800/z900 family of processors. It

consists of a mother card with two daughter cards which

have two ports each. Each daughter card is capable of

operation at 1 Gb/sec in Compatibility Mode or 2 Gb/sec

in native mode up to a distance of 10 km. From 10 to 20

km, an RPQ is available which runs at 1 Gb/sec in both

Peer and Compatibility Modes. The mode is selected for

each port via CHPID type in the IOCDS. The ports are

activated in one port increments.

• HiPerLinks. HiPerLinks, based on single-mode CF links,

are available on 9672s and 9674s only. ISC-3 links

replace HiPerLinks on z800/z900 models.

• ICB. The Integrated Cluster Bus is used to provide high-

speed coupling communication between 9672 G5/G6

and/or z900 servers over short distances (~7 meters).

For longer distances, ISC links must be used. Up to

eight ICB links (16 possible via RPQ) are available on

the general purpose z900 models and up to 16 ICB links

are available on the z900 Coupling Facility Model 100.

ICB is not offered on the z800.

• ICB-3. The Integrated Cluster Bus 3rd Generation is

used to provide high-speed coupling communication

between two z800/z900 systems over short distances

(~7 meters). For longer distances, ISC-3 links must be

used. Up to 16 ICB-3 links are available on both the

general purpose z900 models and the z900 Coupling

Facility Model 100. Up to fi ve ICB-3 links are available

for the z800 general purpose models and up to six on

the z800 0CF model. The performance of the ICB-3

link has been improved by higher data rates and new

buffering capabilities.

• IC-3. The Internal Coupling-3 channel emulates the cou-

pling links between images within a single server. No

hardware is required, however a minimum of two CHPID

numbers must be defi ned in the IOCDS. IC-3 links pro-

vide the fastest Parallel Sysplex connectivity. Up to 32

ICs are available on z800/z900 models.

IBM provides extensive services to assist customers with

migrating their environments and applications to benefi t

from Parallel Sysplex clustering. A basic set of IBM ser-

vices is designed to help address planning and early

implementation requirements. These services can reduce

the time and costs of planning a Parallel Sysplex environ-

ment and moving it into production. An advanced optional

package of services is also available and includes data

sharing application enablement, project management and

business consultation through advanced capacity

planning and application stress testing. For more infor-

mation on Parallel Sysplex Professional Services, visit

the IBM Web site at

ibm.com/servers/eserver/zseries/pso/services.html

13

Geographically Dispersed Parallel Sysplex

The Geographically Dispersed Parallel Sysplex™ (GDPS™)

complements a multisite Parallel Sysplex environment by

providing a single, automated solution designed to dynam-

ically manage storage subsystem mirroring, processors,

and network resources to help allow a business to attain

“continuous availability” and near transparent business

continuity/disaster recovery without data loss. GDPS pro-

vides the ability to perform a controlled site switch for both

planned and unplanned site outages, while maintaining full

data integrity across multiple storage subsystems.

GDPS requires Tivoli NetView® for OS/390, System Auto-

mation for OS/390, and remote copy technologies. GDPS

supports both the synchronous Peer-to-Peer Remote

Copy (PPRC) as well as the asynchronous Extended

Remote Copy (XRC) forms of remote copy. GDPS/PPRC is

designed to be a continuous availability solution and near

transparent business continuity/disaster recovery solution

that allows a customer to meet a Recovery Time Objective

(RTO) of less than an hour, a Recovery Point Objective

(RPO) of no data loss, and protects against metropolitan

area disasters (up to 40 km between sites). GDPS/XRC

is a business continuity/disaster recovery solution that is

designed to allow a customer to meet an RTO of one to

two hours, an RPO of less than a minute, and protects

against metropolitan as well as regional disasters, since

the distance between sites is unlimited. XRC can use

either common communication links and channel extender

technology between sites or dark fi ber.

Note: Dark fi ber refers to dedicated strands of fi ber optic

cable with no electronics between the ends (source and

destination).

Continuous Availability Recommended Confi guration

Note: This Coupling Facility could be a z900 Model 100,

9672 R06, 9674 C04 or C05.

Geographically Dispersed Parallel Sysplex Support for

Peer-to-Peer Virtual Tape Server (PtP VTS):

The GDPS solution has been extended to include tape

data in its management of data consistency and integrity

across sites with the announced support of the Peer-

to-Peer VTS confi guration (IBM United States Hardware

Announcement 101-215). The PtP VTS is designed to pro-

vide a hardware-based duplex tape solution and GDPS

automatically manages the duplexed tapes in the event of

a planned site switch or a site failure. At the present time,

the GDPS PtP support is only available for a GDPS/PPRC

(Peer-to-Peer Remote Copy) confi guration.

z8000CF

112

23

4567

8910

11

ESCON / FICON Express

sysplex timers

z/OS ICF z/OSIC

Internal Coupling Facility

Dedicated (External) Coupling Facility*

112

23

4567

8910

11

14

A new I/O VTS selection option is provided especially for

use with GDPS, so that all virtual volumes are processed

from a primary VTS, and a copy is stored on the secondary

VTS. Control capability has been added to allow GDPS to

“freeze” copy operations, so that tape data consistency

can be maintained across GDPS managed sites during a

switch between the primary and secondary VTSs. Synchro-

nization of system data sets such as catalogs, the tape

control database, and tape management databases is also

provided with the PtP VTS after an emergency switchover.

Operational data, data that is used directly by applications

supporting end users, is normally found on disk. For the

past several years, GDPS has provided continuous avail-

ability and near transparent business continuity for disk

resident data. However, there is another category of data

that “supports” the operational data, which is typically

found on tape subsystems. Support data typically covers

migrated data, point in time backups, archive data, etc.

For sustained operation in the failover site, the support

data is indispensable. Furthermore, several enterprises

have mission-critical data that only resides on tape. By

extending GDPS support to data resident on tape, the

GDPS solution provides continuous availability and near

transparent business continuity benefi t for both disk and

tape resident data. Enterprises will no longer be forced

to develop and utilize processes that create duplex tapes

and maintain the tape copies in alternate sites. For exam-

ple, previous techniques created two copies of each

DBMS image copy and archived log as part of the batch

process and required manual transportation of each set of

tapes to different locations.

Automatic Enablement of CBU for Geographically Dispersed

Parallel Sysplex

The intent of the GDPS (CBU) is to enable automatic

management of the reserved PUs provided by the CBU

feature in the event of a processor failure and/or a site

failure. Upon detection of a site failure or planned disaster

test, GDPS is designed to dynamically add PUs to the

confi guration in the takeover site to restore processing

power for mission-critical production workloads.

GDPS is discussed in detail in two white papers

which are available at ibm.com/server/eserver/zseries/

pso/library.html. GDPS is a service offering of IBM Global

Services. For IBM Installation Services for GDPS refer to

the IBM Web site.

Key attributes can include

• Fast, automatic recovery:

– CF: rebuild in surviving CF

– Central Electronic Complex (CEC), z/OS, OS/390:

restart subsystems on surviving image

– TM/DBMS: restart in place

• Surviving components absorb new work

• No service loss for planned or unplanned outages

• Near unlimited, plug-and-play, growth capacity

15

IBM ^ zSeries is the enterprise class e-business

server optimized for integration, transactions and data of

the next generation e-business world. In implementing

the z/Architecture with new technology solutions, the

z800/z900 servers are designed to facilitate the IT busi-

ness transformation and reduce the stress of business-to-

business and business-to-customer growth pressure. The

zSeries represents a new generation of servers that feature

enhanced performance, support for S/390 Parallel Sysplex

clustering, improved hardware management controls and

innovative functions to address e-business processing.

The I/O subsystem includes Dynamic Channel Path Man-

agement (DCM) and Channel CHPID Assignment. These

two functions effectively increase the number of CHPIDs

that can be used for I/O connectivity. DCM allows channel

paths to be dynamically and automatically moved from

less utilized devices to constrained devices under the

supervision of the Workload Manager. Channel CHPID

Assignment permits the assignment of a CHPID to any

physical port. This allows the assignment of up to 256

CHPIDs to usable channel paths. Combined, the use of

these two functions allows the full exploitation of the I/O

bandwidth.

These are some of the signifi cant enhancements in the

zSeries that bring improved performance, availability and

function to the platform. The following sections highlight

the functions and features of the hardware platform.

z800 Design and Technology

The z800 is designed to be a leading server

for e-business. It utilizes the z/Architecture and state-

of-the-art technology to provide balanced processor,

memory and I/O performance. The z800 design is a

derivative of the z900. Almost all z900 functions are sup-

ported on the z800. The z800 scales to about 20% of

a z900 and extends the zSeries to small and medium

size customers and workloads. Its balanced design

allows effi cient scaling while utilizing the most advanced

zSeries functions such as 64-bit enablement, the Intelligent

Resource Director and HiperSockets.

The heart of the z800 is the Basic Processor Unit (BPU)

which contains the memory and processor subsystems.

Key parts in the BPU package are an advanced Multichip

Module (MCM), Memory Controller (MC) modules, memory

DIMMS, Key Store DIMMS, and optional CMOS Cryptographic

modules.

z800 MCM

Note: PU chips can be enabled as CP, ICF, IFL, SAP or

spares by microcode.

Actual size of a z800 MCMused in all Models

Technology ExcellencePowerful Processor Packaging

SD0 SD1SC0

MBAPU1 PU3

PU2 PU0 PU4CLK

71 m

m

71 mm

IBM ^ zSeries 800

16

Base Processor Unit

The z800 has a storage capacity of up to 32 GB. The entry

confi guration of 8 GB can be scaled in 8 GB increments

to 16 GB, 24 GB and 32 GB. Dense 256 Mb Double Data

Rate (DDR) memory chips are used in banks of DIMMS.

Memory is protected by design and built-in Error Checking

and Correcting circuitry. The MC chip is an integrated

memory controller.

The z800 I/O subsystem has been designed and sized to

provide suffi cient connectivity for even the most demand-

ing application by providing 16 slots for channels and

network adapters. The z800 supports only current and

advanced high bandwidth advanced technology. It does

not support parallel channels or the fi rst and second gen-

erations of Open Systems Adapters. OSA-Express and

FICON Express cards utilize the latest technology to help

provide the best performance for channel and network

attachments. Up to 240 ESCON channels are available

utilizing the 16-port ESCON card design.

Eight PCICC and six PCICA cards can also be plugged

into the I/O slots for high-performance cryptographic func-

tion. The one MBA chip supports six 1 GB/sec Self Timed

Interconnect (STI) busses giving z800 a total I/O bandwidth

of 6 GB/sec. Four STIs attach to the I/O cage and two can

be used for Integrated Cluster Bus 3rd Generation (ICB-3)

high-speed Parallel Sysplex attachments. In addition to

ICB-3s, the z800 can utilize InterSystem Coupling Facility

The z800 MCM contains 10 chips [fi ve Processor Units

(PUs), one Memory Bus Adapter (MBA), two Storage Data

(SD), one Storage Control (SC), one Clock (CLK)]. The

z800 MCM can scale up to four Central Processors. The

z800 has 8 MB of on-module L2 cache compared to the

z900’s 16 or 32 MB of L2 cache. The fast L2 cache on

the MCM, next to the Processor Units, enables a powerful

four-way multiprocessor which can dynamically share data

between processors.

The PU used in the z800 is the same as the z900. They

have 64-bit capabilities and an improved compression

engine compared to 9672 Generation 6 servers. The PU

has 512 KB of on-chip (L1) memory. Processor Units can

be confi gured as Central Processors, a dedicated I/O

processor System Assist Processor, Integrated Coupling

Facilities, Integrated Facility for Linux or as spares which

can be enabled for emergencies or permanent upgrades.

The processor unit uses the most advanced IBM CMOS

technology, CMOS 8SE. This technology utilizes copper

interconnects, Silicon-On-Insulator (SOI) and low-k dielec-

tric technological innovations to help provide the density

and speed required for high performance, advanced

64-bit function and mainframe reliability. (All models,

except those which utilize all PUs, can transparently spare

a PU.) The cycle time of the z800 processors is 1.6 ns

compared to the z900’s 1.3 ns. The zSeries processors

are signifi cantly faster than the G5-based Multiprise® 3000

which has a cycle time of 2.4 ns. The 33% faster engine is

used by traditional CPs, ICFs or IFLs.

MCMMC0 MC1CRYPT0 CRYPT1

Bank 2

Bank 1

Bank 3

Bank 4Key Store

STI STI STI STI STI STI

8 GB 16 GB 24 GB 32 GB Main Edge Connector

17

3rd Generation (ISC-3) and IC-3 for Parallel Sysplex

attachments, making it a fully functional machine which

can be used as a server, Coupling Facility or a server with

an Integrated Coupling Facility.

There are minor differences between a z800 and z900:

Design Differences

• The z800 has a larger entry memory confi guration (8 GB

vs. z900’s 5 GB).

• The z800 has larger memory increments (8 GB) minimiz-

ing the need to upgrade memory.

• The z800 has no partial memory restart function. The

z800 has one Primary Memory Array vs. the z900’s two

or four.

• The z800 has no concurrent memory upgrade.

• The z800 has a cycle time of 1.6 ns vs. 1.3 ns for z900.

• The z800 has no Internal Battery feature.

• The z800 has one power phase.

• The z800 has no native parallel channels. Parallel

channel connectivity is obtained via ESCON and the

OPTICA converter.

• The z800 has no OSA-2 support.

• The z800 has a smaller MCM which scales to a 4-way.

• All z800s have one SAP standard. The z900 models

have two or three SAPs standard.

• There is no spare PU on the z800 4-way. All z900s

have at least one spare.

• The z800 has a smaller entry point (performance) than

the z900. There are four z800 uniprocessors.

• The z800 is air-cooled (no closed loop liquid cooling).

• Some model upgrades may require an OS IPL.

• The z800 uses less power, cooling and space.

• The z800 requires 30 inches of service clearance on

all sides.

Offering Differences

The z800 Dedicated Linux Model

• Software is priced differently

• The z800 model 0E1 has an IFL engine standard

• Cryptographic Coprocessor is optional

• z/OS.e is available on the z800

The z800 has been designed to provide the platform for

the reliability, availability and serviceability that demanding

24x365 applications need. z800 technology integration

enhances reliability by providing fewer chances for failure.

Use of highly reliable burned-in technology assists in elimi-

nating early life failures. Robust design such as constant

memory, error checking and correction, transparent spar-

ing and concurrent maintenance allow robust availability.

The z800 has two service elements. The z800 fi ts effi ciently

into a single frame which has a smaller footprint than

the z900 base frame. The z800 is an extension of the

z900 design to allow small- and medium-size customers to

exploit function and features of the zSeries and its benefi ts

to e-business applications.

z800 5-PU Logical Structure

Clock

PU0L1

PU2

L1

PU3

L1

MBA

PU1L1

PU4L1

ICB-3 Links1 Gbyte/s

I/O Cage

ESCON 16 PortFICON Express 2 PortOSA-E GbE 2 portOSA-E FEN 2 portOSA-E ATM 2 portOSA-E HSTR 2 portISC-3 1-4 PortPCICC 2 ProcessorsPCICA 2 Processors

Up to 16 I/O Adapter: ETR-Links

MC1Crypto 0 Crypto 1

STI- Links1 Gbyte/s

MCM

Processor card

up to 32GB total Memory

Le

ft b

an

k D

IMM

S a

nd

Co

ntr

ol S

tore

Rig

ht b

an

k DIM

MS

Memory

Memory

Memory

Memory

(To other z800 or z900)

1 Cache Control Chip + 2 Cache Data Chips8 MB Shared L2 Cache

MC0

18

Relative Performance of z900 Servers

z900 Relative/Avg PerformanceBased on ITRs

12-wayG6

12-wayG6

10-wayG5

16-wayzSeries

4-wayzSeries

Relative P

erform

ance

z900 Zn7 z800 Xn7 Yn6

z800 Relative/Avg PerformanceBased on ITRs

2-wayG5 based

10-wayG4

10-wayG3

4-wayG5

4-wayzSeries

5-way

Relative P

erformance

z800 MP2000RA6-RD6 MP3000 RA5-RY5 RA4-RY4

Note: The fi gures on this page are to be used to depict the

relationship between different Parallel Enterprise servers

and zSeries in terms of increasing capacity within each

family. Comparing relative performance of one model to

other models should be done using LSPR.

19

The z800 has a total of 12 models to offer fl exibility in

selecting a system to meet the customer’s needs. Ten of

the models are general purpose systems. One non-general

purpose model is the Dedicated Linux Model 0LF, the

other model is the Coupling Facility Model 0CF. There

are a wide range of upgrade options available which

are described below. and shown on the following pages.

Capacity Upgrade on Demand, Capacity BackUp (CBU)

and Customer-Initiated Upgrade (CIU) are available. The

z800 has also been designed to offer a high performance

and effi cient I/O structure to meet the demands of e-busi-

ness as well as high demand transaction processing appli-

cations. The z800 has one 16-slot I/O cage to house the

different I/O cards. Up to 240 ESCON channels (16 cards)

will fi t into the I/O cage; or a total of 16 FICON Express

(or FCP) channels (eight cards) and 120 ESCON channels

(eight cards) can be accommodated in a fully confi gured

system. There is one system design for the zSeries 800.

This is a fi ve Processor Unit (PU) MultiChip Module (MCM)

with up to 32 GB of memory (entry storage is 8 GB).

All z800 models have one memory bus. The PU has a

cycle time of 1.6 nanoseconds. The z800 models and a

discussion of confi gurations follow.

z800 General Purpose Models

These ten models are general purpose systems and range

from a 1-way to 4-way symmetrical multiprocessor (SMP)

server. These models can upgrade from one model to the

next. All models have one System Assist Processor (SAP)

as standard and six STI links for I/O attachment. Any of

the spare PUs on the MCM can be assigned as a Central

Processor (CP), Integrated Coupling Facility (ICF) engine

or Integrated Facility for Linux (IFL) engine. Transparent

sparing allows a spare PU, if available, to replace a failing

CP, SAP, ICF or IFL.

z800 Dedicated Linux Model, z800 Linux Model 0LF

The Model 0LF is the Dedicated Linux Model. All engines

are IFLs and can run one to four independent IFLs. This

model can be upgraded by adding IFLs until the maximum

of four is reached. The fi fth PU is an SAP. All IFLs run at

full speed.

z800 Family Models

z800 Coupling Facility Model 0CF

The Model 0CF is the standalone Coupling Facility Model

in the z800 family. This model can have one to four ICF

engines. All ICF engines run at full speed. It is recom-

mended that the z800 CF Model 0CF be used in produc-

tion data sharing confi gurations for isolating the physical

Coupling Facility for availability and fl exibility.

The Coupling Facility Control Code (CFCC) on the z800

0CF is a 64-bit implementation, using the full addressing

capability of the z/Architecture. This capability provides

storage relief for any software that needs to use large lock

structures; DB2 data sharing is just one example.

z800 Capacity Upgrade on Demand (CUoD)

Capacity Upgrade on Demand (CUoD) allows for the

nondisruptive addition of one or more Central Processors

(CPs), Internal Coupling Facilities (ICFs) and/or Integrated

Facility for Linux (IFLs). Capacity Upgrade on Demand can

very quickly add processors up to the maximum number

of available inactive engines. This helps provide customers

with value for much needed dynamic growth in an unpre-

dictable e-business world. The Capacity Upgrade on

Demand function combined with Parallel Sysplex technol-

ogy enables dynamic capacity upgrade capability.

z800 Server

CMOS 8S with copper interconnect5 PUsUp to 4 CPs8-32 GB Memory1.6 ns Cycle time6 STI busses

Other Models Available:

zSeries Dedicated Linux Model z800 Linux Model 0LF

z800 Coupling Facility Model 0CF

0A10B10C10E10X20010A2002003004

20

The CUoD functions are:

• z800 continues to support the dynamic CUoD function

introduced on G5/G6.

– Nondisruptive CP, ICF, and IFL upgrades are available

on full engine general purpose models (Models 001,

002 and 003) within minutes.

• Dynamic upgrade of all I/O cards in the z800 I/O Cage.

zSeries Server Capacity BackUp (CBU)

Capacity BackUp (CBU) is offered with the zSeries proces-

sors designed to provide reserve emergency backup CPU

capacity for situations where customers have lost capacity

in another part of their establishment and want to recover

by adding reserve capacity on a designated zSeries

system. A CBU system normally operates with a “base”

CPU confi guration and with a preconfi gured number of

additional Processor Units (PUs) reserved for activation in

case of an emergency.

The zSeries server technology is ideally suited for provid-

ing capacity backup since the reserved CBU processing

units are on the same technology building block, the MCM,

as the regular CPs. Therefore, a single processor can

support two diverse confi gurations with the same MCM.

For CBU purposes, the z800 general purpose full engine

models (001, 002, 003) can scale from a one-way to a

four-way system.

The following chart describes the possible nondisruptive

CBU upgrades. (Concurrent sub-uni or sub-dyadic CBU

upgrades are not supported.)

From/To 0A1 0B1 0C1 0X2 001 0A2 002 003 004

0E1 Yes* Yes* Yes* Yes* Yes* Yes* Yes* Yes* Yes*

0A1 n/a Yes* Yes* Yes* Yes* Yes* Yes* Yes* Yes*

0B1 n/a n/a Yes* Yes* Yes* Yes* Yes* Yes* Yes*

0C1 n/a n/a n/a Yes* Yes* Yes* Yes* Yes* Yes*

0X2 n/a n/a n/a n/a Yes* Yes* Yes* Yes* Yes*

001 n/a n/a n/a Yes* n/a Yes* Yes* Yes* Yes*

0A2 n/a n/a n/a Yes* n/a Yes* Yes* Yes* Yes*

002 n/a n/a n/a n/a n/a n/a n/a Yes Yes

003 n/a n/a n/a n/a n/a n/a n/a n/a Yes

* Yes - While model upgrades to the processor itself are concurrent, some software may not be able to take advantage of the increased capacity without performing an Initial Program Load (IPL). 1) ICFs and IFLs can be added concurrently if the initial LPAR setup is done properly 2) CBU applies to whole zSeries general purpose engine additions only. It does not apply to IFL or ICF Processor additions.

The “base” CBU confi guration must have suffi cient

memory and channels to accommodate the potential

needs of the larger CBU target machine. When capacity is

needed in an emergency, the primary operation performed

is activating the emergency CBU confi guration with the

reserved PUs added into the confi guration as CPs.

Upon request from the customer, IBM can remotely acti-

vate the emergency confi guration. This is a fast electronic

activation that eliminates time associated with waiting for

an IBM CE to arrive onsite to perform the activation. A

customer request through the Hardware Master Console

and Remote Support Facility could drive activation time

down to minutes; a request by telephone (for customers

without RSF) could drive activation to less than an hour.

21

The z800 supports concurrent CBU downgrade on full

engine models. This function enables a Capacity BackUp

Server to be returned to its normal confi guration without an

outage (i.e. Power-on reset).

z800 Server Customer-Initiated Upgrade (CIU)

Customer-Initiated Upgrade (CIU) on the z800 is the capa-

bility to initiate a processor upgrade when spare PUs are

available via the Web using IBM Resource Link™. Custom-

ers are able to download and apply the upgrade using

functions on the Hardware Management Console via the

Remote Support Facility.

This unique and important function for zSeries gives the

customer greater control and ability in adding capacity to

the system to help meet resource requirements for unpre-

dictable e-business workloads and for applications that

are diffi cult to size. CIU is a low risk and well tested and

tried function using similar technology as that used for

CUoD.

Automatic Enablement of CBU for Geographically

Dispersed Parallel Sysplex (GDPS)

The intent of the GDPS CBU is to enable automatic man-

agement of the reserved PUs provided by the CBU feature

in the event of a processor failure and/or a site failure.

Upon detection of a site failure or planned disaster test

GDPS is designed to dynamically add PUs to the proces-

sors in the takeover site to restore processing power for

mission-critical production workloads.

I/O Connectivity

The z800 contains an I/O subsystem infrastructure that

uses an I/O cage that provides 16 I/O slots, compared

to the G5/G6 style cage with 22 slots. ESCON, FICON

Express, OSA-Express and ISC-3 cards plug into the

zSeries I/O cage. All I/O cards can be hot-plugged in the

I/O cage for advanced availability.

Cage Layout and Options

Note: The I/O cage has eight slots in the front and eight

slots in the back.

The I/O cage takes advantage of an exclusive IBM pack-

aging technology that provides a subsystem with approxi-

mately seven times higher bandwidth than the previous

G5/G6 I/O cage. Each z800 model comes with one

I/O cage in the Frame (the Frame also contains the pro-

cessor CEC cage). The I/O cage, using 16-port ESCON

cards, can hold 240 ESCON channels; previous packaging

required three I/O cages to package the same number

of channels. For FICON Express, the I/O cage can accom-

modate up to 16 cards or 32 FICON Express channels

per cage.

CEC

I/O Cage

22

I/O Cards and Channels

The following topics describe I/O cards and the functionality

supported by the I/O cage as well as coupling links and

virtual networks on the z800.

Supported z800 Networking and I/O Adapters:

• ESCON (16 port)

• ISC-3

• FICON Express

• PCICC

• PCICA

• OSA-Express Token-Ring

• OSA-Express Gb Ethernet

• OSA-Express Fast Ethernet

• OSA-Express 155 ATM

Up to 240 ESCON Channels

• A 16-port channel card which plugs into the z800 I/O

cage is used for all ESCON channel orders. Up to 15

ports are used for ESCON connectivity; one port is

reserved as a spare port.

• Channels are available in four port increments and

are allocated for maximum availability across multiple

ESCON adapters.

The chart below shows channel increments and the

number of ESCON adapters needed.

ESCON Confi guration

Number of Channels Cards 4 - 28 2

32 - 60 4

64 - 88 6

92 - 120 8

124 - 148 10

152 - 180 12

184 - 208 14

212 - 240 16

Up to 32 FICON Express Channels

The z800 supports up to 32 FICON Express channels.

FICON Express is available in long wave (LX) and short

wave (SX) operation. The FICON Express card has two

channels per card. The LX and SX cannot be intermixed

on a single card. The maximum number of FICON Express

cards is 16 installed in the I/O cage.

Up to 32 Fibre Channels (FCP Channels) Channels

The z800 will support up to 32 FCP channels for Linux.

The same 2-port FICON or FICON Express channel card

features used for FICON channels are used for FCP chan-

nels as well. FCP channels are enabled on these existing

cards as a microcode load with a new mode of operation

and new CHPID defi nition. FCP is available in long wave-

length (LX) and short wavelength (SX) operation, though

the LX and SX cannot be intermixed on a single card.

Note, maximum combined native FICON (FC), FICON

Bridge (FCV), and FCP channels is 32.

Parallel Channels

Direct connection of parallel channels is not supported on

the z800. In order to connect devices that have parallel

interfaces an ESCON Converter, such as the one produced

by OPTICA, must be used. The ESCON converter will

accept an ESCON cable from the server and convert the

signal to parallel type protocol, then transmit the signal

over the bus and tag cable to the parallel device.

InterSystem Coupling-3 (ISC-3)

A four-port ISC-3 card is provided on the z800 family of

processors. It consists of a mother card with two daughter

cards which have two ports each. Each daughter card port

is capable of operation at 1 Gb/sec in Compatibility Mode

or 2 Gb/sec in Peer Mode up to a distance of 10 km.

The mode is selected for each port via CHPID type in the

IOCDS. The ports are orderable in one port increments.

An RPQ (8P2197) is available to allow ISC-3 distances up

to 20 km.

23

Integrated ClusterBus-3 (ICB-3)

An ICB-3 is used to provide high-speed coupling commu-

nication between two zSeries servers over short distances

(less than 7 meters). A maximum of fi ve ICB-3 links is

possible on the general purpose z800 models and six are

available on the Coupling Facility model. These ICB-3 links

do not take up any of the 16 slots available in the cage.

Internal Coupling-3 (IC-3)

IC-3 links emulate the coupling links between images

within a single server. IC-3 links are defi ned in the IOCP.

There is no physical channel involved. Defi nitions of IC-3

links do count toward the maximum of 256 CHPIDs on the

z800. A Parallel Sysplex environment can be set up on a

single server using IC-3 capabilities.

Channel CHPID Assignment

The z800 provides customers with the option of mapping

CHPID numbers to physical channel ports. This is called

Channel CHPID Assignment. Channel CHPID Assignment

helps customers maintain G5/G6 I/O defi nitions during

system upgrades and in establishing new I/O defi nitions. It

also allows for a logical sequence of CHPID numbers to be

assigned to a control unit. A CHPID Mapping tool is avail-

able on Resource Link, ibm.com/servers/resourcelink, to

assist with mapping.

IBM leads the industry in helping to bring greater security

to e-business with its high-availability CMOS Crypto-

graphic Coprocessors. For the z800, the two Crypto-

graphic Coprocessors Single Chip Modules (SCMs) have

been moved from the MCM to the Basic Processor Unit

(BPU) Cage. The SCMs are plugged directly into the rear

of the BPU backplane.

The z800 servers can also support a combination of

up to eight optional Peripheral Component Interconnect

Cryptographic Coprocessor (PCICC) or the PCI

Cryptographic Accelerator (PCICA) features. Each

PCICC/PCICA feature contains two cryptographic copro-

cessor accelerators, for a maximum of 16 coprocessor

accelerators. Approximately 800 SSL transactions can be

completed by the cryptographic capabilities of the z800.

The combination of the two coprocessor types enables

applications to invoke industry-standard cryptographic

capabilities — such as DES, Triple DES, or RSA — for

scalable e-transaction security and the fl exibility to adopt

new standards quickly.

The PCICA feature is designed to address the high-perfor-

mance SSL needs of e-business applications, and has

a design point different from the existing zSeries CMOS

Cryptographic Coprocessor and zSeries PCICC feature.

PCICA Cryptographic support for IFL engines is supported

on the z800.

Cryptography

24

The e-business world is demanding. It requires fast data

access, continuous data availability, and improved fl ex-

ibility, all with lower cost of ownership. zSeries storage

connectivity can help you achieve these goals.

FICON and FICON Express Channel Card Features

Performance

With its 2 Gigabit per second link data rate capability,

the FICON Express channel card feature is the latest

zSeries implementation for the Fibre Channel Architecture.

The FICON Express card has two ports and can achieve

improved performance over the previous generation

FICON channel card. For example, attached to a 100

MB/sec link (1 Gb/sec), a single FICON Express feature

confi gured as a native FICON channel is capable of sup-

porting up to 7200 I/O operations/sec and an aggregate

total throughput of 120 MB per second on the z800 while

the older FICON feature confi gured similarly only gets up

to 5000 I/O operations per second and 80 MB per second

throughput. With 2 Gb/sec links, customers may expect up

to 170 MB/sec of total throughput. The 2 Gb/sec link data

rates are applicable to native FICON and FCP channels

on zSeries only and for full benefi t require 2 Gb/sec capa-

ble devices as well. Customers can leverage this addi-

tional bandwidth capacity to help consolidate channels

and reduce confi guration complexity, infrastructure costs,

and the number of channels that must be managed.

Please note, no additional hardware or code is needed in

order to obtain 2 Gb/sec links. The functionality is incorpo-

rated in all zSeries with May 2002 LIC. The link speed is

auto-negotiated between server and devices.

Fibre Channel Connectivity

Flexibility - Three channel types supported

The FICON/FICON Express channel card features now

support three different channel types: 1) FCV Mode for

FICON Bridge Channels, 2) FC mode for Native FICON

channels (including the FICON CTC function), and 3) FCP

mode for Fibre Channels (FCP channels). Support for FCP

devices means that zSeries servers will be capable of

attaching to select fi bre channel switches/directors and

FCP/SCSI devices and may access these devices from

Linux for zSeries.

Distance

All channels defi ned on FICON and FICON Express LX

channel card features support a maximum unrepeated

distance of up to 10 km (6.2 miles, or up to 20 km via

RPQ, or up to 100 km with RPQ and repeaters) over

nine micron single mode fi ber and up to 550 meters (1,804

feet) over 50 or 62.5 micron multimode fi ber through Mode

Conditioning Patch (MCP) cables. The maximum unre-

peated distances for channels defi ned on the SX FICON/

FICON Express channel cards are up to 500 meters and

300 meters (984 feet) for 50 and 62.5 micron multimode

fi ber, respectively. The FICON/FICON Express channel

cards are designed to reduce the data droop effect that

made long distances not viable for ESCON. This distance

capability is becoming increasingly important as customers

are moving toward remote I/O, vaulting for disaster recovery

and looking to Geographically Dispersed Parallel Sysplex

for availability.

Shared infrastructure

Both FCP and FICON (FC-SB-2) are adopted by NCITS

(ANSI) as standards to the Fibre Channel Architecture.

Using open connectivity standards leads to shared I/O

fi ber cabling and switch infrastructures, facilitated data

sharing, storage management and SAN implementation,

and integration between the mainframe and UNIX® and

Intel® technologies.

25

FICON Bridge Channel

Introduced fi rst on the 9627 G5 processors, the FICON

Bridge (FCV) channel is still an effective way to use FICON

bandwidth with existing ESCON control units. FICON/

FICON Express LX channel cards in FCV (FICON Con-

verted) Mode of operation can attach to the 9032 Model

005 ESCON Director through the use of a director bridge

card. Up to 16 bridge cards are supportable on a single

9032 Model 005 with each card capable of sustaining up

to eight concurrent ESCON data transfers. 9032 Model 005

ESCON Directors can be fi eld upgradeable at no-charge

to support the bridge cards, and bridge cards and ESCON

cards can coexist in the same director.

Native FICON Channels

Native FICON channels and devices can help to reduce

bandwidth constraints and channel contention to enable

easier server consolidation, new application growth, large

business intelligence queries and exploitation of e-business.

Currently, the IBM Enterprise Storage Server (ESS) models

F10, F20 and 800 have two host adapters to support native

FICON. These host adapters each have one port per card

and can either be FC 3021 for long wavelength or FC 3032

for short wavelength on the F10/F20 or FC 3024 for long

wavelength and 3025 for short wavelength on the 800. All

three can support up to 16 FICON ports per ESS. The

Model 800 is 2 Gb/sec link capable.

The IBM Enterprise Tape Controller 3590 Model A60 pro-

vides up to two FICON interfaces which can coexist with

ESCON on the same box. Customers can utilize this IBM

highest capacity, highest performance tape drive to sup-

port their new business models.

Four Fibre Channel directors provide dynamic connectivity

to native FICON control units. The IBM 2032 models 001

and 064 (resell of the McDATA ED-5000 and ED-6064)

are 32- and 64-port high-availability directors. The IBM

2042 models 001 and 128 (resell of the Inrange FC/9000)

are 64- and 128-port high-availability directors. All have

features that provide interface support to allow the unit

to be managed by System Automation for OS/390. In

addition, the McDATA 6064, and soon the INRANGE

FC/9000-64/-128 directors will be 2 Gb/sec link capable

as well.

Though native FICON channels don’t exploit zSeries IRD

Dynamic Channel Path Management like ESCON and

FICON Bridge channels do, the raw bandwidth and dis-

tance capabilities that native FICON end-to-end connec-

tivity has to offer makes them of interest for anyone

with a need for high-performance large data transfers or

enhanced multisite solutions.

FICON CTC function

Native FICON channels support CTC on the z900 and

z800. G5 and G6 servers can connect to a zSeries FICON

CTC as well. This FICON CTC connectivity will increase

bandwidth between G5, G6, z900, and z800 systems.

Because the FICON CTC function is included as part of the

native FICON (FC) mode of operation on zSeries, FICON

CTC is not limited to intersystem connectivity (as is the

case with ESCON), but will also support multiple device

defi nitions. For example, ESCON channels that are dedi-

cated as CTC cannot communicate with any other device,

whereas native FICON (FC) channels are not dedicated

to CTC only. Native can support both device and CTC

mode defi nition concurrently, allowing for greater connec-

tivity fl exibility.

FICON Support for Cascaded Directors

Native FICON (FC) channels now support FICON cas-

caded directors. This support is for a two director, single

hop confi guration only. This means that a Native FICON

(FC) channel or a FICON CTC can connect a server to

a device or other server via two (same vendor) FICON

26

Directors in between. This type of cascaded support is

important for disaster recovery and business continuity

solutions because it can provide high availability, extended

distance connectivity, and (particularly with the implemen-

tation of 2 Gb/sec Inter Switch Links) has the potential for

fi ber infrastructure cost savings by reducing the number of

channels for interconnecting the two sites.

FICON cascaded directors have the added value of ensur-

ing high integrity connectivity. New integrity features are

introduced within the FICON channel and the FICON cas-

caded switch fabric help to ensure the detection and

reporting of any miscabling actions occurring within the

fabric and helps to prevent data from being delivered to

the wrong end point.

FICON cascaded directors are offered in conjunction with

INRANGE and McDATA switch vendors.

FICON Connectivity

= LX ONLY

z900

z800

All FICON Channels =100MB/s

= LX or SX

2032

2042

ESCD9032

Model 5

FICONBridge

FICONBridge

32 or 64

PORT

64 or 128

PORT

= LX ONLY

ESCONCU

ESCONCU

ESCONCU

ESSF10, F20

MAGSTAR3590 A60

MAGSTAR3590 A60

ESSF10, F20

FCP Channels

zSeries now supports FCP channels, switches and FCP/

SCSI devices with full fabric connectivity under Linux

for zSeries. Support for FCP devices means that zSeries

servers will be capable of attaching to select FCP/SCSI

devices and may access these devices from Linux for

zSeries. This expanded attachability means that customers

have more choices for new storage solutions, or may have

the ability to use existing storage devices, thus leveraging

existing investments and lowering total cost of ownership

for their Linux implementation.

The support for FCP channels is for Linux only. Linux may

be the native operating system on the zSeries server, or

it can be in LPAR mode or operating as a guest under

z/VM 4.3 or subsequent releases. Please note, FCP device

support is not available for native z/VM 4.3; rather, z/VM

4.3 acts as facilitator for the FCP function, allowing it to

pass through the z/VM systems direct to the Linux guest.

The 2 Gb/sec capability on the FICON Express channel

cards means that 2 Gb/sec link speeds are available for

FCP channels as well.

FCP Full fabric connectivity

FCP full fabric support means that any number of (single

vendor) FCP directors/switches can be placed between

the server and FCP/ SCSI device thereby allowing many

“hops” through a storage network for I/O connectivity. This

support along with 2 Gb/sec link capability is being deliv-

ered together with IBM switch vendors Brocade, Inrange,

and McDATA. FCP full fabric connectivity enables multiple

FCP switches/directors on a fabric to share links and there-

fore provide improved utilization of intersite connected

resources and infrastructure. Further savings may be real-

ized in the reduction of the number of fi ber optic cabling

and director ports.

27

The Open Systems Adapter-Express (OSA-Express)

features (Gigabit Ethernet, Fast Ethernet, 155 ATM, and

Token-Ring) are designed to support the I/O infrastructure

of zSeries. The z800 does not support FDDI. These features

combined with z/OS or OS/390, z/VM or VM/ESA, Linux

and VSE/ESA, are designed to deliver a balanced system

solution to maximize throughput and minimize host inter-

rupts to continue to satisfy your business goals. The

zSeries OSA-Express feature plugs into the I/O Cage on

the z800.

A high-performing Gigabit Ethernet feature with a 66 MHz,

64-bit PCI bus capable of achieving line speed of 1 Gb/sec

is available on the z800. This design incorporates two

ports of connectivity in a single I/O slot. Each port uses

one CHPID. These features attach to the STI bus at 333

Mb/sec.

The infrastructure for Fast Ethernet and 155 ATM and the

Token-Ring available on the zSeries servers offers two

ports of connectivity in a single I/O slot. The Fast Ethernet

runs at either 10 or 100 Mb/sec. The ATM runs at 155

Mb/sec. The Token-Ring runs at either 4 or 16 or 100

Mb/sec permitting connection to higher speed Token-Ring

switch backbones and servers. Each OSA-Express port

uses one CHPID. These features also attach to the STI bus

at 333 Mb/sec.

Open Systems Adapter Features

(OSA-Express)

zSeries OSA-Express Fast Ethernet

Queued Direct Input/Output (QDIO)

The OSA-Express Gigabit Ethernet, Fast Ethernet, and 155

ATM (Ethernet LAN Emulation), and Token-Ring features

support QDIO, which was fi rst introduced in Communica-

tion Server for OS/390 Version 2 Release 7.

Queued Direct Input/Output (QDIO), a highly effi cient

data transfer architecture, breaks the barriers associated

with the Channel Control Word (CCW/ESCON) architecture

increasing data rates and reducing CPU cycle consump-

tion. QDIO is designed to dramatically reduce system

overhead and improves throughput using S/390 memory

queues and a signaling protocol to directly exchange data

between the OSA-Express microprocessor and Communi-

cations Server for OS/390 2.10, and z/OS.

QDIO Mode - TCP/IPnon-QDIO modeSNA PassthruTCP/IP PassthruHPDT MPC

IP WANIntranet

Server

SNA DLSwTCP/IP

Native SNA

Server

TCP/IP applications

TN3270 browser access to SNA

Enterprise Extender for SNA

end points

Remote Office

IP WANIntranet

Remote Office

4/16 MbpsToken-Ring

4/16 MbpsToken-Ring

Internet orextranet

Switch/Hub/

Router

IP Router

pSeries, RS/6000

xSeries, Netfinity

ServerServer

DLSw Router

Switch/Hub/

Router

10/100 MbpsToken-Ring

10/100 MbpsToken-Ring

28

zSeries OSA-Express Gigabit Ethernet

NON-QDIO operational mode

The OSA-Express Fast Ethernet, the Token-Ring, and the

155 ATM (native, Ethernet and Token-Ring LAN emulation)

features also support the non-QDIO mode of operation.

The adapter can only be set (via the CHPID type param-

eter) to one mode at a time. The non-QDIO mode does not

provide the benefi ts of QDIO. However it does provide for

protocol support similar to the OSA-2 adapter but at higher

levels of performance. This support includes native SNA,

APPN®, High Performance Routing, TCP/IP passthru, and

HPDT MPC.

TCP/IP applicationsTN3270 browser access to SNAEnterprise Extender

for SNA end points

QDIO Mode - TCP/IP

pSeries, RS/6000

xSeries, Netfinity

Switch/Hub/

Router

Server

GigabitEthernet

Server

Server

Server

IPRouter

IPRouter

Remote Office

4/16/100 MbpsToken-Ring

10/100 MbpsEthernet

4/16 MbpsToken-Ring

IP WANIntranet

Internet orextranet

zSeries OSA-Express Token-Ring

Server to User Connections

A key strength of OSA-Express and associated Com-

munications Server protocol support is the ability to

accommodate the customer’s attachment requirements,

spanning combinations of TCP/IP and SNA applications

and devices. Customers requiring TCP/IP connections

from the remote site to the TCP/IP or SNA applications

on zSeries and S/390 servers can use OSA-Express with

QDIO and either direct TCP/IP access or appropriate SNA

to IP integration technologies such as TN3270 Server and

Enterprise Extender. Customers who require the use of

SNA-based connections from the remote site can use a

TCP/IP or SNA transport to the data center and connection

into zSeries and S/390 servers using OSA-Express in non-

QDIO mode.

QDIO Mode - TCP/IPnon-QDIO modeSNA PassthruTCP/IP PassthruHPDT MPC

Server

Server

IP WANIntranet

Server

SNA DLSwTCP/IP

Native SNA

Server

TN3270 browser access to SNA

Enterprise Extender for SNA end points PCP/IP

applications

Remote Office

IP WANIntranet

Remote Office

4/16 MbpsToken-Ring

4/16 MbpsToken-Ring

4/16 MbpsToken-Ring

4/16 MbpsToken-Ring

DSLw Router

16/100 MbpsToken-Ring

Server

Server

Internet orextranet

4/16/100 MbpsToken-RingBackbone

Switch/Hub/

Router

4/16 MbpsToken-Ring

IP Router

100 MbpsToken-Ring

10/100 MbpsToken-Ring

10/100 MbpsToken-Ring

29

LPAR Support of OSA-Express

For customers who use the Processor Resource/Systems

Manager™ (PR/SM™) capabilities of the zSeries and S/390

servers, IBM offers Multiple Image Facility (MIF), allowing

the sharing of physical channels by any number of logical

partitions (LPARs). Since a port on an OSA-Express fea-

ture is like a channel, sharing of an OSA-Express port is

done using MIF. The LPARs are defi ned in the Hardware

Confi guration Defi nition (HCD), and each LPAR is given a

specifi c partition ID. Depending upon the feature, and how

it is defi ned, SNA/APPN/HPR and TCP/IP traffi c can fl ow

simultaneously through any given port.

z800 OSA-Express Asynchronous Transfer Mode

ATM Network

Server

ATM Native155 Mbps

ATM

ATM LE Network

Server

ServerLANEmulationServer

4/16 MbpsToken-Ring

ATM LANE

10/100 Mbps Ethernet

Switch/Hub/

Router

155 Mbps

Transparent Sparing

z800 offers a fi ve-processor MCM with a maximum of four

Central Processors. The added capacity is available for

nondisruptive customer growth or, in the case of processor

failure, for transparent sparing.

Enhanced Dynamic Memory Sparing

The z800 memory subsystem has a robust recovery design.

Error Checking and Correcting (ECC) and memory sparing

functionality are key features to ensure the memory sub-

system availability.

ESCON Port Sparing

The ESCON 16-port I/O card is delivered with one unused

port dedicated for sparing in the event of a port failure on

that card. Other unused ports are available for nondisrup-

tive growth of ESCON channels.

Concurrent Maintenance

• Concurrent Service for All I/O Cards: All cards that plug

into the I/O Cage are able to be added and replaced

concurrent with system operation. This eliminates any

need to schedule outage to service or upgrade the I/O

subsystem on this cage.

• Upgrade for Coupling Links: The z800 has concurrent

maintenance for the ISC-3 card. Also, Internal Coupling

Links can be added concurrently. This eliminates the

need for scheduled downtime.

• Cryptographic Cards: The PCICC cards and PCICA

cards plug in the I/O cage and can be added or

replaced concurrent with system operation.

• Redundant Cage Controllers: The Power and Service

Control Network features redundant Cage Controllers

for Logic and Power control. It is designed to enable

nondisruptive service to the controllers and eliminates

customer scheduled outage.

• Auto-Switchover for Service Element (SE): The z800 has

two Service Elements standard. In the event of a failure

on the Primary SE, the switchover to the backup is

handled automatically. There is no need for any interven-

tion by the customer or Service Representative.

Concurrent Capacity Backup Downgrade (CBU Undo)

This function allows the customer to downgrade the disaster

backup machine to its normal confi guration without requiring

the Power On Reset (POR). As with z800 upgrades, certain

downgrade paths may require Operating System IPL.

Advanced Availability Functions

30

• z/Architecture

– 64-bit Architecture

• Intelligent Resource Director

– LPAR CPU Management

– Dynamic Channel Path Management

– Channel Subsystem Priority Queuing

• HiperSockets

• InterSystem Channel-3

• Integrated Cluster Bus-3

• Internal Coupling Channel-3

• Channel CHPID Assignment

• Nondisruptive replacement of I/O

• Two port OSA-Express adapters at line speed

• ESCON Port Sparing

• 1Gb/sec / 2Gb/sec Auto-negotiated FICON Express

• FICON CTC

• FCP channels for Linux

• Concurrent Maintenance for ISC-3 adapter card

• Concurrent upgrade for Coupling Links

• Concurrent Service for all I/O cards

• Total 512K subchannel addresses

• Redundant Cage Controllers

• Auto-Switchover for Service Element

• Enhanced Dynamic Memory Sparing

• Enhanced Hardware Compression

• Cryptographic Coprocessors (Single Chip Module)

• Integrated Facilities for Linux (IFLs)

• Nondisruptive CBU downgrade

• Customer-Initiated Upgrade (CIU)

Note: zSeries servers support all G5/G6 functions, except

Asynchronous Data Mover Facility (ADMF) Integrated

Coupling Migration Facility (ICMF).

zSeries 800 Features / Functions

zSeries 800 Model Upgrades

• Vertical upgrades within z800 General Purpose Models

• Vertical upgrades within z800 Coupling Facility Model

• Coupling Facility model can upgrade to General Purpose

Models

• Vertical upgrades within z800 Linux Model 0LF

z800 Upgrade Path Matrix

Model

0A1

0B2

0C1

0X2

001

0A2

002

003

004

0CF

0B10A10E1

-

-

-

-

-

-

-

-

-

-

-

-

-

-

--

0C1

X

-

-

-- - - - X

-

-

-

-

-

0X2

X

X

-

-

-

-

-

-

-

001

X

X

X

-

-

-

-

-

X

-

-

-

XX

0A2

X

X

X

XX

-

-

-

-

X

002

X

X

X

X

X

-

--

X

003

X

X

X

X

XX

-

-

X

004

X

X

X X X X

X

X

XX

-

X

X

-Supported Upgrade Path

Not a Viable Upgrade

Matrix boxes indicate Software Dependencies

Matrix boxes indicate Viable Concurrent Upgrade Paths

Matrix Legend

XX X

X

X

X

X X X X X0E1 X X-

X

- -

31

Processor Options zSeries 800 Family

CP +SAP Model PUs STD IFL/ ICB-3 ISC-3 STIs SPARE+SPARE ICFs +IFL

1+1+2+1 0E1 5 2 3 5 5 5 2

1+1+3+0 0A1 5 1 3 5 24 6 3

1+1+3+0 0B1 5 1 3 5 24 6 3

1+1+3+0 0C1 5 1 3 5 24 6 3

2+1+2+0 0X2 5 2 2 5 24 6 2

1+1+3+0 001 5 1 3 5 24 6 3

2+1+2+0 0A2 5 2 2 5 24 6 2

2+1+2+0 002 5 2 2 5 24 6 2

3+1+1+0 003 5 3 1 5 24 6 1

4+1+0+0 004 5 4 0 5 24 6 0

ICF +SAP Model PUs STD ICFs ICB-3 ISC-3 STIs SPARE+SPARE

1+1+3 1 32+1+2 0CF 5 1 2 6 24 6 23+1+1 3 14+1+0 4 0

IFL +SAP Model PUs STD IFLs ICB-3 ISC-3 STIs SPARE+SPARE

1+1+3 1 32+1+2 0LF 5 1 2 0 0 6 23+1+1 3 14+1+0 4 0

zSeries 800 Family Confi guration Detail

I/O Feature1 I/O Cage Total Channels4 Increments Comments or Adapters / slots used

ESCON - 15/16 port Yes 240 / 16 49 1 spare port per card

FICON Express - 2 port7 Yes 32 / 16 2 -

PCICC - 2 processors Yes 16 / 8 2 Not defi ned in IOCP

PCICA - 2 processors Yes 12 / 6 2 -

Fast Ethernet Yes 24 / 12 2 -

Gbit Ethernet7 - 2 port Yes 24 / 12 2 Different features

155 ATM7 - 2 port Yes 24 / 12 2 Different features

TR - 2 ports Yes 24 / 12 2 -

FE, Gbit, and - - - 24 ports ATM (12 card)

FICON Express, PCICC/CA, FE, - - - Confi gured GbE, ATM, TR as FC, FCV,

ISC-3 (1 & 2 Gbit) Yes 24 / 6 19 20 km via -2 + 2 ports RPQ (H/W 1Gb)

ICB-3 - 1 STI No 5 general 1 1 GB STI purpose 6 peer mode 0CF only

ISC-3, ICB-3 - - - 26 channel maximum

IC Channel6 No 32 / 0 2 u-code support

ISC-3, ICB-3, - - - 58 channel IC Channels maximum

microcode HiperSockets- 4 / 0 1 support - 1 CHPID for each defi ned HiperSockets

1. Max 256 CHPIDS; 2. 28 I/O slots per nI/O Cage; 3. 22 I/O slots per cI/O Cage; 4. Supported and I/O slots required; 5. nI/O Cage plus cI/O Cage; 6. RPQ to 12: if no cI/O Cage present - RPQ to 16; 7. MM & SM; 8. 2 defi ned channel; 9. Microcode enabled

32

Channels

ESCON FICON Express

Minimum 0 0

Maximum 256 96

Increments 4 2

Notes: - Min. 1 Feature of 2 ESCON or FICON Express cards required - Total CHPIDS all types (ESCON, FICON Express, OSA-E, PCICC/CA, ISC-3, ICB-3, IC-3); Max. 256

Coupling Links

Links IC ICB-3 ISC-3 Max # Links

z800 - 0CF 32 6 24 26

z800 General Purpose Servers 32 5 24 26

z800 0LF 0 0 0 0

I/O Connectivity

Channel Type Maximum I/O Cards Maximum channels/ ports/engines

ESCON 16 cards max 240 channels

FICON Express 16 32 channels

OSA-Express 12 24 ports

PCICC 8 16 engines

PCICA 6 12 engines

PCI Cryptographic Coprocessor (PCICC)

PCICC Dual PCICC Cryptographic F e a

Minimum 0 0

Maximum 8 16***

Increments 1 2 1 card slot/feature **2 Crypto engines/feature; 2 CHPIDs per feature ***Combined total of PCICC and PCICA engines cannot exceed 16

PCI Cryptographic Accelerator (PCICA)

PCICA Dual PCICA Cryptographic Features* Engines**

Minimum 0 0

Maximum 6 12***

Increments 1 2* 1 card slot/feature **2 Crypto engines/feature; 2 CHPIDs per feature ***Combined total of PCICC and PCICA engines cannot exceed 16

OSA Networking Features

Minimum Maximum Increments

OSA-Express* Features 0 12 1*GbE, FastE, ATM, TR; 2-ports/feature; 2 CHPIDs/feature; 1 card slot/feature

Summary of z800 Features z/OS

33

Processor Unit Assignments

General Purpose Models

Processor Storage Confi gurations

Physical Characteristics

zSeries 800 All Models

Frame

Power requirements; 50/60 Hz - Volts 200-240- kVA 3.2

Heat Output KBTU/hr 10

Air Flow CFM .39Air Flow m*3/m in 11.1

Floor space - Sq meters .83- Sq feet 8.9

Including service clearance - Sq meters 5.99- Sq feet 64.5

Approximate weight - kg 545 - lbs 1201

Height - cm 182 cm- inches 71 inWidth - cm 72 cm- inches 29 inDepth - cm 115 cm- inches 45 in Note: z800s use single phase power. UPS support is strongly recommended to protect against power outages and line disturbances

5

1 to 4 CPs1 SAP3 ICFs3 IFLs

General Purpose Models

5

0 CPs1 SAP0 ICFs1 to 4 IFLs

Linux Model (0LF)

Coupling Facility Model (0CF)

5

0 CPs1 SAP1 to 4 ICFs0 IFLs

8 GB standard 16 GB 24 GB 32 GB

CF Level Function

12 64-bit support for Coupling Facility

10 z900 GA2 support

9 MQSeries shared message queues WLM Multisystem Enclave Support Intelligent Resource Director** IC3/ISC3/ICB3 Peer Mode**

8 Dynamic ICF expansion into shared ICF pool Systems Managed Rebuild

7 Shared ICF partitions on server models DB2 Delete Name optimization

6 ICB & IC TPF support

5 DB2 cache structure duplexing DB2 castout performance improvement Dynamic ICF expansion into shared CP pool*

4 Performance optimization for IMS & VSAM RLS Dynamic CF Dispatching Internal Coupling Facility* IMS shared message queue extensions

3 IMS shared message queue base

2 DB2 performance VSAM RLS 255 Connectors/1023 structures for IMS Batch DL1 (non-BMP)

1 Dynamic Alter support CICS temporary storage queues System Logger

Notes: – G1 base can be upgraded to CF Level 4 – G2 base can be upgraded to CF Level 5 – G3 and G4 can be upgraded to CF Level 8 – G5 base CF level code is CF Level 6 – G6 base CF level code is CF Level 8 – Detailed information regarding CF Levels can be found in “Coupling Facility Level (CFLEVEL) Considerations” at ibm.com/s390/pso/cftable.html

*G3, G4, G5 and G6 only **z800, z900 required

Please note that although a particular back level machine may be updated to a more current CFCC level, NOT all the functions of that CFCC level may be able to run on that hardware platform, i.e., G3/G4 can be upgraded to CF Level 8 but it cannot use dynamic ICF expansion into shared ICF pool.

Coupling Facility — CF Level of Support

34

z800 Frame and I/O Confi guration Content: Planning for I/O

The previous frame confi gurations and I/O tables show

the capability and fl exibility built into the I/O subsystem.

The z800 can support up to 240 ESCON channels in its

I/O Cage. 240 ESCON channels, with the 16-port card

(one port is a spare), will fi ll all 16 card slots in the I/O

Cage demonstrating the packaging effi ciency of the z800

design. A more typical confi guration of 120 ESCON chan-

nels (eight cards) and eight FICON Express channels

(four cards), four OSA-Express ports (two cards) and eight

ISC-3 links (two cards) still fi ts within the I/O Cage (using

all 16 card slots).

Fiber-Optic Cabling and System Connectivity

In the world of open systems and Storage Area Networks

(SANs), the changing requirements for fi ber optic cabling

are fast becoming directly dependent upon the physical

system confi guration in the data center. As industry-stan-

dard components continue to be embraced in the open

systems and SAN environment, the fi ber optic cabling

options become numerous and complex.

Today’s marketplace is seeing the adoption of new Small

Form Factor (SFF) fi ber optic connectors, short wavelength

(SX) and long wavelength (LX) laser transceivers, and

increasing link speeds from one Gigabit per second

(Gb/sec) to 10 Gb/sec. New industry-standard SFF fi ber

optic connectors and transceivers are utilized on the

zSeries ESCON and FICON Express features, on the ISC-3

feature, and on the zSeries 900 ETR feature. These new

features must coexist with the current infrastructure that

utilizes a different “family” of fi ber optic connectors and

transceivers.

As a result of this complex and continually changing land-

scape, IBM is providing you with some options:

• Fiber Quick Connect (FQC): FQC, a zSeries confi gu-

ration option, reduces the cable bulk associated with

the installation of potentially 240 (z800) to 256 (z900)

ESCON channels in one I/O cage. Fiber harnesses,

which are factory-installed, enable connection to Fiber

Transport Services (FTS) direct-attach fi ber trunk cables.

Each trunk has 72 fi ber pairs. Four trunks can displace

the 240 to 256 fi ber optic cables on the z800 or z900.

• Conversion kits: Cables that are 2 meters (6.5 feet)

in length (eight features from which to choose on

z900 only). These kits are used when the send and

receive transceivers/connectors on the servers/switches/

directors/devices are different from one another. Conver-

sion kits are only available as features on zSeries 900.

• Mode Conditioning Patch (MCP) cables: These cables

are 2 meters (6.5 feet) in length (seven features from

which to choose on z900 only). An MCP cable enables

reuse of existing multimode fi ber optic cables with

long wavelength (LX) ISC-3, FICON, FICON Express,

and OSA-Express Gigabit Ethernet features which are

designed to support use of 9 micron single mode fi ber

optic cables. MCP cables are for use with one gigabit

links only and are offered as features on zSeries 900

only.

• IBM Network Integration and Deployment Services for

zSeries Fiber Cabling (zSeries Fiber Cabling Service):

The zSeries Fiber Cabling Service delivers to a con-

tracted service to meet the needs of your zSeries 800

or zSeries 900 system confi guration be it small, medium,

or large. This service is an analysis of your existing fi ber

optic infrastructure, with the future in mind, to effectively

plan and install the appropriate cabling options, includ-

ing jumper cables and specialty cables customized for

your system environment.

In planning for zSeries systems, refer to Planning for: S/390

Fiber Optic Links (ESCON, FICON, Coupling Links, and

Open System Adapters), GA23-0367, and the Installation

Manual Physical Planning (IMPP) manual. Refer to the

services section of Resource Link for further details on the

zSeries Fiber Cabling Service.

Access Resource Link at ibm.com/servers/resourcelink.

35

While zSeries servers are supported by a number of differ-

ent operating systems, their most advanced features are

powered by z/OS. z/OS is the foundation for the future of

zSeries, an integral part of the z/Architecture designed and

developed to quickly respond to the demanding quality of

service requirements for enterprise e-business.

z/OS is the robust operating system that is based on the

64-bit z/Architecture. It is designed to deliver the highest

qualities of service for enterprise transactions and data,

and extends these qualities to new applications using the

latest software technologies. It provides a highly secure,

scalable, high-performance base on which to deploy Inter-

net and Java-enabled applications, providing a compre-

hensive and diverse application execution environment.

z/OS takes advantage of the latest software technologies:

new object-oriented programming models that permit the

rapid design, development and deployment of applica-

tions essential to enterprise e-business. It helps protect

your investment in your present mainframe applications

by providing options for integrating existing applications

within your e-business infrastructure. It provides a solid

base for delivering on the benefi ts of industry-specifi c

UNIX and e-business applications, supporting new tech-

nologies such as Enterprise JavaBeans™, XML, HTML,

LDAP, Digital Certifi cates and Unicode. It supports such

technological advances as Parallel Sysplex processing,

TCP/IP networking capability and complies with industry

standards.

z/OS helps make critical data and processing functions

accessible to end users regardless of their location in the

heterogeneous e-business world. The z/OS base includes

z/OS Communications Server, which enables: worldclass

TCP/IP and SNA networking support, including enterprise

class dependability, performance, and scalability; highly

secure connectivity; support for multiple protocols, and

effi cient use of networking assets.

z/OS

The z/OS operating system combines many features that

change the playing fi eld of I/T infrastructure design:

• Intelligent Resource Director expands the capabilities of

z/OS Workload Manager to react to changing conditions

and prioritize critical business workloads.

• Support for 64-bit real memory and initial support of

64-bit virtual storage.

• A new installation and confi guration infrastructure that

simplifi es the installation and confi guration of z/OS and

related products.

• Software pricing models designed to support e-business

reality.

z/OS.e

Unique for the z800 is z/OS.e, a specially priced offering

for z/OS, providing select function at an exceptional price.

z/OS.e is intended to help customers exploit the fast grow-

ing world of next generation e-business by making the

deployment of new applications on the z800 very attrac-

tively priced.

z/OS.e uses the same code base as z/OS with custom

parameters and invokes an operating environment that is

comparable to z/OS in service, management, reporting,

and reliability. In addition, z/OS.e invokes zSeries hardware

functionality just as z/OS does. No new z/OS skills and

service procedures are required for z/OS.e.

z/OS.e is specifi cally for Java, Enterprise Java, C/C++,

and Web-based data transaction processing applications,

giving these workloads a price/performance customers

expect. z/OS.e disables traditional workloads. z/OS.e will

not execute CICS, IMS, COBOL, or FORTRAN applica-

tions. However, precompiled COBOL DB2 stored pro-

cedures and other precompiled COBOL applications

using the Language Environment® preinitialization interface

(CEEPIPI) are supported. You cannot use the following

compilers: COBOL, PL/I, VisualAge® PL/I, and FORTRAN.

However, z/OS.e supports execution of precompiled PL/I

and VisualAge PL/I applications.

36

At only a fraction of the cost of z/OS, z/OS.e makes the

decision to run new workloads on the mainframe easy

due to its reduced total cost of ownership and exceptional

robustness and functionality. z/OS.e and z800 together

help reduce the total cost of ownership of hardware, soft-

ware, people, and environments — making the combina-

tion very cost-effective for new applications.

With very few exceptions, z/OS.e has the same features

and functionality as z/OS. As a result, unless otherwise

specifi ed, z/OS features described herein are applicable to

z/OS.e running on a z800 server.

Intelligent Resource Director

Intelligent Resource Director (IRD) is a key feature of the

z/Architecture which extends the Workload Manager to

work with PR/SM on z800/z900 servers to dynamically

manage resources across an LPAR cluster. An LPAR

cluster is the subset of the systems that are running as

LPARs on the same CEC. Based on business goals, WLM

can adjust processor capacity, channel paths, and I/O

requests across LPARs without human intervention.

IRD assigns resources to the application; the application is

not assigned to the resource. This capability of a system

to dynamically direct resources to respond to the needs

of individual components within the system is an evo-

lutionary step. It enables the system to continuously allo-

cate resources for different applications, and this helps to

reduce the total cost of ownership of the system. IRD is

made up of three parts that work together to respond to the

demands of e-business:

• LPAR CPU Management

• Dynamic Channel Path Management

• Channel Subsystem Priority Queuing (see page 5)

The z/OS Intelligent Resource Director (IRD) Planning

Wizard helps to plan your IRD implementation by asking

questions about your enterprise setup, and produces a

worksheet that describes the issues on each of your sys-

tems that you must consider before you can implement

IRD. The z/OS IRD Planning Wizard supports z/OS V1.2

and higher.

64-bit Real Storage Support

z/OS provides 64-bit real storage support for the

z800/z900 servers. z/OS will continue to provide 31-bit real

and expanded storage support for G5/G6, and Multiprise

3000 servers. The 64-bit real support is designed to elimi-

nate expanded storage and help eliminate paging. The

64-bit real support may allow you to consolidate your cur-

rent systems into fewer LPARs or to a single native image.

These z/OS functions are enhanced to exploit 64-bit real

storage above 2 GB:

• Traditional Access Methods (BSAM, QSAM, and others)

• VSAM for extended format data sets

• Hierarchical File System (HFS)

• Extended Remote Copy (XRC)

These IBM products are enhanced to exploit 64-bit real

storage above 2 GB:

• DB2 Version 6 (with PTF), DB2 V7

• IMS Version 7

In addition, z/OS V1.2 and V1.3 deliver basic 64-bit virtual

storage management support. Assembler programs can

obtain virtual storage above 2 GB for storing and manipu-

lating data.

zSeries Bimodal Support for z/OS

IBM is announcing the z/OS Bimodal Migration

Accommodation Offering to assist customers in migrating

from OS/390 to z/OS. This addresses many customer

requests to have a “fallback” option to 31-bit mode when

fi rst migrating to z/OS in 64-bit mode on a z/Architecture

37

server. IBM has reconsidered the investment in 31-bit sup-

port on a zSeries server to encourage our customers to

move forward. This offering is available for 6 months for

each z/OS license (5694-A01) starting from the registration

of a z/OS license to a z/Architecture server. It only applies

to z/OS Version 1 Release 2, 3, and 4, and does not apply

to z/OS.e.

Managed System Infrastructure for Operations

Automation Support

z/OS Managed System Infrastructure for Operations (msys

for Operations) plays an important role in the area of

outage avoidance. msys for Operations addresses certain

self-healing, self-managing qualities of the IBM autonomic

computing on zSeries today. msys for Operations is an

automation infrastructure within z/OS delivering functionality

that targets system resources. It is based upon IBM well-

proven automation technology.

Functions control and manage both hardware and software

resources making fully automated solutions possible. The

focus is on simplifying complicated operator interaction,

detecting failure situations and reacting to them quickly

and precisely. This is achieved through panel driven oper-

ator dialogs and automated recovery routines that run in

the background.

z/OS Managed System Infrastructure for Setup:

Self-Confi guring Support

z/OS Managed System Infrastructure for Setup (msys for

setup) is the strategic solution for product installation, con-

fi guration and function enablement. msys for Setup allows

usage of consistent interfaces with wizard-like confi gura-

tion dialogs. In z/OS V1.4, the msys for Setup Framework

has been enhanced to provide multi-user capability. The

workplace has been improved with the provision of the

"Control Panel," which clarifi es which parts of the sysplex

or system are being updated, and has clearer dialogs and

a job progress indicator.

The dialogs use defaults and best practices values when-

ever possible and derive low-level values from answers

to high-level questions. After the confi guration parameters

have been specifi ed, msys for Setup can automatically

update the system confi guration directly. The user can see

in detail what the changes will be before they are made.

System-Managed CF Structure Duplexing

System-Managed Coupling Facility (CF) Structure

Duplexing is designed to signifi cantly enhance Parallel

Sysplex availability. It provides a robust failure recovery

capability via CF structure redundancy, and it enhances

Parallel Sysplex ease of use by reducing the complexity

of CF structure recovery. These benefi ts are achieved by

creating a duplicate (or duplexed) copy of a CF structure

and then maintaining the two structure instances in a syn-

chronized state during normal CF operation. In the event

of a CF related failure (or even a planned outage of a CF),

failover to the remaining copy of the duplexed structures

is initiated and quickly completed transparent to the CF

structure user and without manual intervention.

TCP/IP Networking Enhancements

z/OS can provide near continuous availability for TCP/IP

applications and their users with two key features in z/OS:

Sysplex Distributor and VIPA nondisruptive Takeover and

Takeback. This is a prime example of IBM innovation and

integration in software and hardware to bring value added

qualities — namely very high resiliency and availability —

to the z800/z900 and S/390 networking environment.

Virtual IP Address Nondisruptive Takeover

VIPA represents an IP address that is not tied to a specifi c

hardware adapter address. The benefi t is that if an adapter

fails, the IP protocol can fi nd an alternate path to the same

software, be it the TCP/IP services on z800/z900 or an

application.

38

VIPA Takeover introduced in OS/390 V2.8 supports move-

ment to a backup IP stack on a different server in a Parallel

Sysplex cluster in case of a failure of the primary IP stack.

VIPA Nondisruptive Takeover enhances the initial V2.8

functions, providing VIPA takeback support. This allows

the movement of workload back from the alternate to the

primary IP stack.

Sysplex Distributor

Introduced in OS/390 V2.10, Sysplex Distributor is a soft-

ware-only means of distributing IP workload across a

Parallel Sysplex cluster. Client connections appear to be

connected to a single IP address, yet the connections are

routed to servers on different z800/z900 or S/390 servers.

In addition to load balancing, Sysplex Distributor simplifi es

the task of moving applications within a Parallel Sysplex

environment.

e-business Security

z/OS Security Server is designed to address the demands

of e-business enterprises. In z/OS V1.3, full function PKI

(Public Key Infrastructure) support enables customers to

create and manage large numbers of Digital Certifi cates.

Many large e-business enterprises are in need of this large

scale, full life-cycle capability for Digital Certifi cates. UNIX

System Services provides greater security granularity for

HFS and zFS fi le systems with support for Access Control

Lists (ACLs).

z/OS provides industry-standard Lightweight Directory

Protocol (LDAP) Version 3 services supporting thousands

of concurrent clients.

Security Server (RACF®) in z/OS V1.4 supports Enterprise

Identity Mapping (EIM). EIM defi nes a user’s security con-

text that is consistent throughout an enterprise, regardless

of the User id used and regardless of which platform the

user is accessing. RACF commands are enhanced to allow

a security administrator to defi ne EIM information for EIM

applications to use. The EIM information consists of the

LDAP host name where the EIM domain resides, the EIM

domain name, and the bind distinguished name and pass-

word an application may use to establish a connection with

the domain.

System Services

z/OS Version 1 Release 4 base elements

Base Control Program (BCP)

JES24

ESCON Director Support

MICR/OCR Support2

Bulk Data Transfer base

DFSMSdfp™

EREP/MVS™ V3.5

High Level Assembler V1.4

ICKDSF R16

ISPF

TSO/E3

3270 PC File Transfer Program V1.11

FFST™/ESA

TIOC

z/OS Version 1 Release 4 optional priced features

DFSMSdss™

DFSMShsm™

DFSMSrmm™

JES34

Bulk Data Transfer (BDT) File to File1

BDT, SNA, NJE1. Disabled on z/OS.e2. Not licensed on z/OS.e3. TSO usage is limited to 8 concurrent users on z/OS.e4. z/OS.e only supports the latest JES that ships with the product

The backbone of the z/OS system is the Base Control

Program (BCP) with JES2 or JES3. These provide the

essential services that make z/OS the system of choice

when workloads must be processed reliably, securely, with

complete data integrity and without interruption.

The existence of a completely integrated set of system

services assures that a customer can focus on extracting

the maximum business value from the z/OS installation.

The system manages the workload, program libraries and

I/O devices. Complexities are minimized and problem

determination is facilitated with recovery and reporting

facilities.

39

Highlights

Workload Manager (WLM) addresses the need for managing

mixed workload distribution, load balancing and the distri-

bution of computing resources to competing workloads. It

does this while providing fewer, simpler system externals

and performance management goals expressed in Service

Level Agreement terms, automatic work and resource

management. All this is done with a single policy that can

be used across the sysplex to provide a single control point,

eliminating the need to manage each individual image.

Dynamic balancing of JES2 batch initiators across a sys-

plex has been enhanced in z/OS V1.4 to provide better uti-

lization of processor resources. WLM is designed to check

every 10 seconds to see if re-balancing is required. WLM

is more aggressive in reducing initiators on constrained

systems and starting new ones on less utilized systems

helping to ensure that processors are more evenly utilized.

WLM Improvements for WebSphere

Performance block reporting for enclaves and multi-period

classes are designed to provide improved workload bal-

ancing for middleware applications such as WebSphere.

WLM Enqueue Management establishes a new interface to

allow reporting of resource contention. The priority of the

task holding the enqueue can be increased to allow the

resource to be released more quickly.

Data Management

DFSMSdfp provides a comprehensive set of functions

to manage storage resources on the system. Data man-

agement functions support storage and retrieval of data

on disk, optical and tape devices. Program management

functions allow creation and retrieval of executable pro-

gram libraries. Device management functions provide the

means to defi ne and control the operation of input and

output storage devices. Distributed File Manager (DFM)

supports access to remote data and storage resources.

In z/OS V1.3, DFSMS focuses on improving a customer’s

business continuance by adding features that minimize

the occurrence of system outages and enhance a cus-

tomer’s disaster recovery capabilities. The new functions

also improve a customer’s business effi ciency by provid-

ing better system performance and throughput and by

providing usability enhancements that increase Storage

Administrator productivity.

Benefi ts

• Improved business continuity

– Coupled Extended Remote Copy to enhance XRC

disaster recovery for very large customers

– SMS data set separation on separate storage

controllers

– SMS overfl ow storage group for peak workload han-

dling

– VSAM RLS Supports System-Managed Coupling

Facility Structure Duplexing

• Improved Performance

– Large storage (64-bit) support for all VSAM record

organizations (extended and non-extended format

VSAM)

– DFSMShsm recall workload can be balanced across

multiple hosts by placing recall requests in a common

queue in the Coupling Facility

– DFSMSdss one-step HFS data set copy

For more detailed information on the new DFSMS enhance-

ments in z/OS V1.3, visit: storage.ibm.com/software/sms/

index.html.

Parallel Sysplex

zSeries Parallel Sysplex technology provides industry-

leading availability by allowing z/OS workloads to be bal-

anced across multiple servers to provide near continuous

availability. This form of clustering, known as single system

image, also provides tremendous scale. Up to 32 zSeries

servers with z/OS can appear as a single image (see page

9, Parallel Sysplex Clustering Technology).

40

Base Control Program

• The BCP has support for the IEEE fl oating point hard-

ware, which is standard on all servers supported by

z/OS

• DB2 can support customers with a requirement for more

than 10,000 DB2 dynamically-allocated table spaces

• Increased number of system symbols

• Batched group buffer pool writes in single CF operation

which is designed to help reduce overhead and improve

performance in update-intensive DB2 data sharing

• CFRM performance has been enhanced to help elimi-

nate I/O bottlenecks that impact CFRM CDS

• Multisystem cascaded transactions subordinate failure

notifi cation allows IMS to exploit RRS multi-sys cas-

caded transactions feature

JES2 and JES3

• In z/OS V1.2, JES2 and JES3 allow an installation to

have up to 999,999 jobs. In addition, both provide the

installation the ability to obtain (spinoff) their JESlog data

sets prior to job completion.

• The JES2 Health monitor, in z/OS V1.4, provides

improved diagnostics. Even when JES2 is not respond-

ing to commands, the JES2 monitor, running in a sepa-

rate address space, will be able to provide information

about JES2’s status. JES2 also provides enhanced

recovery from corrupted checkpoint data to prevent

multisystem outages

• In z/OS V1.4, JES3 provides additional tolerance for

initialization errors and the MAINPROC refresh function

which provides dynamic addition of systems to the sys-

plex

System Management Services

z/OS Version 1 Release 4 base elements

HCD

SMP/E V3

Managed System Infrastructure for Setup

Managed System Infrastructure for Operations

z/OS Version 1 Release 4 optional priced features

RMF™

SDSF

HCM

z/OS provides systems management functions and fea-

tures to manage not only host resources, but also distrib-

uted systems resources. These capabilities have a long,

successful history of usage by S/390 customers. z/OS has

enhanced many of these systems management functions

and features to provide more robust control and automa-

tion of the basic processes of z/OS.

Highlights

• msys for Setup can be used to defi ne the following

technologies

– Parallel Sysplex (z/OS R1, R2, R3, R4)

– Base Sysplex (R2)

– TCP/IP (R2)

– ISPF (R2)

– UNIX System Services (R3)

– Language Environment (R3)

• msys for Operations enhancements in z/OS V1.3 include

automation to handle ENQ resources contention and

auxiliary storage shortages. msys for Operations can

now interface with the Hardware Management Console

(HMC) to provide hardware functions such as deactivat-

ing LPARs.

• RMF can show the contention for Cryptographic Copro-

cessors, including a description of which workloads are

using or are delayed in access to the cryptographic

coprocessors

• Application State Recording, a new feature of z/OS V1.4

provides more granular performance reporting for mid-

dleware such as WebSphere

Benefi ts can include:

• Increased system availability

• Improved productivity of system programmers

• A more consistent approach for confi guring z/OS

components or products

• System set-up and automation using best practices

which can greatly improve availability

41

msys for Setup

msys for Setup is part of IBM ^ advanced self-

management technology and helps customers to enable

functions as quickly and easily as possible. The value of

msys for Setup is extended in z/OS V1.4 with the delivery

of further msys for Setup exploitation and major enhance-

ments to the framework. The msys for Setup framework

improvements include:

• Multiple User Support: With z/OS V1.4, multiple users can

be logged on and work concurrently from different worksta-

tions. Furthermore, as part of the user enrollment process,

the msys for Setup user administrator can control which

msys for Setup workplace functions a user can access.

• Improved User Interface: The graphical user interface

(msys for Setup workplace) has been redesigned and

is now easier to learn and use. These valuable ease of

use enhancements make working with msys for Setup

more intuitive.

In addition to these framework highlights, TCP/IP provides

additional confi guration capability through msys for Setup:

• The TCP/IP plug-in provides customization of the

TN3270 Server

• End-user defi nition of port reservation and port sharing

is now supported

msys for Operations

The objective of msys for Operations is to simplify day-to-

day operational tasks associated with a Parallel Sysplex

environment and z/OS. This is achieved by reducing oper-

ator complexity, creating greater operational awareness of

important indicators and improving system recoverability.

All of these factors are essential to z/OS availability and

in turn directly affect the performance and availability of

every business application.

It is important to note that msys for Operations is not a

product nor will it be displacing any product. It is designed

to remove the necessity for many customers to write their

own automation exploiting code to achieve control over

specifi c system events. Today many installations write and

maintain their own versions of this type of code. For the

less sophisticated customer, this can be virtually impos-

sible. By supplying msys for Operations, each installation

can decide to enable and make use of the new capabilities

or leave them disabled, continuing to use existing automa-

tion routines.

Whether interest is in the panel driven operator dialogs

that assist in the control of couple data sets, coupling

facilities and managing Coupling Facility structures OR in

the background recovery routines that guard against con-

sole buffer shortages, long running enqueues or auxiliary

storage shortages, z/OS customers should fi nd something

that can help benefi t operations in their organizations and

help lead to improved availability.

SMP/E

SMP/E provides the ability to install software products and

service either from DASD or tape, or directly from a net-

work source, such as the Internet. By installing directly

from a network source, SMP/E is enabling a more seamless

integration of electronic software delivery and installation.

System Automation

The unique and rich functions of System Automation for

OS/390 (SA OS/390) Version 2.2 (separately orderable)

can ease z/OS, z/OS.e and OS/390 management, reduce

costs, and increase application availability. SA OS/390

automates I/O, processor, and system operations, and

includes “canned” automation for IMS, CICS, Tivoli OPC,

and DB2. Its focus is on Parallel Sysplex automation,

including multi- and single-system confi gurations, and on

integration with end-to-end Tivoli enterprise solutions. With

the new patented manager/agent design, it is now pos-

sible to automate applications distributed over a sysplex

by virtually removing system boundaries for automation.

42

Security Services

z/OS Version 1 Release 4 base elements

Cryptographic Services (Integrated Cryptographic Service Facil-ity, Open Cryptographic Services Facility, System SSL, and Data Confi dentiality Services)

z/OS Version 1 Release 4 optional priced features

Security Server includes:

- RACF

- Network Authentication Service (Kerberos services)1

- LDAP Server1

- Firewall Technologies2

- DCE Security Server

- Open Cryptographic Enhanced Plug-ins1

- Public Key Infrastructure Services1

z/OS Version 1 Release 4 optional no-charge features

Network Authentication Service Level 3

System SSL Security Level 3

Open Cryptographic Services Facility Security Level 3

1. These components are now a licensed part of the z/OS base and can be used without purchasing/enabling Security Server2. Firewall technologies (IKE and GUI only) are now part of the z/OS base

The optional Security Server for z/OS combines the tradi-

tional benefi ts of RACF with an integrated set of security

functions essential to e-business applications. It forms the

basis for all security services from traditional applications,

UNIX applications, and distributed systems. Access to

resources can be selectively controlled, audited, and man-

aged with appropriate centralized or decentralized control

as required by each installation.

Highlights

• Full function PKI support

• New cryptographic algorithms and standards

• More granular access control for UNIX fi le systems (zFS

and HFS)

• Integrated package of security and directory functions,

with advanced security capabilities

• Tivoli administration interface

Benefi ts can include:

• Extensive security controls over emerging e-business

opportunities

• Flexible control of access to protected resources, includ-

ing installation-defi ned items

• Choice of centralized or decentralized control of security

profi les

• Choice of platform for DCE security server, with RACF for

access control, and remote administration

• Support for the Kerberos V5 network authentication

protocol

• Support for z800/z900 cryptographic features

RACF

• Digital Certifi cates can be automatically authenticated

without administrator action.

• Administrative enhancements enable defi nition of pro-

fi les granting partial authority. Handling of new pass-

words and removal of class authority are simplifi ed.

• Customers designing e-business applications need a

way to associate more users under a RACF Group defi -

nition, so RACF allows you to create a new kind of Group

that can contain an unlimited number of users.

SSL

• Ability for applications to create multiple SSL environ-

ments within a single process. An application can now

modify environment attributes without terminating any

SSL sessions already underway.

• IPv6 Support: This support allows System SSL to be

used in an IPv6 network confi guration. It also enables

System SSL to support both IPv4 and IPv6 Internet pro-

tocol addresses.

• Performance is improved with CRL Caching: Today, SSL

supports certifi cate revocation lists (CRLs) stored in an

LDAP server. Each time a certifi cate needs to be vali-

dated, a request is made to the LDAP server to get

the list of CRLs. CRL Caching enables applications to

request that the retrieved list of CRLs be cached for a

defi ned length of time.

43

• Support for the AES Symmetric Cipher for SSL V3 and

TLS Connections: System SSL supports the Advanced

Encryption Standard (AES), which provides data encryp-

tion using 128-bit or 256-bit keys for SSL V3.0 and TLS

V1.0 connections.

• Support for DSS (Digital Signature Standard) Certifi -

cates: System SSL has been enhanced to support

Digital Signature Standard certifi cates defi ned by the

FIPS (Federal Information Processing Standard) 186-1

Standard.

• Enhanced Environment Close: System SSL now permits

existing connections to remain active and run to comple-

tion after their SSL environment has been closed. This

removes the requirement that the customer application

must manage the SSL environment until all SSL connec-

tions have been closed.

• Enhanced PKCS#12 Support: We have upgraded

System SSL support of PKCS#12 fi les to new RFC levels.

This upgrade enhances the ability of System SSL to

interoperate with other certifi cate management products.

• Sysplex Session ID Caching: The sysplex session

cache support makes SSL V3.0 and TLS (Transport

Layer Security) V1.0 server session information available

across the sysplex. An SSL session established with a

server on one system in the sysplex can be resumed

using a server on another system in the sysplex. This

can be performed as long as the SSL client presents

the session identifi er obtained for the fi rst session when

initiating the second session.

• Externalization of CMS APIs: Allows you to write certifi -

cate management application to interact with System

SSL. Also allows System SSL applications to be written

to communicate with other applications using the

PKCS#7 standard.

• Serviceability: System SSL is being enhanced to provide

additional debugging support.

• User ID Support of RACF Key Rings: This support allows

SSL applications that are using a RACF (SAF) key ring

to no longer be required to be the owner of the SAF

key ring. This helps to simplify the administration of key

rings.

• System SSL of RSA Private Keys Stored in ICSF: With

z/OS V1R4, support is introduced that is designed to

allow a certifi cate’s private key to reside in ICSF thus

lifting a restriction where the private key had to reside in

the RACF database.

• Fail-over LDAP provides greater availability: You can

now specify a list of Security Server-LDAP servers to be

used for storing certifi cate revocation lists (CRLs). When

certifi cate validation is being performed, this list will be

used to determine which LDAP server to connect to for

the CRL information.

LDAP

• Client access to information in multiple directories is

supported with the LDAP protocol.

• LDAP Server now at V3 level. Bulk load utility for populat-

ing the LDAP Directory.

• The LDAP server supports thousands of concurrent cli-

ents, increasing the maximum number of concurrently

connected clients by an order of magnitude.

• Mandatory Authentication Methods (required by IETF

RFC 2829) supported in z/OS V1.4: The CRAM-MD5 and

DIGEST-MD5 authentication methods have been added.

The methods avoid fl owing the user’s password over

the connection to the server. The LDAP Server, the

C/C++ APIs, and the utilities are updated with this sup-

port. Interoperability is improved for any applications

that make use of these methods.

• TLS: z/OS LDAP now provides support for TLS (Trans-

port Layer Security) as defi ned in IETF RFC 2830 as an

alternative to SSL support. It also provides support, via

an LDAP extended operation, that allows applications to

selectively activate TLS for certain LDAP operations at

the application’s discretion.

44

• Server Activity Log: By enhancing the logging done by

the LDAP Server to provide information about the LDAP

operations being requested and the requestor, LDAP

provides greater fl exibility in what is logged. In addition,

this capability enhances reliability, availability, and ser-

viceability of the LDAP Server. It also provides compat-

ibility with some Netscape-provided logging.

• Modify DN: Today the LDAP Server is designed to only

support modifi cation of the most signifi cant portion of a

DN (Distinguished Name). z/OS V1R4 has expanded this

support to allow any portion of the DN to be changed.

This essentially means that relocation of an entry, and

possibly a subtree, to a different location in the DIT

(directory information tree) is possible. The availability of

this support further completes the LDAP Version 3 sup-

port defi ned in RFC 2251, and allows easier manage-

ment of directory content by allowing movement within

the DIT.

• ACL Updates: Access control has been improved

with the addition of “deny” support and “attribute

level access control.” These enhancements allow fi ner-

grained access control defi nitions to be established,

allowing for greater interoperability with other IBM-pro-

vided LDAP directory products, and the fl exibility of the

access control model is increased.

• Entry UUID: This support adds a UUID to each entry,

allowing unique identifi cation of the entry in the DIT

throughout its lifetime. Even if an entry’s Distinguished

Name changes, its UUID will not. This identifi er can

be used by applications and middleware that need to

ensure they are working with the same entry over time.

ICSF

Also featured as part of Security Management is the

Integrated Cryptographic Service Facility, which provides

cryptographic functions for data security, data integrity,

personal identifi cation, digital signatures, and the manage-

ment of cryptographic keys. These functions are provided

through the combination of secure cryptographic hard-

ware, the ICSF cryptographic API, and the ICSF adminis-

tration interface.

z/OS supports the PCI Cryptographic Coprocessor feature

for the S/390 Parallel Enterprise Server™ G5/G6 and

z800/z900 servers. These pluggable cryptographic copro-

cessor cards are designed to provide additional cryp-

tographic capabilities, and more fl exible and scalable

cryptographic function. ICSF is able to route cryptographic

requests to either the CMOS Cryptographic Coprocessor

or to a PCI Cryptographic Coprocessor based on workload

and capability of the coprocessors. These coprocessors

therefore help increase e-business capacity, as well as

provide an opportunity for more rapid implementation of

new cryptographic algorithms.

z/OS enhances SSL performance through support of the

z800/z900 IBM PCI Cryptographic Accelerator (PCICA),

a fast cryptographic processor designed to provide lead-

ing edge performance of the complex RSA cryptographic

operations used in the Secure Sockets Layer (SSL) pro-

tocol. This will benefi t functions that use System SSL,

such as the z/OS HTTP Server (and WebSphere), TN3270

server, LDAP server and CICS Transaction Gateway server.

PKI Services

PKI Services is a z/OS component that provides a com-

plete Certifi cate Authority (CA) package for full certifi cate

life cycle management.

• Component of the z/OS Security Server (RACF)

• User request driven via customizable Web pages for

browser or server certifi cates

• Automatic or administrator approval process adminis-

tered via same Web interface

• End user / administrator revocation process

• Certifi cate validation service for z/OS applications

• With z/OS V1.4 multiple instances can share database

via VSAM record -level sharing within a Parallel Sysplex

cluster.

45

Firewall

• Enhanced Security Server-Firewall Technologies provide

sysplex-wide Security Association Support: This function

is designed to enable VPN (virtual private network) secu-

rity associations to be dynamically reestablished on a

backup processor in a sysplex when a Dynamic Virtual

IP Address (DVIPA) takeover occurs. When the Dynamic

Virtual IP Address give-back occurs, the security asso-

ciation is designed to be reestablished on the original

processor in the sysplex. When used in conjunction with

z/OS Communications Server’s TCP/IP DVIPA takeover/

give-back capability, this function provides customers

with improved availability of IPSec security associations.

Network Authentication Service

• A component of Security Server, Network Authentication

Service, provides authentication, delegation and data

confi dentiality services which are interoperable with

other industry implementations based on the MIT Kerbe-

ros V5 reference implementation. Network Authentication

Service, administered with RACF commands, supports

both the native Kerberos API functions as well as the

GSS-API Kerberos security mechanism and does not

require DCE.

• IPv6 supported by Kerberos with z/OS V1.4 for improved

network security scalability.

• Kerberos in z/OS V1.4 provides an alternative database

to RACF by offering support for its own registry database

using the UNIX System Services NDBM (New Database

Manager) support. NDBM provides full Kerberos admin-

istration support.

Application Enablement Services

z/OS Version 1 Release 4 base elements

Language Environment3

C/C++ IBM Open Class Library

DCE Application Support1

Encina® Toolkit Executive2

z/OS Version 1 Release 4 optional priced features

C/C++ with Debug Tool

C/C++ without Debug Tool

DFSORT™

GDDM®-PGF V2.1.31

GDDM-REXX V3.21

HLASM Toolkit V1.4

1. Disabled on z/OS.e2. Not licensed on z/OS.e3. z/OS.e only supports the latest Language Environment that ships with this product. See LE limitations for z/OS.e

z/OS provides a solid infrastructure on which you can build

new applications, extend existing applications, and run

existing OLTP and batch processes.

Highlights

The IBM ^ brand is about uncompromising fl ex-

ibility in selecting, building and deploying the applications

your business needs. Toward that end, IBM offers the

industry’s broadest range of platforms and operating

systems. IBM is committed to industry-standard, cross-

platform technologies — such as Java, XML, HTML, SOAP

and UDDI — that are at the heart of a fl exible e-business

infrastructure. Support for these standards in our key mid-

dleware — including DB2 Universal Database, WebSphere

Application Server and MQSeries — means you won’t be

locked in to a single platform as your business grows. As a

result, you always have the fl exibility to deploy applications

in a cost-effective way.

46

C/C++

• z/OS V1.2 and V1.3 provide two levels of the C/C++

compiler as a migration aid. One is identical to the

compiler provided with OS/390 V2.10. The other is fully

compliant with the ISO C++ standard, also known as

the ANSI C++ standard. This includes support for ISO

Standard C++ Libraries, and other language features of

ISO C++ 1998. New application development involving

C++ classes should make use of the C++ Standard

Class Library, instead of the C/C++ IBM Open Class

Library.

• Enhanced ASCII support provides the ability to produce

code that contains ASCII string literals and character

constants. This allows ASCII dependent logic to con-

tinue working on ASCII platforms, thus eliminating the

need to fi nd all such places in the code and converting

them to EBCDIC when porting UNIX applications to

z/OS.

• The C/C++ Compiler includes support for IEEE Floating

Point, and 64-bit long integer format. Support is also

added to the C/C++ Runtime Library.

• Extra Performance Linkage (XPLINK)

When you run a C or C++ application, there is overhead

associated with each function call. The more highly func-

tionalized a program, the more overhead. XPLINK cuts

down on the overhead associated with these function calls

and improves the performance of these applications. In

order to exploit the bulk of “high-performance linkage”

customers must recompile their C and C++ programs

under the new XPLINK environment. The new IBM SDK for

z/OS Java 2 Technology Edition V1.4 has been rewritten to

take advantage of this unique z/OS function.

Java

SDK for z/OS, Java 2 Technology Edition, V1.4 provides a

full-function Software Development Kit (SDK) at the Java 2

technology level, compliant with the Sun SDK 1.4 APIs.

With SDK for z/OS, Java 2 Technology Edition, V1.4, you

can:

• Test and deploy Java applications at the Java 2 SDK 1.4

API level

• Continue the “write once, run anywhere” Java paradigm

at the Java 2 API level

• Take advantage of the new Java 2 function, including

XML

• Continue to take advantage of:

– Security APIs introduced in the SDK 1.3 product

– Java Record Input/Output (JRIO) APIs

– Persistent reusable technology

• Leverage traditional zSeries benefi ts: scalability, reliabil-

ity, availability, and serviceability

The program will be available via download from the

IBM ^ zSeries Java Web site and by tape from

IBM Software Delivery and Fulfi llment (SDF).

Note: SDK for z/OS Java 2 Technology Edition V1R4

requires z/OS V1.4 or later

For additional information about zSeries Java products, go

to: ibm.com/servers/eserver/zseries/software/java/

47

Unicode

z/OS provide Unicode Callable System Services - code

page and case conversions from EBCDIC to Unicode:

• DB2 V7 is the fi rst exploiter

• New hardware instruction on zSeries processor has

been implemented to provide superior performance

• Unicode Normalization Services allows programmers to

decompose or compose characters from another code

page and can apply normalization forms to have the

same meaning

REXX Functions

z/OS V1.4 extends the REXX language on z/OS when used

in a UNIX System Services MVS REXX environment. It

includes functions for standard REXX I/O. A number of

I/O stream commands are provided to help control stream

processing. Additional functions are also included to easily

access some common fi le services and environments vari-

ables. Also included with this package is the ability to

interrupt a running REXX program and enter an immediate

REXX command such as TS to start interactive tracing.

Provides:

• Greater interoperability of z/OS as compared to other

platforms

• Enhancements for porting REXX CGIs and other programs

Network Communication Services

z/OS Version 1 Release 4 base elements

z/OS Communication Server (Multiprotocol/HPR Services, TCP/IP Services, SNA/APPN Services)OSA Support Facility

z/OS Version 1 Release 4 optional no-charge features

z/OS CommunicationsServer Security Level 3

z/OS Communication Server Network Print Facility1

1. Not orderable on z/OS.e

The z/OS base includes z/OS Communication Server,

which enables: world class TCP/IP and SNA networking

support, including enterprise class dependability; perfor-

mance and scalability; highly secure connectivity; support

for multiple protocols; and effi cient use of networking

assets.

Highlights

• IPv6 support provides increased scalability and simplifi ed

confi guration.

• HiperSockets, introduced in z/OS V1.2, provides very

high-speed, low latency TCP/IP data communications

across LPARs resident within the same z800/z900 server.

HiperSockets acts like a TCP/IP network within the server.

• HiperSockets Accelerator provides an “accelerated

routing path” which concentrates traffi c between

OSA-Express external network connections and

HiperSockets connected LPARs. This function can

improve performance, simplify confi guration, and increase

scalability while lowering cost by reducing the number

of networking adapters and associated I/O cage slots

required for large numbers of virtual servers.

48

• The Sysplex Distributor has been extended to control

workload balancing, working in conjunction with Cisco

MultiNode Load Balancing (MNLB).

• Host-based Intrusion Detection Services (IDS) comple-

ments network-based IDS sensors and scanners by

providing defense mechanisms that discard attacking

packets before they cause damage, discard packets

exceeding established thresholds, and limit the number

of connections from “greedy” users.

• OSA-Express Queued Direct Input/Output support (now

includes IP Broadcast support, used by DHCP, for IPv4)

• LPAR-to-LPAR communication sharing a single

OSA-Express Ethernet or Token-Ring port

• Integration of SNA/APPN, TCP/IP and AnyNet®

• A single high-performance TCP/IP stack providing support

for both IPv4 and IPv6 applications

• High Performance Native Sockets (HPNS) for TCP/IP

applications

• Support for the latest security protocols - SSL & TLS

• Multinode Persistent Sessions for SNA applications

running in a Parallel Sysplex environment

• Simple Network Time Protocol Support (SNTP) for

client/server synchronization

• SNA 3270, Sockets, and APPC application support

• Native ATM support for high-speed networking

• Easy access to host applications from Java technology-

enabled Web browser

• Greater performance and mobility for CICS Sockets

Benefi ts can include:

• Simplifi ed deployment of client/server applications

• Function for new e-business Internet and intranet applica-

tions

• Multivendor, multiplatform connectivity

• High performance, high availability, network choice

• SNA class of service over IP networks

• World class TCP/IP services

• Dramatic improvements in TCP/IP performance include

optimization of the TCP/IP stack, and inclusion of a

number of performance related capabilities such as:

– UNIX Sendmail is supported including the POP3

server.

– TN3270 sessions use Secure Sockets Layer, with

increased number of supported ports (255).

– Multi-Node Persistent Sessions (MNPS) includes

recovery for Dependent LU Requester (DLUR)-owned

LUs. This leads to full Parallel Sysplex exploitation with

native IP networks, including nondisruptive session-

switching.

– Client/Server Affi nity improvements to allow recovery

over sync points in multiphase commit giving higher

availability for these applications.

– Simple Network Management Protocol (SNMP)

Distributed Protocol Interface (DPI) instance level

registration.

– X-Motif uses Data Link Libraries (DLL) to reduce disk

space.

– Virtual Private Network (VPN) easier to establish.

Further improvement have been made to TCP/IP sysplex

support to increase usability, availability and performance.

Sysplex Sockets, XCF Dynamics, and System Symbolics

continue to improve performance, provide nondisruptive

growth and reduce defi nition effort. Dynamic Fast

Response Web caching within the TCP/IP service stack

will provide up to two times improvement in performance.

Service Policy Agent offers Priority Networking for TCP/IP,

Internet Security with enhanced, further improved Firewall

technologies and inclusion of the latest security standards

such as IPSec and SNMPv3. Enhanced addressing for

TN3270 Server reduces consumption of resources and

increase capacity.

49

Benefi ts can include:

• Enhanced Multipath Load Balancing.

• Support for dynamic updates to Service Policy.

• Higher availability in Parallel Sysplex environments with

Virtual Addressing Takeover (VIPA).

• Support of Internet Key Exchange (IKE) protocol to

automatically create and distribute encryption keys for

dynamic IP clients.

• Addition of Secure Sockets Layer (SLL) and Transport

Layer Services (TLS) authentication to the TN3270e

server to protect against unauthorized access to SNA

applications from TCP/IP clients.

• Support of Triple DES session encryption for SNA

applications.

• Service Policy Agent for IBM Communications Server

Enhancements.

• Simplifi ed confi guration and diagnostic for Enterprise

Extender (EE).

UNIX System Services

z/OS Version 1 Release 4 base elements

z/OS UNIX System Services

z/OS contains the UNIX application services (shell, utilities

and debugger) and the UNIX System Services (kernel and

runtime environment). The shell and utilities provide

the standard command interface familiar to interactive

UNIX users. z/OS includes all of the commands and

utilities specifi ed in the X/Open Company’s Single UNIX

Specifi cation, also known as UNIX 95 or XPG4.2.

The z/OS UNIX Services Debugger provides a set of com-

mands that allow a C language program to be debugged

interactively. The command set is familiar to many UNIX

users. With Language Environment, z/OS supports indus-

try standards for C programming, shell and utilities, client/

server applications, and the majority of the standards for

thread management and the X/Open Single UNIX Speci-

fi cation. The combination of open computing and z/OS

allows the transparent exchange of data, easy portability

of applications, cross-network management of data and

applications, and the exploitation of traditional MVS system

strengths in an open environment.

Highlights

• X/Open UNIX 95 Branded

• Permanent z/OS UNIX Kernel (restart capability provided

in z/OS V1.3)

• Integrated/converged z/OS UNIX Sockets

• Web application and UNIX C program performance

improvements

• Improved z/OS UNIX setup

• Web threading improvements

• Flexibility improvements — HFS fi les can be program

controlled or APF authorized

• Addition of new UNIX commands

• Multiprocess/Multiuser Kernel Support

Benefi ts can include:

• Development and execution of UNIX applications —

z/OS is a UNIX platform

• Portability of applications to and from other platforms

• Use of UNIX development skills in a z/OS environment

• Consolidate multiple UNIX systems

• Scalability for high growth UNIX applications

50

UNIX

• Performance enhancements include recompiled and opti-

mized functions within the kernel, and shell and utilities;

addition of Socket Functions; use of Communication

Storage Management buffer transfer instead of data

movement; and optimized NFS Logical File System.

• Multiprocess/MultiUser allows faster process creation for

customers and reduced storage usage for servers.

• Semaphores without contention using the hardware

Perform Locked Operation (PLO) instruction.

• Shared memory (captured storage) reduces real storage

when sharing large amounts of virtual storage.

• UNIX System Services and UNIX debugger add support

for IEEE-fl oating point.

UNIX Parallel Environment

• Enhanced to support MPI 1.2 specifi cation for C/C++

applications

• Support for Intelligent Miner data with the use of WLM

facilities

USS

• Make porting from other platforms easier with support of

the Magic Number (#!), double-square-bracket conditional

testing, and other functions.

• Parallel Sysplex support to share UNIX fi le systems ben-

efi ts with Web server applications and others who access

the hierarchical fi le system. This support can make your

data and information that reside in the HFS available to

your customers at any time, no matter where the applica-

tions are running in the Parallel Sysplex environment.

• Shared HFS availability has been improved in z/OS V1.4.

If a system goes down, dead system recovery moves fi le

systems that have been defi ned as AUTOMOVE=YES to

another system in the sysplex. z/OS provides a method

for customers to indicate where fi le systems should be

moved. The availability of this function will improve perfor-

mance and workload balancing.

Distributed Computing Services

z/OS Version 1 Release 4 base elements

Network File System (NFS)

DCE Base Services

Distributed File Service (including zSeries File System (zFS) and SMB)

• Network File System (NFS) acts as a fi le server to worksta-

tions, personal computers, or other authorized systems

in a TCP/IP network. It also provides a z/OS client. The

remote data sets or fi les are mounted from the mainframe

(z/OS) to appear as local directories and fi les on the client

system. NFS also provides access to the Hierarchical File

System (HFS).

• DCE enables data encryption using the data encryption

standard (DES) algorithm and the commercial data mask-

ing facility (CDMF).

Highlights

• Remote Procedure Call (RPC) lets calls between programs

running on different platforms appear as local procedure

calls.

• Directory Services allows resources to be found anywhere

in an enterprise without the need to know local names.

• Security Services helps solve security problems common

in a distributed environment by handling identifi cation and

certifi cation of users, clients, servers and systems.

• Distributed Time Services synchronizes clocks running

on different nodes.

• Security based on Kerberos authentication with access

to RACF data as well.

Benefi ts can include:

• Transparency of data and logic

• Distributed, consistent directory service

• Security for both clients and servers, including

encryption if required

• Scalability of distributed applications

• Interoperability and portability

51

zSeries File System (zFS)

zFS is a UNIX fi le system that can be accessed with the

z/OS hierarchical fi le system fi le Application Programming

Interfaces (APIs). It provides signifi cant performance gains

in most customer environments requiring fi les 8K in size or

greater. zFS introduces a new construct called an aggre-

gate which allows space sharing between fi le systems.

HFS does not support space sharing between fi le systems.

zFS also provides a facility to take an almost instantaneous

read-only copy of a fi le system. zFS has two modes of

operation:

• Compatibility mode aggregate: An aggregate defi ned to

only contain a single zFS fi le system. The VSAM Linear

Data Set is used for the name of the zFS fi le system.

The result is an HFS compatibility mode aggregate or fi le

system where the VSAM Linear Data Set cluster name =

the zFS Aggregate name = the zFS File System name.

• Multifi le system aggregate: An aggregate defi ned to con-

tain one or more zFS fi le systems. The extended function

in zFS allows multiple zFS fi le systems to be defi ned in

the same zFS aggregate for space sharing purposes. The

zFS aggregate is a VSAM linear data set and the zFS

aggregate name is the same as the VSAM linear data set

cluster name. Note: It is recommended that compatibility

mode aggregates be used for the initial deployment of

zFS.

zFS or zFS-related administration, system management,

performance, confi guration support, and scalability have

been further enhanced in z/OS V1.4:

• Dynamic reconfi guration for fi le system confi guration

options.

• Dynamic use of secondary allocation for a zFS aggregate

(data set) or fi le system.

• Use of fi le systems in different zFS aggregates with the

same name. This allows administrators to restore aggre-

gate data to a new aggregate and simultaneously mount a

fi le system from the new and original aggregate to recover

fi le system data.

• Use of static system symbol substitutions providing sys-

tem-specifi c information to be specifi ed and enables the

confi guration to be shared between systems in a sysplex.

• Improvements in the UNIX System Services automount

support for zFS.

• Addition of ISHELL support for zFS.

• zFS aggregate awareness in UNIX System Services. This

allows the automove of zFS fi le systems in the same zFS

aggregate (data set) to the same system in a sysplex

when the owning system goes down.

• Ability to perform I/O operations in parallel for a zFS

aggregate that spans multiple DASD volumes. This is

designed to provide improved performance when using

multi-DASD volume aggregates.

• Support for 64-bit user virtual buffer addresses.

Distributed File Services (DFS) SMB

Microsoft® Windows® networking compatible fi le and print

serving is available with Native SMB File and Print Serving

for Windows Clients. SMB fi le serving enables z/OS to

share HFS, zFS, Sequential fi les and Record Files Systems

(RFS) such as PDS, PDS/E or VSAM data sets with Windows

workstations. SMB can automatically handle the conver-

sion between ASCII and EBCDIC making full use of

USS fi le tagging Access Control Lists (ACLs) support.

This allows development of applications on Windows for

deployment on z/OS. z/OS also supports printing of SMB

fi les without requiring that code be installed on the clients

and without requiring unique printer setup on the worksta-

tions. OS/2® client fi le serving support is also available.

SMB Support has been further enhanced in z/OS V1.4 by:

• Simplifi ed user administration with Windows Domain ID

mapping

• Performance improvements with RFS and large PDS or

PDS/E fi le systems

• Exploitation of zFS performance

52

e-business Services

z/OS Version 1 Release 4 base elements

IBM HTTP Server

Text Search

z/OS Version 1 Release 4 optional no-charge features

IBM HTTP Server North America Secure

Businesses increasingly use the Internet to market prod-

ucts and conduct business with suppliers and customers.

WebSphere Application Server for OS/390 (separately

orderable) enables the use of z/OS as a Web server with

the benefi ts of security, the utilization of large storage

capacity, centralized skills, a single point of entry and

control, consolidation of multiple Web sites, and secure

Internet transactions.

Text Search is a powerful, full-text indexing and search

server that supports high-speed searching of Web sites

and other documents stored on the z/OS server. Free text

searching is supported, as well as Boolean logic. Text

Search returns a ranked list of hits. A full API set is pro-

vided so that Text Search functions can be used in other

programs and products. It can also be used for Web-

usage mining.

The IBM HTTP Server offers HTTP 1.1 compliance, support

for Java technology, and the ability to manage Internet

processing through the Workload Manager (WLM). In addi-

tion, it provides:

• Automatic browser detection to respond to requests with

the version of a Web page or document appropriate for

that browser

• Dramatic improvements in single and multiple processor

environments coupled with signifi cant CPU requirement

reductions provide higher throughput and shorter

response time

• Platform for Internet Content Selection (PICS) provides

a way for users to fi lter material they encounter on the

Internet and accept or reject the material based on its

rating

• Web usage statistics

Benefi ts can include:

• e-business with security

• Utilization of large storage capacity

• Single point of entry and control

• Consolidation of multiple Web sites

• Secure Internet transactions

• Exploitation of z/OS WLM

Print Services

z/OS Version 1 Release 4 optional priced features

Infoprint® Server

– IP PrintWay™

– NetSpool™

– z/OS Print Interface

Today, businesses are looking for better ways to get infor-

mation to workers throughout the enterprise, and to suppli-

ers, partners and customers around the globe. Application

output that was once printed on centralized data center

printers and mailed must now be electronically distributed

and printed, or presented over the Web. Infoprint Server

provides a reliable, high availability, secure and scalable

foundation for your e-business output infrastructure. Info-

print Server and its companion product, Infoprint Server

Transforms, include a print interface, printer inventory,

VTAM® application output capture program, and print driv-

ers and management tools that let you manage any print

job to any printer defi ned to Infoprint Server.

53

These capabilities give you the fl exibility to deliver the

output of e-business anywhere you need it:

• Legacy CICS and IMS applications that generate SNA

Character String (SCS) or 3270 output formats can print

to LAN-attached PCL printers, without changes to the

application program.

• Support for the output of e-business includes the ability to

send output as e-mail instead of, or in addition to print.

• A consolidated printer inventory lets you defi ne all printers

used with Infoprint Server, and printers driven by Print

Services Facility (PSF) in one place. Printers can be

defi ned and modifi ed from a single easy-to-use interface.

• IP PrintWay provides support for printers attached to the

network using TCP/IP, VTAM-controlled coax printers, and

for printers and servers over the Internet using the industry-

standard Internet Printing Protocol (IPP). Easy to use ISPF

menus also enable management of distributed printers.

• The Print Interface supports print submission from appli-

cations running in UNIX System Services (USS), from

Windows users via native Windows SMB, from applica-

tions on other servers, and over the Internet using IPP.

• Data stream transforms let you print AFP™ applications on

printers using PCL, PostScript or PDF. You can also print

PCL, PostScript and PDF output on AFP printers.

• A transform from SAP to AFP and a certifi ed SAP Output

Management System lets you print SAP application output

on your fast, reliable AFP printers, and receive print com-

pletion notifi cation back at the SAP Application Server.

Benefi ts of consolidating your enterprise printing onto z/OS

using Infoprint Server can include:

• Reduced total cost of ownership for distributed print oper-

ations

• Improved productivity with simplifi ed print operations and

management

• Investment protection and leverage for your AFP applica-

tions and printers

• Faster deployment of e-business initiatives with fl exible

output delivery options

Softcopy Publications Support

z/OS Version 1 Release 4 base elements

BookManager® READ V31

BookManager Bookserver

GDDM (including PLCK and OS/2 Link and REXX code)1 V3.2

z/OS Version 1 Release 4 optional priced features

BookManager Build1

1. Disabled on z/OS.e

Test

To further reduce migration time, the z/OS and z/OS.e

products are system integration-tested using a produc-

tion-like environment. The z/OS environment includes sub-

systems, such as CICS, IMS, DB2 and WebSphere. This

additional testing supplements existing functional tests,

with a focus on tasks performed by customers in the

production environment, thus helping establishments move

more quickly to new functions.

54

Publications

For a list of the publications available for z/OS

and z/OS.e, visit the z/OS library Web site at:

ibm.com/servers/eserver/zseries/zos/bkserv.

Installation Considerations

z/OS V1.4 provides a strong foundation for exploitation of

further zSeries architecture enhancements. Customers are

encouraged to migrate to this release so that they are well

positioned to take full advantage of what zSeries has to

offer. Customers are able to upgrade from OS/390 2.10

or any previous release of z/OS and are able to order

z/OS via Customized Offerings (ServerPac, SystemPac®

and CBPDO) for a complete system.

Note: z/OS.e can be ordered by ServerPac and SystemPac

only.

For more information about SystemPac, visit: ibm.com/

ca/custompac

Customers are strongly encouraged to implement WLM

goal mode before installing z/OS V1.4 rather than concur-

rent with their V1.4 installation. Goal mode is required for

z/OS V1.3 and later.

z/OS V1.4 and V1.5 will be Supported on the Following IBM

Servers:

• S/390 Parallel Enterprise Server G5/G6 (or compatible

server) (31-bit mode)

• Multiprise 3000 Enterprise Server (or compatible server)

(31-bit mode)

• IBM ^ zSeries 800 and 900 servers (or compatible

servers) (64-bit mode*)

(* For migration purposes, 31-bit mode for z/OS 1.2, z/OS

1.3 and z/OS 1.4 is supported for up to six months with the

z/OS Bimodal Migration Accommodation offering.)

Migration/Coexistence

IBM has converged on a consistent migration and coexis-

tence policy. This consistent migration and coexistence

policy is based on the current coexistence policy. Migra-

tion forward as well as backward should be made within

the same releases supported by the coexistence policy.

Four releases is the general migration and coexistence

policy that should be assumed, except where special pro-

visions have been provided.

This consistent coexistence, migration and fallback policy

applies to release migrations for:

• Single system confi gurations

• Individual systems within a multisystem confi guration

• Cases where a simultaneous IPL is used to migrate all

systems in a multisystem confi guration at the same time.

For additional information on coexistence and release

migration information, refer to z/OS Planning for Installation

(GA22-7504) at: ibm.com/servers/eserver/zseries/zos/

bkserv/fi nd_books.html.

The following table describes the migration/coexistence

supported releases. The release shown in column 1 is the

highest release running in a multisystem confi guration.

Migration/Coexistence Supported Releases (OS/390 & z/OS)

Release Migration/Coexistence Release

R10 R10, R9, R8

z/OS R1 {z/OS R1 OS/390 R10} (1), R9, R8

z/OS R2 z/OS R2, {z/OS R1, OS/390 R10} (1), R9, R8

z/OS R3 z/OS R3, z/OS R2, {z/OS R1, OS/390 R10} (1), R9

z/OS.e R3 {z/OS.e R3, z/OS R3}, z/OS R2, {z/OS R1, OS/390 R10}, OS/390 R9

z/OS R4 z/OS R4, z/OS R3, z/OS R2, {z/OS R1, OS/390 R10} (1)

z/OS.e R4 {z/OS.e R4, z/OS R4}, {z/OS.e R3, z/OS R3}, z/OS R2, {z/OS R1 and OS/390 R10}

1. OS/390 R10 and z/OS R1 treated as one coexistence level

55

This information is being provided to you to facilitate

release planning and to help ensure appropriate positioning

for future software migrations.

Since z/OS allows the JES element to be separately

staged, z/OS also supports the coexistence of certain

lower-level JES releases with the JES release provided

with z/OS.

Note: Specifi c functions might only be available on the

up-level systems, or it might be necessary to up-level all

systems to enable some functions.

z/OS.e only supports the latest JES and LE that ships with

the product.

For additional information on z/OS and z/OS.e planning,

refer to z/OS and z/OS.e Planning for Installation,

available on the z/OS and z/OS.e Web sites in the

z/OS Library at: ibm.com/servers/eserver/zseries/zos and

ibm.com/servers/eserver/zseries/zose

For the latest information regarding z/OS and OS/390

marketing and service withdrawal dates visit:

ibm.com/servers/eserver/zseries/zos

/support/zos_eos_dates.html.

Wizards

By using your browser on the Internet, you can get help

to setup some of the more complex functions that you do

infrequently.

Our wizards are interactive assistants that ask you a series

of questions about the task you want to perform (for exam-

ple, setting up a Parallel Sysplex environment). The wiz-

ards simplify your planning and confi guration needs by

exploiting recommended values and by building custom-

ized checklists for you to use. For confi guration tasks,

our wizards also generate outputs like jobs, policies, or

parmlib members that you can upload to z/OS and use.

For more information about wizards visit the Web site at:

www-1.ibm.com/servers/eserver/zseries/zos/wizards/

Order z/OS through the Internet

ShopzSeries (formerly SHOPS390) provides an easy way

to plan and order your z/OS ServerPac or CBPDO. It

will analyze your current installation, determine the correct

product migration, and present your new confi guration

based on z/OS. Additional products can also be added to

your order (including determination of whether all product

requisites are satisfi ed).

IBM Service is available through ShopzSeries as an Inter-

net-based, strategic software tool available to fulfi ll orders

24x7 (365 days a year). Through Service in ShopzSeries,

customers can quickly and easily order and receive cor-

rective or preventive service electronically over the Internet

or by standard physical media. For preventive service,

customers can order just critical service (HIPERs and PTFs

that resolve PE PTFs), the latest recommended service

(which includes all critical service), or all available service.

Service in ShopzSeries reduces customers’ research time

and effort by using their uploaded SMP/E Consolidated

Software Inventory (CSI) so that all applicable service,

including reach ahead service, for the installed FMIDs

in the target zones is selected. ShopzSeries also uses

the CSI information to limit the size of the service order,

only sending applicable service that has not already been

processed by SMP/E. IBM Technical Support is available

through RETAIN for problems and Q&A.

ShopzSeries is available in the U.S. and several countries

in Europe. In countries where ShopzSeries is not available

yet, please contact your IBM representative (or Business

Partner) to handle your order via the traditional IBM ordering

process.

For more details and availability, visit the ShopzSeries Web

site at: ibm.com/software/shopzSeries.

56

z/VM is the follow-on product for VM/ESA customers. It

opens new and exciting opportunities for customers who

have built enterprise-wide automation and infrastructure

enhancements on the VM platform in support of their appli-

cations, database systems, and e-business solutions.

Using virtualization technology as a foundation, z/VM offers

new function and technology for customers who want to

exploit IBM Virtual Machine (VM) capabilities on the main-

frame. Virtualization technology allows customers to virtual-

ize processor, communications, storage and I/O resources,

thus avoiding the overhead of planning, purchasing and

installing new hardware to support new workloads.

z/VM supports a wide variety of existing IBM ^

zSeries and S/390 servers. This offers today’s VM/ESA cus-

tomer the ability to maintain their existing VM environments

on the latest technology while positioning themselves to

grow into the zSeries.

z/VM offers an ideal platform for consolidating Linux work-

loads onto a single z800/z900 or S/390 server. Running

Linux as a guest of z/VM enables you to run hundreds

of Linux images while benefi ting from the reliability, scal-

ability, availability, and serviceability characteristics of

z800/z900 or S/390 servers.

z/VM Version 3

z/VM offers a new technology base for customers looking

to use IBM Virtual Machine technology on the industry’s

best-of-breed server platform, z800/z900. When z/VM is

running on a zSeries server, it’s possible to run 64-bit

capable OS/390 2.10, z/OS, and Linux for zSeries as guest

systems of z/VM, in addition to ESA/390 guest operating

systems such as OS/390, VSE/ESA, TPF, and Linux for

S/390. To operate z/OS as a guest of z/VM on a zSeries

server, z/VM and z/OS must be operating in 64-bit mode.

z/VM will allow customers to develop and test their 64-bit

Parallel Sysplex applications in a guest environment before

putting them into production. This reduces the need to

invest in separate standalone confi gurations.

z/VM also reduces storage constraints by eliminating the 2

GB central storage limitation providing plenty of headroom

for increasing e-business demands and growing back-

offi ce applications within a single machine image. Custom-

ers experiencing real memory constraints can experience

relief by running z/VM in 64-bit mode on a zSeries server.

This constraint relief is provided for ESA/390 guest operat-

ing systems. Support for large real memory with z/VM may

benefi t customers running a large number of Linux on

zSeries and S/390 guest systems.

Additional enhancements in z/VM Version 3 include:

• Native FlashCopy™ for Enterprise Storage Server (ESS)

for high-speed data copy

• Guest support enhancements for 3494 VTS and FICON

attached 3590 A60 Tape Controller

Connectivity enhancements for TCP/IP Feature for z/VM:

• Improved security with the inclusion of a Secure Socket

Layer (SSL) server

• Transparent data access to remote systems data with an

NFS Client

• Capability and usability improvements to FTP server for

Web browsers

• Reduced load on hosts with support for IP Multicasting

• Improved data transfer performance with QDIO sup-

porting Gigabit Ethernet, Fast Ethernet, and 155 ATM

(Ethernet Lan Emulation)

• Support for the DFSMS/MVS® Program Management

binder and loader functionality to enhance application

affi nity between CMS and OS/390 or z/OS

z/VM

57

z/VM Version 4

Licensed using the IBM International Program License

Agreement (IPLA) which includes a one-time charge (OTC)

pricing structure, z/VM Version 4 offers a wide variety

of features and functions for exploiting zSeries servers or

S/390 servers at a substantially lower cost. z/VM Version

4 is priced on a per-engine basis and is designed to sup-

port the IBM Integrated Facility for Linux (IFL) processor

features for Linux based workloads and standard engines

for all other zSeries and S/390 workloads (an engine is

also referred to as a central processor). z/VM Version 4

supports the z800/z900, S/390 Parallel Enterprise Server

Generation 5 and 6, and the S/390 Multiprise 3000, or

equivalent.

To help improve the performance of I/O to network

devices, the z/VM Control Program (CP) provides a fast

CCW translator for translating a wide range of channel

programs that perform I/O to network adapters. This fast

translator for network devices includes support for 64-bit

indirect data address words (IDAWs), which allows guest

machines to read and write data above the 2 GB limit

using 64-bit I/O addressing. 64-bit IDAW support was fur-

ther extended to the existing DASD fast CCW translator.

This enhancement is also designed to include 64-bit IDAW

support for DASD channel programs that are simulated

via the minidisk cache (MDC). Additional guest-support

improvements that may benefi t Linux virtual machine per-

formance include DASD fast CCW translation using 64-bit

IDAWs and (when corresponding function is available from

Linux on zSeries) enhanced page-fault handling, which

allows a Linux guest to continue processing while the page

faults are handled by z/VM.

When corresponding function is available from Linux on

zSeries, z/VM provides the capability for Linux guest

virtual machines to use clear-key RSA functions of the

IBM PCI Cryptographic Coprocessor (PCICC) or the IBM

PCI Cryptographic Accelerator (PCICA) for Secure Socket

Layer (SSL) acceleration on zSeries and S/390 servers.

z/VM V4.2 offers some ease-of-use functions to manage

Linux images and a migration facility to help existing cus-

tomers of the Virtual Image Facility™ move their confi gura-

tion fi les and data to a z/VM V4.2 system.

z/VM V4.2 extended its hardware support by exploiting

technological enhancements for the z800/z900 servers,

such as:

• Faster communications between and among virtual

machines and logical partitions with HiperSockets

• High-speed OSA-Express Token-Ring

• Improved z/OS Parallel Sysplex support with virtualized

Coupling Facility (CF) duplexing

• FICON channel-to-channel adapter (CTCA) communica-

tions for guests

Connectivity enhancements to TCP/IP for z/VM, Level 420

are designed to include a new Internet Message Access

Protocol (IMAP) server, improved security of the TCP/IP

stack by preventing some Denial of Service (DOS) attacks,

and support for HiperSockets. A “Guest LAN” capability

is designed to allow a VM guest to install a virtual

HiperSockets adapter and connect it with other virtual

network adapters on the same VM host system to form

an emulated LAN segment.

To aid application development within the Language

Environment (LE), z/VM consolidated existing VM C-lan-

guage sockets APIs into a single consistent socket library.

58

z/VM V4.3 extended the virtualization technology for Linux

guests by providing additional accounting information to

record the use of system resources by a virtual machine.

FCP-based Small Computer System Interface (SCSI) sup-

port is available for Linux on zSeries only. When available,

z/VM V4.3 will provide for the use of a Fibre Channel

Protocol (FCP) channel on zSeries processors connected

to a fi bre-channel fabric to access selected devices on

SCSI controllers connected to the fabric.

I/O management facilities enable z/VM to exploit the hard-

ware I/O Priority Queuing facility to prioritize guest and

host I/O operations. An automated shutdown function

enables guests to shut themselves down when signaled

to do so by a z/VM Control Program (CP) command. This

support will be exploited by z/VM as a guest and can

also be exploited by other guest operating systems. z/VM

V4.3 allows multiple VM guests to share a tape device by

allowing the CP ATTACH command to be issued for the

same tape device on different guests without intervening

CP DETACH commands. This support removes the need to

manage dedication of a tape device from one VM guest to

another since the tape device can now remain ATTACHed

to several guests concurrently.

Level 430 of TCP/IP for z/VM exploits the multicast capabil-

ity of a HiperSockets adapter, improves the security of the

TCP/IP stack by detecting, reporting, and preventing more

types of Denial of Service (DoS) attacks than provided in

z/VM V4.2, and improves performance of the TCP/IP stack.

A new utility is introduced in z/VM V4.3 to automate the

connection of a newly installed z/VM system to a TCP/IP-

based network. This z/VM TCP/IP confi guration wizard

requires no knowledge of TCP/IP for z/VM and is similar to

the network confi guration utilities used in Linux for zSeries

distributions during Linux installation. A new function in

z/VM V4.3 makes it easier to dynamically confi gure TCP/IP

for z/VM, Level 430. The new IFCONFIG command follows

the general syntax of the Linux/UNIX ifconfi g command.

The Guest LAN capability, introduced in z/VM V4.2, has

been improved to simulate a Queued-Direct I/O (QDIO)

network adapter and now emulates the multicast and

broadcast capabilities of the hardware.

Improvements in systems management include the capa-

bility to manage guest performance to achieve user-

defi ned goals. The performance of CP timer management

is improved for environments where a large number of

requests are scheduled, particularly for short intervals, and

where timer requests are frequently canceled before they

become due. A system with large numbers of Linux or

z/OS guests with certain workloads would be an example

of such an environment. System performance may be

improved with better utilization of large real storage when

Expanded Storage is unavailable, full, or nearly full while

CP is replenishing its available-page list.

RealTime Monitor (RTM) and Performance Reporting Facility

(PRF) have been enhanced to support z/VM, including

new and changed monitor records in z/VM V3. RTM simpli-

fi es performance analysis and the installation management

of VM environments. PRF uses system monitor data to

analyze system performance and to detect and diagnose

performance problems. RTM and PRF are optional, per-

engine priced features of z/VM V4 as is the Directory

Maintenance Facility (DirMaint™). RACF for z/VM is now

available as an optional, per-engine priced feature. RACF

works with the existing system features of z/VM to provide

improved data security for an installation.

For further information see the z/VM Reference Guide,

GM13-0137 or visit the z/VM Web site at:

ibm.com/zseries/zvm/.

59

VSE/ESA

VSE/ESA is designed to protect extensive customer invest-

ments in existing core VSE applications, data, IT skills,

business processes, end user training, and equipment.

Beginning with VSE/ESA V2.5, standards-based,

no-charge connectors provide fl exible interoperability

between VSE and Linux on zSeries. Connectors let Linux

based e-business applications access core VSE applica-

tions and data. In addition, optional IBM middleware such

as CICS Transaction Gateway, DB2 UDB or DB2 Connect,

and MQSeries complement VSE connectors.

z800, VSE, Linux (perhaps exploiting z800 IFLs), and z/VM

are a compelling combination for those seeking a com-

petitive IT advantage. IBM ^ zSeries servers offer

a unique opportunity to reduce IT cost by consolidating

existing servers on the same z800 running VSE. In addi-

tion, new, state-of-the-art Linux Web applications and

existing VSE applications and data can form a comprehen-

sive, integrated solution combining the best of e-business

and traditional transaction and batch processing.

VSE customers with growing traditional VSE workload,

growing Linux workload (perhaps resulting from consolida-

tion and/or new e-business applications), or both will fi nd

z800 to be a robust, cost-effective server solution.

Traditionally, z/OS (and its predecessors) has been the

preferred growth path for many VSE customers. It remains

an attractive migration target for many VSE users today.

Affi nity between VSE and z/OS has been an enduring part

of IBM’s strategy for VSE. One objective of affi nity is to help

ensure that VSE customers can easily and smoothly adapt

their core programs and IT skills to z/OS. Using z/VM to

run concurrent VSE and z/OS systems, z800 servers are

an especially productive platform for those migrating from

VSE to z/OS.

VSE/ESA Version 2 Release 7 (when available) will support

HiperSockets and PCICA hardware encryption assist. The

improved performance possible with HiperSockets makes

the combination of VSE and Linux even more effective.

Beginning with VSE/ESA V2.6, VSE supports OSA-Express.

VSE/ESA operates in basic, or 31-bit, mode. Linux for

zSeries is available for new applications requiring 64-bit

capability. That means in order to utilize the full potential of

zSeries servers, most VSE customers will want to use z/VM

for fl exibility and exploitation.

For more information on VSE, see the VSE Web site at

ibm.com/servers/eserver/zseries/os/vse/.

60

© Copyright IBM Corporation 2002

IBM Corporation

Software Communications

Route 100

Somers, NY 10589

U.S.A.

Produced in the United States of America

12-02

All Rights Reserved

References in this publication to IBM products or services do not imply that IBM

intends to make them available in every country in which IBM operates. Consult

your local IBM business contact for information on the products, features, and

services available in your area.

IBM, the IBM logo, IBM eServer, IBM ̂ , the e-business logo, AFP,

AnyNet, APPN, BookManager, CICS, DB2, DB2 Connect, DB2 Universal

Database, DFSMS/MVS, DFSMSdfp, DFSMSdss, DFSMShsm, DFSMSrmm,

DFSORT, DirMaint, Encina, Enterprise Storage Server, ESCON, FlashCopy,

FFST, FICON, FICON Express, GDDM, GDPS, Geographically Dispersed Parallel

Sysplex, HiperSockets, Hiperspace, IMS, Infoprint, Intelligent Miner, IP Printway,

iSeries, Language Environment, MQSeries, Multiprise, MVS, Netfi nity, NetSpool,

NetView, Open Class, OS/2, OS/390, Parallel Sysplex, PR/SM, Processor

Resource/Systems Manager, pSeries, RACF, Resource Link, RMF, RS/6000,

S/390, S/390 Parallel Enterprise Server, Sysplex Timer, SystemPac, Tivoli, Tivoli

Storage Manager, Virtual Image Facility, VisualAge, VM/ESA, VSE/ESA, VTAM,

WebSphere, xSeries, z/Architecture, z/OS, z/OS.e, z/VM, and zSeries are trade-

marks or registered trademarks of the International Business Machines Corpora-

tion.

Intel is a trademark of the Intel Corporation in the United States and other

countries.

Java and all Java-based trademarks and logos are trademarks or registered

trademarks of Sun Microsystems, Inc. in the United States or other countries.

Linux is a registered trademark of Linus Torvalds.

UNIX is a registered trademark of The Open Group.

Windows NT is a registered trademarks of Microsoft Corporation.

Other trademarks and registered trademarks are the properties of their respec-

tive companies.

IBM hardware products are manufactured from new parts, or new and used

parts. Regardless, our warranty terms apply.

Photographs shown are engineering prototypes. Changes may be incorporated

in production models.

This equipment is subject to all applicable FCC rules and will comply with them

upon delivery.

Information concerning non-IBM products was obtained from the suppliers of

those products. Questions concerning those products should be directed to

those suppliers.

All customer examples described are presented as illustrations of how these

customers have used IBM products and the results they may have achieved.

Actual environmental costs and performance characteristics may vary by cus-

tomer.

All statements regarding IBM’s future direction and intent are subject to change

or withdrawal without notice, and represent goals and objectives only.

Prices subject to change without notice. Contact your IBM representative or

Business Partner for the most current pricing in your geography.

Performance is in Internal Throughput Rate (ITR) ratio based on measurements

and projections using standard IBM benchmarks in a controlled environment.

The actual throughput that any user will experience will vary depending upon

considerations such as the amount of multiprogramming in the user’s job stream, the I/O confi guration, the storage confi guration, and the workload processed.

Therefore, no assurance can be given that an individual user will achieve

throughput improvements equivalent to the performance ratios stated here.

GM13-0117-04

To Learn More

Visit the S/390 World Wide Web site at ibm.com/eserver/

zseries or call IBM DIRECT at 1 800 IBM-CALL in the U.S.

and Canada.

Australia 132 426

Austria 0660.5109

Belgium 02-225.33.33

Brazil 0800-111426

Canada 1-800-IBM-CALL

China (20) 8755 3828

France 0800-03-03-03

Germany 01803-313233

Hong Kong (20) 2825 6222

Hungary 165-4422

India (80) 526 9050

Indonesia (21) 252 1222

Ireland 1-850-205-205

Israel 03-6978111

Italy 167-017001

Japan 0120 300 426

Korea (02) 781 7800

Malaysia (03) 717 7890

Mexico 91-800-00316

Netherlands 020-513.5151

New Zealand 0800-801-800

Philippines (02) 819 2426

Poland (022) 878-6777

Singapore 1800 320 1975

South Africa 0800-130130

Spain 900-100400

Sweden 020-220222

Switzerland 0800 55 12 25

Taiwan (06) 2725 9300

Thailand (02) 273 4444

Vietnam Hanoi (04) 843 6675

Vietnam HCM (08) 829 8342

United Kingdom 0990-390390

United States 1-800-IBM-CALL