(MIDAW) Facility - Messmer The Brain House

GSE z/OS Expertforum Switzerland # 65, 16.-18.10.2006 

Silvio Silvio’s Silvio s Corner 

Corner 

z/News, Hints and Tips 

Silvio Sasso 

IBM Switzerland, ITS Service Delivery for z/OS 

sisa@ch.ibm.com 

Zürich | 16. Oktober 2006 


Silvio Sasso's Corner, GSE z/OS 

Expertforum CH #64, 9.-10.5.2006, 

® 

© 2006 IBM Corporation 


® 

1

The objective of this news session is to provide you with up-to-date and last minute 

technical information, hints and tips related to IBM mainframe hardware and software, 

such as IBM system z9, zSeries, z/Architecture and z/OS. 

This corner allows me to present you... 

ƒHardware news: IBM hardware announcements, new features and options 

ƒSoftware news: z/OS and Parallel Sysplex update 

ƒVarious resources containing additional documentation (e.g. product specific 

information or other interesting Websites etc.) 

ƒSystem programmer goodies, tools, hints and tips 

ƒUseful technical news and flashes 

ƒRecommended readings: new Redbooks and whitepapers etc. 

ƒTips for education, workshops and conferences 

ƒand much more... 

Note: the information contained in this document has not been submitted to any formal IBM test and is distributed on an "as is" basis 

without any warranty either expressed or implied. The use of this information or the implementation of any of the techniques or hints and 

tips described is a customer responsibility and depends on the customer’s ability to evaluate and integrate them into the customer’s 

operational environment. Customers attempting to adapt these techniques to their own environments do so at their own risk. 




Objectives 

© 2004 IBM Corporation 2

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

CICS* 

DB2* 

DB2 Universal Database 

DirMaint 

ESCON* 

FICON* 

GDPS* 

HiperSockets 

HyperSwap 

* Registered trademarks of IBM Corporation 

IBM* 

IBM eServer 

IBM logo* 

IMS 

NetView* 

OMEGAMON* 

On Demand Business logo 

Parallel Sysplex* 

The following are trademarks or registered trademarks of other companies. 

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

Linux is a trademark of Linus Torvalds in the United States and other countries.. 

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

Microsoft is a registered trademark of Microsoft Corporation in the United States and other countries. 

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


RACF* 

S/390* 

System z9 

Tivoli* 

TotalStorage* 

VSE/ESA* 

VTAM* 

WebSphere* 

z/Architecture* 



z/OS* 

z/VM* 

z/VSE * 

zSeries* 

Trademarks 

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. 


General Information 

� The z Platform: Facts and Figures 

� Exploring the “Wonder” in IBM ’s Software Support 

� Why the Mainframe?... Why NOT the Mainframe? 

� The IBM Education Assistent 

� IBM System z Roadshow: a fresh Look at the Mainframe 

Hardware News 

� IBM System z9 FiconExpress4 

� IBM System z9 MIDAW Facility 

� IBM System z9 minimum Operating System Support for Functions 

Software News 

� z/OS Support Summary 

� z/OS Statements of Directions 




Agenda 

� z/OS 1.8 CFRM Performance Improvement with new Message based Protocol 

� z/OS 1.8 GRS Contention Notification 


APAR's of Interest (HIPER's and Red Alerts etc.) 

Parallel Sysplex Update 

� Parallel Sysplex Aggregation 

Hints and Tips, System Programmer "Goodies", Tools and Resources 

� Parallel Sysplex Utilities shipped with z/OS 

� New useful REXX Exec’s shipped with z/OS 1.8 

Redbooks and Redpapers 

Doc Juke Box 




Agenda… 









6

System z 

Software Summit 

IBM System z … platform for today’s new applications 




Summit with IBM System z 

IBM System z… 

the platform for today’s new applications 

® 


An Evolution …….. 

1964 

S/360 

1968 

IMS 

1969 

CICS 


From 

Datacenter 

1979 

MVS 

1983 

DB2 

The z Platform: Facts and Figures 

1986 

NetView 

1994 

MQ 

Series 

2000 

z/OS 



2002 

IBM 

TCO 

Tools 

2003 

WAS 

V5.0 

for 

z/OS 

2004 

DB2 

V8 

IMS V9 

Candle 

2005 

CICS 

V3 

MQ V6 

z/OS 

V1.7 

To SOA 

Server 

System z Software 

Evolution, not revolution 

Modernizing applications 

2006 

WAS V6 

ESB 

Process 

Server 

Portal 

DB2 V9 


How Do You Define “Mainframe”? 

It depends on your perspective: 



Wikipedia says: “Mainframes (often colloquially referred to as big iron) are large and 

"expensive" computers used mainly by government institutions and large companies for 

mission critical applications, typically bulk data processing such as censuses, 

industry/consumer statistics, ERP, and financial transaction processing.” 

searchDataCenter.com says: “Mainframe is an industry term for a large computer, 

typically manufactured by a large company such as IBM for the commercial applications of 

Fortune 1000 businesses and other large-scale computing purposes. Historically, a 

mainframe is associated with centralized rather than distributed computing. Today, IBM 

refers to its larger processors as large servers and emphasizes that they can be used to 

serve distributed users and smaller servers in a computing network” 

Mainframes.com says: “"A mainframe is a continually evolving general purpose 

computing platform incorporating in it architectural definition the essential functionality 

required by its target applications." 

Answers.com says: “A state-of-the-art computer for mission critical tasks. In the 

"ancient" mid-1960s, all computers were mainframes, since the term referred to the main 

CPU cabinet. Today, it refers to a class of ultra-reliable medium and large-scale servers 

designed for enterprise-class and carrier-class operations. 




Reports of the Death of the Mainframe 

… where Premature 

“I predict that the last mainframe will be 

unplugged on March 15, 1996.” 

Stewart Alsop, March, 1991 

“It’s clear that corporate customers still like to 

have centrally controlled, very predictable, reliable 

computing systems – exactly the kind of systems 

that IBM specializes in.” 

Stewart Alsop, February, 2002 

Source: IBM Annual Report, 2001 





Source: IBM Annual Report, 2001 


The Value of Mainframe Computing 

Mainframe Computing Delivers Value for Core Commercial Workloads 

� Designed for high availability and responsiveness 

� Maximum throughout per unit cost 

� Tight centralized control for 

Security 

Stability / Change Management 

Backup / Recovery 

Auditability 

Resource / Cost Management and Accounting 

� Simplified and low cost operations and administration 






Customers continue to add Capacity 

INVENTORY (KMIPS) 

10,000 

9,000 

8,000 

7,000 

6,000 

5,000 

4,000 

3,000 

2,000 

1,000 

0 

G4 

2Q97 

G5 

3Q98 

1Q97 

2Q97 

3Q97 

4Q97 

1Q98 

2Q98 

3Q98 

4Q98 

1Q99 

2Q99 

3Q99 

4Q99 

1Q00 

2Q00 

3Q00 

4Q00 

1Q01 

2Q01 

3Q01 

4Q01 

1Q02 

2Q02 

3Q02 

4Q02 

1Q03 

2Q03 

3Q03 

4Q03 

1Q04 

2Q04 

3Q04 

4Q04 

1Q05 

2Q05 

3Q05 

4Q05 

CAGR 1997-2000 = 26% CAGR 2000-2005 = 19% 


G6 

2Q99 


z900 

4Q00 

z800 

1Q02 



z990 

2Q03 

z890 

2Q04 

z9109 

3Q05 

Source: IBM STG Finance 


System z 

The Mainframe for Mixed Commercial Workloads 






IBM System z Platform Coherence 

IMS 

v9 


DB2 

v8 


Integrated Tool Set / Enterprise COBOL and PL/I v3 

WebSphere 

v6 

CICS 

v3 

Operating System z/OS 

System z Hardware, zAAP, zIIP 



NetView 

v5.2 

WebSphere 

MQ v6 


Transaction Management 

The System z Application “Sweet Spot” 



� Transaction monitor – manages a transaction 

A program or subsystem that manages or oversees the sequence of events 

that are part of a transaction 

Makes sure the ACID properties of a transaction are maintained 

Includes functions such as interfacing to databases and networks and 

transaction commit/rollback coordination 

Provides an API so applications can exploit the services of the transaction 

monitor 

� IBM’s z/OS-based transaction monitors: 

IMS - Information Management System 

CICS - Customer Information Control System 

WebSphere Application Server for z/OS 

� A key strength of the z/OS platform is support for high-volume, 

high-performance transaction management using transaction monitors 




IMS 

Information Management System 

“IMS IMS Runs Runs the the World” World since 1968 

1968 

� Most Corporate data is managed by IMS 

Over 95% of Fortune 1000 Companies use IMS 

IMS manages over 15 billion GBs of production data 

$2 trillion/day transferred through IMS by one customer 

� Over 50 billion transactions a day run through IMS 

IMS serves close to 200 million users per day 

Over 79 million IMS trans/day handled by one customer on a single 

production Sysplex, 30 million trans/day on a single CEC 

120 million IMS trans/day, 7 million/hour handled by one customer 

4,000 trans/second (250 million/day) across TCP/IP to a single IMS 

Over 3,000 days without an outage at one large customer 

21,000 trans/second on a single z990, with 4 IMS servers 






CICS 

Customer Information Control System 

� CICS provides an execution environment for concurrent program 

execution for multiple end users, who have access to multiple data types 

� CICS will manage the operating environment to provide performance, 

scalability, security, and integrity 

30+ years of applications 

>30B transactions per day 

5,000 packages, 2,000 ISVs 

30M CICS users 

50K CICS/390 licenses, 16K customers 

950,000 CICS application programmers 

490 of IBM’s top 500 customers 





CICS 


IBM System z and DB2 

Where you put your Data matters 

� Integrity 

� High availability 

� Security 

� Systems and database management 

DB2 for Z in: 

25 of the top 25 worldwide banks* 

23 of the top 25 US retailers** 

9 of the top 10 global life / health insurance 

providers*** 



Top companies as identified in: 

* WW Banks from The Banker.com: http://www.thebanker.com/news/fullstory.php/aid/1699/Tio_1000_World_Banks.html 

**US Retailers from National Retail Federation July 2005: http://www.stores.org/pdf/TOP100printwithad.pdf 

***Insurance - 2005 Ward's 50 Benchmark Group: www.memic.com/news/Wards50.asp 




WebSphere Application Server for z/OS 

