Silvio's Corner - zExpertenforum

Silvio Sasso's Corner, GSE z/OS

Expertforum CH #75, 18.-19.10.2011,

Lugano

1© 2004 IBM CorporationZürich | 26. Oktober 2004

zEnterprise. A new Dimension in Computing

®

®

GSE z/OS Expertforum Switzerland # 76, 24.-25.4.2012

Zürich, April 24, 2012 © 2012 IBM Corporation

Silvio’s Cornerz/News, Hints and Tips

Silvio Sasso

IBM Switzerland

ITS Service Delivery for z/OS

[email protected]


Expertforum CH #75, 18.-19.10.2011,

Lugano



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 z, z/Architecture and z/OS.

ƒUseful technical news and flashes

ƒTips for education, workshops and conferences

ƒVarious resources containing additional documentation (e.g. product specific information or other interesting Websites etc.)

ƒRecommended readings: new Redbooks and whitepapers etc.

ƒand much more...

ƒSystem programmer goodies, tools, hints and tips

This corner allows me to present you...

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

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

ƒSoftware news: z/OS and Parallel Sysplex update


Expertforum CH #75, 18.-19.10.2011,

Lugano



Trademarks

Trademarks

See URL for a list of trademarkshttp://www.ibm.com/legal/copytrade.shtml


Expertforum CH #75, 18.-19.10.2011,

Lugano



Acknowledgements

Acknowledgements

Grateful acknowledgement to several current and former IBMers for significant contributions to this presentation, specially to:

� Geoff Smith

� Mark A. Brooks

� Michael Rubens

� Joe Gera

� Susan Tuczynski

� Heinz Tschumi


Expertforum CH #75, 18.-19.10.2011,

Lugano



Agenda

General Information

Software News

Hardware News

� z/OS Update and Statement of Direction

� Java Levels shipped with z/OS 1.12 and z/OS 1.13

� IBM - the unrivalled Patent Leader

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

� IBM increases Mainframe Security Level Certification

� IBM zEnterprise z196 Update

� System z ISV and Apps

� IBM zEnterprise zBX Update

� z/OS Support Summary

� z/OS Hot Topics Newsletter News

� Top worldwide Banks use System z


Expertforum CH #75, 18.-19.10.2011,

Lugano



Agenda

Parallel Sysplex Update

Redbooks and Redpapers

Doc Juke Box

� Enable/disable Structure Allow Auto Alter with z/OS 1.13

Hints and Tips, System Programmer "Goodies"

� Extended SMF Dump Statistics Report

� Run Time Diagnostics with z/OS 1.13

� z/OS 1.13 SDSF Syslog/Operlog Viewing Enhancements

� Orderly System Shutdown: the Importance of Z EOD


Expertforum CH #75, 18.-19.10.2011,

Lugano






Expertforum CH #75, 18.-19.10.2011,

Lugano



IBM - The unrivalled Patent Leader

IBM achieved new Record in 2010

IBM is the unrivalled worldwide patent leader

• In 2010, IBM received a record of 5'896 U.S. patents

• In 2011, IBM even topped this record by receiving 6’180 U.S. patents

• This marks the 19th consecutive year IBM has led the annual list of patent recipients

• IBM's 2011 number of patents more than quadrupled Hewlett-Packard's and was six

times more than Oracle/Sun's

• Doesn’t this say something about the competition's R&D investment?

• Top 10 of 2011 U.S. Patent Leaders*:

1. IBM 6,180

2. Samsung 4,894

3. Canon 2,821

4. Panasonic 2,559

5. Toshiba 2,483

6. Microsoft 2,311

7. Sony 2,286

8. Seiko Epson 1,533

9. Hon Hai 1,514

10. Hitachi 1,465 *Data provided by IFI CLAIMS Patent Services


Expertforum CH #75, 18.-19.10.2011,

Lugano



Increased IBM Mainframe Security Level Certification

IBM increases Mainframe Security Level Certification

• System z PR/SM and RACF are now both certified at the highest level of trusted

commercial grade security

• IBM RACF for z/OS 1.12 has achieved Common Criteria certification at Evaluation

Assurance Level 5 (EAL5) under the Common Criteria Evaluation and Certification

Scheme

• Common Criteria is an internationally approved set of security standards that provides an

assessment of products' ability to meet security standards, providing a yardstick to help

customers with their security decisions

• EAL5 is the highest commercial grade assurance level and exceeds what other

commercial platforms offer

• Now this advantage which existed with PR/SM also extends to RACF


Expertforum CH #75, 18.-19.10.2011,

Lugano



z/OS Hot Topics Newsletter News

• Easy-to-use, hands-on, technical information not often

found in standard z/OS product references

• Articles by z/OS designers, testers, developers and service

• Emphasis on presenting technical information in a lively,

informal manner

• Published semi-annually to coincide with the SHARE user

conference

• Latest issue: GA22-7501-21, issue 25 Learn about how

z/OS is making a smarter planet

• Announcement: Starting this year, Hot Topics will

produce one issue annually

z/OS Hot Topics Newsletter

http://www.ibm.com/systems/z/os/zos/bkserv/hot_topics.html


Expertforum CH #75, 18.-19.10.2011,

Lugano



Top worldwide Banks use System z

• Based on asset size, 96 out of the top 100 worldwide banks use System z 1

1 Based on ‘The Banker’, System z install base and financial records

Worldwide top Banks rely on System z






Expertforum CH #75, 18.-19.10.2011,

Lugano



System z ISV and Apps

• As of year end 2011:

– 1,500+ new and upgraded applications added for z/OS and Linux on System z

• 4,100+ total z/OS applications

System z ISV and Apps

– 100+ new ISV partners on the platform in 2011

• As of year end 2011, 7,000+ are applications supported on z/OS and Linux for System z:

– z/OS:

• Over 1,200 new or upgraded applications for z/OS in 2011

• More than 4,100 total z/OS applications

• 3,000+ total Liunx applications

– Linux on System z:

• Over 370 new or upgraded applications for Linux on System z in 2011


Expertforum CH #75, 18.-19.10.2011,

Lugano



zEnterprise

A New Dimension in Computing




Expertforum CH #75, 18.-19.10.2011,

Lugano



IBM zEnterprise zBX Update

zBX Update


Expertforum CH #75, 18.-19.10.2011,

Lugano




Service levels to match your business needs

DistributedSystems

Select IBM Blades in zBX

z/OS

TCA Focus

TCO Focus

Linux on z/VM®

� Expanded ISV support

for enterprise

applications

� Targeted for

applications that interact

with mainframe data

and transactions

� Provisioned and

managed by System z

� Extreme consolidation of servers and networking

� Superior levels of virtual server provisioning, monitoring and workload management

� Industry-best virtual I/O bandwidth and reliability

� Fewer components and reduced complexity

� System z qualities of dynamic resource management and capacity-on-demand

� Seamless integration with z/OS backup and disaster recovery solutions

� Silo managed islands

of computing

� Less dynamic than z

virtualization

� Minimal resource

sharing with z

resources

� Extreme scalability and performance for transaction processing and data serving

� High availability and cross-system scalability with Parallel Sysplex® and GDPS®

� Leading policy-based capacity provisioning and workload management

� Pervasive, high-performance security support

LOWER HIGHERSCALABILITY, SECURITY,

DYNAMIC WORKLOAD MANAGEMENT

SCALABILITY, SECURITY,

DYNAMIC WORKLOAD MANAGEMENT

zEnterprise System

Increased flexibility for your multi-architecture strategy when data is on z/OS


Expertforum CH #75, 18.-19.10.2011,

Lugano



Putting zEnterprise System to the TaskUse the smarter solution to improve your application design


Syste

m z

Hard

ware

Managem

ent C

onsole

(H

MC

)w

ith U

nifie

d R

esourc

e M

anager

zBX

Select IBM Blades

Blade HW Resources

Optimizers

Data

Pow

er

XI5

0z

z HW Resources

z/OS®

Support Element

Linuxon

System z

z/VM

Unified Resource Manager

Private data network (IEDN)

Customer Network Customer Network

System z Host

Linux on System x

AIX on POWER7

Data

Pow

er

XI5

0z

Blade Virtualization


System z PR/SM™

z/TPF

z/VSE®

Linux on

System zWindows

on System x


Private High Speed Data Network IEDN

Private Management Network INMN

Private Management Network (information only)


Expertforum CH #75, 18.-19.10.2011,

Lugano



zEnterprise 114, 196 and zBX Enhancements – December 16, 2011


Support for 56 System x blades (March 30,

2012)

Additional 8 GbE fibre channel optics -

increased the number of SAN connections for

BladeCenter chassis

Server Application State Protocol (SASP) load

