aa sites overview ims replication - ims ug july 2013 tokyo

IBM GDPS Active-Active Sites &IBM InfoSphere IMS Replicationfor z/OS Overview

Greg VanceIMS Development, [email protected]

System zenvironments

Smarter Computing

© 2013 IBM Corporation

[email protected] environments

Smarter Computing

Availability. References in this presentation to IBM products, programs, or services do not imply that they will be available in all

countries in which IBM operates.

Acknowledgements and Disclaimers

The workshops, sessions and materials have been prepared by IBM or the session speakers and reflect their own views. They are

provided for informational purposes only, and are neither intended to, nor shall have the effect of being, legal or other guidance or advice

to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this presentation, it is

provided AS-IS without warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of,

or otherwise related to, this presentation or any other materials. Nothing contained in this presentation is intended to, nor shall have the

effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the

applicable license agreement governing the use of IBM software.

All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may

have achieved. Actual environmental costs and performance characteristics may vary by customer. Nothing contained in these

materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific

sales, revenue growth or other results.

© 2013 IBM Corporation2

© Copyright IBM Corporation 2013. All rights reserved.

– U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract

with IBM Corp.

IBM, the IBM logo, ibm.com, IMS, DB2, CICS and WebSphere MQ are trademarks or registered trademarks of International Business

Machines Corporation in the United States, other countries, or both. If these and other IBM trademarked terms are marked on their first

occurrence in this information with a trademark symbol (® or ™), these symbols indicate U.S. registered or common law trademarks

owned by IBM at the time this information was published. Such trademarks may also be registered or common law trademarks in other

countries. A current list of IBM trademarks is available on the Web at “Copyright and trademark information” at

www.ibm.com/legal/copytrade.shtml

Other company, product, or service names may be trademarks or service marks of others.

Smarter Computing

Active/Active Sites overview – agenda

� Level set

� Active/Active Sites overview

� Preliminary testing results

� Components

� IMS Replication

System zenvironments


� IMS Replication

� Summary

CD1SOURCECD1TABLE

CD1SOURCECD1TABLE

CD1SOURCECD1TABLE

CD1SOURCECD1TABLE

CD1SOURCECD1SOURCECD1TABLECD1CD1TABLE

CD1SOURCECD1TABLE

CD1SOURCECD1TABLE

CD1SOURCECD1SOURCECD1TABLECD1CD1TABLE

Level set

Active/Active Sites overview

Preliminary testing results

Components

Roadmap

Summary



Summary

Smarter Computing

Customer Requirements for Business ContinuityFocusing on the “mission critical” workload

� Shift from a failover model to a nearly-continuous availability model

– Multi-sysplex, multi-platform solution • “Recover my business rather than my platform”

• Non-disruptive site switch of workloads for planned outages

� Minimize cost and Optimize resource utilization

– Automated recovery processes (similar to other GDPS solutions), minimizing operator learning curve


learning curve

– Provide workload distribution between sites • Dynamically select sites based on their ability to handle workload

• Route around failed sites

� Provide application level granularity

– Current solutions employ an all-or-nothing approach • e.g. complete disk mirroring, requiring extra network capacity).

– Some workloads may require immediate access from every site

– Some workloads may need to update other sites every 24 hours (less critical data).

Smarter Computing

GDPS/Active-Active Sites: From HIGH Availability to CONTINUOUS Availability

GDPS/PPRCGDPS/XRC or

GDPS/GMGDPS/Active-Active

Failover model Failover modelNear Continuous Availability

model

Recovery time = 2 minutes Recovery time < 1 hour Recovery time < 1 minute


Distance < 20 KM Unlimited distance Unlimited distance

GDPS/Active-Active is for mission critical workloads that have stringent recovery objectives that can not be achieved using existing GDPS solutions.

– RTO approaching zero, measured in seconds for unplanned outages

– RPO approaching zero, measured in seconds for unplanned outages

– Non-disruptive site switch of workloads for planned outages

– At any distance

Active-Active is NOT intended to substitute for local availability solutions such as Parallel SYSPLEX

Active/Active Sites overview Level set



Components

IMS Replication

Summary


Summary

Smarter Computing

IBM United States Services Announcement 611-023, dated May 24, 2011 - IBM GDPS active/active continuous availability

At a glance

� IBM® GDPS® active/active continuous availability is the next generation of GDPS and represents a fundamental paradigm shift for near continuous availability solutions.

Overview