The Java Transaction Manager 

� Architected on SOA infrastructure & principles 

Fully J2EE 1.4 platform certified 

Leading Web Services support 

WebSphere Rapid Development & Deployment 

� zAAP enabled (z9-109, z990, z890) 

Run Java applications next to mission critical data 

Lower the cost of computing for WebSphere Application 

Server 

(and all z/OS based Java applications) 

� Common code infrastructure 

Administration skills shared between platforms 

Develop anywhere, run on WebSphere Application Server 

for z/OS 

� Native OS support – leverages the z/OS platform 

� Optimization features designed to provide security 

and data interaction, including support for the 

traditional mainframe SW – CICS, IMS, DB2 

� Enhanced QoS within the product, complementary to 

QoS of the platform 





Integrated WS app server for 

z/OS & DB Serving w/zAAP 

1 st Tier 2 nd Tier 

Client 

Client 

Client 

Standard CP zAAP 

Integrated z/OS Application 

& Database Server 


Virtualization 



Mainframes – The Innovator and Leader in Virtualization Function 

� Share processor, memory, I/O, and network among multiple operating 

environments 

Isolate workloads with EAL5 level security 

Share resources among workloads 

Enable communication for workloads internally with an in-memory TCP/IP network 

�35+ year history of virtualization, innovation and refinement 

Hardware and software based for optimum performance 

and flexibility 

Robust suite of function for creating, provisioning, deploying, and managing virtual 

servers 

�z/VM Virtualization to simplify your IT infrastructure 

Support up to hundreds of concurrent applications with z/VM 

– Share applications, data, as well as hardware among large numbers of servers 

Management tools for operation, maintenance, and accounting 




z/OS Security 

� Security Server for z/OS 

RACF – Resource Access Control Facility 

LDAP 

Firewall 

� Encryption 

On-board cryptographic hardware in System z9 servers 

Integrated Cryptographic Service Facility (ICSF) in z/OS 

– Callable APIs to perform crypto functions from software 



� Public Key Infrastructure (PKI) Services 

Enables a PKI on z/OS 

Operates a Certificate Authority 

Provides administration application, end-user interface, integration with z/OS 

LDAP, ICSF, and HTTP server 

Certified “Identrus Compliant” in 2005 




Driving Value Up and Cost Down 

Evolution of Specialty Engines 

Internal Coupling 

Facility (ICF) 1997 

�Centralized data 

sharing across 

mainframes 


Integrated 

Facility for Linux 

(IFL) 2001 

�Support for new 

workloads and 

open standards 


System z9 

Application Assist 

Processor (zAAP) 

2004 

�Designed to help 

improve resource 

optimization for 

z/OS Java 

technology-based 

workloads 



IBM System z9 

Integrated Information 

Processor (zIIP) 

2006 

�Designed to help 

improve resource 

optimization for 

eligible data 

workloads within the 

enterprise 


zAAP – System z9 Application Assist Processor 

Consider a WebSphere Application that is transactional in nature and 

requires 1000 MIPS today on System z 

80% 

utilization 


JAVA 

JAVA 

JAVA 

1000 MIPS 

for WebSphere 

App 

40% 

utilization 


JAVA 

JAVA 

JAVA 

500 MIPS for WebSphere App + 

500 MIPS now available for additional 

workloads 



JAVA execution 

powered by a 

zAAP 

In this example, with zAAP, we can reduce the standard CP capacity requirement for 

the Application to 500 MIPS or a 50% reduction.* *For illustrative purposes only 


System z: Enterprise Hub for Data and SOA 

Potential advantages of consolidating application and data serving 

� Security Fewer points of intrusion 

� Resilience Fewer Points of Failure 

� Performance Avoid Network Latency 

� Operations Fewer parts to manage 

� Environmentals Less Hardware 



� Utilization Efficient use of resources 

� Scalability Batch and Transaction Processing 

� Auditability Consistent identity 

� Simplification Problem Determination/diagnosis 

� Transaction Integrity Automatic recovery/rollback 



With IFL 

With zAAP 


zIIP – System z9 Integrated Information Processor 

A breakthrough that strengthens mainframe position as the 

world’s premier database serving platform 

Frees-up computing capacity 

Business Intelligence and transaction processing: 

Reduce security risks 

Improve resource optimization 

Lower costs 






Customers’ Viewpoint 





Insurance Services 

Office, Inc. 


IT Infrastructure Trends – Cost 

Decrease in Efficiency as IT Spending Shifts to Operations Labor 

70% of 2005 CIO 

Budget is Labor 

� 70% of CIO budget is labor 

� Operations labor will be 73% of 

CIO labor budgets by 2008 

� $325B in operations labor by 2008 

Source: Tivoli Commissioned Study 1Q05 


Hardware 

Services 

Labor 

Software 


100% 

80% 

60% 

40% 

20% 

0% 

350000 

300000 

250000 

200000 

150000 

100000 

50000 



2001 2002 2003 2004 

App Development App Supt/Maint IT Operations 

0 

2005 2006 2007 2008 

Administration 

Development 

Operations 

Application 

development 

& support 

labor has 

dropped from 

48% to 34% 

of IT Labor 

spend over 

previous 4 

years 


IBM System z 

Managing Growth and Complexity 

Volume of Workloads processed have never been larger 

Mainframe Data Center Staffing Levels have not significantly changed despite 

large Increases in Workload Volumes 

First National Bank of Omaha 

Their disparate computing environment was becoming extremely expensive, requiring FNBO to hire more people as 

more boxes were brought online. “I looked at our infrastructure in 2002 and saw we were growing servers at a rate of 

30 percent per year. For every application I had, I needed another one to five servers behind that, for things like 

development and application and Web serving. And every 20 servers translates to another body to administer them.” 

Ken Kucera, senior vice president and division head of FNBO Enterprise Technology Services 


289 

Ops 

Staff 

5,994 

MIPS 

2001 


2006 

13,272 

MIPS 

260 

Ops Staff 




Mainframe Cost per Unit of Work goes down 

…. As Workload increases 

Cost per unit of work 


Mainframe 

Distributed scale out 


Most TCO benchmarks 

compare single applications 

Workload 



Most businesses 

operate here 


People Cost is the Driver of TCO 

� In a recent typical study, a customer 

thought they only had 24 UNIX servers 

But these were just the PRODUCTION 

servers 

In addition they had 49 servers for 

Development, Test and Disaster Recovery 

� They needed 44 people to support these 

servers and $7M software 

Running at only 20% utilization 

� A comparable System z implementation 

would have required just 20 servers 

Requiring 16 people to support 

Using $6M software 



� They thought the Solaris environment was 1/5 th of the cost of the 

mainframe ….. but in fact the System z TCO was 37% less 




System z Core Values 



Built upon a 40 Year Heritage …. and still relevant 










32

Welcome to IBM Software Support 

IBM Software Handbook 

Exploring the “Wonder ” in IBM ’s Software Support 

The purpose of this document is to provide guidelines and reference materials 

that customers may need when they require IBM service and support 

This guide has been produced with the following objectives in mind: 

- To introduce you to IBM Software Support, including our operating 

systems and software divisions of DB2, Lotus, Rational, Tivoli, and 

Web Sphere 

- Provide information on the support services currently available 

from IBM, including definitions of programs, policies, and 

procedures 

- Help you to effectively utilize IBM Software Support 

- Explain how you can enhance your IBM Software Support 

with additional services to meet your needs 

- Introduce you to the people of IBM Software Support 

Please download and review this guide carefully as it contains important 

information regarding the service and support of your IBM products 

http://techsupport.services.ibm.com/guides/handbook.html 





Exploring the “Wonder ” in IBM ’s Software Support 

IBM Software Support Handbook Contents 






Why the Mainframe?... 

Why NOT the Mainframe? 







35

Why the Mainframe?... Why NOT the Mainframe? 

Why the mainframe?. . . 


Because it is… 

Designed to deliver the power business needs 

Exceptional in security 

Reliable, available, and scalable 

Incredibly virtualized 

Affordable 

Manageable 

A platform companies worldwide believe in 





What is an IBM Mainframe? 

A server designed to deliver the processing power business needs 

IBM System z -- a reliable, open, virtualized 

platform -- delivers a powerful foundation for 

better security as well as intelligent workload 

management and business integration. 






Technology evolution with the Mainframe 

For over 40 years, IBM has continued to 

innovate and enhance mainframe 

technology 

“IBM has redoubled its commitment 

to the mainframe as evidenced by the 

recent introduction of the System z9.” 

Ernie Fernandez, VP System Sales 

1960’s 

S/360 

1980’s 

S/390 


1990’s 

G5/G6 

2000 

z800/z900 



2003 

z890/z990 

2006 

System z9 

BC/EC 

IBM spent $1.2 B 

and involved 

5000 engineers, 

software developers, 

and security experts 

to develop the z9 

in 3 years. 

Even today, the System z team includes world-class technical 

and customer support covering architecture, installation, and 

maintenance, backed by over 1,700 IT professionals and 

over 20 centers worldwide. 



How is security different on the mainframe? 

People 

Manage access to critical 

data through Multiple 

Level Security 

Networks 

Integrates security with the 

network with built-in technology 

resistant to hackers 


Information & 

Applications 

Supports a variety of encryption standards 

to help keep current with industry and 

government security regulations 



A highly secure business environment that 

complies with standards to help build 

industry creditability and gain consumer trust 

Data 

Protection 

Provides end-to-end protection 

that helps keep data uncorrupted 

and uncompromised 

Operating 

System 

Architected for security from within 

to reduce risk and defend against 

viruses 

“The IBM mainframe is the only computing system to earn the highest level of industry security 

certification, EAL5.” Bob Hoey, Worldwide VP Sales for System z 

*EAL (Evaluation Assurance Level) = International standard to define security requirements in computer systems. 



How are reliability, availability, and scalability 

different on the mainframe? 

A mainframe is more reliable 

– Built-in hardware redundancy means: 

Spare hardware in place for uninterrupted operations 

More reliability More availability Maximum customer satisfaction 

Reduced risks associated with downtime 

A mainframe is more available 

– Double instruction set 

– Non-disruptive upgrades for minimal “reboots” 

– Granular disaster recovery solutions 

– Minimal downtime Maximum uptime More sales More profit 

– Associated downtime costs avoided 

Lost revenue, fines, lawsuits, etc. 

A mainframe is more scalable 

