IBM ZVSE ROADMAP User manual

z/VSE Roadmap
6 September 2007
z/VSE: A Roadmap For Cost savings and
Exploiting Technology
Prepared for:
IBM Corporation
By:
Sine Nomine Associates IBM-2007-04569-E-01
43596 Blacksmith Square August, 2007
Ashburn, VA 20147 SNA Proprietary –Confidential

z/VSE-4569
IBM-2007-04569-E-01 ©2007 Sine Nomine Associates
ii
Copyright © 2007 Sine Nomine Associates
All rights reserved.

z/VSE-4569
IBM-2007-04569-E-01 ©2007 Sine Nomine Associates
iii
Table of Contents
1INTRODUCTION AND PREFACE........................................................................1
1.1 Executive Summary.............................................................................................................................1
2THE Z/VSE PIE STRATEGY..................................................................................3
2.1 Pieces of the PIE....................................................................................................................................3
2.1.1 Protect.......................................................................................................................................................3
2.1.2 Integrate....................................................................................................................................................3
2.1.3 Extend.......................................................................................................................................................4
2.1.3.1 Exploiting Connectors .....................................................................................................................4
2.1.3.2 Web Serving......................................................................................................................................4
2.1.3.3 DB2 Connect.....................................................................................................................................4
2.1.3.4 CICS Transaction Gateway ............................................................................................................4
3TECHNOLOGY ENABLEMENT............................................................................5
3.1 System z9.................................................................................................................................................5
3.2 z/VSE 4.1 .................................................................................................................................................5
3.2.1 z/Architecture ..........................................................................................................................................5
3.2.2 Storage Constraint Relief......................................................................................................................6
3.2.3 New Pricing Metrics...............................................................................................................................6
3.2.4 Network Connectivity............................................................................................................................6
3.2.5 Security Enhancements..........................................................................................................................6
3.2.6 SCSI Disk Support..................................................................................................................................7
3.3 Overall Technology Impact................................................................................................................7
4PRICING AND ROI ..................................................................................................8
4.1 The Introduction of MWLC Pricing ...............................................................................................8
4.1.1 What counts as Full-Capacity?.............................................................................................................8
4.1.2 What counts as Sub-Capacity?.............................................................................................................9
4.1.3 Why MWLC? ..........................................................................................................................................9
4.1.4 Applicability............................................................................................................................................9
4.2 ISV Support............................................................................................................................................9
4.2.1 CSI International.....................................................................................................................................9
4.2.2 CA .............................................................................................................................................................9

z/VSE-4569
IBM-2007-04569-E-01 ©2007 Sine Nomine Associates
4
4.3 Reporting Sub-Capacity Utilization ..............................................................................................10
4.4 Does it work? .......................................................................................................................................10
4.5 z9 Hardware.........................................................................................................................................11
4.6 Human Resources...............................................................................................................................11
4.7 Environmental Savings.....................................................................................................................11
5SUMMARY AND RECOMMENDATIONS..........................................................13
APPENDIX A -PRICING SCHEMES....................................................................15
A.1 MWLC Levels......................................................................................................................................15
A.2 TWLC Tiers.........................................................................................................................................15
A.3 MWLC Eligible Program Products...............................................................................................15
APPENDIX B -Z/VSE UTILITIES AND IBM CONNECTORS..........................17
APPENDIX C -RAW DATA....................................................................................19
C.1 Maintenance Costs .............................................................................................................................19
C.2 Environmental Data...........................................................................................................................30
APPENDIX D -REFERENCES..............................................................................32
GLOSSARY....................................................................................................................33

z/VSE-4569
List of Tables
Table 1: Sample Comparative Pricing ............................................................................... 11
Table 2: MWLC Levels...................................................................................................... 15
Table 3: TWLC Tiers ........................................................................................................ 15
Table 4: Program Products eligible for MWLC................................................................. 16
Table 5: z/VSE Utilities and IBM Connectors .................................................................... 18
Table 6: Maintenance Data................................................................................................ 30
Table 7: Environmental Characteristics ............................................................................ 31