� IBM GDPS active/active continuous availability is the next generation of GDPS and a fundamental paradigm shift from a failover model to a near continuous availability model.IBM GDPS active/active continuous availability combines the best attributes of the existing suite of GDPS services and expands them to allow you to achieve unlimited distances between your data center sites with recovery time objectives measured in seconds. IBM GDPS active/active continuous availability is a solution for an environment


seconds. IBM GDPS active/active continuous availability is a solution for an environment consisting of two sites, separated by unlimited distances, running the same applications and having the same data with cross-site workload monitoring, data replication, and balancing. IBM GDPS active/active continuous availability, as with previous GDPS solutions, provides a complete set of services to help achieve near continuous availability. This solution, which is an integration of IBM products and GDPS control software, is delivered through an IBM service engagement which includes project management throughout the implementation cycle.

Statement of direction

� IBM intends to deliver, over time, additional configurations that comprise GDPS active/active continuous availability. In addition to the Active/Standby configuration, IBM plans to make available the Active/Query configuration, which will provide the ability to selectively query data in either site.*

* This statement represents the current intention of IBM. IBM development plans are subject to change or withdrawal without further notice.

Any reliance on this statement of direction is at the relying party's sole risk and does not create any liability or obligation for IBM.

Smarter Computing

Active/Active Sites configurations

� Configurations

1. Active/Standby – general availability on June 30

2. Active/Query – statement of direction

3. …

� A configuration is specified on an application basis


� A application is the aggregation of these components

– Software: applications (e.g., COBOL program) and the middleware run-time environment (e.g., CICS region & DB2 subsystem)

– Data: related set of objects that must preserve transactional consistency and optionally referential integrity constraints (e.g., DB2 Tables)

– Network connectivity: one or more TCP/IP addresses & ports (e.g., 10.10.10.1:80)

Smarter Computing

Active/Active Sites’ ConceptShifting to Continuous Availability from Failover

San Jose

Two or more sites, separated by

unlimited distances, running thesame applications & having the

same data to provide:

– Cross-site Workload Balancing

– Continuous Availability


Madrid

– Continuous Availability

– Disaster Recovery

Smarter Computing


San Jose


Madrid

Replication

Data at geographically dispersed sites are kept in sync via replication

Smarter Computing


San Jose

Transactions


Madrid

Replication

Workloads are managed by a client and routed to one of

many replicas, depending upon workload weight and latency constraints … extends workload balancing to

SYSPLEXs across multiple sites!

WorkloadDistributor

Load Balancing with SASP(z/OS Comm Server)

Smarter Computing


San Jose

Transactions


Madrid

Replication

Tivoli Enterprise Portal

Monitoring spans the sites and now becomes

an essential element of the solution for site health checks, performance tuning, etc.

WorkloadDistributor

Load Balancing with SASP(z/OS Comm Server)

Smarter Computing

IBM InfoSphere Data Replication’s Q-ReplicationHigh volume, low latency DB2 z/OS Replication

ReplicationMetadata

Source DB2 Databases

DB2

ReplicationMetadata

TARGET

Replication Center


Q Capture

Monitor Thread

Log Reader Admin Thread

Pruning Thread

Publish Thread

RestartQ

AdminQ

DB2

Logs

SOURCE

Q Apply

Target DB2 Databases

StoredProcedure

Apply Agent

Apply Agent

Apply Agent

Q Apply

Browser

AdminQ

TARGET

SendQ/ReceiveQ

Event PublisherMessages (XML or CDV)

ReplicationDashboard

ApplyMonitor Tables

Capture Monitor Tables

Smarter Computing

TEP/CDA

Target IMS Databases

ReplicationMetadata

Source IMS Databases

ReplicationMetadata

BookmarkDatabase

IBM InfoSphere IMS Replication for z/OSHigh Volume, Low Latency IMS Data Replication


SOURCE SERVER TARGET SERVER

TCP/IP

IMSLogs

IMS DRA Interface

Administration Administration

One Session Per Subscription

Log

Read/

Merge

UOR

Capture UOR

Analysis

IMS

IMSIMS

UOR Apply

Smarter Computing

Action : From GDPS, we start the workloads in both sitesFrom GDPS, we start the replication from site1 to site2

From GDPS, we start the routing of transactions to site1

We see :GDPS panel to start Workload (subsystems)GDPS scripts to start replication from site1 to site2

Scenario 1 –Start Workload / replication / routing


GDPS scripts to start replication from site1 to site2 GDPS scripts to start routing transactions to site1