– Capacity on Demand offerings: Pay only for what you use 

– Applications added in minutes rather than days 

– Faster response to meet expected or unexpected business needs, customer 

demand, and end-users 

Mainframes are designed to grow with your business, 

not against it 






How does Disaster Recovery perform on System z9? 

Single System Parallel Sysplex GDPS 

�Built In Redundancy 

�Capacity Upgrade on 

Demand 

�Capacity Backup 

�Hot Pluggable I/O 


12 

11 1 

10 

2 

9 

3 

8 

4 

7 5 

6 

�Addresses Planned and 

Unplanned HW/SW Outages 

�Flexible, Nondisruptive 

Growth 

�Capacity beyond largest CEC 

�Scales better than SMPs 

�Dynamic Workload/Resource 

Management 



12 

11 1 

10 2 

9 

3 

8 

4 

7 5 

6 

12 

1 11 

2 10 

3 

9 

4 

8 

5 7 

6 

Site 1 Site 2 

�Addresses Site 

Failure/Maintenance 

�Sync/Async Data Mirroring 

�Sync (PPRC) – 100km 

�Async (XRC) – any distance 

�Eliminates Tape/Disk SPOF 

�No/Some Data Loss 

�Application Independent 



What is the Difference between shared vs. nonshared 

Architecture? 

Appl 

A 

z/OS 

Appl 

B 

Appl 

C 

SHARED I/O 

Linux 

Other 

Applns 

System z server 

�Dynamic allocation of I/O to 

partitions 

�Full I/O sharing across 

partitions 

�CPU Shared across LPARs 

�High Availability 

�Effective Usable Capacity 

�Utilization up to 100% 

�Linux Virtual Servers 


CROSS LPAR 

COMMUNICATION VIA 

MEMORY BUS USING 

HiperSockets 

Less 

Capacity 

needed 

OLTP 

OLTP 

WEB 

BATCH 

DOMINO 



BI 

Appl Appl 

A 

B 

CROSS SYSTEM 

... 

COMMUNICATION VIA LAN 

UNIX UNIX 

SHARED NOTHING 

Appl 

C 

UNIX 

Common Deployments 

�Fixed allocation of I/O 

per system 

�Often I/O sharing 

across system 

�Fixed allocation of CPU 

capacity 

�Availability Issues 

�LESS Usable Capacity 

�Utilization per system 

~ 20-40% 



How does the Mainframe lead in Virtualization? 

Mainframes – the Innovator and Leader in Virtualization Technology 

“We found the mainframe to be the 

first and only one to address the 

whole enterprise virtualization and 

management challenge in a 

comprehensive manner. It therefore 

clearly moves the virtualization 

‘state-of-the-art’ well beyond other 

vendor offerings.” 

Ian Bramley, Managing Director, 

Software Strategies 


Innovation and refinement of virtualization for nearly 

40 years 

– Virtualization technology invented by IBM in 1967 

– Hardware- and software-based for optimum performance 

and flexibility 

– Share resources among various applications 

z/VM Virtualization to simplify your IT infrastructure 

– Run hundreds of “virtual” servers on one physical piece of hardware 

without sacrificing performance 

– Use virtualization to run multiple copies of Linux on the mainframe 

Running Linux on the mainframe combines both the benefits of 

distributed computing with the benefits of the mainframe 

– Reduce time and cost of business growth to help maximize ROI 

More effective management of resources, less complex 

than distributed, and more control over infrastructure equal 

lower cost. 





How can I afford a System z Mainframe? 

Can you afford not to have one is the better question 

Often times, customers find the 

mainframe offers the lowest TCO 

Multiple hardware and software pricing options to suit 

your business 

– System z provides variable hardware and software pricing 

metrics to better align costs with resources consumed and 

utilization 

– Aggressive software pricing for new workloads 

Add capacity either permanently or temporarily 

– For seasonal demand 

– For backup / recovery purposes 

Some customers are finding that the mainframe can be less 

expensive to operate. One customer replaced its Intel ® 

servers with a System z9 mainframe that had the new features. 

At the end of this technology rollout, this customer will save on 

their software budget… without impacting their capacity 

growth. "The mainframe really delivered on its promise for 

this customer.“ 

Jim Sellinger, VP of Technical Sales Support, Americas 




Other 

7% 

People 

14% 

Hardware 

65% 

Software 

14% 

1995 

People expense has tripled as a % 

Software expense has doubled as a % 

Hardware is less than 1/3 of its original % 

Mainframe hardware, software, and labor 

costs have decreased 17.3% per year 



Who will manage my Mainframe? 

The Mainframe Charter: IBM’s long-term plan and commitment to the System z platform. 

Innovation 

Value 

Community 

� Lead through innovation to support 

increasingly integrated, flexible business 

processes for the On Demand Business. 

� Enhance the value proposition and lower the 

cost of mainframe computing solutions in a 

way that is compelling, clear, and consistent. 

� Support programs to foster vitality in the 

mainframe community, helping to promote a 

strong application portfolio, greater access 

to skills, and world-class support services. 

IBM is committed to training 20,000 new students 

on the mainframe by 2010 

Currently, 10,000 students have been trained worldwide. 

China has stated it will train an additional 

10,000 students by 2007. 


400 

350 

300 

250 

200 

150 

100 

50 



0 

Dec-04 Dec-04 

# of Schools Enrolled in System z 

Academic Initiatives 

Mar-05 Mar-05 

Jun-05 Jun-05 

Sep-05 Sep-05 

Dec-05 Dec-05 

Mar-06 Mar-06 

Jun-06 Jun-06 

“z/OS has blown me away in terms 

of polish and usability.” 

– IBM Mainframe Contest 

student participant, 

Michigan State University 

Sep-06 Sep-06 

© 2004 IBM Corporation 45 

Dec-06 Dec-06


Our Customers agree – there’s nothing like a Mainframe 

Dundee City Council 

Hannaford Brothers 

“95% of the Fortune 500 companies continue to use mainframes, and about 

2/3 of all business transactions for U.S. retail banks run on them.” 


From distributed to the mainframe 

Based on a five year period, the council realized that the cost savings associated with 

an IBM mainframe were considerable and by far the best option available. 

Centralizing workload from the distributed to the mainframe 

"It's easier to manage the mainframe than a bunch of Windows servers. We have a 

smaller staff running the mainframe and those functions run 80 percent of our business. We 

used to be fairly distributed, but the difficulty of managing thousands of distributed servers 

was just a nightmare. In the past five years we've made an effort to make everything we 

can centralized." Bill Homa, CIO, Hannaford Brothers 

First National Bank of Omaha 

On the mainframe from the beginning 

“If you look at the business world, look at what’s happened in the past 30 years, and look 

where its going in the next 30 years, what you're always going to see is that the 

mainframe is the most reliable platform.” Ken Kucera, First National Bank of Omaha 

Hardware Today: “Mainframes are Here to Stay” ServerWatch.com 2/06 




Enterprise Software Solutions for System z Servers 

Across Industries, supporting the Mainframe as the Enterprise Data Server 

2001 1Q 

2001 2Q 

2001 3Q 

2001 4Q 

2002 1Q 

2002 2Q 

2002 3Q 

2002 4Q 

2003 1Q 

2003 2Q 

2003 3Q 

2003 4Q 

2004 1Q 

2004 2Q 

2004 3Q 

2004 4Q 

2005 1Q 

2005 4Q 

Current 

Cumulative Count 

Growth of ISVs and applications 

compatible with to the the mainframe Mainframe 

0 100 200 300 400 500 600 700 800 

50 ISV 150 Count 250 350 Application 450 550 Count 650 

ISV Count Application Count 

750 

Now listing 306 ISVs with 856 applications! 




“We expect that the availability of Cúram on 

zSeries ® will enable many social enterprises to 

quickly leverage existing resources to deliver 

greater client value.” 

Ernie Connon, President Cúram Software, Inc. 



…Why NOT the Mainframe? 

Mainframes run applications that run my business 

Used by 95% of the Fortune 500 Companies 

80% of corporate data resides or originates on mainframes 

Mainframes are secure 

2/3 of business transactions for U.S. retail banks run directly 

on mainframes 

Mainframes are dependable and available 

Less than 5 minutes down time per year 

Mean time to failure is 40 years 

Mainframes are expandable, adaptable and flexible 

Add capacity and software updates without a reboot 

Respond automatically to spikes in workload demands 

Align processing priorities with business priorities 

Mainframes are virtualized 

Run hundreds of virtual servers concurrently 

Mainframes often offer the lowest TCO 

Potential business advantages through ease of management, 

software pricing, and long term reduction of IT costs 

Mainframe education is expanding worldwide 

Over 230+ schools are teaching mainframe education 

10,000 students received mainframe education since 2004 






Learn more about System z…. 

See how an IBM mainframe can help your 

business at ibm.com/systems/z 

Lean more about: 

– IBM’s z/OS Operating System for System z servers 

– Security 

– High availability with Parallel Sysplex 

– Linux on System z 

– z/VM virtualization 

Learn more about: 

– Latest hardware/software advances 

– Information about Independent Software Vendors, applications, and more 

– Education 

Learn more about: 

– IBM Academic Initiatives @ www.ibm.com/university/zseries 

– Success stories @ www.ibm.com/systems/z/solutions 

– z/OS Basic Skills Information Center @ 

http://publib.boulder.ibm.com/infocenter/zoslnctr/v1r7/index.jsp 

– IBM’s z/OS graphical interface @ 

http://www.ibm.com/servers/eserver/zseries/zos/zmc/ 






The IBM Education Assistent 

What’s the IBM Education Assistant? 

Framework to host short focused multi-media education content 

Simple, short, 

focused 

education 

modules 

Easy-to-use 

interface & 

navigation 

Multi-media 

content with 

audio 



Available 

24x7 – On 

demand or 

downloadable 

Caters to 

novice to 

advanced 

clients 




When to use IBM Education Assistant 

Get an overview or 

more in-depth 

understanding of a 

particular product 

or technology. 

Visually learn how 

to complete a 

specific task or 

configuration. 



Use IBM software 

products to 

complete a practice 

lab scenario. 




z/OS IBM Education Assistant Demo 

Formats: 

Presentations – (some are audio-enabled) 

Additional education material – links to external sources of 

product documentation, Redbooks, and whitepapers 

English 




IBM Education Assistant for z/OS 