IBM-2007-04569-E-01 ©2007 Sine Nomine Associates
1
1Introduction and Preface
“With its announcement of z/VSE 4, IBM has executed a hat trick. It has brought new
technical life to an operating system that has not been part of the swift flow of
mainstream computing. It has brought the usage-based pricing model used by z/OS
mainframe shops to the VSE users who had previously been neglected. And it has set the
stage for fresh hardware initiatives by speeding the exit of users with older machines.”
Hesh Wiener, Big Iron
The intent of this document is to provide those responsible for making the long-term decisions on
the nature and direction of their company's IT strategy with the information and arguments to
continue with their investment with z/VSE.
This white paper illustrates the value of upgrading hardware and software portfolios to VSE
customers currently running pre-z/VSE 4.1 systems on pre System z9 processors. For those
running a standard portfolio of z/VSE products on Multiprise, 9672 or z8xx/z9xx classes of
machine, there are significant TCO savings to be realized.
1.1 Executive Summary
Tracings its heritage back to the days of S/360, z/VSE continues to meet its users business
requirements with a robust, lean, and efficient environment. Sine Nomine Associates’ own
experiences with z/VSE date back over twenty years to an organization that had been a VSE
customer since the DOS Rel 16 days. It was the backbone of an organization that turned over $4
billion per year and did so with great reliability.
Subsystems such as VTAM, CICS, POWER, and TCP/IP provide the infrastructure that satisfies
most of the VSE customer requirements. To VSE customers like these it is no wonder why the
question of “Why are you still running VSE?” is one that is usually answered with “Because it
works and works very well.”
Increasingly, however, there are business requirements and cost pressures that cause those
running VSE to look at how their investment can be maximized and the needs of their users
satisfied. With the introduction of the System z9 family and the availability of z/VSE 4.1 IBM
has attempted to help the VSE community address these concerns.
Today, for those customers facing end of life on their existing hardware there are compelling
technical and financial reasons to look at upgrading both the operating system and the hardware
on which it belongs. The combination of z/VSE and z9 address the questions of:
ØHow can value be most efficiently generated to maximize ROI?
ØHow can modernization of technology be applied to preserve the best of the existing
applications and enable developing services to rapidly adapt to new demand?
z/VSE 4.1 provides a strong foundation and enabling services to allow organizations to adapt
without risking the farm through:
ØTechnology enablement:

IBM-2007-04569-E-01 ©2007 Sine Nomine Associates
2
Ø64-bit VSE constraint relief
Øz/Architecture
Øz/VSE connector strategy which is part of the “Protect, Integrate and Extend”
(PIE) strategy described later in this document
ØCompanion Operating System to server consolidation strategy
ØOperational coordination benefits
ØSecurity features
ØPricing and ROI improvements:
ØMid-Range Workload License Charge (MWLC) Pricing
Øz9 hardware pricing
ØLower operational costs resulting from coordinated management
ØEnvironmentals
ØPersonnel optimization
VSE brings all those features into a focused coherent solution that provides strong ROI today, and
room to grow for tomorrow.

IBM-2007-04569-E-01 ©2007 Sine Nomine Associates
3
2The z/VSE PIE Strategy
The IBM VSE team have coined the acronym “PIE” to scribe a strategy of “Protect, Integrate,
and Extend” for z/VSE:
ØProtect existing customer investments in core z/VSE programs, data, equipment, business
and IT skills, plus business processes, and end user training. This is achieved by
modernizing applications by extending z/VSE resources to the web; exploiting the latest
in IBM servers and storage; and enhanced z/OS affinity.
ØIntegrate z/VSE with the rest of IT, based on open and industry standards via the use of
VSE connectors, SOA Web Services, and IBM middleware.
ØExtend solutions by using Linux on System z to exploit existing core VSE investments
and introducing new applications and workloads in a low cost, low risk, fast time-to-
market manner.
2.1 Pieces of the PIE
The following sections describe how the PIE strategy can be used to future-proof z/VSE-based
systems.
2.1.1 Protect
On facet of the protection part of the z/VSE PIE comes in the form of subsystems such as CICS
Transaction Server (TS), TCP/IP, and VTAM which facilitates the interoperation and affinity
with z/OS. Another facet is the enhanced hardware support that z/VSE provides which enables
the exploitation of devices such as the DS8000 or the encryption capabilities of the TS1120 tape
subsystem.
2.1.2 Integrate
Connectors enable the integration of VSE systems with other network-enabled systems and
provide real-time access to VSE resources (like VSAM, POWER, DL/I, Librarian, ICCF,
console) from remote platforms. VSE programs can also access remote data like databases or flat
files. In addition there are a set of utilities for download, that helps you to manage your VSE
system. Table 4 in the appendices describes these connectors and utilities.
Connectors are the building blocks used to connect different applications on heterogeneous
platforms and operating systems. z/VSE connectors are based on J2EE standards and use
WebSphere Common Connector Framework. They consist of:
ØClient components written in Java: meaning they can run on any Java-compatible
platform, such as Linux running on the IBM System z
ØServer components that run on the VSE host