SDF screen to check the GDPS actions

TEP interface to check the replication / workload status

Smarter Computing

LLAdvisorSecondary

Site G5Site G4Network

GDPS Web Interface

LB 2°°°° TierSysplexDistrib

LB 2°°°° TierSysplexDistrib TEMS & TEMA

Netview BackupGDPS

Code

G5C1Backup Controller

TEMS & TEMA

LLAdvisorPrimary

Netview MasterGDPS

Code

G4C1Primary Controller

TEP Interface

LB 1°°°° TierCSM


LLAgent

Netview & SA

LLAgent

Netview & SA

Workload 1

CICS/DB2 Appl

Workload 1

DB2 Rep

CICS/DB2 Appl

DB2

LLAgent

Netview & SA

LLAgent

Netview & SA

Workload 1

DB2 Rep

CICS/DB2 Appl

Workload 1

CICS/DB2Appl

ActiveActive ActiveActive

G4 Production 1 G4P1G4 Production 2 G4P2 G5 Production 2 G5P2G5 Production 1 G5P1

TEMS & TEMATEMS & TEMA

StandbyStandby

IMS IMSDB2

Smarter Computing

Sample Scenario ---Site 1 Planned Outage

GDPS Script:

� Stop routing transactions to Site1 “Active” workloads– Replication from Site1 to Site2 will stop as there are no more changes

� Stop Replication to Site1 for any workloads using Site1 as “Standby”


“Standby”

� Start routing Site1 “Active” transactions to Site2

� The workloads are now processing transactions in Site2 … a recovery point is maintained in anticipation of shift back to Site1

� Then, as required by the scenario:

– Stop workloads in Site1

– Close down all systems in Site1

Smarter Computing

LLAdvisorSecondary


GDPS Web Interface



Netview BackupGDPS

Code


TEMS & TEMA

LLAdvisorPrimary

Netview MasterGDPS

Code


TEP Interface



LLAgent

Netview & SA

LLAgent

Netview & SA

Workload 1

CICS/DB2 Appl

Workload 1

DB2 Rep

CICS/DB2 Appl

DB2

LLAgent

Netview & SA

LLAgent

Netview & SA

Workload 1

DB2 Rep

CICS/DB2 Appl

Workload 1

CICS/DB2Appl




StandbyStandby

IMS IMSDB2


Smarter Computing

Sample Scenario ---Return from Outage when Site1 is ready for work!

GDPS Script:

� Once Site1 is available,– Replication from Site2 back to Site1 will commence from the recovery point

stored


� Once caught up, Stop routing transactions to Site2 “Active” workloads

– Replication from Site2 to Site1 will stop as there are no more changes

� Start routing “Active” transactions to Site1– Replication from Site1 to Site2 will automatically start

once changes show up on Site1

� The Active workloads are now processing transactions in Site1

Smarter Computing

LLAdvisorSecondary


GDPS Web Interface



Netview BackupGDPS

Code


TEMS & TEMA

LLAdvisorPrimary

Netview MasterGDPS

Code


TEP Interface



LLAgent

Netview & SA

LLAgent

Netview & SA

Workload 1

CICS/DB2 Appl

Workload 1

DB2 Rep

CICS/DB2 Appl

DB2

LLAgent

Netview & SA

LLAgent

Netview & SA

Workload 1

DB2 Rep

CICS/DB2 Appl

Workload 1

CICS/DB2Appl




StandbyStandby

IMS IMSDB2


Smarter Computing

Sample Scenario ---Both Site1 and Site2 can be “active”!

� Today, this can be a second DB2 workload or an IMS workload– Replication for Workload 1 data goes from Site1 to Site2

– Replication for Workload 2 data goes from Site2 to Site1


� During Outages, GDPS must recognize if an unavailable site is also acting as a Standby site for other workloads

– Replication for a second workload may stop during the outage

– Catch-up for the second workload will also occur upon restart after the outage

Smarter Computing

Sample Environment 2

PLEX1 PLEX2

Routing for:

Workload_1

Workload_2

Routing for:

Workload_3C1 C2

PB

SASP-compliant Routers

Site 1Mix of active/standby

workloads

Site 2Mix of active/standby

workloads


Workload_1

Workload_2

Workload_3

Workload_1

Workload_2

Workload_3

S/W Replication

PLEX1 PLEX2

Workload_1

Workload_3

Workload_1

Workload_3

SYS11

SYS12

SYS21

SYS22