http://publib.boulder.ibm.com/infocenter/ieduasst/stgv1r0/index.jsp 






Education Assistant – Enhanced PSP 





A fresh Look at the Mainframe 



The IBM System z Roadshow 





55

IBM System z Roadshow 





The worldwide IBM System z Software Roadshow «A Fresh Look at the Mainframe» will make a stop in Zürich! 

Don’t miss this unique Opportunity and visit the English spoken Sessions which will be run in parallel to 

Software Customer Event. 

Mainframes are especially used to manage complex Calculations and large financial Transactions. The Price of 

such Systems often exceeded 1 Mio. Dollar, and according to a Research done by IDC, the Market for this 

high-end Systems decreased from 19 Mrd. Dollar in 2000, down to 12 Mrd. Dollar. 

The Systems are known to be complex in Terms of Handling, and they require highly skilled personal for 

Installation, Maintenance and Operation. 

In April 2006, IBM presented an Entry-Level System priced with 100’000 Dollar, which is especially customized 

for smaller Companies. 

In Addition, IBM now wants to simplify the Operating System and the Programming Language to bring it in Line 

with the operational Facilities of other Systems. 

To achieve this Target, IBM has planned to invest about 100 Mio. Dollar in the next 5 Years. 


IBM System z Roadshow Details 

Datum: Mittwoch, 8. November 2006 

Ort: IBM Forum Schweiz, Zürich-Altstetten, Vulkanstrasse 106 

Anmeldung: http://www.ibm.com/ch/events/kundentagung 





09.30 – 10.30 Der neue Mainframe – im strategischen Zentrum Ihrer Unternehmensoperation 

Erleben Sie anhand eines On Demand Fallbeispieles der Versicherungsbranche, welches 

Potenzial im Systems z steckt. Sie erfahren darüber hinaus, wie man existierende Assets 

mit Web Services weiternutzen kann, um eine höhere Flexibilität zu erreichen. 

11.00 – 12.00 Leistungsfähige Tools für die Applikationsentwicklung und Monitoring-Umgebungen 

Mit Websphere Tools lassen sich COBOL/CICS Anwendungen kompilieren und prüfen oder 

Java Anwendungen erstellen, welche im WS Application Server eingesetzt werden können. 

Lernen Sie zudem, wie Sie mit Tivoli ® Enterprise-Portal Ihre Mainframe-Umgebung 

überwachen können. 

13.00 – 13.45 Information Management On Demand 

Diese Session zeigt auf, wie Sie Daten, die geografisch und zeitversetzt verteilt sind, mithilfe 

von DB2® und Information Integration jederzeit mit hoher Leistung für andere zugänglich 

machen können. Erhalten Sie zudem einen Überblick über andere DB2 Tools. 



13.55 – 14.40 Mainframe-Architektur und -Design 





Ein Mainframe, der autonom Entscheidungen treffen kann, um Service Level Agreements zu 

erfüllen und Kosten zu sparen? Ja, das gibt’s – erfahren Sie mehr in diesem spannenden 

Vortrag, der auch auf das Policy Management und die Automation eingeht. 

14.50 – 15.35 Sicherheit und Disaster Recovery in der Mainframe On Demand Umgebung 

In dieser Präsentation werden die spezifischen Anforderungen an Mainframes in Disaster- 

Situationen dargelegt. Ein geografisch zerstreuter paralleler Sysplex® ist in so einer Situation 

die ideale Lösung. System z Security liefert Ihnen zusätzlich eine sichere Infrastruktur, um Ihr 

System gegen Angriffe zu schützen und die Datenintegrität zu sichern. 

15.45 – 16.30 Warum der Mainframe zu den günstigsten IT-Plattformen zählt 

Das Referat zeigt Ihnen auf, welche Kosten ein Mainframe im Gegensatz zu anderen 

Plattformen verursacht. IBM System z unterstützt die Server-Konsolidierung und virtualisierung 

auf höchstem Niveau zu einem unschlagbaren Preis-Leistungs-Verhältnis! 







Diese Referenten präsentieren Ihnen die spannenden Vorträge zu strategischen, technologischen und operativen 

Themen rund um Mainframe und IBM System z Software: 

David Rhoderick 

ist ein «Mainframe Evangelist» des «Competitive Project Office» der IBM Software Group. Er ist auf Verteilung, 

Konfiguration und Installation von Software sowie auf die finanziellen Aspekte des Mainframe-Einsatzes 

spezialisiert. David Rhoderick ist seit 31 Jahren bei IBM und war unter anderem massgeblich an der Entwicklung 

des OS/2 Betriebssystems für PCs beteiligt. 

Innes Read 

ist wie David Rhoderick «Mainframe Evangelist» beim «Competitive Project Office» der IBM Software Group. 

Seine Kernkompetenz sind die CICS Produkte von IBM sowie die Thematik der Transaktionsverarbeitung. Weitere 

Spezialgebiete sind Open Source, Linux und Virtualisierung. 

John J. Thomas 

ist Senior Software Engineer beim «Competitive Project Office» der IBM Software Group. Seit einigen Jahren 

befasst er sich mit der technischen Analyse der NET Technologie von Microsoft im Vergleich mit der Middleware 

von IBM. Derzeit bringt er frischen Wind in die Mainframes und entwickelt darüber hinaus SOA-Lösungen und 

Entwicklungs-Tools für IBM System z. 









60

IBM System z9 FICON Express4 



Developed to improve Capacity and Performance of FICON/FCP Channels to 4 Gbps 

� Up to 25% improvement in FICON channel throughput when processing a mix of read and write 

data transfers 1 

� Up to 65% improvement in FICON channel throughput when processing all read or all write data 

transfers 1 

� 220% cumulative MB/sec throughput improvement in DB2 table scan tests for extended format 

data sets with FICON Express4 on z9 EC with the MIDAW facility compared to FICON Express2 

with the IDAW facility on z9-109 2 

Helps to support reduced cost of storage operations and shorter backup windows 

with faster channel link data rates 

Enables migration to higher performance with 1/2/4 Gbps auto-negotiating links 

1. Large sequential data transfers on z9 EC with FICON Express4 operating at 4 Gbps (running z/OS V1.7) when compared to FICON Express2 on z9-109 (running 

z/OS V1.6) 

2. Results of internal DB2 table scan tests with the z9 EC, the MIDAW facility, FICON Express4 operating at 4 Gbps (running z/OS V1.7), and the DS8000 

compared to z9-109, and FICON Express2 operating at 2 Gbps (running z/OS V1.6) 


Expertforum IBM System CH #64, z9 9.-10.5.2006, 

– The Enterprise Hub 



Transparent Auto-Negotiate 1, 2, 4 Gbps 

Small Form Factor (independent repair) 

FC or FCP, Shared and Spanned 

Support Cascaded Directors 

No FCV - FICON Bridge 

LC Duplex 

LX 

or 

SX 



FC3321 - FICON Express4 10KM LX 

– 10 KM (6.2 miles) unrepeated 

– 4 PORT 

– 9/125 micron single mode fiber 

FC3322 FICON Express4 SX 

– 55-860 Meters unrepeated, depending on Fiber and 

Speed 

– 4 PORT 

– Supports 50/125 or 62.5/125 micron multimode 

fiber 

FC3323 FICON Express4-2C 4KM LX 

– 4 KM (2.48 miles) unrepeated 

– 2 PORT 

– 9/125 micron single mode fiber 

FC3324 FICON Express4 4KM LX 




z9 BC only 

No RPQ 8P2295 FCV (FICON Bridge) support on z9 BC 

© 2004 IBM Corporation 62 

( m in.) 

FLASH 

FLASH 

( m in.) 

FLASH 

QDR 

SRAM 

FLASH 

NEW! 

QDR 

SRAM 

FLASH 

QDR 

SRAM 

FLASH 

QDR 

SRAM


Data Performance 

14000 

12000 

10000 

8000 

6000 

4000 

2000 

I/Os per second* 

4k block size, Channel 100% utilized 

0 



350 

300 

250 

200 

150 

100 

50 




0 

MB/sec throughput (Full Duplex)* 

Large Sequential R/W mix 

17 

74 74 

120 

170 

270 

Escon Ficon G5/G6 

350 

Ficon z900 Ficon Express - 1GB/s 

Ficon Express - 2GB/s Ficon Express2 - 2GB/s 

Ficon Express4 - 4GB/s 


IBM Storage ready for System z9 and FICON Express4 

IBM System z9 and IBM storage 4 Gbps FICON/FCP connectivity may help to: 

� Support faster link speeds and shorter backup windows 

� Enable channel and link consolidation to help simplify management and reduce the cost of the 

storage infrastructure 

� Support easier migration to 4 Gbps bandwidth with auto-negotiating links 

IBM has a full range of Disk, 

SAN, Tape, Software, & Services 

for System z9 


Disk 

SAN 

Virtualization 

* All statements regarding IBM’s future direction and intent are subject to 

change or withdrawal without notice, and represent goals and objectives only. 


Tape 

DS8000 – 4 Gbps FICON/FCP Planned 2Q06* 

DS6000 – 2 Gbps FICON/FCP 




IBM SAN256B and SAN32B-2 4 Gbps FCP, FICON planned 2Q06 

IBM SAN 140M, SAN32M and SAN256M (Planned 2006*) 4 Gbps 

FICON/FCP 

Cisco MDS 9500 and 9216 4 Gbps FICON/FCP 

IBM SVC 4 Gbps FCP for Linux on System z Planned 2Q06* 

VTS 2 Gbps FICON/FCP 

TS7510 Virtualization Engine – 2 Gbps FCP for Linux on System z 

Planned 2Q06* 

IBM TS1120 4 Gbps FCP Tape Drive 

IBM TS1120 Tape Controller 4 Gbps FICON Planned 2Q06* 

IBM LTO Gen 3 - 4 Gbps FCP for Linux on System z Planned 2006* 

IBM 3494 and 3584 Tape Libraries 

IBM TS3310 Tape Library - 4 Gbps FCP for Linux on System z 

Planned 2Q06* 


Modified Indirect Data Address Word (MIDAW) Facility 

z9 BC and z9 EC – Enhanced performance on FICON 

MIDAW facility – a new System Architecture and Software Exploitation designed 

to improve FICON Performance 

� Can improve FICON performance for 

- Extended format data sets – including DB2 and VSAM 

� Can improve channel utilization and can significantly improve I/O response times 