IBM-2007-04569-E-01 ©2007 Sine Nomine Associates
4
2.1.3 Extend
The extend slice of the PIE can be implemented by a Linux system acting as both a gateway to
the Internet and as a host for new e-business applications. Running in an IFL the Linux system
will not affect the MSU rating of the System z and thus the software bill for the z/VSE portfolio.
It also allows its applications to be accessed from z/VSE at memory-to-memory speeds via the
use of hipersockets. Linux is able to exploit the z/VSE connectors to extend the reach of the
existing z/VSE applications and to promote the growth of new ones.
There are several ways people are using Linux on System z to extend their existing applications.
2.1.3.1 Exploiting Connectors
Java-based connector provide connectivity to z/VSE via TCP/IP. They provide access to, for
example a Web Application Server, VSAM, POWER, the Librarian, ICCF and the z/VSE
console.
The DB2-based connector uses DRDA over TCP/IP to provide JDBC/ODBC access to z/VSE-
based DB2 systems as well as VSAM and DL/I based data.
Tools such as the z/VSE navigator provide a face to z/VSE that is intuitive to today's workstation
users which means they can be immediately productive when using the system: there is no
requirement to train them how to use the older 3270 mechanisms.
2.1.3.2 Web Serving
One simple strategy is the serving of z/VSE data exported via NFS through an Apache webserver.
This can be done via a z/VSE-based webserver but using Apache allows access to a greater pool
of programmers are familiar with Apache's way of doing things.
A more complex strategy is to run WebSphere on the Linux system and using facilities like the
MQ client, DB2 Connect and the CICS Transaction Gateway to serve data and transactions to and
from the z/VSE system.
2.1.3.3 DB2 Connect
DB2 Connect enables a Linux system, and the clients that connect to it, to access z/VSE-based
DB2 instances.
2.1.3.4 CICS Transaction Gateway
The CICS Transaction Gateway enables Java applications running on another server or
workstation to access a CICS system running on z/VSE via the Java Daemon gateway. This
technology enables the serving of Java applets from a webserver.
Impact: The PIE strategy is a roadmap for maintaining and enhancing the viability of z/VSE
based systems into the future. The connectors and utilities are not “vaporware” and are available
now to facilitate the extension of z/VSE systems and applications. Access to strategic middleware
such as WebSphere and thus to a range of new applications is also a key to enhancing the value of
z/VSE.

IBM-2007-04569-E-01 ©2007 Sine Nomine Associates
5
3Technology Enablement
When it comes to z/VSE one side of the business driver coin is the advances in technology that
come with the new processors and z/VSE 4.1. The advances in technology translate into
improved application delivery, the integration of existing applications to the web, and secured
extension of data visibility to new applications.
3.1 System z9
The latest in the mainframe family of processors are the System z9 Business Class (z9 BC) and
Enterprise Class (z9 EC) series.
The z9 BC is designed as a midrange mainframe and promises extensive growth options and
excellent price/performance for those customers requiring a lower-capacity entry point and more
granular growth options than offered with the System z9 Enterprise Class. There are two models:
R07and S07, each capable of running from 1 to 7 processors. The full range of speciality engines
(IFL, CF, ZIIP and ZAAP) and an extensive range of cryptographic assists are available.
The z9 EC is designed as a large mainframe solution that is highly scalable and has greater
cryptographic capabilities and a higher capacity entry point than the z9 BC. It also supports the
full range of speciality engines. Five models are available: S08, S18, S28, S38 and S54, which
provides from 1-54 n-way processors.
Impact: The z9 provides arange of processors with improved performance with enough
granularity for users to choose an entry level appropriate to their needs and to grow when
required. The speciality engines enable collaborative processing with the introduction of Linux.
The cryptographic facilities enable rapid security services to be implemented which are needed
when extending z/VSE to the network.
3.2 z/VSE 4.1
Version 4.1 of z/VSE was announced on January 9, 2007 and made generally available on March
16. There are some significant features described in the announcement that may have both
technical and financial implications to a VSE-based IT operation.
3.2.1 z/Architecture
z/VSE works in z/Architecture mode only and thus requires a processor capable of operating in
this mode. It exploits z/Architecture's ability to address 64-bit real storage although it only uses
31-bit virtual addresses. Candidates for exploiting this feature include “data-in-memory”
techniques such as CICS Shared Data Tables, VSE Virtual Disk, or more and larger buffer pools.
z/VSE is supported on the IBM System z9 EC and z9 BC servers as well as the IBM eServer
zSeries z990, z890, z900 and z800 servers.
Impact: Selected system functions of z/VSE are able to exploit 64-bit real addressing which
means the below 2GB requirements for these functions is relieved and the space available for