balancing

Improved network monitoring and metrics for p

and x Blades within the zBX

Two additional memory options for HX5 blades

- 192 and 256 GB

SAP support for Linux and Windows on x86

blades in the zBX

HiperSockets integration with the

IntraEnsemble Data Network (IEDN)

HiperSockets Completion Queue

z196 z114

zBX


Expertforum CH #75, 18.-19.10.2011,

Lugano



zEnterprise 114, 196 and zBX Enhancements – Announcement, March 6, 2012

z/VM 6.2 dedicated connection support for

HiperSockets integration with the IEDN

z/VM 6.2 guest exploitation support for High

Performance FICON for System z (zHPF)

Support transfer of a zBX to a different target CPC

z/VM V6.2 support for improved network monitoring and

metrics

z/VM 6.2 network monitoring metrics and HiperSockets

Vswitch bridge

RPQ for additional Fibre Channel optics for installed

BladeCenter(s)

z196 z114

zBX



Expertforum CH #75, 18.-19.10.2011,

Lugano



IBM Blades and Optimizers Integrated within the zBX

• Select IBM POWER7 and IBM System x blades

– Brings a larger application portfolio to zEnterprise

• Front end applications to centralized data serving … e.g. SAP

• Front end to core CICS® or IMS™

transaction processing … e.g. WebSphere

– Applications certified to run on zBX supported POWER7 and System x blades will run on them when installed in the zBX

• IBM WebSphere® DataPower® Integration

Appliance XI50 for zEnterprise

– Purpose-built hardware for simplified

deployment and hardened security helps

businesses quickly react to change and

reduce time to market

– DataPower XI50z can provide

connectivity, gateway functions, data

transformation, protocol bridging, and

intelligent load distribution.

PS701 HX5XI50z



Expertforum CH #75, 18.-19.10.2011,

Lugano



Support for 56 System x Blades in zBX Model 2 (Available March 30, 2012)

• General Purpose Blade Configuration (POWER7 and System x)

– Number allowed in a zBX is determined by blade enablement features ordered

– Supported blades and software must be procured and installed (entitled) into slots by the client

– Select System x blades, singlewide, up to 14 per BladeCenter chassis, 56 per zBX

– Select POWER7 blades, singlewide, up to 14 per BladeCenter chassis, 112 per zBX

– POWER7, System x and DataPower XI50z blades can all coexist in the same BladeCenter chassis

• Optimizer Blade Configuration (DataPower)

– Optimizer blades are shipped with the zBX OR can be installed by MES in the field by an SSR

– DataPower XI50z blades, doublewide, up to 7 per BladeCenter, 28 per zBX

• Can coexist in the same BladeCenter with general purpose blades

• zBX Hardware Infrastructure

– Slots required to hold the enabled blades determine the number of zBX BladeCenters and racks

– Maximum configuration:

• Up to eight BladeCenter H chassis (each provides slots for 14 single wide blades)

• Up to four racks (no more than two BladeCenter H chassis per rack)

– Racks and BladeCenters are shipped for new build or can be installed by MES in the field by an SSR

– TOR switches, cabling and power internal to the zBX is shipped with the zBX and installed an SSR



Expertforum CH #75, 18.-19.10.2011,

Lugano



New Blades Provide Added Flexibility for Workload Deployment and Integration

IBM zEnterprise

BladeCenter Extension (zBX)

Machine Type: 2458 Mod 002

One to four – 42u racks –

capacity for up to 112 blades

• Up to 112 PS701 Power blades

• Up to 28* HX5 System x blades

• Up to 28 DataPower XI50z

blades (double-wide)

Optimizers• IBM WebSphere DataPower

Integration Appliance XI50z for

zEnterprise

Select IBM Blades• IBM BladeCenter PS701 Express

• IBM BladeCenter HX5 (7873)

� IBM System x Blades

– IBM BladeCenter HX5 7873 dual-socket 16-core blades

– Four supported memory configurations for zBX – 64 GB, 128 GB, 192 GB,

256 GB

� IBM POWER7 Blades

– IBM BladeCenter PS701 8-core processor 3.0GHz

– Three configurations supported in zBX - 32 GB, 64 GB, 128 GB

� Flexibility in ordering – acquired though existing channels,

including IBM

� Unified Resource Manager will install hypervisor on blades in

the zBX

– Integrated hypervisor (KVM-based) for System x blades

– PowerVM Enterprise Edition for POWER7 blades

� Up to 112 Blades supported on zBX

– Ability to mix and match blades in the same chassis

– Number of blades supported varies by type

� Blades assume System x warranty and maintenance when

installed in the zBX*Support for 56 System x blades (March 30, 2012)



Expertforum CH #75, 18.-19.10.2011,

Lugano



IBM System x blades: IBM BladeCenter HX5 7873-A4x/A5x/A6X/A7x

*The last character in the SSCT model is determined by geography. “U” is correct in the USA.

It is not necessary to order extended warranty or enhanced service response. When a supported System x blade is installed in the zBX under IBM warranty or service, a System z SSR services the blade as part of the zBX. Typically 24 x 7, 2 hour response.

1111146244X194544X1946

Qlogic 8 Gb Fibre Channel Expansion Card CIOv

1111009946M616846M6170

Broadcom 10Gb virtual fabric CFFh

11119012No Internal Raid

2222542843W772643W772750GB MLC SSD

1111576546M690846M6906SSD Exp Card

1111174159Y588946M6843Speed Burst Card

161284GB/Core

016

88

160

80

A17Q2422

46C057046C0599

46C055849Y1527

Memory 8 GB 1333 MHzMemory 16 GB 1333 MHz

16161616Total Cores

SingleSingleSingleSingleBlade width

2222# Intel Processors (Sockets)

1111A17969Y307469Y3072

Additional Processor2.13 GHz 105W (E7-2830 8C)

1111A16S69Y307469Y3071

Initial Processor 2.13 GHz 105W (E7-2830 8C)

1111Blade base - HX5 (7873)

Config 3 (7873-A7x*)

Config 2 (7873-A6x*)

Config 1(7873-

A5x*)

Config 0(7873-

A4x*)

FeatureCode

Option Part

Number (for

SSCT)

SBB PartNumber

Blade *

Link to the IBM Standalone Solutions Configuration Tool (SSCT):http://www-947.ibm.com/support/entry/portal/docdisplay?brand=5000008&lndocid=MIGR-62168

• Four Supported Configurations:

Client acquired, not configured or

shipped by System z manufacturing

• Processor Chips

– Intel® Xeon® E7-2830 processor

• Nehalem microarchitecture

• Westmere-EX core (32 nm)

• Memory DIMMs

– DDR3, 1333 Mhz capable

– Operating frequency 1066 MHz

– 6.4 GT per second

• Speed Burst Card

• SSD Expansion Card

• SSD Internal Disks (Two 50 GB)

– Hypervisor storage controlled by


• 10 GbE 2-port Expansion Card

– CFFh PCIe 2.0 x16 slot

• QLogic 8Gb FC Expansion Card

– CIOv PCIe 2.0 x4 slot

– 2 ports



Expertforum CH #75, 18.-19.10.2011,

Lugano



IBM System x Blade Hypervisor and Operating Systems

• zBX Integrated Hypervisor for IBM System x Blades

– Linux Kernel-based Virtual Machine (KVM) technology

– License included in z196 or z114 FC 0042 – “Manage Firmware for a System x blade”)

– Supports both Linux on System x and Windows on the same blade

– Supports up to 8 virtual servers (guests) per System x blade

– Includes Certified Windows1 VirtIO Drivers with installation support using the


• Operating Systems

– Separately acquired and licensed by the customer

For license, System x blades are “2-socket servers”. Consider the number of guests required.

– 64-bit Linux on System x

• Red Hat® Enterprise Linux (RHEL) 5.5, 5.6 and 6.0

http://www.redhat.com/rhel/versions/rhel5/

• Novell® SUSE® Linux Enterprise Server (SLES) 10 (SP4) and SLES11 (SP1)

http://www.suse.com/products/server/

– 64-bit Windows Server

• Windows Server 2008 R2 – Datacenter Edition, 64 bit version

• Windows Server 2008 (SP2) – Datacenter Edition, 64 bit version



Expertforum CH #75, 18.-19.10.2011,

Lugano



Operating System Environments extend application flexibility

� Support for Linux and Windows environments on System x blades in zBX

– 64-bit version support only

– Linux: RHEL 5.5, 5.6, 6.0 & Novell SUSE SLES 10 (SP4) and SLES 11 SP1

– Microsoft Windows Server 2008 R2 and Microsoft Windows Server 2008 (SP2) (for

either we recommend Datacenter Edition)