- Internal IBM DB2 Table Scan tests(*) with the z9 EC, FICON Express2 and the DS8000 control unit 

comparing MIDAW facility configurations to pre-MIDAW configurations showed: 

� 36% to 58% reduction in response times 

� 35% to 56% reduction in channel busy 

� 56% to 126% improvement in I/O throughput 

– Supported on z/OS 1.6 and above and corresponding supporting devices 

* Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance 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 or performance improvements equivalent to the numbers 

stated here. 







Parallel DB2 Table Scan, EF 4K (single channel) 

5 

4 

3 

2 

1 

0 

I/O Response Time (sec) 

pend connect 

1 2 3 1 2 3 

Number of DB2 partitions 


Configuration: 

MIDAW : z/OS 1.7 

Pre-MIDAW: z/OS 1.4 

DB2 for z/OS Version 8 

4000 byte row size 

System z9 EC 

FICON Express2 

2 Gbit/sec link 

DS8000 control unit 

Throughput 

(MB/sec) 

pre-MIDAWs MIDAWs 

Channel 

Busy% 

200 

150 

100 




50 

0 

100 

80 

60 

40 

20 

0 

1 2 3 


1 2 3 


� This document contains performance information 

� Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance 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 or performance improvements 

equivalent to the numbers stated here. 



MIDAW Facility Details 

The Modified Indirect Data Address Word (MIDAW) Facility is a Modification to a 

Channel Programming Technique that has existed since S/360 Days 

� MIDAWs are a new method of gathering/scattering data into/from discontiguous storage locations 

during an I/O operation 

� Extended MIDAWs require the IBM® System z9 server and z/OS® Release 1.7 (or APAR 

OA10984 with Release 1.6) 

� MIDAWs are implemented by the Media Manager (M/M) 

� To take advantage of M/M, users must use dataset types, such as Linear Data Sets and 

Extended Format datasets that enable the system to use M/M 

� Tuning of the MIDAW facility is simple: Just make sure that the processor and operating system 

are at the correct level, and use data set types which enable the system to use M/M 

� The use of MIDAWs will not cause the bits to move any faster across the FICON link, but they 

reduce the number of frames and sequences flowing across the link, which makes the channel 

more efficient 








The most significant Performance Benefit of MIDAWs is achieved with Extended 

Format (EF) Datasets 

� Extended format (EF) datasets have been introduced in 1993 

� Both VSAM and non-VSAM (DSORG=PS) datasets can be EF 

- In the case of non-VSAM datasets, a 32-byte suffix is appended to the end of every physical record (i.e. 

block) on DASD 

- VSAM, appends the suffix to the end of every Control Interval (CI), which normally corresponds to a 

physical record 

- This suffix is used to improve data reliability and facilitates other functions 

� Besides reliability, EF datasets enable three new functions: 

- DFSMS Striping 

- Access Method Compression 

- Extended Addressability (EA) 








Media Manager (M/M) and the ECKD (Extended Count Key Data) Architecture 

� The main objective of M/M is to shield middleware and most operating system components 

from device dependencies 

� ECKD is a heritage architecture which z/Architecture inherited from S/360 

� CKD facilitates variable length records and keyed records on DASD 

� M/M requires that data sets have fixed length records and no keys 

� Over the years z/OS (and its legacy systems) has changed to fixed length non-keyed data sets 

in order to adapt to M/M’s requirements 

- When using Extended Format, the QSAM and BSAM access methods will map the logical variable length 

blocks to fixed length blocks in order to use M/M 

- All EF data sets use M/M, both non-VSAM and VSAM 

- Since z/OS 1.3, VSAN non-EF datasets also use M/M 

- So, when using traditional DSORG=PS datasets, it is important to use EF, but with VSAM it doesn’t 

matters 








Media Manager (M/M) and the ECKD (Extended Count Key Data) Architecture 

� M/M has always been used for linear VSAM datasets, such as those used by DB2, z/FS file 

systems, and the System Logger used by CICS®. HFS and PDSEs use M/M 

� PDS’s do not use M/M (because a PDS directory contains keyed records) 

- Consequently it is advantageous to convert all PDSs to PDSEs, including all program libraries 

- It is also good to convert all SAM datasets to Extended Format 

- BDAM cannot use M/M or EF data sets 

- It is better to use BSAM or VSAM in place of BDAM 

- IMS OSAM does not use M/M 

- For optimal sequential I/O it is better to use VSAM than OSAM (although OSAM does have less CPU 

overhead than VSAM) 

� When using EF datasets, M/M supplies the storage for the 32-byte suffix and automatically 

appends the suffix to the user’s data 








z/Architecture Channel Programs 

� In order to understand what MIDAWs are, and why they 

are important to FICON performance, it is helpful to review 

the channel programming architecture of zSeries, which 

mostly dates back to the days of S/360 

� An I/O operation is represented by a channel program 

� A channel program consists of a series of CCWs (Channel 

Command Words) which form a chain 

� Media manager uses format 1 CCWs 

� The command code specifies to the channel subsystem 

and the I/O device the operation to be executed, and the 

count field specifies the number of bytes to transfer 

� When the channel subsystem has completed the transfer of information specified by a CCW, it 

can fetch the next CCW 

- Such fetching is called chaining, and the CCWs belonging to such a sequence are said to be chanied 








z/Architecture Channel Programs 

� Two types of chaining are provided: chaining of data and chaining of commands 

� One flag in the CCW indicates data chaining and one indicates command chaining 

� The last CCW of a channel program is one where both chaining flags are off 

� Unless the IDA flag is set, the data address in the CCW points directly at a continuous segment 

of real storage 

� Since ranges of virtual addresses may span discontiguous real 4 KB frames, direct addressing 

cannot generally be used to address more than 4 KB 

Indirect Addressing 

� Indirect Data Addressing (IDA) permits a single CCW to control the transfer of data that spans 

non-contiguous 4 KB frames in main storage 

� When the IDA flag is set, the data address in the CCW points to a list of words (IDAWs), each of 

which contains an address designating a data area within real storage 








Indirect Addressing 

� Prior to MIDAWs, Media Manager used 

Format 2 IDAWs, which enabled it to use 

data addresses above 2 gigabytes (real 

addresses) 

� Format 2 IDAWs designate 4 KB chunks; 

so there is one IDAW for every 4 KB 

� The number of IDAWs is determined by 

however many IDAWs are needed to 

satisfy the count field in the CCW 

� The first IDAW can designate any 

location, but all subsequent IDAWs must 

point at 4 KB boundaries 

- Eliminating this restriction is an essential 

feature of MIDAWs 







Control of IDAWs 


� MIDAWS data transfer is passed to the next IDAW when a 4 KB boundary is reached, but the 

CCW is considered complete when the number of bytes transferred is equal to the count field 

specified in the CCW 

� The MIDAW facility is a conceptually a simple modification to IDAWs 

� MIDAWs remove the 4 KB boundary restrictions of IDAWs 

� A MIDAW is not just an 8 byte pointer, but rather it is 16 bytes, including an 8-byte pointer and a 

two-byte count field 

� The last bit in the flag byte of the CCW indicates that the data address points at a MIDAW list 

� The sum of all MIDAW counts must sum to the CCW count 








Record-Level versus Track-Level Channel Commands 

� Channels communicate with a device over a channel “link” or “path” 

� Output data is received by the device and packaged into “records”, which are grouped into 

“tracks” 

� S/360 architecture defined “record-level” command operations, not-track level operations 

� Although the z/Architecture allows partial records to be read, the CCW count field must match 

the record length when updating a record 

� In 1999 z/Architecture quietly introduced the concept of “track-level” command operations in 

conjunction with the 2105 control unit model (i.e. Shark or ESS) 

� Media Manager implemented track-level commands 

� When using a track-level command to read data, the DASD control unit will allow a single CCW 

to read multiple records 

� When using a track-level command to update data, the DASD control unit will allow a single 

CCW to update multiple records that reside on the same track, while at the same time 

prohibiting a partial record update 









� Track-level operations are beneficial because they potentially reduce the number of CCWs 

� As the data transfer speeds increase, the channel engine overhead of each CCW represents a 

larger impact 

� However, at first these track-level operations didn’t achieve what they were intended to achieve, 

at least not with FICON channels, because the command chaining within a track had to be 

replaced by data chaining 

� IDAWs are not applicable due to the 4 KB boundary restrictions of IDAWs 

� For example, to read 12 4 KB records from a non-EF data set on a 3390 track, Media Manager 

chained 12 CCWs together using data chaining 

� To read 12 4 KB records from an EF data set, the Media Manager data-chained 24 CCWs 

together (2 CCWs per 4 KB record) 

� Using MIDAWs, M/M can transfer a whole track using a single CCW 

� To span multiple tracks in one channel program, command chaining was used, and still is used 

� However, with the advent of MIDAWs, M/M no longer uses data chaining 









� If track-level CCWs were the foundation for improved FICON performance, MIDAWs represent the 

building that rests upon the foundation 

� In other words, the value of track-level CCW operations was severely constrained prior to MIDAWs 

MIDAWs improve the Performance 

� MIDAWs and IDAWs have basically the same performance characteristics; both perform better 

than data chaining 

� There are two reasons 

- One reason pertains to the number of CCWs used, which in turn affects the number of frames sent across 

the link 

- By reducing the number of frames, it takes less time for the FICON channel and the control unit host adapter 

- The second reason pertains to FICON multiplexing and the fact that MIDAWs removes some of the data 

chaining activity on the link 

- Multiplexing only affects performance when there are concurrent I/Os on the channel 







Summary 

� The MIDAW facility achieves superior performance for a large variety of workloads by improving 

the efficiency of the channel subsystem 

� Since MIDAWs are only used by the Media Manager, and MIDAWs only benefits small record 

sizes, only certain types of data sets are beneficiaries 

� Some examples of data sets which are accessed through Media Manager are VSAM data sets 

(including all linear data sets), Extended Format data sets, and PDSEs 

� The most benefit occurs with Extended Format data sets that have small block sizes 

� Since DB2 depends on Extended Format data sets to stripe the logs, or to enable data sets to be 

larger than 4GB, DB2 is a major beneficiary 

Documentation 


� For more information on the IBM System z9 MIDAW facility and its performance refer to the 

following redpaper: 

- MIDAW Performance with FICON Channels using DB2 and other Workloads, REDP-4201-00 






IBM eServer zSeries 

