Download System z Foundation

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Machine learning wikipedia , lookup

Theoretical computer science wikipedia , lookup

Transcript
TGVL: System z Foundation
TGVL: System z Foundation – Learning Points Summary
Jan 20-22, 2008
IBM System z
z10 EC
TGVL: System z Sales Foundation Class Overview
z10 BC
1Q2009
TGVL: System z Foundation
Learning Points – System z Class Overview
1. The four Enterprise roles of the Mainframe are:

Business Resilience Manager

Security Manager

Workload Manager

Hub for Data and SOA
2. Specialty Engines reduce the Total Cost of Ownership for System z.
3. System z Capacity on Demand provides both temporary and permanent
offerings
4. Parallel Sysplex is an architecture for continuous availability.
5. GDPS is a High Availability and Disaster Recovery Solution
TGVL: System z Sales Foundation Class Overview
1Q2009
TGVL: System z Foundation
Learning Points – System z Specialty Engines
1. Specialty Engines reduce the Total Cost of Ownership for System z..
2. All ICFs, IFLs, zAAPs, and zIIPs are carried over to all System z Upgrades
without cost!
3. Specialty Engines play a key role in IBM’s System z Cost & Value strategy.
4. IFLs support Linux or Linux under z/VM exclusively.
5. ICF’s Support Coupling Facilty Control Code (CFCC – for Parallel Sysplex)
exclusively.
6. zAAPs supprort Java processing under z/OS.
7. zIIPs were first supported by DB2.
8. All PU chips for System z10 Servers contain 4 PUs (Cores).
9. Techline should be used for System z10 Capacity Analysis and for Order
Configurations.
TGVL: System z Sales Foundation Class Overview
1Q2009
TGVL: System z Foundation
Learning Points – System z Capacity on Demand
1.
On-line Permanent Upgrade

2.
3.
4.
5.
Permanent upgrade performed by customer (previously referred to Customer Initiated Upgrade - CIU)
Capacity Backup (CBU)

For disaster recovery

Concurrently add CPs, IFLs, ICFs, zAAPs, zIIPs, SAPs

Pre-paid
Capacity for Planned Event (CPE)

Replace capacity for short term loss due to a planned event such as a facility upgrade or system relocation

Predefined capacity for a fixed period of time (3 days)

Pre-paid
On/Off Capacity on Demand (On/Off CoD)

Production Capacity

Supported through software offering – Capacity Provisioning Manager (CPM)

Payment:
1.
Post-paid or Pre-paid by purchase of capacity tokens
2.
Post-paid with unlimited capacity usage
3.
On/Off CoD records and capacity tokens configured on Resource Link
Customer Initiated Upgrade (CIU)

Process/tool for ordering temporary and permanent upgrades via Resource Link

Permanent upgrade support:
1.
Un-assignment of currently active capacity
2.
Reactivation of unassigned capacity
3.
Purchase of all PU types physically available but not already characterized
4.
Purchase of installed but not owned memory
TGVL: System z Sales Foundation Class Overview
1Q2009
TGVL: System z Foundation
Learning Points – System z High Availability – Parallel Sysplex
1. Parallel Sysplex is a High Availability Solution implemented via
hardware, software, and microcode
2. A Coupling Facility (CF) provides Serialization and buffering
Services to members of a Parallel Sysplex – CFCC is the Operating
System for all CFs
3. Sysplex Timers (and/or FTP) assures synchronized clocks for all
members of a Parallel Sysplex – Required for Data Recovery
4. CF to Server connections can be ISC, ICB, PSIFB, or IC links – IC
links are virtual links when CF is LPAR on the same server
5. Parallel Sysplex protects end users from Planned or Unplanned
outages
6. WLM manages workloads across all members of a Parallel Sysplex
according to the customers “Business” priorities.
7. z/OS and Middleware may be level n, n-1, or n-2.
TGVL: System z Sales Foundation Class Overview
1Q2009
TGVL: System z Foundation
Learning Points - High Availability - GDPS
1. GDPS is a Continuous Availability (CA) and Disaster Recovery (DR)
Solution.
2. Recovery Time Objective (RTO) – Time to get all applications up and
running (after disaster).
3. Recovery Point Objective (RPO) – If data recovery backleveled the
data, how long? (what is the time currency of the data after recovery).
4. Metro Mirror is a Synchronous Disk replication technique limited to
distances less than 100K. (Example: GDPS/PPRC)
5. Global Mirror is an Asynchronous Disk replication technique across
unlimited distances. (Examples: DPS/Global Mirror and GDPS/XRC)
6. Hyperswap provides CA within a data center via GDPS/PPRC – this
protects from a Storage Control Failure with a RPO of 0 and an RTO of
less than 1 hr (typically far less).
TGVL: System z Sales Foundation Class Overview
1Q2009
TGVL: System z Foundation
Learning Points - z/OS and Workload Management
1. z/OS – IBM’s flagship Operating System
2. Current Release of z/OS – V1R10
3. z/OS release that requires z Architecture Server – V1R6 (and beyond)
4. z/OSe supports only z/800, z/890, and z9 BC. z/OSe does not support CICS, IMS,
or COBOL Development
5. zNALC now replaces z/OSe and is intended for New Workloads on System z and
significantly lowers the cost of z/OS – zNALC only effects the cost of z/OS
6. WLM is a standard subset of z/OS – no additional charge
7. WLM distributes resources among workloads according to customer business
priorities (Described within Policies set by the customer) across a Parallel Sysplex
8. IRD is a subset of PR/SM
9. IRD works with WLM to dynamically distribute Processor and I/O hardware
resources among LPARs running on the same physical server
10. IBM’s goal is to train 20,000 additional Mainframe professionals before 2010
TGVL: System z Sales Foundation Class Overview
1Q2009
TGVL: System z Foundation
Learning Points - System z Software Pricing

System z Monthly License Charges (MLC) pricing is typically used for DB2, CICS, IMS,
MQSeries, COBOL compilers, PL/1 compilers, Domino, z/OS, z/VSE.

z/OS.e disables or disallows certain products, applications, and workloads (such as IMS, CICS)
and supports z800/z890/z9 BC/z10 BC servers only.

zNALC replaces z/OSe and NALC for reduced z/OS pricing for qualified workloads across all
System z Servers..

Parallel Sysplex License Charges (PSLC) applies to qualified Parallel Sysplexes and
significantly lowers software prices by aggregating capacity across the entire qualified Parallel
Sysplex.

WLC Sub-Capacity Software pricing is determined by the processor capacity used during the
peak rolling four hour average for the LPAR(s) in which the software is running.
TGVL: System z Sales Foundation Class Overview
1Q2009