– The zBX web page will host the most current blade ordering information: http://www.ibm.com/common/ssi/cgi-

bin/ssialias?infotype=SA&subtype=WH&appname=STGE_ZS_ZSUSEN&htmlfid=ZSL03128USEN&att

achment=ZSL03128USEN.PDF

� Support of AIX environments on POWER7 blades in zBX

– AIX: AIX 5.3 Technology Level 12 or higher, AIX 6.1 Technology Level 5 or higher, AIX

7.1

– For the most current POWER7 blade ordering information: http://www.ibm.com/common/ssi/cgi-

bin/ssialias?infotype=SA&subtype=WH&appname=STGE_ZS_ZS_USEN&htmlfid=ZSY03019USEN&a

ttachment=ZSY03019USEN.PDF

� Certifications inherited from blades

– SAP support for Linux and Windows on x86 blades in the zBX

� Operating Systems are customer acquired and installed



Expertforum CH #75, 18.-19.10.2011,

Lugano



WebSphere DataPower Appliances…

WebSphere DataPower Appliances provide a low startup cost,

helping companies increase their ROI and reduce their TCO with

specialized, consumable, dedicated appliances that

combine superior performance and hardened security

SIMPLIFY your connectivity infrastructure

ACCELERATE your time to value

SECURE your SOA, Web 2.0, B2B, and Cloud environments

GOVERN your evolving IT architecture



Expertforum CH #75, 18.-19.10.2011,

Lugano



WebSphere DataPower Appliances meet your connectivity needs

� Extreme volume at microsecond latency

� Extended messaging protocol bridging

� Enhanced QoS and performance

� Unparalleled B2B performance

� Secure B2B messaging (AS1, AS2,

AS3)

� Trading partner profile management

� B2B Transaction Viewer

� Consumable hardware ESB

� “Any-to-any” conversion at wire-speed

� Dynamic routing; intelligent load distribution

� XI50B brings the XI50 capabilities to bear in

an optimized IBM BladeCenter form-factor

� DataPower XI50z brings the XI50 capabilities

in an optimized IBM zEnterprise zBX

� Web Services security

� Rich authentication and

authorization

� Centralized policy management

XB60XM70

XI50 / XI50B XS40XI50z



Expertforum CH #75, 18.-19.10.2011,

Lugano



Ensemble Load BalancingU

nifie

d R

esourc

e M

anager

SE

z/VM

zLin

ux: W

eb S

erv

er

zLin

ux: W

eb S

erv

er

zLin

ux: W

eb S

erv

er

SE

z/VM

zLin

ux: W

eb S

erv

er

zLin

ux: W

eb S

erv

er

zLin

ux: W

eb S

erv

er

z196/z114 z196/z114

Hypervisor

Lin

ux: W

eb S

erv

er

Lin

ux: W

eb S

erv

er

Lin

ux: W

eb S

erv

er

Accele

rato

r

Accele

rato

r

Load Balancer

zEnterprise Ensemble

Recommendations

(SASP)

Load Balance

Load BalanceLoad Balance

zBX



Expertforum CH #75, 18.-19.10.2011,

Lugano



Transfer of installed zBX to a new ‘managing' CPC – April 24, 2012

Donorz196/z114

zBX Targetz196/z114

DETACH zBX

ATTACH zBX

• Rules for the move MES changes to the donor and target managing CPCs

–The customer number for the donor CPC and the target CPC must be the same.

– The donor CPC retains Ensemble and Automate/Manage features for blades and IFLs with NO changes.

– The zBX retains blade enablement features but they may be reduced or increased.

– The target CPC must add Ensemble and Automate/Manage features for blade enablement features kept on the zBX and for

its own IFLs if they are not already present.

– The zBX need NOT remain in the same Ensemble or at the same location.

– Ensemble virtual server configuration information in the zBX is not preserved.

• Move ordering procedure: MES changes ordered for two CPCs in the same eConfig session.

–Detach FC #0030 is driven for the donor CPC. Detach can NOT be ordered separately.

–Attach FC #0031 and ensemble feature additions are driven for the target CPC which must be installed.

– Target CPC feature adds are allowed, e.g. HMC and OSA features needed to create an ensemble.

– If packing material required to move the zBX, order it on the donor CPC before ordering the move MES

–Can NOT order other MES changes for the target CPC until after zBX install completes the move MES. To avoid delaying

other planned MES changes, consider ordering with the move or installing before the move.



Expertforum CH #75, 18.-19.10.2011,

Lugano



New 1 GbE SX or LX zBX to Customer Network ConnectionsIncreased SAN Connections (available now)

• Networks – Redundant zBX-002 “B” frame top of rack switches

– Intranode management network (INMN) - 1000BASE-T (OSM)

– Intraensemble data network (IEDN) - 10 GbE SR or LR (OSX)

– Corporate network to zBX - 10 GbE SR or LR or 1 GbE SX or LX

Note: z196 may also connect via the corporate network (OSD)

• Storage – Redundant 8 Gbps SX Fibre Channel

– Up to twelve SAN connections per BladeCenter chassis

to the SAN for POWER7 and System x blades

IBM blades 8 Gbps SX FCUp to 12 links per

BladeCenter H chassis

A EDCBZ

INMN (OSM)

IEDN (OSX)

Local Open

SAN

Storage

z196 orz114 zBX Model 2

Corporate

Network

10 GbE SR or LR or 1 GbE SX or LX connections

10 G

bE SR or L

R IEDN to

other

ense

mble nodes

Corporate network connections



Expertforum CH #75, 18.-19.10.2011,

Lugano



IBM zEnterprise zBX Reference Material (1 of 2)


• z196 Redbooks®:

– z196 Enterprise Class Technical Introduction, SG24-7832-01

– z196 Enterprise Class Technical Guide, SG24-7833-01

– IBM System z Connectivity Handbook, SG24-5444-12

– z196 Enterprise Class Configuration Setup, SG24-7834

– IBM zEnterprise Unified Resource Manager, SG24-7921

– z114 Technical Guide, SG24-7954-00 - draft available

• Ensemble Publications

– Introduction to Ensembles GC27-2609

– Ensemble Planning and Configuring Guide GC27-2608

– Ensemble Performance Management Guide GC27-2607

– Hardware Management Console and Support Element

– Operations Guide for Ensembles SC27-2606

• DataPower XI50z Material

– http://publib.boulder.ibm.com/infocenter/bladectr/documentation/index.jsp?topic=/com.ibm.bla

decenter.dp_xi50b.doc/dp_xi50b_product_page.html


Expertforum CH #75, 18.-19.10.2011,

Lugano



IBM zEnterprise zBX Reference Material (2 of 2)


• zBX Publications– z196 System Overview SA22-1086

– Hardware Management Console Operations Guide SC28-6895

– Support Elements Operations Guide SC28-6896

– zBX Installation Manual (2458-002) - need to fix link when pub avail GC27-2610

– zBX Installation Manual for Physical Planning (2458-002) GC27-2611

– zBX Safety Inspection GC28-6889

– zBX Service Guide GC28-6884

– zBX Parts Catalog - Appendix in zBX Service Guide GC28-6884

– System z Statement of Limited Warranty GC28-6883

– BladeCenter HS22 (Type 7870) Installation and User's Guide 59Y6959

– BladeCenter HS22 (Type 7870) Problem Determination and Service Guide 59Y6960*

– BladeCenter PS701 and PS702 (Type 8406) Installation and User's Guide - fix link 44R5338

– BladeCenter HS22 (Type 7870) Problem Determination and Service Guide 59Y6960*

– 7014 Series Model T00 and Model T42 System Rack SA38-0577

– IBM eServer™ xSeries® Rack Planning Guide 02R2777

– Installation and Maintenance Guide - DPI C13 PDU+, DPI C13 3-phase PDU+, DPI C19 PDU+, and DPI C19

3-phase PDU+ 43V6030

– Installation and Maintenance Guide - Ultra Density Enterprise C19/C13 PDU+ and PDU Modules 46M1388

– BladeCenter Advanced Management Module User's Guide 44R5380

– IBM Safety Information 02R2735

– Complete Hardware Guide for IBM Ethernet Switch J48E GA32-0663


Expertforum CH #75, 18.-19.10.2011,

Lugano



IBM zEnterprise z196 Update

z196 Update


Expertforum CH #75, 18.-19.10.2011,

Lugano



FICON Express8S – SX and 10KM LX in the PCIe I/O drawer


• For FICON, zHPF, and FCP environments

– CHPID types: FC and FCP

• 2 PCHIDs/CHPIDs

• Auto-negotiates to 2, 4, or 8 Gbps

• Increased performance compared to

FICON Express8