990 – z990 (2084) 

Announced 5/03 – first zSeries 

Superscalar Server 

4 models – Up to 32-way 

Specialty Engines 

– CP, IFL, ICF, zAAP 

On Demand Capabilities 

– CUoD, CIU, CBU, On/Off 

CoD 

Memory – up to 256 GB 

Channels 

– Four LCSSs 

– Up to 1024 ESCON 

channels 

– Up to 240 FICON Express2 

channels 

– Token-Ring, GbE, 

1000BASE-T Ethernet 

– Coupling Links 

Crypto Express2 

Parallel Sysplex clustering 

HiperSockets – up to 16 

Up to 30 logical partitions 

Operating Systems 

– z/OS, z/VM, VSE/ESA, 

z/VSE, TPF, z/TPF, Linux 

on zSeries 


IBM eServer 

zSeries 890 – z890 

(2086) 

Announced 4/04 – zSeries 

Superscalar Server for mid range 

1 model – Up to 4-way 

– 28 capacity settings 


– CP, IFL, ICF, zAAP 


– CUoD, CIU, CBU, On/Off 

CoD 


Channel 

– Two LCSSs 

– Up to 420 ESCON 

channels 

– Up to 80 FICON Express2 

channels 

– Networking Adapters 

(OSA) 


Cryptographic Coprocessors 



Up to 30 partitions 


– z/OS, z/OS.e, z/VM, 

VSE/ESA, z/VSE, TPF, 

z/TPF, Linux on zSeries 




IBM System z Family 

IBM System z9 

EC – z9 EC (2094) 

Announced 7/05 


5 models – Up to 54-way 

Granular Offerings for 8 CP engines 

and below 


– CP, IFL, ICF, zAAP, zIIP 


– CUoD, CIU, CBU, On/Off CoD 


Channels 

– Four LCSSs 

– Multiple Subchannel Sets 

– MIDAW facility 

– 63.75 subchannels 

– Up to 1024 ESCON channels 

– Up to 336 FICON channels 

– Enhanced FICON Express4 

Gbps 

– 10 GbE, GbE, 1000BASE-T 


Configurable Crypto Express2 




Enhanced Availability 


– z/OS, z/VM, VSE/ESA, z/VSE, 

TPF, z/TPF, Linux on System z 

IBM System z9 

BC – z9 BC (2096) 

Announced 4/06 


2 models – 7 configurable PUs 

Extreme Granularity 


– CP, IFL, ICF, zAAP, zIIP 


– CUoD, CIU, CBU, On/Off CoD 


Channels 

– Two LCSSs 

– Multiple Subchannel Sets 

– MIDAW facility 

– 63.75 subchannels 

– Up to 420 ESCON channels 

– Up to 112 FICON channels 

– Enhanced FICON Express4 

Gbps 

– 10 GbE, GbE, 1000BASE-T 


Configurable Crypto Express2 




Enhanced Availability 


– z/OS, z/OS.e, z/VM, VSE/ESA, 

z/VSE, TPF, z/TPF, Linux on 

System z 



IBM System z9 Operating System Support 

System z9 Minimum Operating System Support for Functions (1) 

Basic System z9 support 

60 Logical Partitions (30 for z9 BC) 

63.75K Subchannels 

OSA-Express2 1000BASE-T Ethernet 

MIDAW Facility 

AIX ® 

CPACF Enhancements 

Crypto Express2 exploitation 

HiperSockets IPv6TCP/IP 

OSA-Express2 Large send 

OSA-Express2 CDLC support 

Multiple Subchannel Sets (MSS) 

FICON Link Incident Report 

Single System Image 

Enhanced Perf Assists for z/VM Guests 

z/OS.e 

z/OS 

1.4 (4) 

1.4 (4) 

1.6 

1.6 (4) 

1.6(4) 

1.7 

1.6 

1.4 (4) 

1.7 

1.7 

1.6 up 

to 32 

N/A 

HiperSockets 

SLES 9 SP2 

IBM work with LDPs 

z/OS 

(3) 

SLES 9 

5.2 

N/A 

Not supported 

5.1 

SLES 9 SP3 

RHEL 4 U3 

5.1 

SLES 9 SP3 (5) 

RHEL 4 U3 (5) 

z/VM 

Linux on 

System z 

4.4 

SLES 9 

RHEL 4 

4.4 

SLES 9 

RHEL 4 

4.4 

SLES 9 

RHEL 4 

4.4 

SLES 9 

RHEL 4 

Not supported 

N/A 

4.4 

Not supported 

4.4 

5.1 up 

to 24 

5.2 

IBM work with LDPs (3) 

IBM work with LDPs 

SLES 9 up to 32 

RHEL 4 up to 32 

(3) 


1. indicates VSE/ESA 

2. indicates TPF 

3. IBM is working with its Linux Distribution Partners (LDPs) that this function will be provided in future 

Linux on System z distribution releases/service updates 

4. Additional features or Web downloads required 

5. IBM is working with LDPs on Kernel space exploitation (3) 

Note: Please refer to the latest PSP bucket for latest PTFs for new functions/features z/OS.e - z800, z890 and z9 BC only 

1.4 (4) 

1.4 (4) 




z/VSE 

VSE/ESA (1) 

3.1 

2.7 (1) 

3.1 

3.1 

2.7 (1) 

3.1 

3.1 

2.7 (1) 

3.1 

2.7 (1) 

z/TPF 

TPF (2) 

1.1 

4.1 (2) 

1.1 

4.1 (2) 

1.1 

4.1 PUT 13 (2) 

New Engine 

1.1 

1.1 up 

to 54 

SLES = SUSE Linux Enterprise Server 

RHEL = Red Hat Enterprise Linux 



IBM System z9 Operating System Support 

System z9 Minimum Operating System Support for Functions (2) 

N_Port ID Virtualization 

FCP Program Directed re-IPL 

sub-capacity 

AIX ® 

zIIP Support 

Crypto Remote Key Loading 

Crypto ISO 16609 

TCP/IP 

FICON Express4 (CHIPD type FC) 

FICON Express4 

(CHIPD type FCP) 

z/OS.e 

z/OS 

N/A 

N/A 

1.4(4) 

1.6 

1.6 (4) 

1.6 (4) 

1.4 (4) 

N/A 

4.4 (guest) 

Not supported 

4.4 

Not supported 

5.1 

5.1 

4.4 

4.4 

SLES 9 SP3 


SLES 9 SP3 


HiperSockets 

Linux on 

System z 

IBM Software Group 

products are enabled (6) 

N/A 

N/A 

N/A 

SLES 9 

RHEL 4 

SLES 9 

RHEL 4 

1. indicates VSE/ESA 

2. indicates TPF 

3. IBM is working with its Linux Distribution Partners (LDPs) that this function will be provided in future 

Linux on System z distribution releases/service updates 

4. Additional features or Web downloads required 

5. IBM is working with LDPs on Kernel space exploitation (3) 

Note: Please refer to the latest PSP bucket for latest PTFs for new functions/features z/OS.e - z800, z890 and z9 BC only 

z/VM 

z/OS 




z/VSE 

VSE/ESA (1) 

3.1 

3.1 

2.7 (1) 

Not Supported 

3.1 

2.7 (1) 

3.1 

z/TPF 

TPF (2) 

1.1 

4.1 16 (2) 

Not supported 

New Engine 1.1 

4.1PUT 16 (2) 

SLES = SUSE Linux Enterprise Server 

RHEL = Red Hat Enterprise Linux 









82

z/OS Support Summary 

z/OS 

1.1 

1.2 

1.3 

1.4 

1.5 

1.6 

1.7 

1.8 

1.9* 

G5/G6 

Multiprise ® 

3000 

x 

x 

x 

x 

x 


z900 

z800 

x 

x 

x 

x 

x 

x 

x 

x 

x 

z990 

z890 

x c 

x c 

x 1 

x 

x 

x 

x 

x 

z9 EC 

z9 BC 



x 

x 

x 

z/OS Planning Information 

x 1 

x 

x 

DS8000 

DS6000 

x 

x 

x 

x 

x 

x 

End of 

Service 

3/04 

10/05 

3/05 

3/07 

3/07 

9/07 

9/08* 

9/09* 

9/10* 

Coexists 

with z/OS 

1.4 

1.5 

1.6 

1.7 

1.8 

1.8* 

1.9* 

1.10* 

1.11* 

z/OS 1.5 , z/OS 1.6, and z/OS 1.7 are planned to coexist with z/OS 1.8 

z/OS 1.8 is planned to coexist with z/OS 1.9 and 1.10 

x c - Compatibility support only 

x 1 – IBM eServer zSeries ® 990 (z990) compatibility or exploitation feature required (orderable until December 2006) 

There is no IBM Bimodal Accommodation Offering available for z/OS 1.5 or higher releases. 

Planned 

Ship Date 

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

9/06 

9/07* 


z/OS Planned Roadmap 

Encryption Facility for z/OS 12/05 �� 

z/OS OMEGAMON Mgt Console 12/05 �� 

Enhanced Crypto Support for 1.7 5/06 �� 

zIIP for 1.6/1.7 6/06 �� 

1.6 

1.7 

9/04 

Architectural Level Set 


9/05 

1.8 

9/06 



z/OS Planning Information 

1.9* 

1.10* 

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

9/07 

9/08 


z/OS Statements of Direction (1 of 3) 

Beyond z/OS 1.8 


z/OS Statements of Direction 

z/OS 1.8 is planned to be the last release to support APPC communication 

between HCD and HCM 

� TCP/IP communication remains supported 

z/OS 1.8 is planned to be the last release to include the C/C++ IBM Open Class 

(IOC) Dynamic Link Libraries (DLLs) 

� You should plan to migrate to the standard C/C++ libraries 

� You should consult the IBM Open Class® Library Transition Guide 

In a future release of z/OS Communications Server, support for the in-stack version 

of the TN3270 Server is planned to be discontinued 

� The standalone TN3270 server introduced in z/OS 1.6 offers significant 

advantages, and remains supported 

In a future release, IBM plans to replace the RMF LDAP backend 









IBM plans to make it possible to define a logical partition (LPAR) group capacity limit on System 

z9 servers 

IBM intends to release an X.25 over TCP/IP product that uses the X.25 NPSI enablement 

interface available on IBM Communication Controller for Linux for System z9 and zSeries V1.2 