CF21

CF22

CF11

CF12

PB

Active Replication from 1 to 2

Active Replication from 2 to1

Inactive Replication from 2 to 1

Active Replication from 1 to 2



Smarter Computing

Active/Active Sites functions

� Start/stop a controller – start and stop an A/A Sites controller

� Start/stop a site – start and stop individual sysplexes (each sysplex maps

to a site)

� Stop/start a workload – start and stop individual workloads

� Monitoring – monitor the A/A Sites configuration and, if any conditions that

will potentially impact a workload and/or site switch, generate an alert

� Planned workload switch – switch the workload site to the other site


� Planned workload switch – switch the workload site to the other site initiated by operator action

� Unplanned workload switch – switch failed workload to the other site,

either automatically or based upon operator prompt, after the workload failure detection interval

� Planned site switch – switch all workloads executing to the other site

initiated by operator action

� Unplanned site switch – switch the failed site’s workloads to the other site,

either automatically or based upon operator prompt, after the site failure detection interval




Components

IMS Replication

Summary


Summary

Smarter Computing

Preliminary testing results*

� Planned workload switch

– Operator initiated switch from the active instance of a workload to the standby instance took 20 seconds

– Not possible with disk replication

� Unplanned workload switch

– Automatic switch from the active instance of a workload to the standby instance took 120 seconds (workload failure detection interval is 60 seconds)




� Planned site switch (9 * CICS-DB2 and 1 * IMS workloads)

– Operator initiated switch of workloads in one site to the other site took 20 seconds

– Current GDPS and disk replication will take 1-2 hours

� Unplanned site switch

– Automatic switch of failed site workloads to the surviving site took 107 seconds (site failure detection interval is 60 seconds)

– Current GDPS and disk replication will take about one hour

* IBM laboratory results; actual results may vary.




ComponentsIMS Replication

Summary


Smarter Computing

Minimum releases of required products installed on z/OS production and controller images for Active/Standby configuration

� Operating system

– z/OS V1R11

� Applications/Middleware

– DB2 for z/OS V9

– IMS 10

– WS MQ V7.0

� Management and monitoring

– GDPS/Active-Active V1.1

– NetView for z/OS V6.1

– System Automation for z/OS V3.3

– IBM Multi-site Workload Lifeline V1.1

– IBM Tivoli Monitoring V6.2.2