• 10KM LX - 9 micron single mode fiber

– Unrepeated distance - 10 kilometers (6.2 miles)

– Receiving device must also be LX

• SX - 50 or 62.5 micron multimode fiber

– Distance variable with link data rate and

fiber type

– Receiving device must also be SX

• 2 channels of LX or SX (no mix)

• Small form factor pluggable (SFP) optics

– Concurrent repair/replace action for each SFPLX SX

FC 0409 – 10KM LX, FC 0410 – SX

OR

2, 4, 8 Gbps

2, 4, 8 Gbps

FLASH

SFP+

SFP+IBM

ASIC

IBM

ASIC

PCIeSwitch

HBAASIC

HBAASIC

FLASH


Expertforum CH #75, 18.-19.10.2011,

Lugano



zEnterprise zHPF supports data transfers larger than 64 k bytes


� zHPF multi-track data transfers are no longer limited to 64 k bytes

– Up to 256 tracks can be transferred a single operation

– Eliminating the 64 k byte limit is designed to allow a FICON Express8

channel to fully exploit its available bandwidth

– This enhancement is exclusive to z196 and z114

� Designed to help provide

– Higher throughput for zHPF multi-track operations

– With lower response time

� Requires:

– FICON Express8 and 8S or FICON Express4 channel

– CHPID TYPE=FC definition

– Control unit support for zHPF

� z/OS operating system support

White Paper: “High Performance FICON (zHPF) for System z Analysis”http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP101789

High Performance FICON (zHPF) for DS8000 System z Attached Analysis: AG Storage ATS Offeringhttp://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/FLASH10668


Expertforum CH #75, 18.-19.10.2011,

Lugano



FICON performance on System z


1200

14000

31000

20000

52000

23000

92000

0

10000

20000

30000

40000

50000

60000

70000

80000

90000

100000

I/O driver benchmark I/Os per second4k block sizeChannel 100% utilized

FICONExpress4and

FICONExpress2

zHPF

FICON Express8

zHPF

FICON Express8FICON

Express4andFICONExpress2

ESCON

zHPF

FICON Express8S

FICON Express8S

z10 z10z196z10

z196z10

z196z114

z196z114

350

520

620

770

620

1600

0

100

200

300

400

500

600

700

800

900

1000

1100

1200

1300

1400

1500

1600

1700

FICON Express44 Gbps

I/O driver benchmarkMegaBytes per secondFull-duplexLarge sequentialread/write mix

FICONExpress44 Gbps

FICON Express88 Gbps

FICON Express88 Gbps FICON

Express8S8 Gbps

FICON Express8S8 Gbps

z10z9 z10

z196

z10

z196

z10z196z114

z196z114

zHPF

zHPF

zHPF

77% increase

108% increase


Expertforum CH #75, 18.-19.10.2011,

Lugano



OSA-Express4S GbE and 10 GbE fiber for the PCIe I/O drawer


� 10 Gigabit Ethernet (10 GbE)

– CHPID types: OSD, OSX

– Single mode (LR) or multimode (SR)

fiber

– One port of LR or one port of SR

• 1 PCHID/CHPID

� Gigabit Ethernet (GbE)

– CHPID types: OSD (CHPID OSN not

supported)

– Single mode (LX) or multimode (SX)

fiber

– Two ports of LX or two ports of SX

• 1 PCHID/CHPID

� Small form factor optics – LC Duplex

FC 0406 – 10 GbE LR, FC 0407 – 10 GbE SR

PCIeIBM

ASIC

FPGA

PCIeIBM

ASIC

FPGA

FC 0404 – GbE LX, FC 0405 – GbE SX


Expertforum CH #75, 18.-19.10.2011,

Lugano



OSA-Express4S 10 GbE performance (laboratory)


Mixed Streams – 1492 Byte MTUs

1240

2080

0

500

1000

1500

2000

2500

MB

ps

680

1180

0

200

400

600

800

1000

1200

1400

MB

ps

615

1120

0

200

400

600

800

1000

1200

1400

MB

ps

11801680

0

500

1000

1500

2000

2500

MB

ps

Inbound Streams – 1492 Byte MTUs

OSA-E3 OSA-E4S

80% increase

70% increase 70% increase

40% increase

Mixed Streams – 8000 Byte MTUsInbound Streams – 8000 Byte MTUsOSA-E3 OSA-E4S

OSA-E3 OSA-E4S OSA-E3 OSA-E4S

Notes:

� AWM on z/OS

� z/OS is doing checksum

� 1 megabyte per second

(MBps) is 1,048,576

bytes per second

MBps represents payload

throughput (does

not count packet

and frame headers)

Maximum transmission units (MTUs)


Expertforum CH #75, 18.-19.10.2011,

Lugano






Expertforum CH #75, 18.-19.10.2011,

Lugano



z/OS Update and Statement of Direction

z/OS Statement of Direction

April 11, 2012

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

• After 11 years of successful releases of z/OS Version 1, IBM is announcing the next

version of z/OS, z/OS Version 2, which is designed for smarter computing

• In response to customer requests, a new release schedule of approximately every two

years is also being announced

• Changes to service and support for existing releases are also being announced in order

to better assist customers in their migration effort

• The first release of z/OS Version 2 is planned to be available in the second half of 2013

• z/OS is planned to make a new release available on a schedule of approximately every

two years, providing customers ample time to drive growth and application deployments

• Future releases are planned to be available approximately every two years after z/OS

Version 2’s availability in the second half of 2013

• With the new version of z/OS, IBM plans a new cadence along with new delivery of

business value to better leverage your IBM System z® investments


Expertforum CH #75, 18.-19.10.2011,

Lugano




z/OS Statement of Direction...

April 11, 2012


• It is intended that the new enhancements to service and support schedules for z/OS

Version 2 will afford customers more opportunity to leverage the maximum business value

from System z and z/OS and respond to customer requests to have more time between

releases

• In addition, the enhanced support policy better aligns with IBM's middleware software

support practices to help you with planning efforts

• A z/OS release every other year gives you more time to develop new applications under

z/OS and more fully utilize the function in new z/OS releases

• It allows you to spend more time to plan for the release and to understand the features in

the release

• IBM recognizes the need to provide important time-sensitive functionality between

releases, such as support for new hardware

• Existing delivery mechanisms of product features, Small Programming Enhancements

(SPEs), or web deliverables may be used as appropriate to help address customer needs


Expertforum CH #75, 18.-19.10.2011,

Lugano





April 11, 2012


• Enhancements will be considered for interim delivery both through the service stream

and through web deliverables