IBM intends to deliver enhancements to the consoles component in the future, not in 2007 as 

originally planned 

z/OS 1.8 is planned to be the last release that will include the APPC Application Suite in z/OS 

Communications Server 

� Note that APPC itself remains an integral part of z/OS Communications Server's SNA 

functions. There are no plans to remove APPC from z/OS. For more information, see: 

http://www.ibm.com/software/network/commserver/zos/ 







Layer 3 Virtual MAC for z/OS and z/OS.e environments 



� When the associated OSA-Express function is available, the z/OS Layer 3 VMAC function will 

help to simplify the network infrastructure and facilitate load balancing when multiple operating 

system instances are sharing the same OSA port or Media Access Control (MAC) address 

� With Layer 3 VMAC, each operating system instance can now have its own unique "logical" or 

"virtual" MAC (VMAC) address 

� Instead of sharing the same physical MAC address, each TCP/IP stack and its associated IP 

addresses are accessible using their own VMAC addresses. 

Network Traffic Analyzer 

� When the associated Open Systems Adapter (OSA) function is available, the Network Traffic 

Analyzer function will help to provide a new diagnostic trace facility, allowing OSA packet 

trace records to be sent directly to the host operating system 

QDIO Diagnostic Synchronization 

� When the associated OSA function is available, the QDIO Diagnostic Synchronization function 

will help provide system programmers and network administrators the ability to coordinate and 

simultaneously capture both software (z/OS) and hardware (OSA-Express2) traces 






z/OS 1.8 CFRM Performance Improvement 

z/OS 1.8 CFRM Message based Protocol 

With z/OS V1R8, Parallel Sysplex environments can realize significant 

improvements in availability 

The new message-based protocol offers advantages over the existing policy-based protocol 

for Parallel Sysplex configurations that have a large number of structures and structure 

connectors, especially during scenarios involving system failure and coupling facility recovery 

The role of the CFRM couple dataset in a recovery situation 

With the policy-based mode of CFRM processing that exists prior to z/OS V1R8, the CFRM 

couple data set, as the centralized repository for coupling facility resource usage, often 

becomes a bottleneck when recovery for a failed system or coupling facility is required 

� This recovery implies recovery for multiple structures and connectors 

� Each element of recovery requires every surviving system to access the CFRM couple data 

set under serialization, implying that access is limited to one system at a time. Because 

each system potentially must access the CFRM couple data set many times, contention on 

the data set greatly slows the recovery process 






z/OS 1.8 CFRM Message based Protocol… 

The new message-based protocol available with z/OS V1R8 defines a single system as 

“manager” and all other systems as participants in the recovery process 

� The manager system is responsible for coordinating events and confirmations with the 

participant systems, and is also responsible for updating the CFRM active policy, thus 

reducing I/O to the CFRM couple dataset to a single, central control point 

� Communication between the manager system and the participant systems, on which 

applications or subsystems are running, is through XCF signaling 

� Message-based processing applies on a structure basis 

� XCF signaling structures are not eligible to use message-based processing and will 

continue to use the policy-based protocol 

To enable message-based processing, a new version of the CFRM couple data set is required 

The IXCL1DSU format utility supports the new following keyword to indicate that the CFRM 

couple data set is to be formatted to support message-based processing: 

ITEM NAME(MSGBASED) 






z/OS 1.8 CFRM Message based Protocol… 

Once a primary CFRM couple data set that supports message-based processing is active in 

the sysplex, message-based processing can become enabled for each structure for which 

there are no events pending delivery for either the structure or connectors to the structure 

IBM recommends that an installation enable the new message-based processing protocol 

because of the large performance, availability, and scalability benefits that message-based 

processing provides 

Once all systems are at z/OS 1.8 and there is no intention of falling back to z/OS 1.7, 

message-based processing can be enabled and, also non-disruptively, disabled, according to 

the installation's requirements 

The installation can also change the manager system while message-based processing is 

enabled without affecting the sysplex operation 

� This can be done by issuing a SETXCF START Command with the new MSGBASED 

Keyword, as follows: 

SETXCF START,MSGBASED 

For more information, refer to z/OS V1R8 MVS Setting up a Sysplex, SA22-7625-12 




z/OS 1.8 GRS Contention Notification 


z/OS 1.8 GRS Contention Notification 

With z/OS 1.8 Star configurations can choose which system is to act as the 

contention notifying system 

This can be done by using the new CNS Keyword with the SETGRS command, as follows: 

SETGRS CNS=sysname 

All systems in the global resource serialization star complex compatible with z/OS V1R7 

require a PTF for the SETGRS CNS command to work 

If any system in the complex is earlier than z/OS V1R7 or without the PTF installed, the 

command cannot be issued by any member of the complex 

If the contention notification system (CNS) fails, one of the remaining systems automatically 

becomes the new CNS 

An installation might consider automation for the rare case the system moves the CNS 

� If so, key off message ISG364I for the SYSTEM INITIATED cases and set the CNS 

through SETGRS to the system you choose 

It is recommended that installations use the SETGRS CNS=sysname command to prevent the 

GRS contention notification function from being assigned to a possibly low weighted LPAR 











92

APAR's and Red Alerts 

II14067 DFSMS 1.7 PDSE Maintenance Recommendations 

II14219 DB2 z/OS zIIP Exploitation Support Information 

OA14966 (Hiper) ABEND0C4 in ICYDIE 

OA15026 SMSPDSE ABEND0F4 RC24 and ABEND0C1 resulting in a System Outage (IPL required) 

OA15764 SMSPDSE ARA Control Blocks not freed at Task Termination 




APAR's of Interest 

OA15142 Hang when System-managed CF Duplexing Stop Direction changed for Site Recovery Managemen 

OA15126 ABEND073 RC28 IXLM2XSR ARWE Request Lock after IFCC 

OA15364 System Logger Offload Dataset Deletion Management may be inhibited by existing Dataset Allocations 

OA15409 New Function: Permit greater Parellelism in XCF Couple Dataset Access Channel Programs 

OA15906 IXLRT READBYCONN,TCONNAME may return RC8/RSN 80B incorrectly 

OA15968 (Hiper) Updates to zIIP Support 

OA16112 Enable deletion of Structure Dumps via SETXCF FORCE in all cases 

OA16180 ABEND1C5 RSN00090010 in IXGT3LBM during local Buffer Processing due to a zero Buffer Address 

OA16534 System Logger indicates Logstream Recovery failed when it was really successful, IXG210I issued 

OA16139 (Hiper) Excessive Time to initialize SADMP in IPCS.pdf 


APAR's and Red Alerts... 

OA16640 (Hiper) WAIT0A2 RSN15A when System in Basic Mode is joining the Sysplex 

OA16673 Unable to reconnect to ISTGENERIC after a Change in the Policy Size 




APAR's of Interest 

OA17844 SMF IEE393I SMF Physical I/O Error or HFs IGW027E HFS SYNC I/O Error with D/T2094 and MIDAW 

OA17335 zIIP Algorithm Update 

PK26453 CICS 3.1, CICS Storage Creep in ECDSA, Subpool WBGENRAL 









95

Parallel Sysplex Aggregation 

What is Parallel Sysplex Aggregation? 





Sysplex aggregation is a set of rules that IBM have defined that determine the basis that 

will be used when deciding how some z/OS®-related software should be charged 

The concept of sysplex aggregation was introduced when IBM announced Parallel Sysplex and 

the 9672 range of CPCs 2 in 1994 

At its most simplistic, sysplex aggregation allows you to pay for software on two CPCs as if 

those CPCs were in fact a single CPC 

The reason this is attractive is that the software price per additional unit of processing 

power decreases as the CPC size increases 

� As the number of MSUs increases, the incremental cost of each additional MSU gets 

smaller and smaller 

When qualified for Parallel Sysplex Aggregation, there are 2 attractive license models 

� Aggregated Parallel Sysplex License Charge (PSLC) 

� Aggregated Workload License Charge (WLC) 



Aggregation Rules and Criteria 





There are a number of rules and criteria that IBM have specified that determine whether a 

given CPC is eligible for sysplex aggregation 

A very important point is that your systems must always conform to these rules 

� it is not sufficient that they just conform when the CPC is originally installed 

The restatement of the sysplex aggregation criteria specifically states 

- “You must also notify IBM when you believe that your systems no longer qualify for 

pricing under this criteria” 

- The complete restatement announcement is available on the Web at: 

� http://www-306.ibm.com/common/ssi/rep_ca/8/897/ENUS204-268/ENUS204-268.PDF 



Aggregation Requirements 

- Sysplex aggregation hardware requirements: 





The sysplex aggregation criteria break out into hardware, software, and operational 

requirements, as follows: 

� All CPCs in the Parallel Sysplex must have a common time source 

o This means they must all be connected to the same Sysplex Timer® or STP network 

� Because the Sysplex Timer and STP support connection of up to 24 CPCs, it is very 

likely that all your CPCs are already connected to the same common time source 

� All systems in the Parallel Sysplex must be connected to at least one common 

Coupling Facility (CF) 

� You can use either shared or dedicated CPs in your z/OS LPAR’s 



Aggregation Requirements… 

- Sysplex aggregation software requirements: 





� MVS/ESA 5.2.2, OS/390®, or z/OS must be executing in all LPARs that are to be 

considered for aggregation 

� All z/OS, z/OS.e, and OS/390 images that comprise the Parallel Sysplex environment 

must have at least one common systems enablement function activated to use the CF 

across all images in the PricingPlex. Eligible systems enablement functions are: 

o Application data sharing, including: 

- IMS TM: with IMS DB or DB2‚ 

- CICS: with IMS DB, DB2, or VSAM/RLS 

- TSO and DB2 data sharing 

An eligible Independent Software Vendor’s Data Base from Group C of the PSLC 

Exhibit. 

o WebSphere MQ shared message queues 

o HSM common recall queue 

o Enhanced Catalog Sharing 




- Sysplex aggregation software requirements: 

� Eligible systems enablement functions (cont.) 

o GRS Star 

o JES2 Checkpoint in the Coupling Facility 

o RACF® database caching 

o SmartBatch multisystem processing 

o VTAM® Generic Resources 

o VTAM MulitNode Persistent Sessions 





o Automated tape sharing and switching (prior to z/OS 1.2) 

o System Logger SYSLOG (OPERLOG) 

o System Logger LOGREC 

o System Logger Resource Recovery Services (RRS) 