– Optional OMEGAMON products (required only if the


– WS MQ V7.0

� Replication

– InfoSphere Replication Server (DB2)

V10

– InfoSphere IMS Replication for z/OS

V10.1

– Optional OMEGAMON products (required only if the

customer wants to monitor the behavior of the respective

products/resources that they deal with (DB2, CICS, storage,

etc.)

•OMEGAMON XE on z/OS V4.2.0

•OMEGAMON XE for Mainframe Networks V4.2.0

•OMEGAMON XE for Storage V4.2.0

•OMEGAMON XE for DB2 Performance Expert (or

Performance Monitor) on z/OS V4.2.0 (if DB2 is running)

•OMEGAMON XE on CICS for z/OS V4.2.0 (if CICS is

running)

•OMEGAMON XE on IMS V4.2.0 (if IMS is running)

•OMEGAMON XE for Messaging V7.0 (if MQ is running)




Components

IMS ReplicationSummary


Smarter Computing

IMS Software-Based Data MirroringInfoSphere IMS Replication

� Unidirectional Replication of IMS data

– Subscription Level Replication

• Transaction consistency

• All or nothing at DB level

• Basic replication monitoring

• TCP/IP for data transmission

� IMS “Capture”

– DB/TM, DBCTL, Batch DL/I, FDBR

IMS

InfoSphere IMS Replication

IMS


– Capture x’99’ log records

• Increase in log volume due to change data capture records

� IMS “Apply”

– Uses IMS Database Resource Adapter interface

– Parallel Apply

– Conflicts will be detected

• Manual resolution will be required

� Classic Data Architect

– Administration (some administration can be done via z/OS console commands)

– Basic replication monitoring

Smarter Computing

Classic DataArchitect

Target IMS Databases

ReplicationMetadata

Administration AdministrationIMSIMS


ReplicationMetadata

BookmarkDatabase

IMS Replication Architecture


SOURCE SERVER TARGET SERVER

TCP/IP

IMSLogs

IMS DRA Interface

Administration

One Session Per Subscription

Log

Read/

Merge

UOR

Capture UOR

Analysis

IMSUOR Apply

Smarter Computing

IMSIMS


Multi-Target Configuration

IMSIMS

Source Server

TargetServer


IMSLogs

IMS

IMS

• Multiple Subscriptions

• Each subscription associated with one of the

target servers

• Single server sends updates to appropriate target

Server

TargetServer

Smarter Computing

IMS

IMS

Sample Two-way Replication Configuration

IMS

Source Server

TargetServer

Workload A Update/Query

Workload A Query


IMS

IMS

TargetServer

IMS

Source Server

Workload B Query

Workload B Update/Query

Smarter Computing

Source Server Details

ReplicationMetadata

IMSDBCTL

Partner Product

IMSTM / DB

Partner Product

Exit

IMSLogs

IMSLogs

TCP/IP

TCP/IP

•User exits to notify server of new IMS

instance

•Merge Waits for Batch

DL/I to complete

•Idle IMS regions can


Change

Stream

Ordering

SOURCE SERVERRECON

IMS Logger Exit

BATCHDL/I

Partner Product

Exit

Capture Services

IMSLogs

Log Info Source IMS Databases

TCP/IP

TCP/IP

•Idle IMS regions can slow processing

Smarter Computing

Target Server Details

Writer

Services

Staged

Unit-of-Recovery

Data

IMS

DRAthread

WriterApply

Service

ChangeMessages


TARGET SERVER

Dependency Analysis

Writer

ServicesService

• Parallelism based on dependency analysis within a subscription

• Database and root key used for analysis

Smarter Computing

Classic Data Architect – Replication Management


Smarter Computing

Classic Data Architect - Monitoring Throughput


Smarter Computing

Classic Data Architect - Monitoring Latency


Smarter Computing

Adaptive Apply

� Adaptive apply error handling is the default behavior

– Can be set to standard apply, which does not tolerate conflicts

� If a conflict is detected, the action will be to ignore update

� Conflicts are:

– Before image mismatch


– Before image mismatch

– Unable to locate segment to process update

� All conflicts are logged in the event log• Manual resolution will be required

Smarter Computing

Current Restrictions

� All segments for a DB must have change capture logging enabled and will be replicated

– Must augment the DBD with the EXIT=(…,LOG) specification

– IMS change capture restrictions

� DEDB FLD calls not supported


� Subset Pointers not managed

� ISRT HERE -> ISRT FIRST

� Workload Restrictions

– All logically related DBs must be in the same subscription

– Workload with logically related DBs will be serialized

– UORs with unkeyed or non-unique keyed segments will be serialized

� External load of target DB

– Must be a static image copy

Smarter Computing

Performance considerations

� Transactional consistency vs. Parallelism

– All updates for a given UR processed as a single transaction during apply

– All transactions involving the same ‘resource’ will be serially processed in commit order

– Running transactions in parallel can have application consistency implications

� Increase in log data


� Increase in log data

� Multiple source IMSs to 1 Apply Target implications

� Internally achieved 53K updates per second

– ~116,000 updates per second when deploying two apply servers

– sustained <2sec latency

– your results may vary

Smarter Computing

Replication Summary

� Asynchronous Replication

– Allows for unlimited distance support

� Low Latency through parallelism

– Allows for almost immediate data availability and low RTO

� Transaction Consistency


� Transaction Consistency

– Access with integrity on target system and low RTO

� Subscription independence

– Switch can be at a workload level vs. system level

Smarter Computing

IMS Replication / DASD Mirroring / IMS RSR

IMS Replication DASD Mirroring (at distance)

RSR

Continuous Availability Model – No Restart

Disaster Recovery Model

Restart z/OS and subsystems

Disaster Recovery Model

Restart IMS

Allows for data access at target Cannot access data at target Cannot access data at target

9904 log record based; Uses DL/I calls to update target DB

DASD based 5950/5050 record based; Uses DB recovery methodology to update target DB

No source log data saved/used at target All data can be mirrored All source log data can be transmitted/saved


No source log data saved/used at target All data can be mirrored All source log data can be transmitted/saved at target

MSDBs not supported All data can be mirrored MSDBs not tracked

FLD call not supported All data can be mirrored All DB updates supported for supported DBs

Subset pointers not supported All data can be mirrored All updates supported

Insert HERE rules for unkeyed segments can change order of segments

Data is identical Segment order identical

Some logical relationships not supported All data can be mirrored All logical relationships supported

IMS to IMS only solution

Integrated with GDPS Active/Active Sites

solution

All enterprise data can be managed as one group.

IMS only solution

Not part of strategic IBM solution


Level set



Components

Summary


Smarter Computing

Thank you

� Current GDPS family of offers

– Over 12-year history of disaster recovery and continuous availability for System z customers

– A proven track record of success, with almost 600 clients worldwide and growing

– Ongoing investment and updated – up to GDPS V3.8


� NEW GDPS/ Active-Active family of offers

– The next generation of GDPS

– Concept: Active applications, transactional integrity, shared data, replication, and automation over global distances for true continuous availability worldwide

• First configuration is Active/Standby

• Statement of Direction on Active Query configuration

• Additional configurations planned for the future

Smarter Computing

There are multiple GDPS service products under the GDPS solution umbrella to meet various customer requirements for Availability and Disaster Recovery.

Continuous Availability of Data within a Data Center

Continuous access to data in the event of a storage subsystem

outage

Single Data Center

Applications remain active

Two Data Centers

Systems remain active

Multi-site workloads can withstand site and/or

storage failures

Continuous Availability / Disaster Recovery within

a Metropolitan Region

Two Data Centers

Rapid Systems Disaster Recovery with “seconds”

of Data Loss

Disaster recovery for out of region interruptions

Disaster Recovery atExtended Distance

Continuous Availability Regionally and Disaster

Recovery Extended Distance

Three Data Centers

High availability for site disasters

Disaster recovery for regional disasters

GDPS/PPRCGDPS/PPRC HM GDPS/GM & GDPS/XRC GDPS/MGM & GDPS/MzGM

Continuous Availability, Disaster Recovery, and

Cross-site Workload Balancing at Extended

Distance

Two or More Data Centers

All sites active

GDPS/Active-Active


RPO=0 & RTO=0

Tivoli – NetView, SAz

STG – System z, DS8K, PPRC

GTS – GDPS control code,

Services

A/S RPO=0 & RTO<1 hr or

A/A RPO=0 & RTO mins

Tivoli – NV, SAz, SA-MP, AppMan

STG – System z, DS8K, VTS,

PPRC

GTS – GDPS control code, Services

RPO secs & RTO <1 hr

Tivoli – NV, SAz

STG – System z, DS8K,

Global Mirror, XRC


A B

C

Tivoli – NV, SAz


MGM, MzGM


Components

RPO – recovery point objective

RTO – recovery time objective

Synch replication

Asynch replication

RPO secs & RTO secs

Tivoli – SA, NetView

AIM - Multi-site Workload Lifelife

IM - DB2 &IMS replication


Global Copy


CD1CD1CD1

CD1

A/S RPO=0 & RTO<1 hr or

A/A RPO=0 & RTO mins

and RPO secs & RTO <1 hr

Smarter Computing

Please direct follow-up questions to [email protected].

Questions


Smarter Computing

The following are trademarks of the International Business Machines Corporation in the United States and/or other countries.

* Registered trademarks of IBM Corporation

AIX*

APPN*

CICS*

DB2*

DB2 Connect

DirMaint

DRDA*

Distributed Relational Database Architecture

e-business logo*

ECKD

Enterprise Storage Server*

ESCON*

FICON*

GDPS*

Geographically Dispersed Parallel Sysplex

HiperSockets

HyperSwap

IBM*

eServer

IBM logo*

IMS

InfoPrint*

Language Environment*

MQSeries*

Multiprise*

NetView*

On demand business logo

OS/390*

Parallel Sysplex*

PR/SM

Processor Resource/Systems Manager

RACF*

Resource Link

RMFS/390*

Sysplex Timer*

System z

System z9

System z10

TotalStorage*

Virtualization Engine

VSE/ESA

VTAM*

WebSphere*

z/Architecture

zEnterprise

z/OS*

z/VM*

z/VSE

zSeries*

Trademarks


The following are trademarks or registered trademarks of other companies.

* All other products may be trademarks or registered trademarks of their respective companies.

Intel is a trademark of Intel Corporation in the United States, other countries, or both.

Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation.

Red Hat, the Red Hat "Shadow Man" logo, and all Red Hat-based trademarks and logos are trademarks or registered trademarks of Red Hat, Inc., in the United States and other countries.

SET and Secure Electronic Transaction are trademarks owned by SET Secure Electronic Transaction LLC.

Notes:

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 configuration, the storage configuration, 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.

IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.

All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.

This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area.

All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

aa sites overview ims replication - ims ug july 2013 tokyo

Technology