• You will always be able to go to the z/OS website (http://www.ibm.com/zos) to find new

and exciting information on the features and functions of z/OS

• IBM plans to support an n-2 approach, where three consecutive releases are planned to

be supported for coexistence, fallback, and migration

• For example, where "n" is z/OS Version 2.1, IBM intends to support upgrades from

z/OS V1.12 directly to z/OS Version 2.1 with full coexistence, migration, and fallback

support

• Similarly, IBM intends to support direct migration from z/OS V1.13 to z/OS Version 2.1

with full coexistence, migration, and fallback support

• Customers will not be able to migrate older releases such as z/OS V1.11 to z/OS

Version 2.1 and should plan to upgrade to a more current release


Expertforum CH #75, 18.-19.10.2011,

Lugano





April 11, 2012


• IBM is announcing that support is planned to be provided for z/OS V2.1 for five years

with optional fee-based extended service for three additional years

• This is referred to by IBM as "5 plus 3" or "5+3"

• This is a change from our current policy of three years plus a two-year optional fee-

based extended service and is intended to enable you to better leverage your System z

investments and upgrade more seamlessly

• It is intended that the new release schedule and support plans for z/OS Version 2 will

allow you more opportunity to exploit z/OS and System z functions for maximum

business value

• Servers supported with z/OS Version 2:

– IBM System z9 Enterprise Class (z9 EC) and IBM System z9 Business Class (z9 BC)

– IBM System z10® Enterprise Class (z10 EC™), IBM System z10 Business Class™ (z10 BC)

– IBM zEnterprise™ 196 (z196) and zEnterprise 114 (z114)


Expertforum CH #75, 18.-19.10.2011,

Lugano





April 11, 2012


• Storage control units supported with z/OS Version 2:

– 3990 Model 3 and 3990 Model 6

– 9393

– 2105

– 21072421, 2422, 2423, and 2424

• Beginning with z/OS Version 2, IBM intends to no longer offer support for the following

older DASD storage devices:

– 2835-2 3880-23

– 3380-CJ2 3880-3

– 3830-2 3880-4

– 3830-3 399

– 3851 3990-1

– 3880-1 3990-2

– 3880-11 3995-151

– 3880-13 3995-153

– 3880-2 3880-23


Expertforum CH #75, 18.-19.10.2011,

Lugano





April 11, 2012

• Service periods for z/OS V1.11, V1.12, and V1.13:

– z/OS V1.11: Following the withdrawal of program services on September 30, 2012,

up to two years of extended service will be available through IBM Lifecycle Extension

for z/OS V1.11

– z/OS V1.12: z/OS support is planned to be increased from three years to four years.

Support for Version 1.12 is planned to be extended from September 30, 2013, to

September 30, 2014

– z/OS V1.13: z/OS support is planned to be increased from three years to five years.

Support for Version 1.13 is planned to be extended from September 30, 2014, to

September 30, 2016

In addition, the ordering period for z/OS V1.13 is planned to be extended until z/OS

Version 2 becomes available



Expertforum CH #75, 18.-19.10.2011,

Lugano





April 11, 2012


• A two-year versus annual release cycle does not mean that z/OS will contain twice as

much function as before and therefore require twice the testing lead time

• Though IBM intends to deliver significant functionality with each z/OS release, it does

not imply twice the required testing

– Some of the release content is designed as support for future function or has to do

with error recovery, and as such, is not necessarily code that would be tested by

customers or ISVs

– Some content is planned to package incremental functions in more appropriate

ways so as to deliver a larger functional benefit at once

– Therefore, the releases beginning with z/OS Version 2 are intended to be

packaged in ways that might actually make testing easier as ISVs and developers

will not have to test many incremental capabilities, and can test more complete

functions all at once


Expertforum CH #75, 18.-19.10.2011,

Lugano




Annual Cycles split Functions over multiple Releases

Functions z/OS

V1.7

z/OS

V1.8

z/OS

V1.9

z/OS

V1.10

z/OS

V1.11

z/OS

V1.12

z/OS

V1.13

Consoles restructuring X X X

Parallel VARY processing X X

Password phrases X X X

SMF data to System Logger X X X X

NFS V4 X X

Message Flooding Automation X X X

System REXX™ (SYSREXX) X X

Large (1 MB) pages X X X

Extended Address Volumes (EAVs) X X X X

zHPF X X

Catalog constraints X X

Implementing functions over several releases makes it more difficult to see value in each step


Expertforum CH #75, 18.-19.10.2011,

Lugano






• Summary

– Version 2 of z/OS targeted to Availability 2H2013

– A Version 2 release is the next z/OS release, no “V1.14”

– Release delivery cycle is planned to be every two years, in the second half of that

calendar year

– z/OSMF will be on the same cycle as z/OS

– N+1 or N+2 release migrations support two or four year migration cycle

– New five Year Support with optional fee based service extension

– IBM plans to deliver hardware support updates between releases (PTFs, web

deliverables)

– Minimum supported hardware levels

• Changes to Current Releases:

– R12 Support extended to four years

– R13 Support extended to five years to bridge customers to Version 2 migrations

– R13 orderable until Version 2 becomes available


Expertforum CH #75, 18.-19.10.2011,

Lugano



z/OS Support Summary

z/OS Support Summary


• Transition Timing (to 5+3)

– Release 11 has three Years Support +2 LCE

– Release 12 has four Years Support +3 years service

– Release 13 has five Years Support +3 years service

– 5 + 3 Model transitions at R13 and continues with Version 2 going forward

• Migration and Support

– Longer support lifecycles align with delivery cycles

– Maintaining “N+2” migration paths, now becomes every two or four years

– Bridge migration from currently supported releases


Expertforum CH #75, 18.-19.10.2011,

Lugano



Java Levels shipped with z/OS 1.12 and z/OS 1.13

• There are different Java levels shipped with z/OS 1.12 and z/OS 1.13

• For a smooth migration, in a mixed Sysplex with z/OS 1.12 and z/OS 1.13, to prevent any problems related to these different load module names, do the following:

• Otherwise, with z/OS 1.13 jobs using the old (z/OS 1.12) load module names may fail with S806 ABENDs (load module not found)

• Copy the old (z/OS 1.12) load modules into a LNKLST library accessible in z/OS 1.13



• Because of the different Java levels supplied in these 2 releases of z/OS, the names of the load modules delivered are different

• When all systems in a Sysplex are migrated to z/OS 1.13, update the JCL and procedures to use the new (z/OS 1.13) load module names and then delete the old (z/OS 1.12) load modules in the z/OS 1.13 LNKLST library

• As a consequence, when migrating to z/OS 1.13 users may have to update their JCL and procedures to specify the new Java load modules names shipped with z/OS 1.13


Expertforum CH #75, 18.-19.10.2011,

Lugano



Java Levels shipped with z/OS 1.12 and z/OS 1.13 (cont.)

• z/OS 1.12 was shipped with Java Version 5 and Java Version 6.0

• z/OS 1.12:

• z/OS 1.13:



• In z/OS 1.13, Java Version 6.0.1 and Java Version 7 are delivered

• ServerPac dataset names used for the Java libraries:

JVMLDM56Java V5 64-Bit Modification Level 0OMVS.JAVA64V5




Load Module NameJava Version and LevelDataset Name:

JVMLDM67Java V6 64-Bit Modification Level 1OMVS.JAVA64M1



JVMLDM61Java V6 31-Bit Modification Level 1OMVS.JAVA31M1

Load Module NameJava Version and LevelDataset Name:


Expertforum CH #75, 18.-19.10.2011,

Lugano






Expertforum CH #75, 18.-19.10.2011,

Lugano



APAR's of Interest

APAR's and Red Alerts• OA32240 (Hiper) ABEND073 RC28 in IOSHSSUB can occur during HyperSwap after adding

Devices dynamically in the alternate Subchannel Set

• OA36875 (Hiper) New Function: change HyperSwap API Pacing Delay Algorithms

• OA37064 (Hiper) IOSHM0308I FreezeAll failed

• OA37588 New Function: System Logger processes Log Data Delete Requests during Logstream Offload

• OA37802 CFCC nondisruptive Dumps are needed when Duplex Requests are determined to be out of Sync

• OA37878 (Hiper) ABEND0C4 in IAXUA during steal Frame Processing

• OA38014 (Hiper) Overlay of what is loaded past IGVSTBL in the Nucleus

• OA38093 (Hiper) IOSNODEBLOCKLATCH Latch Hang and Deadlock

• OA38400 (Hiper) ABEND073 RC28 in Lock Manager called from IAXV6 while processing a Page Fault by an SRB

• OA38451 (Hiper) System and Address Space Fix Counts may be invalid after an Attempt to FREEMAIN a locked Page

• OA38559 (Hiper) IXLCONN SUSPEND=FAIL Setting is lost after System-managed Rebuild

• OA38637 Coupling Facility Structure is not deallocated during Copy Phase of System-managed Rebuild

• OA38650 (Hiper) Basic HyperSwap Config incomplete

• OA38742 (Hiper) Difference in ASMIORQR / ASMIORQC Counts become large enough to affect

Frame Steal Processing and ASMIORQR incremented to high

• OA38759 (Hiper) IOS291I issued for Alias Devices after making Hardware Configuration Changes

• OA38791 (Hiper) ABEND0C4 in ISTTRQAI when using APPN ROUTE Selection Trace

• OA38796 (Hiper) High Async Service Times for XCF Signalling Structures

• OA38834 (Hiper) SYS.BPX.A000.FSLIT.FILESYS.LSN orphaned Latch causes Mount Latch Contention

BPXFVLAT ABEND878 OSI_LKFS FROM GFUBSYNC


Expertforum CH #75, 18.-19.10.2011,

Lugano



APAR's of Interest

APAR's and Red Alerts…• OA38842 (Hiper) SIGIO ASYNCIO Hang TCB Exit Signal pending ABENDU4083 ABEND0C1 AIOEXITMODETCB

• OA38942 (Hiper) ADR351E (001)-ZBLK (01), unexpected EOF on DDNAME when Source Dataset Extents

dumped from EAS Region of a EAV

• OA39091 IEA796E issued during STP Sync Check Processing

• OA39149 (Hiper) IOSVFDSD ABEND S00D3-013 when building CCW to read Volume Label

• PM51093 (Hiper) DB2 V10 NFM Recover Utility getting RC00C901012 in DSNIBHRE with various ERQUALs

due to broken Page during Log Apply

• OAxxxxx (Hiper) bla bla bla...


Expertforum CH #75, 18.-19.10.2011,

Lugano



APAR's of Interest

APAR's and Red Alerts…• And last, but not least, a special notice of attention:

It has come to IBM's attention that customers may not be validating the currency of their security and system

integrity service levels and promptly installing all security and integrity PTFs when made available by IBM

IBM strongly recommends that users of the z/OS Operating System validate the currency of security and system

integrity service and take action to promptly install all security and integrity PTFs

Security and system integrity fixes are included in Recommended Service Upgrades (RSUs) and maintaining

RSU currency minimizes exposure to security and integrity issues

IBM also recommends that customers subscribe to the System z Security Portal

The portal enables you to receive the latest critical service information on security and system integrity APARs

for z/OS and z/VM

If you are not subscribed to this portal, instructions are located at URL:

http://www.vm.ibm.com/security/aparinfo.html

Once you are registered at the portal, subscribers will receive an email notification of all new posts

Important information about critical security and system integrity APARs and associated fixes are posted to this

portal which can help you to plan the timely installation of this critical service


Expertforum CH #75, 18.-19.10.2011,

Lugano






Expertforum CH #75, 18.-19.10.2011,

Lugano



Enable/disable automatic Structure Alteration

Enable/disable Start Alter Processing with z/OS 1.13

• SETXCF MODIFY Command Enhancement

• OA37566 as well

SETXCF MODIFY,STRNAME=strname,ALTER=DISABLED

• Only systems with support will honor ALTER=DISABLED indicator inthe active policy

• So you may not get the desired behavior until the function is rolled around the sysplex

• APAR OA34579 for z/OS V1R10 and up

• But fall back is trivial since downlevel code ignores it

SETXCF MODIFY,STRNAME=strname,ALTER=ENABLED

STRNAME=strname

STRNAME=strprfx*

STRNAME=ALL | STRNAME=*

D XCF,STRUCTURE, ALTER={ENABLED|DISABLED}


Expertforum CH #75, 18.-19.10.2011,

Lugano



z/OS 1.13 Run Time Diagnostics

Run Time Diagnostics with z/OS 1.13

• Allows installations to quickly analyze a system experiencing “sick but not dead” symptoms

• Looks for evidence of “soft failures”

• Reduces the skill level needed when examining z/OS for “unknown”problems where the system seems “sick”

• Provides timely, comprehensive analysis at a critical time period with suggestions on how to proceed

• Runs as a started task in z/OS V1R12

• S HZR

• Starts at IPL in z/OS V1R13

• F HZR,ANALYZE command initiates report


Expertforum CH #75, 18.-19.10.2011,

Lugano



z/OS 1.13 Run Time Diagnostics

Run Time Diagnostics with z/OS 1.13...

• Does what you might do manually today:

• Evaluate local lock conditions

• Examine address spaces with high CPU usage

• Review critical messages in the log

• Look for an address space that might be in a loop

• Analyze contention

– GRS ENQ

– GRS Latches

– z/OS UNIX file system latches

• Perform additional analysis based on what is found

• For example, if XES reports a connector as unresponsive, RTD will investigate the appropriate address space


Expertforum CH #75, 18.-19.10.2011,

Lugano



How to?




Expertforum CH #75, 18.-19.10.2011,

Lugano



Extended SMF Dump Statistics Report


• When dumping SMF, by either using IFASMFDP (dataset recording) or IFASMFDL (logger recording), a standard SMF dump statistics report will be written to SYSPRINT

• This statistics report contains the number records read and written of each SMF record type

• But there’s no information on what SMF record sub-types and how many of them have been read and written

• When using SMF logger, wouldn’t it be very useful to get a statistic on the individual systems in the Sysplex participating in the SMF logger sharing environment?

• Provided as additional material of Redbook “SMF Logstream Mode -Optimizing the new Paradigm” (SG24-7919), there’s a tool which will produce this kind of detail information

• How many records of each SMF record type have been dumped from an individual system?

• What SMF record sub-types and how many of them have been dumped from an individual system?


Expertforum CH #75, 18.-19.10.2011,

Lugano




Extended SMF Dump Statistics Report (cont.)

• This tool consists of IFASEXIT SMF logger exits

• These exits provide following enhancements to the SMF standard dump statistics report:

• These IFASEXITs have been written by Mario Bezzi (IBM Italy), who is a co-author of the SMF logger redbook (SG24-7919)

• Create an additional SMF dump statistics report with the number of SMF records of each type and sub-type dumped from an individual system

• The tool is easy to install and immediately provides the detailed information you may always have missed!

• Also write the extended SMF dump statistics report to installation-determined SMF record type

– Note: this extended statistics report will be written to SYSPRINT in addition to the SMF standard dump statistics report

– This is optional and can be enabled/disabled by appropriate installation options


Expertforum CH #75, 18.-19.10.2011,

Lugano





• On the redbooks additional material web page, the tool can be downloaded as zipped XMIT files

• To download and install the tool, proceed as follows:

• On your workstation, unzip file “SG247919.zOStools.zip”

• Go to the redbooks homepage:

• Click on the folder marked “SG247919”

– ftp://www.redbooks.ibm.com/redbooks/

• Click on “Additional Materials”

• Binary download file “SG247919.zOStools.zip” to your workstation

• Binary upload file “SMFDPUX.V2R1M1.CNTL.XMIT” to a z/OS system

• On your z/OS system, RECEIVE (un-XMIT) file “SMFDPUX.V2R1M1.CNTL.XMIT”to a PDS

– A documentation in form of a PPS-show

• The resulting PDS will contain a couple of members, such as:

– An ASMPARMS JCL sample to assemble and link-edit the installation options

– XLOADLIB, an XMIT-member containing a load library with the IFASEXITs


Expertforum CH #75, 18.-19.10.2011,

Lugano





• To download and install the tool, proceed as follows (cont.):

• To finally install the IFASEXITs into a load library accessible by your z/OS systems, I would highly recommend to use an SMP/E usermod (see next foils)

• RECEIVE (un-XMIT) the XLOADLIB member into a (new) load library, e.g.:

• The target load library must be:

– HLQ.IFASEXIT.SMFLOAD

• Part of the LNKLST concatenation

• APF-authorized

• When using an SMP/E usermod to install the IFASEXITs, as recommended, because it already contains other parts of SMF, the best candidate load library would be SYS1.LINKLIB

• Edit and execute member ASMPARMS in the unloaded PDS to update the installation options according to your needs

• Specify HLQ.IFASEXIT.SMFLOAD as target library


Expertforum CH #75, 18.-19.10.2011,

Lugano





• SMP/E sample usermod:

//STEP01 EXEC PGM=GIMSMP,REGION=0M,PARM='PROCESS=WAIT'

//SMPCSI DD DISP=SHR,DSN=SMPE.Z113GX1.CSI

//SMPOUT DD SYSOUT=*

//SMPRPT DD SYSOUT=*

//SMPLIST DD SYSOUT=*

//SMPLOG DD SYSOUT=*

//SYSPRINT DD SYSOUT=*

//SMPPTFIN DD DATA,DLM=$$

++USERMOD(USMF003) .

++VER(Z038) FMID(HBB7780) .

++MOD(SMFDPUXU) DISTLIB(SMFLOAD) LKLIB(SMFLOAD) .

++MOD(SMFDPUX1) DISTLIB(SMFLOAD) LKLIB(SMFLOAD) .



++MOD(SMFUXPP) DISTLIB(SMFLOAD) LKLIB(SMFLOAD) .

++MOD(SMFUXPRM) DISTLIB(SMFLOAD) LKLIB(SMFLOAD) .

++JCLIN .

....


Expertforum CH #75, 18.-19.10.2011,

Lugano





• SMP/E sample usermod (cont.):....

//STEP02 EXEC PGM=IEBCOPY

//SMFLOAD DD DSN=HLQ.IFASEXIT.SMFLOAD,DISP=SHR

//LINKLIB DD DSN=SYS1.LINKLIB,DISP=SHR

//SYSIN DD *

COPY INDD=SMFLOAD,OUTDD=LINKLIB TYPE=MOD

SELECT MEMBER=((SMFDPUXU,,R))

SELECT MEMBER=((SMFDPUX1,,R))



SELECT MEMBER=((SMFUXPP,,R))

SELECT MEMBER=((SMFUXPRM,,R))

/*

$$

//SMPCNTL DD *

SET BDY(GLOBAL) .

RECEIVE SYSMODS S(USMF003) .

SET BDY(Z113TM1) .

APPLY S(USMF003) REDO .

/*

//SMFLOAD DD DSN=HLQ.IFASEXIT.SMFLOAD,DISP=SHR

//


Expertforum CH #75, 18.-19.10.2011,

Lugano





• To activate the IFASEXITs:

• Last, but not least, to use the IFASEXITs to produce the extended SMF dump statistics, you have to update your SMF dump JCL deck(s)

• Update your SMFPRMxx parmlib member(s) with the following statements:

• Dynamically activate the IFASEXITs by issuing the following MVS Command:

SMFDLEXIT(USER1(SMFDPUX1),

USER2(SMFDPUX2),

USER3(SMFDPUXU))

SET SMF=xx

• In your SMF dump JCL, you have to specify IFASEXITs you want to use (see next foil for an example)


Expertforum CH #75, 18.-19.10.2011,

Lugano





• IFASMFDL sample JCL with IFASEXITs to produce an extended SMF dump statistics report written to SYSPRINT:

//STEP01 EXEC PGM=IFASMFDL

//DUMPDEF DD DSN=HLQ.SMF.DEF.Dyyddd.DATA,DISP=(,CATLG,DELETE),

// UNIT=(SYSDA,5),SPACE=(CYL,(4369,4369),RLSE),

// LRECL=32760,RECFM=VBS,BLKSIZE=0,BUFNO=20,

// DSNTYPE=LARGE

//SYSPRINT DD SYSOUT=*

//SYSMDUMP DD SYSOUT=*,RECFM=FB,LRECL=4160,BLKSIZE=0

//SYSIN DD *

LSNAME(IFASMF.CHHCD001.DEF,OPTIONS(DUMP))

OUTDD(DUMPDEF,TYPE(0:255))

RELATIVEDATE(BYDAY,01,01)

ABEND(NORETRY)

START(0000)

END(2400)

USER1(SMFDPUX1)

USER2(SMFDPUX2)

USER3(SMFDPUXU)

//


Expertforum CH #75, 18.-19.10.2011,

Lugano





• Extended SMF dump statistics report sample:

DETAILED ACTIVITY REPORT FOR OUTPUT DDNAME: DUMPDEF

RECORD RECORD SYSTEM RECORDS BYTES RECORD RECORD START START END END

TYPE SUBTYP ID WRITTEN WRITTEN MINLEN MAXLEN DATE TIME DATE TIME

2 N/A M1 1 18 18 18 12.044 12:07:35.33 12.044 12:07:35.33

3 N/A M1 1 18 18 18 12.044 12:07:38.25 12.044 12:07:38.25

16 N/A D1 2199 1935280 616 2256 12.043 00:00:33.13 12.043 23:59:24.00

16 N/A D2 3429 2984792 616 2256 12.043 00:00:05.55 12.043 23:59:32.53

16 N/A M1 10 8224 816 880 12.043 01:00:44.35 12.043 19:01:09.34

16 N/A N1 12280 10706824 616 1680 12.043 00:00:31.05 12.043 23:54:03.02

16 N/A N2 14094 12313944 616 1968 12.043 00:00:03.22 12.043 23:56:30.33

16 N/A P1 8124 6246424 616 2672 12.043 00:00:18.07 12.043 23:59:37.51

.....

41 1 D2 24 3504 146 146 12.043 08:59:02.21 12.043 20:02:02.53

41 1 M1 12 1752 146 146 12.043 14:18:00.43 12.043 14:18:00.53

41 1 P4 152 22192 146 146 12.043 11:58:18.36 12.043 13:19:35.28

41 2 D2 24 3504 146 146 12.043 08:59:02.21 12.043 20:02:03.04

41 2 M1 12 1752 146 146 12.043 14:18:00.43 12.043 14:18:00.53

41 2 P3 3 438 146 146 12.043 11:55:24.09 12.043 11:55:24.12

41 2 P4 149 21754 146 146 12.043 12:00:06.59 12.043 13:19:35.54

41 3 D1 96 39552 412 412 12.043 00:09:11.23 12.043 23:54:20.57

41 3 D2 96 39552 412 412 12.043 00:13:09.46 12.043 23:58:12.33

41 3 E2 96 39552 412 412 12.043 00:06:08.08 12.043 23:51:10.12

.....


Expertforum CH #75, 18.-19.10.2011,

Lugano



z/OS 1.13 SDSF Syslog/Operlog Viewing Enhancements


• In today’s environments, specially in Parallel Sysplex configurations, lots of WTO messages are produced by various components and products

• Because the system logs are “flooded” with these messages, in case of a problem it’s vary difficult and time consuming to scroll through the Syslog/Operlog to find right messages identifying an error

• If not deleted by automation or MPF exits, these messages are also written to Syslog and/or Operlog

• For viewing Syslog/Operlog online, SDSF shipped with z/OS 1.13 provides a nice enhancement which makes it much easier to browse the logs for appropriate messages:

• This is through whether one is looking at online logs with SDSF, or at logs saved in a DASD dataset (eg. a daily Syslog/Operlog dataset)

• SDSF has added color support for messages based on WTO descriptor codes

• Per default, SDSF will use the standard color assigned to a specific descriptor code

• SDSF default settings can be changed according to installation requirements


Expertforum CH #75, 18.-19.10.2011,

Lugano




z/OS 1.13 SDSF enhanced Syslog/Operlog Panel Example

Test WTO

messages

issued with

various

descriptor

codes, eg.

1 and 2 etc.


Expertforum CH #75, 18.-19.10.2011,

Lugano





• To change the default message colors, on the command line of the SDSF log panel issue SET SCREEN, and the following Pop-up appears:


Expertforum CH #75, 18.-19.10.2011,

Lugano





• On the SET SCREEN Pop-up, you now can change the default message color settings according to your needs

• Recommendation:

• Use default message colors except for messages with descriptor codes 5 and 13

– Normal messages without descriptor code: green

• Change descriptor code 13 (automation information) messages to appear in pink color

• Default message colors:

– Descriptor code 2 (immediate action) messages: white

– Descriptor code 1 (system failure) messages: red

– Descriptor code 12 (important information) messages: yellow

• Change descriptor code 5 (command response) messages to appear in turquoise color


Expertforum CH #75, 18.-19.10.2011,

Lugano




z/OS 1.13 SDSF Syslog/Operlog Panel Example 2

Command

response

message with

descriptor code 5

Important

information

message with

descriptor code 12


Expertforum CH #75, 18.-19.10.2011,

Lugano



Importance of the Z EOD Command

Orderly System Shutdown: the Importance of Z EOD

• For a proper system termination, an MVS Z EOD Command should be issued during shutdown

• Unfortunately, today I often see installations which don’t issue a Z EOD command anymore, whether for a single system or a system in a Sysplex

• Regardless of the configuration (single system, Parallel Sysplex or GDPS), this should always be done after JES has been terminated and OMVS has been shut down

• For a system in a Parallel Sysplex or GDPS, this should be the last action before issuing the V XCF,sysname,OFF command

• But still today, installations should be aware that not issuing a Z EOD command during system termination may lead to a loss of data or missing statistics

• Because of this, I would recommend to review your shutdown procedure and your automation to ensure that Z EOD is included in the termination of a system


Expertforum CH #75, 18.-19.10.2011,

Lugano




Orderly System Shutdown: the Importance of Z EOD (cont.)

• Use the HALT (Z EOD) command to record statistics before stopping the operating system

• Allows SMF to continue writing records after switching to a new dataset

• Closes the system log

• After the stop of all subsystem processing (through the use of the appropriate subsystem command) and when you have been notified that all system activity has completed, you can issue the HALT EOD command to ensure that important job and system statistics and data records in storage are recorded

• Note: do not use the HALT command if you intend to keep running, because this command:

During the next IPL, you might see message IEE949I, indicating the presence of old SMF data from a previous IPL. This SMF data was written after HALT was issued


Expertforum CH #75, 18.-19.10.2011,

Lugano




Orderly System Shutdown: the Importance of Z EOD (cont.)

• The HALT EOD command causes the system to take the following steps:

• When these actions are completed, the system sends you the message:

• Store the internal I/O device error counts in the logrec dataset

IEE334I HALT EOD SUCCESSFUL

• An EOD record is recorded on the logrec dataset

• Empty the SMF buffers onto the active SMF dataset in SYS1.MANx

• Switch to another SMF dataset in SYS1.MANx, allowing the previously active SMF dataset to be dumped according to your installation's procedures

• Close the system log and put it on the JES spool

– Note: there are special considerations when using SMF logger. These will be covered on the next slides


Expertforum CH #75, 18.-19.10.2011,

Lugano




Z EOD and SMF Logger Considerations

• Also with SMF logger, it is still important to issue the Z EOD command during system shutdown

• For this reason, always issue the Z EOD command as part of the process of shutting down a system to avoid any data loss of SMF data, regardless of the SMF recording mode

• Empty the SMF buffers to the current active SMF dataset

• Because there is more space for SMF buffers in log stream mode (up to 2 GB per log stream) than in dataset mode (maximum of 1 GB of buffer space), you could potentially lose more SMF data in log stream mode if you shut the system down without giving SMF a chance to empty all its buffers into the corresponding log streams

• In dataset mode, the following actions take place:

• Switch to the next available SMF dataset to allow the previous active datasets to be dumped

• Issue the IEE334I HALT EOD SUCCESSFUL message

• A type 19 record is created for each online direct access device (if the type 19 records are enabled in the SMFPRMxx Parmlib member)


Expertforum CH #75, 18.-19.10.2011,

Lugano




Z EOD and SMF Logger Considerations...

• When in log stream mode, the following actions take place:

• SMF empties all its buffers to the corresponding log streams

• Up to z/OS V1R11, SMF disconnects from the log stream

• Starting with z/OS 1.12, SMF no longer disconnects from the log stream as part of Z EOD processing

• Issue the IEE334I HALT EOD SUCCESSFUL message

• If the SYS1.MAN datasets are still defined in the active SMFPRMxx member, the IEFU29 exit is invoked to ensure that those datasets are emptied and the data captured

– Note that the IEFU29L exit is not invoked

• However, in log stream mode, the corresponding messages (IEE334I and IFA705I) only indicate that the SMF buffers have all been written to the log stream

• It is possible, even likely, that when that message is issued, the records are still in interim storage and have not been moved to the offload datasets yet


Expertforum CH #75, 18.-19.10.2011,

Lugano





• There are two situations to consider for each log stream:

• Furthermore, starting with z/OS 1.12, SMF no longer disconnects from its log streams as a result of the Z EOD command, and without that disconnect, there is no trigger to System Logger during system shutdown that it should move everything from interim storage to the offload datasets

• The log stream, or the structure the log stream resides in, is being used by more than one system

• Even though SMF does not disconnect from the log stream when the Z EOD command is issued, when the system that is being shut down is partitioned from the Sysplex, one of the other systems that is connected to the same log stream or the same structure will do an offload and clean up the connection from the system that was shutdown

• This is one of the reasons why each log stream should be used by multiple systems


Expertforum CH #75, 18.-19.10.2011,

Lugano





• The log stream, or the structure the log stream resides in, is only being used by one system

• In this case, the data in the log stream remains in the log stream until that system connects to the log stream again

• The only real exposure is for a CF-only log stream, and even in that case, the only exposure is if the CF goes down before the system reconnects to the log stream

• There are two situations to consider for each log stream (cont.):

• If this is a concern to you, you can manually initiate an offload by running the IBM-provided IXGOFLDS process on another member of the Sysplex

• If the availability of all your SMF data is critically important to you, you might integrate the start of this process (for each SMF log stream) on another member of the sysplex as part of your shutdown automation process

• IXGOFLDS sample JCL:

//IXGOFLDS EXEC PGM=IXGM1OFL,

// PARM='LOGSTRM=IFASMF.PLEXTEST.RMF’


Expertforum CH #75, 18.-19.10.2011,

Lugano




Shutting down z/OS Systems in a GDPS Environment

• Phase 1

• There are two distinct phases in the final shutdown processing that are defined using the special message id SYSTEM_SHUTDOWN message/user data policy item for the MVS Component entry type

• Phase 2

• System Automation for z/OS allows you to shut down z/OS systems either through the INGREQ ALL command in a GDPS environment or from a GDPS controlling system

– This phase begins when the resource that is identified by the GDPS STOPAPPL parameter (the STOPAPPL resource) has been terminated

– In this phase you can specify additional INGREQ stop commands or any other commands through Netview to terminate any subsystems that are still present

– This phase begins after the takeover of OMVS and any local automation manager (PAM and SAMs)

– Only Netview commands or z/OS commands issued through Netview can be specified (for example, the MVS Z EOD command)


Expertforum CH #75, 18.-19.10.2011,

Lugano




Shutting down z/OS Systems in a GDPS Environment (cont.)

• SA for z/OS policy message processing item:


Expertforum CH #75, 18.-19.10.2011,

Lugano





• SA for z/OS policy message processing item SYSTEM_SHUTDOWN:

Please note that phase 2 does not specify

the Z EOD command, but a REXX exec

named ZEOD. See next foil for reasons.


Expertforum CH #75, 18.-19.10.2011,

Lugano




• When you specify the Z EOD command to be issued during phase 2, as of today SA for z/OS will issue the command, but unfortunately it does not wait for the command to complete, eg. it does not wait for message IEE334I (HALT EOD successful)

• SA for z/OS just issues Z EOD the command and then passes control to GDPS, which then will immediately issue the V XCF,sysname,OFF command to remove the system from the Sysplex

• As the Z EOD command will take a couple of seconds, this results in the removal of the system from the Sysplex before the Z EOD actions have been completed

• To prevent this, and to ensure that the Z EOD command has been completed before SA for z/OS passes control to GDPS, instead of directly specifying the Z EOD command for phase 2, define a small REXX exec which does the following:

1. Issue the Z EOD command

2. Wait for message IEE334I (HALT EOD successful)

3. Return (to SA for z/OS)



Expertforum CH #75, 18.-19.10.2011,

Lugano





• ZEOD (Z EOD) sample REXX exec:

/* REXX **************************************************************/exit_rc = 0 'TRAP AND DISPLAY MESSAGES IEE*' 'MVS Z EOD' do while exit_rc = 0 'WAIT 20 SECONDS FOR MESSAGES' select when (event()='M') then do

'MSGREAD' if msgid() = 'IEE334I' then do exit_rc = 1

end else do say 'Message IEE334I not trapped. Waiting for message' 'WAIT CONTINUE'

end end when (event()='T') then exit_rc = 12 when (event()='G') then exit_rc = 8 otherwise exit_rc = 20

end end

Thanks to Christoph Toneatti (Swiss Re) for providing this REXX sample


Expertforum CH #75, 18.-19.10.2011,

Lugano




Z EOD Command Reference Material

• SMF Log Stream Mode - Optimizing the new Paradigm, SG24-7919

• z/OS MVS System Commands, SA22-7627

• System Automation for z/OS Planning and Installation, SC34-2571


Expertforum CH #75, 18.-19.10.2011,

Lugano






Expertforum CH #75, 18.-19.10.2011,

Lugano



� z/OS 1.13 Implementation, SG24-7946-00

� SG24-7961-00 z/OS V1R13 DFSMS Technical Update

� zFS Reorganization Tool, REDP-4769-00

� Approaches to optimize Batch Processing on z/OS, REDP-4816-00

� Systems Programmer's Guide to z/OS System Logger, SG24-6898-01

� IBM zEnterprise Unified Resource Manager: Building an Ensemble, SG24-7921-00

� Implementing and Managing InfiniBand Coupling Links on System z, SG24-7539-00

� FICON Planning and Implementation Guide, SG24-6497-03

� A structured Approach to assessing heterogenous Workload Deployment to the

IBM zEnterprise System, REDP-4709-00

� Performance Considerations and Measurements for CICS and System Logger, REDP-3768-00

� Using SDSF in a JES3 Environment, REDP-4531-00

� IBM PureFlex System Products and Technology, SG24-7984-00

Redbooks News

New Redbooks and New Redbooks and RedpapersRedpapers


Expertforum CH #75, 18.-19.10.2011,

Lugano






Expertforum CH #75, 18.-19.10.2011,

Lugano



Silvio’s Corner Doc Jukebox

� z/OS 1.13 Installation Planning Checklist, TD105918

� IBM z/OS Statement of Direction, ENUSZP12-0025

� z/OS Statement of Direction FAQ, ZSQ03055-USEN-00

� IBM changes its z/OS Release Plan and extends its Support, ZSL03177-USEN-00

� IBM Lifecycle Extension for z/OS 1.11, ENUSZP12-0032

� IBM zEnterprise z196 and z114 I/O and FICON Express8S Channel Performance, ZSW03196-USEN-01

� IBM zEnterprise and Unified Resource Manager Enhancements, ENUS112-026

� DS8000 HyperPAV - Why is there IOSQ time with HyperPAVs, FLASH10765

� A heavy I/O Batch Processing Comparison, Whitepaper, February 2012

The following Documentations will also be supplied on the GSE z/OS Expert Forum CH Website


Expertforum CH #75, 18.-19.10.2011,

Lugano



Last, but not least…

http://thebrainhouse.ch/gse/silvio

How to get the Handouts for this Session

• The Handouts for this Session and the Documentations listed in the “Doc Jukebox”will be provided on the GSE z/OS Expertforum CH Homepage

To have immediate access to the handouts for this session and the doc‘s provided in the „Doc Jukebox“ the day after this conference, please write down this link!

Silvio's Corner - zExpertenforum

Documents

Transcript of Silvio's Corner - zExpertenforum