Even though there are other CF exploiters, like XCF for example, it is only one or more items 

in the list above that will meet the requirement for use of a systems enablement function 




- Sysplex aggregation operational requirements: 





� The z/OS, z/OS.e, and OS/390 images participating in the above systems enablement 

function(s), in the same sysplex, must account for at least 50% of the total MSUs 

consumed by MVS-based systems on each eligible CPC. 

Note: This is not 50% of the total capacity the CPC, but 50% of the used capacity. 

Further, it is 50% of the capacity used by MVS-based systems (including those running 

under VM), so it excludes capacity used by VM itself and its other guests, Coupling 

Facility, or Linux LPARs, as well as any capacity used on any special purpose engines 

(zAAPs, for example). This is a very important point that is often misunderstood. 

� To determine eligibility for the 50% rule, the following calculation is applied for each CPC: 

o Sum the utilization of all the systems in each sysplex on the CPC for the 8-hour 

prime shift, for the 5 working days in the week (a total of 40 hours) 

o Sum the utilization for all MVS-based LPARs on the CPC for the same time period 

o Divide the utilization of the largest sysplex on this CPC by the total MVS-based 

utilization on this CPC 

o In order for this CPC to be eligible for aggregation, the PrimaryPlex utilization must 

be using more than 50% of the total for every week in the month. 




- Sysplex aggregation operational requirements (cont.): 

� Calculation of eligibility for the 50% rule 

Documentation 





o The PLEXCALC tool provided by IBM does these calculations for you, using SMF 

Type 70 records from every MVS-based LPAR (or VM guest) in the CPC 

o The Sysplex Calculator tool PLEXCALC is a no-charge tool provided on an as-is basis 

that can be downloaded from the following Web site: 

http://www.ibm.com/servers/eserver/zseries/swprice/sysplex/sysplex_calc.html 

Important Note: to ensure that your installation always is in complience with the 

50% rule, it is highly recommended that you run PLEXCALC on a regular basis! 

- Restatement of Criteria for aggregated Sysplex, ENUS204-268 

- z/OS Systems Programmers Guide to Sysplex Aggregation, REDP-3967-00 









103




Parallel Sysplex Utilities 

ICXDELUT: Deletion Utility for XCF Group Members 

The IXCDELET utility can be used to delete XCF group members that are 

created, quiesced, or failed 

Implemented with z/OS 1.7 

Sample JCL to run the utility is shipped in SYS1.SAMPLIB 

Use discretion when considering whether to use the IXCDELET utility 

Do not use the utility unless you understand the use of the 

member by its owning XCF application 

Sample JCL to run the IXCDELET utility to delete created, 

quiesced, or failed XCF group members: 

//IXCDELUT JOB 

//S1 EXEC PGM=IXCM2DEL,PARM=’GRPXYZ,MEM01’ 

//SYSPRINT DD SYSOUT=A 

/* 

For more information refer to: 

z/OS 1.7 MVS Setting up a Sysplex, SA22-7625, Appendix D 






IXGOFLDS Utility to initiate a Logstream Offload 

Can be used to initiate an Offload of all Log Blocks from primary Storage 

(e.g. a CF Structure) to DASD (secondary Storage) for a defined Logstream 

Instead of writing a Job to perform a Connect to the Logstream and then 

issuing an Offload (IXGOFFLD) Request, the IXGOFLDS utility can be used 

A JCL Sample to run the utility is shipped in SYS1.SAMPLIB 

Can be run as Batch Job or Started Task 

Sample Start Command to run the IXGOFLDS utility as Started Task: 

S IXGOFLDS,LOGSTRM=LOG_STREAM_NAME 

When the Procedure does not complete successfully, Message IXG274I will be 

issued to the Console stating which Function failed and listing the Return and 

Reason Code 


IXGDELLS Utility to delete a Logstream 

Can be used to delete a defined Logstream from the LOGR Couple Dataset 

Instead of writing a Job to perform the Logger Inventory Request, IXGDELLS 

can be used 

A JCL Sample to run the utility is shipped in SYS1.SAMPLIB 

Can be run as Batch Job or Started Task 

S IXGDELLS,LOGSTRM=LOG_STREAM_NAME 





Sample Start Command to run the IXGDELLS utility as Started Task: 

When the Procedure completes successfully, the Logstream will be deleted 

from the Logger Inventory and Message IXG273I will be issued to the Console 

When the Procedure does not complete successfully, Message IXG274I will be 

issued to the Console stating which Function failed and listing the Return and 

Reason Code 


REXX Exec’s shipped with z/OS 1.8 

Background 

To efficiently analyze Problem Data, such as Dumps, Traces and Logs etc., IBM 

Support Labs have a lot of tools, e.g. additional IPCS Functions etc., for their 

internal use 

These Tools (REXX Exec’s etc.) have been and still are used by 

� First Level Support 

� Second Level Support 

As these Tools can also be of great Help and Value for Customer System Engineers 

etc., IBM has decided to ship them as Part of z/OS 1.8 and follow-on Releases 



In Case of a Problem, these Functions will allow you to quickly check additional 

Areas and Informations in an SVC Dump, for Example: 

� Dispatchability and Lock Contention 

� CPU Usage 

� Ready-to Execute Work 







Starting with z/OS 1.8, the following REXX Exec’s will be shipped: 

Name Exec Abstract 

• ALET2DSP IAXAR2D DataSpace Name associated with input AR/ALET 

CMD2FILE BLSXC2FI Writes output from an input IPCS cmd to output dataset 

DAEINFO IEAVDAE Formats DAE information that resides in storage 

DATAINFO BLSXDINF List and Where in storage addresses 

DISPINFO IEAVDISP Dispatchability and lock contention information 

DUMPINFO IEAVDUMP General and environment information about the dump 

FRRSDATA IEAVFRRS Validity check FRR stacks 

IOSBLKS IOSFSMGB Information about IOS blocks 

IPLPARMS BLSXIPLP Values used during system initialization (IPL) 

LOCKSTAT IEAVLOCK Information about locks held at time of dump 

LOGDATAS IEAVLOGD One line summary of input LOGREC Dataset or LOGDATA 

SAVEAREA BLSXSAVA Maps standard savearea chain. Input save area addr 

SCTSIOT IEFDDSUM Displays all DDs and DSNs in a job 

SIOTPLUS IEFSIOTP Maps some fields in SIOT, EDL, DDWA, VOLUNIT, etc. 

SLIPDATA IEAVSLIP Display SLIP control block data 

SLOTCNT ILRSLOTC Auxiliary slot usage information 

SUMTRACE BLSXSUMT CPU usage information based on entries in SYSTRACE 

SVC99RB IEFSVC99 Maps dynamic allocation request block and text units 

TCBMAP IEAVTCBM Picture of TCB structure of the default ASID 

VSMINFO IGVVSMIN Map of Virtual Storage boundaries 

WJSIPAMT BPXWAMT Displays the automount rules set for this system 

WUQSUM IEAVWUQS Ready-to-execute work (ie. WEBs) 











109

Redbooks and Redpapers 

� z/OS Planned IPL Avoidance Checklist, REDP-4069-00 

� z/OS Systems Programmers Guide to Sysplex Aggregation, REDP-3967-00 

� z/OS Parallel Sysplex Configuration Overview, SG24-6485-00 

� ABCs of z/OS System Programming Volume 7, SG24-6987-00 

� Understanding LDAP - Design and Implementation, SG24-4986-00 




Recommended Readings 

� The Role of IBM System z in the Design of a Service Oriented Architecture, REDP-4190-00 

� Introduction to the new Mainframe: z/OS Basics, SG24-6366-00 

� Introduction to the New Mainframe: Networking, SG24-6772-00 

� z/OS V1R7 DFSMS Technical Update, SG24-7225-00 

� How does the MIDAW facility improve the performance of FICON channels using DB2 and other workloads?, 

REDP-4201-00 

� DB2 for z/OS: Data Sharing in a Nutshell, SG24-7322-00 

� A Structured Approach to Modernizing the SNA Environment, SG24-7334-00 

� Enterprise Workload Manager V2.1, SG24-6785 









111




Supplemental Documentation 

The following Documentations will also be supplied as Part of the GSE 

z/OS Expert Forum CH Handouts CD: 

� z/OS Hot Topics Newsletter #15 (August 2006), GA22-7501-11 

� Migrating to z/OS R8 Part 1: Get Ready, S2870MW, August 2006 

� Migrating to z/OS R8 Part 2: Get Set, S2871MW, August 2006 

� Migrating to z/OS R8 Part 3: Go, S2872MW, August 2006 

� z/OS Positioning Software for z9 EC and z9 BC Servers, FLASH10477 

� Capacity Table for DS6000 and DS8000, PRS1274 

� DS6000 and DS8000 Hardware and Logical Configuration Concepts, PRS2069 

� Enterprise Disk Copy Services Matrix, TD103375 

� Performance of Metro Mirror over Distance, WP100824 

� The DS8000 in a z/OS Environment, S3080, August 2006 





Supplemental Documentation 

The following Documentations will also be supplied as Part of the GSE 

z/OS Expert Forum CH Handouts CD: 

� IBM System z9 and zSeries I/O Feature Reference Table, TD102278 

� CHPID Mapping Tool Tips related to managing Mapping Files, WP100765 

� IBM System z9 Processor Design Considerations, FLASH10208 

� IBM System z9 and zSeries I/O Feature Reference Table, TD102278 

� IBM System z9 BC 2096 Quick Review, WP100770 

� IBM System z9 EC 2094 Quick Review, WP100769 

� IBM System z9 EC Installation Planning Footprint Considerations, TD103258 

On the Handouts CD, refer to the following Directory: Silvio’s_Corner_Doc_Jukebox 


How to get the Handouts for this Session 

http://www.thebrainhouse.ch/gse/ 




Last, but not least… 

The handouts for this session and the documentations listed in the “Doc Jukebox” will 

be provided on the GSE z/OS Expertforum handouts CD 

This presentation will also be provided for download at: 

Do you want the handouts for this presentation even faster? 

- No problem, just now during this conference, or when attending the next 

GSE z/OS Expert Forum, have a USB stick with you and I’ll give you a 

copy of the handouts immediately! 



The End... 







115 

Zürich, 16. Oktober 2006 © 2006 IBM Corporation

(MIDAW) Facility - Messmer The Brain House

Create successful ePaper yourself

Delete template?

Save as template?