Silvio's Corner - 400 Bad Request

GSE z/OS Expertforum Switzerland # 66, 27.-28.3.2007 

Silvio’s Corner 

z/News, Hints and Tips 

Silvio Sasso 

IBM Switzerland, ITS Service Delivery for z/OS 

sisa@ch.ibm.com 

Zürich | 27. März 2007 

Zürich | 26. Oktober 2004 

Silvio Sasso's Corner, GSE z/OS 

Expertforum CH #66, 27.-28.3.2007, 

® 

© 2007 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 




Agenda 

� Journal of Research and Development 1/2007: IBM System z9 Technology and Design 

� IBM sets Record for most U.S. Patents earned yearly 

� IBM System z9: a new Look at the Mainframe 

Hardware News 

� A Focus on IBM System z9 Functions and Features 

� HyperPAV Functionality and Performance 

Software News 

� z/OS 1.9 Preview 

� A Focus on selected z/OS 1.8 Enhancements 

� Operating System Support for IBM System z9 

� Minimum Operating System Support for System z9 Functions 

� z/OS Support Summary 

� IBM System z New Application License Charges (NALC) 

� z/OS ASM Support for large Page Datasets 


Software News… 

� RMF Spreadsheet Reporter Update 

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

Parallel Sysplex Update 

� SFM for XCF Sympathy Sickness 

� CFRM Performance Enhancements Stage 2 in z/OS 1.8 

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

� z/OS Migration Checker Tool 

� SMP/E Library Change File Record Facility 

Redbooks and Redpapers 

Doc Juke Box 




Agenda 



Zürich | 27.März 2007 






6


IBM System z9 Technology and Design 

A detailed View into IBM System z9 Technology 

Journal of Research and Development, Issue January/March 2007 

Topics 

Technology: 

– Optimization of silicon technology for the IBM System z9 

– Design methods for attaining IBM System z9 processor cycle-time goals 

– High-speed interconnect and packaging design of the IBM System z9 

processor cage 

– High-speed source-synchronous interface for the IBM System z9 processor 

– IBM System z9 eFUSE applications and methodology 

System functional Enhancements: 

– zAAPs and zIIPs: Increasing the strategic value of System z 

– Cryptographic system enhancements for the IBM System z9 

– Sharing FCP adapters through virtualization 

– IBM System z9 Open Systems Adapter for Communication Controller for 

Linux 





IBM System z9 Technology and Design 

A detailed View into IBM System z9 Technology 

Journal of Research and Development, Issue January/March 2007, Topics… 

System Availability: 

– Enhanced I/O subsystem recovery and availability on the IBM System z9 

– Fully redundant clock generation and distribution with dynamic oscillator switchover 

– Reducing planned outages for book hardware maintenance with concurrent book replacement 

– Redundant I/O interconnect 

– Concurrent driver upgrade: Method to eliminate scheduled system outages 

for new function releases 

Design Methodology: 

– Open-standard development environment for IBM System z9 host firmware 

– Advanced firmware verification using a code simulator for the IBM System z9 

– Decimal floating-point in z9: An implementation and testing perspective 

Software Development: 

– Practical software reuse for IBM System z I/O subsystems 

http://www.research.ibm.com/journal/rd/511/tocpdf.html 







IBM Innovation 

IBM sets Record for most U.S. Patents earned yearly 

IFI Claims has released the United States Patent and Trademark Office 

(USPTO) annual list of the top patentees for 2006 

With 3,621, IBM surpassed its own record 

and earned more U.S. patents than any other 

company for the fourteenth consecutive year 

Exceeding the next closest patentee by 1,170 


THE INVASION 

DAY 1: Complexity 

overwhelming data center. 

Need more power. Need more 

capacity. Need to stay within 

budget. Deadlines looming. 

Unusual nervous tics surfacing 

daily. 

DAY 2: Time to rethink the role 

of mainframes. New, rightsized 

IBM system z9 will 

provide ideal solution. 

Twitching all but eliminated. 

Breathing returned to normal. 

< 


IBM System z9 – a new Look at the Mainframe 

With a wide range of capacity levels, the new IBM system z9 TM is just the size you need to handle your most demanding business 

problems. While encryption technology helps to ease security worries, innovative technology allows you to centralize data, transactions and 

applications, while keeping your system in alignment with your business processes. The lower energy requirements are good for the 

environment – and for your bottom line. It‘s a whole new way to look at mainframes. 





IBM System z9 – a new Look at the Mainframe 

You can feel calm and relaxed.You really can! Success is just around the corner when you have a System z9 by your side. 

MEET THE NEW IBM System z9. 











12

A Focus on IBM System z9 Functions and Features 

A Vision for System z9 advanced Data Serving 

� With a strong foundation for transaction processing, built on 40+ years of 

technology innovation, System z servers with z/OS ® and DB2 ® can provide 

a premier platform for data serving, today and into the future* 

� IBM plans to continue to invest in new solutions to address customers' 

strategic information on demand goals* 

Today’s 

Capabilities 

� Industry-leading data integrity and rich 

security features 

� Data sharing solution for centralized 

view of data 

� Scalability and availability for enterprise 

class workloads 

� Comprehensive systems and data 

management environment 


Extension of 

capabilities* 

� New specialty engine (zIIP) with DB2 exploitation - 

for mission critical ERP, CRM, and Data 

Warehousing workloads * 

� Database support improves regulatory compliance 

and autonomics 

� Support of encryption capability (tape subsystem) 

with z/OS centralized key mgmt 

� Data protection designed to achieve highest levels 

of security certifications 


Expertforum IBM System CH #66, z9 27.-28.3.2007, 

– The Enterprise Hub 

� Additional zIIP exploitation 

Future 

direction* 

� DB2 enhancements to help improve 

usability and reduce complexity and 

management costs. 

� DB2 table scan acceleration via IBM 

TotalStorage ® DS8000 

� Support of encryption capability (disk 

subsystem) with z/OS centralized key 

mgmt 

� Handle larger volumes of data, with 

improved scalability 

* All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these Statements of General Direction is at the relying 

party's sole risk and will not create liability or obligation for IBM. 


IBM System z9: Balanced System Design 

GBs 

512 GB 



256 GB 

*z9 EC exploits a subset of its designed I/O capability 

System I/O Bandwidth 

172.8 GB/sec 

96 GB/sec 

24 GB/sec 

64 GB 288.15 450 ~ 600 

32-way 

54-way 

CPUs 

16-way 




Balanced System 

CPU, nWay, Memory, 

I/O Bandwidth* 

System z9 EC* 

zSeries 990 

zSeries 900 

Generation 6 

Generation 5 

ITRs for 1-way 


z9 EC 12-way MCM 

Advanced 95mm x 95mm MCM 

– 102 Glass Ceramic layers 

– 16 chip sites, 217 capacitors 

– 0.545 km of internal wire 


MSC PU PU MSC 

PU 

PU 

CLK 

SD SD 

SD SD 

PU SC PU 


PU 

PU 




CMOS 10Ks0 chip Technology 

– PU, SC, SD and MSC chips 

– Copper interconnections, 10 copper layers 

– 8 PU chips/MCM 

15.78 mm x 11.84 mm 

121 million transistors/chip 

L1 cache/PU 

– 256 KB I-cache 

– 256 KB D-cache 

0.58 ns Cycle Time 

– 4 System Data (SD) cache chips/MCM 

15.66 mm x 15.40mm 

L2 cache per Book 

– 660 million transistors/chip 

–40 MB 

– One Storage Control (SC) chip 

16.41mm x 16.41mm 

162 million transistors 

L2 cache crosspoint switch 

L2 access rings to/from other MCMs 

– Two Memory Storage Control (MSC) chips 

14.31 mm x 14.31 mm 

24 million transistors/chip 

Memory cards (L3) interface to L2 

L2 access to/from MBAs (off MCM) 

– One Clock (CLK) chip - CMOS 8S 

Clock and ETR Receiver 


z9 EC: New Functions/Features of Microcode Level 63J plus MCL’s 

New Specialty 

Engine – IBM zIIP 

CBU for zIIP 

PU Conversions for 

zAAPs and zIIPs 

CBU 

Enhancements 

On/Off CoD 

Enhancements 



24 New 

subcapacity settings 

Server Time Protocol 

Note: Please refer to the latest PSP bucket for latest PTFs for new functions/features 




New FICON 

Express4 

Improved FICON 

Error Recovery 

OSA Layer 2/3 

Enhancements 

Crypto 

Enhancements 

Availability in EU 

after implementation 

of RoHS 



System z9 Specialty Processor Enhancements 

Flexibility for management of Processor Unit (PU) types 

– All zIIPs, zAAPs, ICFs and IFLs now managed as individual separate types/pools by PR/SM 

Help improve weight management 

– Independent PR/SM weight management for both CPs, zAAPs and zIIPs configured to each 

ESA mode logical partition. 

Enhanced z/OS support for zAAPs and zIIPs 

– WLM goal mode management for zAAPs and zIIPs 

– WLM dynamic monitoring of work priorities on zAAPs and zIIPs so that goals can be met 

– Both Java technology and non Java technology work may each have individual goals 

WLM manages each individually and collectively 







System z9 PR/SM Hypervisor PU Pool Rules 

Logical PUs dispatched from supporting pool only 

– Logical CPs from CP pool only, for example 

Pool “width” 

– Width equals the number of PUs in the pool 

– Limits LPAR maximum number of shared logical PUs brought ON 

PUs placed in pools by 

– Activate (POR) 

– Concurrent Upgrade – IBM System z9 On/Off Capacity in Demand (On/Off CoD), Capacity 

BackUp (CBU), Customer Initiated Upgrade (CIU), Capacity Upgrade on Demand (CUoD) MES 

– Dedicated LPAR deactivation 

– Dedicated LPAR configure logical PU OFF 

PUs removed from pools by 

– Concurrent Downgrade – On/Off CoD, CBU, PU Conversion MES 

– Dedicated LPAR activation (“width” permitting) 

– Dedicated LPAR configure logical PU ON (“width” permitting) 

PUs can be CPs, IFLs, ICFs, zAAPs or zIIPs 







System z9 PR/SM Hypervisor PU Dispatching “Pools” 

PU Pool – Physical PUs to dispatch to online logical PUs 

z9 EC with 10 CPs, 1 ICF, 2 IFLs, and 3 zAAPs 

– CP pool contains 10 CP engines 

– ICF pool contains 1 ICF 

– IFL pool contains 2 IFLs 

– zAAP pool contains 3 zAAPs 

– z/OS LPAR can have different initial CP and zAAP weights 

z990 with 10 CPs, 1 ICF, 2 IFLs, and 3 zAAPs 

– CP pool contains 10 CP engines 

– Specialty pool contains 6 engines – ICFs, IFLs, zAAPs 

– z/OS LPAR zAAP weight is set equal to the initial CP weight 







Example: z990 with 10 CP’s, 1 ICF, 2 IFL’s, and 3 zAAP’s 

LPAR Share = Pool PUs x (LPAR Pool Weight)/(Total Pool Weight) 

– Can’t exceed number of Online Logical Processors dispatched from the pool 

– z/OS LPAR – “Initial” weight applies to CPs and to zAAPs 

Pool PUs (Physical) – CP =10, Specialty = 6 (ICF, IFL, zAAP) 

Total Pool Weights – CP = 1000, Specialty = 1500 

LPAR 

Name 

zOS1 

zOS2 

CF1 

CF2 

zVM1 

LINUX1 

LPAR Weight 

Pool Weight > 

250c / 250z 

750c / 750z 

50 

50 

100 

300 

CP 

10 

10 

0 

0 

0 

0 

1000 

Interaction among specialty engine weights impact share 


Shared Logical PUs ON 

zAAP 

2 

3 

NA 

NA 

NA 

NA 

IFL 

NA 

NA 

NA 

NA 

2 

2 

1500 

ICF 

NA 

NA 

1 

1 

NA 

NA 

Total PUs (Physical) > 

CP 

2.5 

7.5 

0 

0 

0 

0 

10 

PU Share 

Specialty 

1.2 




1 

3 

.2 

.2 

.4 

6 

CP 

Specialty 



Example: z9 EC with 10 CPs, 1 ICF, 2 IFLs, and 3 zAAPs 

LPAR Share = Pool PUs x (LPAR Pool Weight)/(Total Pool Weight) 

– Can’t exceed number of Online Logical Processors dispatched from the pool 

– z/OS LPAR – Separate “Initial” weights for CPs and zAAPs 

Pool PUs (Physical) – CP =10, zAAP = 3, IFL = 2, ICF =1 

Total Pool Weights – CP = 1000, zAAP = 200, IFL= 400, ICF= 100 

LPAR 

Name 

zOS1 

zOS2 

CF1 

CF2 

zVM1 

LINUX1 

LPAR Weight 

250c / 100z 

750c / 100z 

50 - ICF 

50 - ICF 

100 - IFL 

300 - IFL 0 NA 2 NA 0 NA 1.5 NA 

Pool Weight > 

Shared Logical PUs On 

CP 

10 

10 

0 

0 

0 

1000 

zAAP 

200 

No interaction among specialty engine weights 

2 

3 

NA 

NA 

NA 


IFL 

NA 

NA 

NA 

NA 

2 

400 

ICF 

NA 

NA 

1 

1 

NA 

100 

Total PUs (Physical) > 

CP 

2.5 

7.5 

0 

0 

0 

10 

zAAP 

1.5 

1.5 

NA 

NA 

NA 

3 

PU Share 

IFL 

NA 

NA 

NA 

NA 

NA 




.5 

2 

ICF 

NA 

NA 

.5 

.5 

1 

© 2004 IBM Corporation 21 

CP 

zAAP 

IFL 

ICF


z9 EC Models and Physical Upgrades 







System z9 – I/O Configuration Growth – Multiple Subchannel 

Sets (MSS) 

System z9 2094 

Logical Channel Subsystem 

128K Subchannels 

63.75K 64K 

Base 

Base 

Base 

Base 

Base 

Base 

Base 

Base 

Base 

Base 

Base 

Base 

Alias 

Alias 

Alias 

Alias 

Alias 

Alias 

Alias 

Alias 

Alias 

Alias 

Alias 


System z9 2094 

DASD Configurations 

Increased to 128K Device 

Bases Aliases 






System z9 – Multiple Subchannel Sets (MSS) 

A 2094 Logical Channel Subsystem can have up to two Sets of Subchannels 

2094 Processor 


63.75K 

SS-0 

Partitions 

Subchannels 

Channels 


64K 

SS-1 

Bases Aliases 






System z9 – Multiple Subchannel Sets per LCSS 

Each 2094 Logical Channel Subsystem can have up to two sets of Subchannels 


Partitions 

Subchannels 

Channels 


2094 Processor 

63.75K 64K 

63.75K 


Partitions 

Subchannels 

SS-0 SS-1 SS-0 SS-1 

Base Alias 

Channels 

64K 

Base Alias 




Bases Aliases 



System z9 Multiple Subchannel Sets Summary 


Set 0 – Up to 65,280 subchannels 

– Always present if the LCSS is defined 

– Any device for allocation 

– Reference in JCL 

– UCB Services 

– Messages 

– Commands 

Set 1 – Up to 65,535 subchannels 

– Optionally defined 

– PAV alias devices only 

– Display Commands 

– Limited messages 

Designed to be compatible with existing 

storage CUs that support PAV 






System z9 HiperSockets IPv6 

Internet Protocol Version 6 (IPv6) 

More unique IP addresses 

– Expands the IP address space 

From 32 bits to 128 bits 

– Follow-on to IPv4 

Minimum software: 

– z/OS V1.7 

– z/VM V5.2 with PTFs planned for 

May 2006 

Very High Speed Interconnection between programs running 

z/OS, z/VM or Linux 


z/VM 

Partition 1 

CHPID 

00 

PCHID 

010B 

CHPID 

01 

PCHID 

010C 

Partition 

14 

z/OS 

Partition 

15 

LCSS 0 LCSS 3 




Linux 

Partition 

18 

MIF-1 MIF-2 MIF-F MIF-1 MIF-2 MIF-3 MIF-F 

CHPID 

02 

PCHID 

010D 

CHPID 

03 

Share 

HiperSockets CHPID 03 

Linux 

CHPID 

FF 

PCHID 

020A 

CHPID 

04 

SPAN 

z/VM 

Partition 

17 


CHPID 

00 

PCHID 

0245 

CHPID 

01 

PCHID 

0246 

CHPID 

05 

Share 

CHPID 

22 

PCHID 

0248 


Linux 

Partition 

3C 

CHPID 

FF 

PCHID 

0249 



System z RAS Overview for high end Systems 






z9 EC Availability Enhancements 

Enhanced driver maintenance 

Enhanced book availability 

Concurrent memory replacement 

Concurrent MBA fanout 

add/replacement 

Redundant I/O Interconnect 

Enhanced ECC memory 

Dynamic oscillator switchover 


Pluggable optics for FICON Express4 







System z9 Enhanced Driver Maintenance 

Ability to concurrently install and activate a new driver* 

– Can eliminate common planned outage 

– Select window of opportunity within code maintenance stream 

– Like some concurrent patches, may need to vary off/on certain devices 

The ability to concurrently move from one patch point on major driver N, to a patch 

point on major driver N+1 

– Cannot move any-to-any, must move from a specific "from" patch bundle to a specific "to" patch 

bundle 

A limited number of specific crossover bundles will be defined for a driver 

Disruptive driver upgrades are permitted at any time 

Concurrent crossover from driver N to driver N+1, to driver N+2 must be done serially; 

no composite moves 

No concurrent back-off possible. Must move forward to driver N+1 once enhanced 

driver maintenance is initiated. Catastrophic errors during update may cause a 

disruptive outage. 

*Requires proper configuration and planning for exploitation 







System z9 Enhanced Driver Maintenance Limitations 

Specific complex code changes may cause a disruptive driver upgrade; this will be 

alerted in advance for planning purposes 

– Design data fixes 

– CFCC level change 

– LPAR code fixes 

Non-QDIO OSA CHPID types will still require CHPID Vary OFF/ON in order to 

activate new code. Not needed if these types do not exist in the IOCDS 

– Adapter type: OSA3270 (OSC) 

– Adapter type: Ethernet (OSE) 

Crypto code load will require a Config OFF/ON in order to activate new code. Not 

needed if crypto is not installed 

FICON and FCP code changes involving code loads will require CHPID "reset" to 

activate. Base code is infrequently changed 






HyperPAV Introduction 


HyperPAV Functionality and Performance 

HyperPAV is a new feature of Parallel Access Volumes (PAV) that reduces the 

number of PAV-aliases needed per logical subsystem (LSS) 

Announced in October of 2006 for z/OS 1.6+ 

Benefits of HyperPAV 

Increased agility of the management algorithms allows HyperPAVs to instantaneously address 

critical workloads like market open 

Substantially reduce the number of aliases per LSS required to meet workload I/O response 

time objectives 

– This is accomplished by no longer statically binding PAV-aliases to PAV-bases and adjusting 

the bindings via the Workload Manager 

– Instead, in HyperPAV mode, PAV-aliases are bound to PAV-bases only for the duration of 

a single I/O operation 

Facilitate the exploitation of larger logical volume sizes 

– 3390-27 and 3390-54 logical volume images with 32K and 64K cylinders 






HyperPAV Support today 



With PAVs, each base volume within a Logical Subsystem (LSS) can be configured with one 

or more aliases 

Each exposure (base or alias) is capable of having an I/O active simultaneously 

For example, a base volume with 2 aliases could have 3 I/Os started at the same time 

Additional I/O’s initiated to the base volume remain queued in z/OS until an exposure to it 

becomes available 

Applications direct I/O to the base volume 

If the base volume is busy during I/O initiation, z/OS will automatically select one of the alias 

exposures assigned to that base volume and start the I/O using that exposure 

As shown in the figure on the next foil, the UCB is the z/OS representation of a device 








Parallel Access Volumes today: WLM Dynamic Alias Management 








Parallel Acess Volumes today: WLM Dynamic Alias Management… 

Alias exposures are relatively static today 

During initialization, z/OS queries the storage server to determine which alias exposures 

belong to which base volumes 

The ESS is used to provide the initial alias/base configuration 

Over the life of an IPL of the storage server, this alias/base configuration can change due 

to I/O loads within the logical subsystem 

WLM is used to determine if alias exposures should be reassigned to different bases, and 

will facilitate those alias moves to meet overall system workload goals 

Each image within a sysplex will share the same view of the LSS, and therefore, the same 

alias/base relationships 

If an alias is moved, all systems in the sysplex must reassociate the alias with its new base 

volume 

Note: The I/O request priority (IORP) is employed to manage the order of queueing behind a UCB, to resolve 

conflicts within the channel and/or subsystem, to order queuing for commands within the subsystem, and to 

allocate link bandwidth 








Parallel Acess Volumes today: WLM Dynamic Alias Management… 

Goal decisions are made every 10 seconds to meet the needs of a selected service class 

Decisions can only result in the addition or subtraction of one alias for any base address 

To minimize IOSQing, efficiency decisions are made every 60 seconds 

Decisions are interlocked among all of the z/OS images in a Sysplex via the WLM Couple 

structure 

Once a decision was made and communicated to all of the z/OS images, a manage alias-I/O 

command was issued to the storage subsystem to change the assignment of the alias within an 

LSS 

– Hence, the algorithm was very lethargic for critical workloads 

IBM implemented the pacing of alias transfers as a design objective in the WLM implementation 

to avoid thrashing 

Unfortunately, experience has shown that one man’s transient fluctuation can be another man’s 

market open 






HyperPAV Alias Management 



HyperPAVs provides a far more agile alias management algorithm that eliminates interlock 

requirements 

Different z/OS images in a Sysplex can simultaneously use the same alias for different base 

addresses 

The z/OS I/O supervisor (IOS) assigns the HyperPAV managed alias addresses based on: 

– I/O request priority (IORP) assigned by the WLM 

– The availability of unused aliases within the pool for the LCU 

– The multi-system state of the logical volume. For example, IOS will not assign 

additional aliases to a logical volume that is reserved 

Aliases are dynamically bound to a base for the duration of the I/O for the z/OS image that 

issued the I/O 

When an I/O completes, the alias is returned to the pool for the LCU where it is then assigned 

to the waiting I/O with the highest IORP 






HyperPAV Alias Management… 



z/OS uses Pools of Aliases 




For each z/OS image in the sysplex, aliases are used 

independently 

WLM is not involved in alias movement so it does not 

need to collect information to manage HyperPAV aliases 


Benefits of HyperPAV 

Attribute 

Alias to base ratio 

Workload Management 

RMF 

Improved Efficiency 

VSCR 



PAV 

Complex. One alias per 9GBs, depending on workload 

and I/O rates and response time requirements 

192 PAV-aliases/64 PAV bases with Mod 27 volume 

sizes 

Sluggish - WLM adjustments every 10 seconds when 

work is not meeting goals, every minute when goals met 

I/O Priority by device 

Multi-system overheads - Aggregate multi-system 

measurements across SYSPLEX to make correct decisions 

Number of PAV-aliases bound to a base per interval 

Alias used for specific base - PAV-aliases bound to the 

same base across all operating system images 

Interlocked - Device-state-change interrupt required in 

order to insure multi-system coordination of dynamic 

PAV-aliases 

Limited parallelism 

PAV-aliases reside in 31 bit storage only 




HyperPAV 

Simple (Peak I/O rate * average response time * 2) (10x 

reduction in the number of PAV-aliases) 

20 PAV-aliases/236 PAV-bases (10,000/sec * 1 ms * 2) 

On Demand - Instantaneous response to changing work 

loads and I/O skews across devices 

I/O priority by LSS (# also I/O) 

No multi-system overhead - No multi-system aggregation 

of measurements needed 

Number of times I/O waited because PAV-alias not 

available, high water mark for PAV-aliases in use 

Alias used for any base ay any time on any system - 

Each operating system image uses PAV-alias for a 

different base at the same time, multiplier for the amount 

of effective number of aliases 

No interlock required 

Improved parallelism for over coming speed of light 

penalty for replication at distance 

10x reduction in PAV-aliases UCBs and device related 

data structures 


HyperPAV Usage 

HyperPAV related Parameters and Commands 

SYS1.PARMLIB(IECIOSxx) 

– HYPERPAV=YES|NO|BASEONLY 



o YES – Attempt to initialize LSSes in HyperPAV mode 

o NO – Do not attempt to initialize LSSes in HyperPAV mode 

o BASEONLY – Attempt to initialize LSSes in HyperPAV mode, but only start I/Os 

on base volumes 

Enhanced commands 

– SETIOS HYPERPAV=YES|NO|BASEONLY 

– SET IOS=xx 

– D M=DEV 

– D IOS,HYPERPAV 

– D DEVSERV QPAV,dddd 





HyperPAV Measurement 

Changes to RMF SMF Records for HyperPAV 



The RMF 78 subtype 3 record has been expanded to include the: 

– number of I/O requests where no HyperPAV aliases were available 

– total number of I/Os 

– maximum aliases in use for the LSS 

– maximum aliases employed by a single base address in the LSS 

– maximum number of I/Os queued waiting for a HyperPAV managed alias to become available 

The RMF 74 subtype 1 and RMF 79 subtype 9 records have been expanded to include: 

– HyperPAV indicator 

– Average HyperPAV alias counts 






Changes to RMF SMF Records for HyperPAV… 








RMF Report Changes for HyperPAV 








RMF Report Changes for HyperPAV… 







HyperPAV Installation 

HyperPAV Requirements 

Hardware Requirements 

– DS/8000 Version 2.4 

– FICON Connectivity 

Software Requirements 



– z/OS V1R6, z/OS V1R7, and z/OS v1R8 with the following APARs: 

o OA13915 – IOS support 

o OA13928, OA13929, OA14002, OA14005 – DFSMS support 

o OA12699 – WLM support 

o OA14556 – GRS support 

o OA14248 – ASM support 

RMF Support is available with the following APAR: 

– APAR OA12865 





HyperPAV Documentation and Reference Material 

HyperPAV Documentation and Reference Material 

z/OS V1R8 Implementation, SG24-7265-00 

Understanding the Performance Implications of HyperPAV’s 

– Dr. H. Pat Artis, Performance Associates, 2006 



z/OS V1R8 MVS Initialization and Tuning Reference, SA22-7592 

z/OS V1R8 MVS System Commands, SA22-7627 

Provided as Part 

of Silvio's Corner 

Doc Jukebox 





HyperPAV Summary 

Conclusions and Summary 



HyperPAV Alias Management provides an agile Solution that substantially reduces the 

Number of Alias Addresses required for a Set of Base Addresses 

HyperPAV allows you to define aliases that are applicable to more devices, since they 

are not statically used 

z/OS can react more quickly to I/O loads 

HyperPAV increases I/O Parallelism 

HyperPAV will significantly reduce the Pressure on the 64K Device Address 

Limit and can potentially facilitate the Management of Petabytes of Data in 

a z/OS Sysplex 

HyperPAV facilitates the exploitation of larger logical volume sizes (3390-27 

and 3390-54 logical volume images with 32K and 64K cylinders) 












48

z/OS 1.9 Preview 

At a Glance 


z/OS 1.9 Announcement 

Announced on February 6, 2007 (Announcement Letter ENUS207018) 

z/OS 1.9 is planned to offer: 

– Advancements in ease of use for both new and existing IT professionals coming to z/OS 

– Centralized policy-based tailoring for application networking and security 

– Centralized encryption key management for Web-based applications 

– Autonomic policy-based application performance management 

Planned availability date is September 2007 

The following foils will provide a brief preview of selected 

enhancements provided with z/OS 1.9 






Scalability and Performance 

54-Way Support 



– Support for up to 54 processors per z/OS image on System z9 EC servers 

– Maximum Number of Processors is the sum of CPs, zAAPs, and zIIPs 

64-Bit GRS 

– This is expected to dramatically increase the number of concurrent enqueues that can 

be supported on a z/OS system 

– In z/OS V1.9, the majority of GRS enqueue-related control blocks reside in storage 

above the 2GB Bar 

– Move QCBs, QELs, QXBs above the bar 

– New authorized APIs intended to provide interoperability with other serialization products 

– Some exits to be called in cross-memory mode (ISGNQXITBATCH, ISGNQXITBATCHCND, 

ISGNQXITQUEUED1, ISGENDOFLQCB) 






Scalability and Performance… 

System Logger Support for SMF Data 

– Expected to support much higher write rates when the CF is used 



o DASDONLY log streams also supported, but lower write rates are expected 

– SETSMF support for changing to/from Logger without an IPL 

– Can specify that SMF records from different systems be combined into one log stream 

– Can specify different log streams for different SMF record types in SMFPRMxx 

o Even better scalability expected (particularly when using the CF) 

o Note that different log streams can have different retention periods 

– New program (IFASMFDL) will be used to retrieve SMF data from log streams, and 

optionally archive it 

o Designed to provide OUTDD filtering to reduce the need for multiple-pass processing 

– No need to figure out in which GDG SMF data is any more! 

o But SYS1.MAN data sets are still supported 







Message Flooding Automation 



– Policy-driven automation for dealing with high volumes of messages occurring at very high 

message rates 

– Parmlib and operator command support 

– Can specify types of messages to monitor, criteria for message flood start/end, and the actions 

– Can apply different policies to message types, jobs and individual message IDs 

– To prevent a flood, you can specify that messages: 

o Not be displayed 

o Not be logged 

o Not be queued for automation 

o Not be propagated to other systems in a sysplex 

o Not be queued to the Action Message Retention Facility (AMRF) 

o Be stemmed by taking action against the address space by issuing a command (such 

as CANCEL) 

– A message rate monitoring facility is provided to assist the installation in establishing 

Message Flood Automation policy 

– Implemented using IEAVMXIT 







TSO/E support for large (>64K TRK) sequential datasets 

– LISTDSI used in REXX Exec’s and CLIST’s 



o Designed to return new SYSSEQDSNTYPE variable indicating dataset 

type (BASIC or LARGE) 

– TRANSMIT/RECEIVE Commands 

o New value for INMTYPE and a new text unit, INMLSIZE 

– PRINTDS Command 

XCF Couple Dataset Performance 

– Improved parallelism in XCF Couple Data Set access channel programs for all supported 

types of Couple Data Sets 

– By more granularly expressing whether or not a particular channel program intends to 

update any data, channel programs that could not have run in parallel previously will now 

be able to do so, resulting in improved I/O performance and throughput 

– This enhancement was originally made available for z/OS V1.4 and higher with APAR OA15409 









Coupling Facility to Coupling Facility (CF) synchronization protocols for CF Duplexing 

– Planned to be streamlined, resulting in improved performance (service time) and throughput 

for duplexed requests that can take advantage of this enhancement 

– Can help reduce the overhead of CF Duplexing, and may help make duplexing a more viable 

alternative for use in providing high availability for CF structure data 

– A future CF level will be required, which is planned to be supported on System z9 servers 

IOS Virtual Storage Constraint Relief 

– IOS will be designed to provide 31-bit virtual constraint relief by relocating configuration 

data tables (CDTs) 

– To reduce the amount of common storage required, most CDT blocks will be moved to a 

common area data space (CADS) 

LE HEAPPOOL Performance Improvements 

– Better cache and boundary alignment 

– Elimination of stack transitions in an XPLINK environment 






Availability 



Internal changes in z/OS UNIX file system processing designed to reduce latch 

contention by: 

– Reducing the time Mount Latches are held 

– Using parallel processing for some mounts 

– Using GRS deadlock contention for LFS Latch set 

z/OS UNIX System Services automount improvements 

– Improved management of automount file systems that are managing a directory located in 

an automove(unmount) file system 

– The automount file system will now inherit the automove(unmount) attribute rather than 

mounting as automove(yes) 

– In a Shared File System configuration, a more consistent (and predictable) file system 

shutdown/recovery behavior is provided based on the file system AUTOMOVE setting 

o In prior releases, the AUTOMOVE specification is not honored if the file system is 

mounted in a mode which the Physical File System (PFS) provides "sysplex-aware" 

capability 






Availability… 

System Logger asynchronous Dataset Recall Support 



– Support for log stream dataset asynchronous recalls that will allow for multiple, concurrent, 

migrated dataset recall requests to be processed by System Logger 

RRS option to retry “unregister” requests when they don’t complete 

– Designed to help you avoid RRS and RM restarts 

– Currently, if RRS was unable to properly or completely unset a resource manager while 

processing a Registration Services "unregister" RM request, the resource manager could 

be left in a "unregister" state with Registration Services but still set with RRS 

– This situation cannot be resolved without recycling RRS 

– To avoid an RRS warm start, z/OS V1.9 is planned to have an option to reset the resource 

manager on the RRS panels 

– Thiw will allow for a cleaner and more acceptable recovery action and also allow the 

terminated RRS resource manager to restart and recover quickly 






Availability… 



WLM Support for faster Termination of canceled Address Spaces 

– WLM design will be changed to increase the priority of canceled address spaces 

– This is expected to help them to be terminated more quickly 

– This can eliminate the need to reset the priority of a canceled job, task, or user 

to speed address space termination when resolving resource contention issues 

WLM Support for a new parameter on the IWMSLIM service 

– Will allow a server region to tell WLM that a number of minimum server regions 

should be started in parallel 

– The new parameter can allow applications to control whether WLM should start 

server regions in parallel or sequentially 

Extended Size of System Trace Table 

– z/OS 1.9 BCP plans to increase the maximum specifiable size of the MVS System 

Trace from the current value of 999K per CPU 

– The practical maximum will be in the order of many MBs per CPU 






Optimization and Management Capabilities 



WLM support for cross-system routing of zAAP and zIIP workloads 

– WLM's routing services will be enhanced to recognize the zAAP and the zIIP 

capacity of a System z server 

– WLM routing services will be enhanced to return weights for zAAPs and zIIPs 

– This is in addition to those returned for CPs, for which weight calculations are 

unchanged 

WLM “Trickle” Support 

– Ability to specify that a small amount of processor resource be used for discretionary 

work that otherwise would “never” get done on a 100% busy system 

– Parmlib controls over amount of processor resource to use and when to consider work 

as being “CPU starved” 

– Intended to help with resource contention issues (aka “priority inversions”) about 

which WLM code is not aware 






Security 

Additional Password Phrase Support 



– Minimum length of a password phrase lowered from 14 characters to 9 

– Password phrases 9 to 13 characters long will require a new password phrase exit 

(ICHPWX11) 

– Sample exit planned to be provided using the new System REXX 

facility to call a REXX to check password phrase quality rules 

– Sample REXX exec planned to be provided 

– Password change logging and enveloping functions to be extended 

to include RACF password phrases 

Kerberos AES support 

– Plan to add AES128, AES256 options to KERB segment of RACF 

user profile 






Security… 

Enhanced System SSL Support 



– Can specify a “tuning” attribute for System SSL CRL checking to allow or disallow 

handshakes based on CRL availability 

Java User and Group SAF Admin Classes 

– Java classes designed to enable RACF user and group administration 

PKI Services and RACF digital certificate enhancements planned: 

– Writeable SAF Key rings 

– Support of certificates with two-byte UTF8 characters (for example, ñ) that can be 

mapped to code page 1047, including RACDCERT and RACF authentication support 

– Allow use of SDBM credentials for LDAP administrators in PKI Services, to accept 

RACF user IDs in addition to X.500 type user IDs 

– Provide e-mail notification to PKI administrators for pending certificate requests 

– Change the maximum period for certificate validity from 3650 to 9999 days 

– Allow queries based on the number of days until certificates will expire 






Security… 



PKI Services and RACF digital certificate enhancements planned: 

– Automated certificate renewal via e-mail before certificates expire 

– New REFRESH reminder message after RACDCERT commands when refreshes are 

needed for RACLISTed DIGTCERT or DIGTNMAP classes 

Improved auditability for z/OS UNIX 

– z/OS UNIX file and directory deletion recorded in new SMF92 subtype 

New Network Security Services function designed to provide: 

– Single, centralized certificate storage for IPSEC 

– Cross-system and cross–sysplex monitoring and management for IPSec security 

– Enhancements to IKE daemon so it can be configured as a Network Security client 

(one per stack) 






Security… 



AT-TLS support for FTP server, FTP client, and TN3270 server 

– Use Application Transparent TLS (AT-TLS) to manage TLS security 

– AT-TLS designed to support more security functions: 

o Can specify a certificate using its label rather than use the default certificate 

o Can use an LDAP server to validate certificates 

o Support for SSL Session Key Refresh 

o Support for SSL Sysplex Session ID Caching 

o Support for new or multiple key rings 

AT-TLS performance improvements planned 

– Expected to be better than TLS implemented by the FTP server and client 

– Security defined in the TN3270 server profile and FTP.DATA continues to be available 






Networking 



Communications Server for z/OS V1.9 is planned to enter into a new era of z/OS 

middleware enablement by enhancing the security and control of Network 

communications 

Security capabilities are planned for in enhancements with expanded applicationtransparent 

security for TN3270 and FTP 

Control enhancements are planned in the areas of network traffic and Sysplex 

operations 

Policy-Based TCP/IP Routing 

– Designed to provide policy-based routing based on job name, source/destination port, 

protocol type (TCP or UDP), source IP address, NetAccess security zone, security 

label, application 

– Can specify that outbound traffic be separated by application 

FTP Unicode support 

– Added file transfer support for UTF-16, UTF-16LE, and UTF-16BE 

– Added file storage support for UTF-16 






Networking… 

z/OS Communications Server is planned to provide: 



– New APIs designed to allow applications to specify source filterlists 

– Support to allow local systems to filter on source addresses even when not attached to 

multicast routers with source address filtering support 

– Host support for IGMPv3 and MLDv2 






Application Development 

System REXX 



– Designed to allow REXX code to run outside the TSO/E environment, via programming 

interface or operator command 

– Support for running REXX routines authorized 

– Support for using System REXX execs to automate complex operator command and 

other system functions 

– System REXX designed to support invoking execs via a program interface and by 

operator command 

– IBM plans to make this available for z/OS V1.8 via a Web deliverable 

SDSF functions designed to be supported via REXX variables 

– Variables loaded with data from the SDSF panels 

– Designed to enable scripts to access the data programmatically 

– Variables changes are intended to provide a capability similar to action characters 

and overtyping 






Application Development… 

Binder improvements 

– New C/C++ front end to Binder APIs 



– RECFM=U verification designed to provide the same protection against writing programs 

into non-program PDS libraries as is provided for PDSE libraries 

– Definition Side-Files in z/OS UNIX archives intended to allow programmers to package their 

Dynamic Link Library (DLL) side-decks in UNIX archive files produced by the ar utility 

– New INFO option to list installed PTFs in Binder SYSPRINT 

– New -IMMED option on the CHANGE and REPLACE control statements 

z/OS UNIX and Language Environment application porting enablement: 

– Changes to awk, bc, ed, file, mailx, od, sed, tr, uuencode, and uudecode commands 

– Language Environment C/C++ Run-Time Library designed to provide multicast source 

filtering APIs per RFC3678 

– Changes intended to provide closer alignment with SUSV3 






Application Development… 

More planned Language Environment improvements: 



– Fewer lower-case English characters in reports and CEEDUMP when NATLANG is UEN or JPN 

– New CEE3MC2 callable service to return national and international currency symbols 

– Enhancements to the CICS CLER transaction 

– New CEE3DLY and CEEDLYM callable services intended to allow you to migrate COBOL 

applications away from ILBOWAT0 

– New AMODE 64 functions designed to help trace a call chain backwards and allow a "goto" 

capability to a known location in the program call stack, similar to AMODE 31 services 

CEETBCK and CEEGOTO 

– Support for XPLINK applications running as IMS transactions in IMS regions running 

with or without Language Environment Library Routine Retention (LRR) active 

– Enhancements planned for the CEEBLDTX utility, which will be designed to run in a UNIX 

shell command 






Usability 

Health Checker: 

– Planned to support checks written in REXX (uses SYSREXX) 



– More health checks planned for VSM, z/OS UNIX System services, Communications 

Server, TSO/E, SDSF 

ISPF Improvements 

– Edit and Browse support for z/OS UNIX and ASCII files 

– System symbol support for data set names on panels 

– Improved EDIT recovery 

o Even after the ISPF Edit save command has issued and the data being edited has 

been saved, Edit undo buffers will be retained by ISPF 

o Intended to allow you to remove changes from edited data even after a save command 

– Cross-system sharing of profile variables in a parallel sysplex 

o Eliminates the need for multiple profile datasets in a sysplex 






Usability… 

DFSMSrmm improvements 

– System symbol support for DFSMSrmm parmlib members 

– Support for multiple RMMPlexes in a sysplex 

– Search and reporting improvements 

– Dataset name and TSO/E subcommand parsing rules relaxed 

IBM Configuration Assistant for z/OS Communications Server 



– Extended to support PBR (policy-based routing) and NSS (Network Security Services) 

configuration 

– Intended to allow you to configure IPSec, Application Transparent TLS, QoS, IDS, and 

PBR policy using a consistent user interface 

– Planned to allow configuration information for all of these technologies to be managed 

collectively and provide health check operations designed to insure consistent configuration 

– Configuration information can be saved and accessed on a z/OS system or on a Windowsbased 

file system 

– To download the IBM Configuration Assistant for z/OS Communications Server, go to 

o http://www.ibm.com/support/docview.wss?rs=852&uid=swg24013160 






Usability… 

Centralized Policy-Based Networking 

– For a cluster of nodes, all using Policy Agent technology 



– Designed to support a cluster of z/OS nodes (within or across a Sysplex) when configured 

as a server 

– Intended to be able to be used as a centralized networking policy server for heterogenous node 

– Centralized management becomes more important as policy scope widens (QoS, IDS, IPSec, 

AT-TLS, etc.) 

SETXCF START,REALLOCATE (CF structure) command Enhancements designed to: 

– Dynamically optimize CF structure placement among CFs in a parallel sysplex in a way that is 

simple and easy-to-use 

– Determine best CF locations for structures and move them nondisruptively 

– Allow you to specify structures to bypass 

– Automatically initiate duplexing for CF structures that should be duplexed 

– Complete pending policy changes for structures without rebuilding in many cases 

– Improve processing for structures which make use of the exclusion list (EXCLLIST) option in 

the CFRM policy 

– Note: available on z/OS R4 and higher via APAR OA08688 






Usability… 



“Maintenance Mode” support for CFs - when in maintenance mode 

– A CF is logically ineligible for CF structure allocation as if it had been removed from the 

CFRM policy (without policy updates) 

– Rebuild and REALLOCATE processing will be intended to remove CF structure instances allocated 

in a CF when it was placed into maintenancemode 

– With the REALLOCATE command, maintenance mode support is expected to greatly simplify 

operational procedures related to taking a CF down for maintenance or upgrade 

RMF Support for CF utilization 

– New RMF function to show information about CF processor resources consumed by CF 

structures 

– Postprocessor and Monitor III support 

– Intended to allow better CF performance monitoring and problem determination 

– Will require a future CF level, planned to be supported on System z9 servers 






Usability… 



Batch interface to RRS to gather the information provided by theISPF dialog 

New fields in DFSMShsm function statistics records (FSRs) 

New tape sublevels in the DFSMSdfp OAM storage hierarchy 

IDCAMS enhanced to support data set name masking for DELETE 

D XCF, COUPLE,TYPE=BPXMCDS command enhancements display 

MAXSYSTEMS, MOUNTS and AMTRULES for the TYPE(BPXMCDS) couple 

dataset 

HCM report printing function is planned to include the ability to print processor, 

channel path, CTC, and ESCON link information based on selected processors 

and switches 





z/OS R8 Functions planned to be rolled back to z/OS R7 

Ability to specify CNS Notification System for GRS Star 

GRS support for more concurrent ENQs 

Default limits unchanged: 


A Focus on selected z/OS 1.8 Enhancements 

– Unauthorized ENQ default limit remains 4096 

– Authorized default ENQ limit is 250,000 

– can specify higher maximums than the defaults 

New maximum is 2,147,483,647 (x’7FFFFFFF’) 

New ISGADMIN authorized interface, T GRS command, and GRSCNFxx parmlib 

support for setting higher maximums 

Both Funcitons are planned for z/OS 1.7 with APAR OA11382 

Planned availability date 30 March 2007 







System Logger Separation of Production and Test Logstreams 

Logger Enhancements to improve Availability and reduce need for unplanned IPLs 

Problem Area 

System Logger installations combine both test and production work in the same sysplex 

� Possible for work on test log streams to have an adverse effect on production log 

streams 

� Problems encountered on a test log stream can lead to outages effecting production 

log streams 

Some Logger tasks, such as data set recall, and data set allocation are single threaded 

� Dataset recall for the test log stream can hold off the dataset recall for 

production log stream 

Sharing of resources 

� LOGR couple dataset extents 







System Logger Separation of Production and Test Logstreams… 

Overview 

Solution 

� Allow installation to define test and production log streams so that there is separation 

of work between the two sets 

o Focus of logger tasks 

- Separate Allocation Task 

- Separate Dataset Management Task 

o Limitation of resources used by test log streams 

- 25% resource allocation for TEST log streams 

- Ability for production log streams to use more than 75% of resources 

� Logger has three basic sets of sub tasking within the IXGLOGR address space: 

o Logger general services 

o Logstream connection handling 

o Logstream resource services 








Overview 

Solution… 

� The 3rd set of Logger sub tasks (log stream resource services) will continue to manage the 

normal production log stream activity 

Benefit 

o An additional set of these log stream resource services sub tasks will be established in 

the IXGLOGR address space to manage the newly established “TEST” group (or class) 

of log streams 

� Enables installation to define and run test and production resources on the same system(s) 

with less interference 

o Reduces the effect of test log stream outages on production log streams 

Interaction and Dependencies 

No special hardware requirements 

No special software requirements 

Installation 

� None 








Usage and Invocation (Definition) 

Provide a GROUP keyword on the following options 

� IXCMIAPU utility for DATA TYPE(LOGR) Define log stream request 

� IXGINVNT API for the definition of log streams 

o Define log stream with TEST attributes 

DEFINE 

LOGSTREAM 

... 

STG_DUPLEX(NO), 

GROUP(TEST) 

o The above parameter will be allowed on the UPDATE log stream request on the 

following condition 

- No connection to log stream, meaning no active or failed-persistent connections 

In order to use the GROUP keyword, the active primary TYPE=LOGR couple dataset in the 

sysplex must be formatted at an HBB7705 level or higher 








Usage and Invocation (Display Command Output) 

Display Examples 

� No new keyword is required in the display command 

o IXG601I 12.39.43 LOGGER DISPLAY 769 

SYSTEM LOGGER STATUS 

SYSTEM SYSTEM LOGGER STATUS 

SY1 ACTIVE – TEST ENVIRONMENT NOT AVAILABLE 

o IXG601I 12.39.43 LOGGER DISPLAY 769 

SYSTEM LOGGER STATUS 

SYSTEM SYSTEM LOGGER STATUS 

SY1 ACTIVE 

LOGR CDS IS NOT AVAILABLE 

TEST ENVIRONMENT NOT AVAILABLE 








Usage and Invocation (Display Command Output)… 

Display Examples 

� D LOGGER,CONN,LSN= *,JOBNAME=MAINASID, DETAIL 

IXG601I 12.39.43 LOGGER DISPLAY 769 

CONNECTION INFORMATION BY LOGSTREAM FOR SYSTEM SY1 

LOGSTREAM STRUCTURE #CONN STATUS 

--------- --------- ------ ------ 

TCHOPRA.TEST.LOGSTRM1 LIST01 000001 INUSE 

DUPLEXING: LOCAL BUFFERS, STAGING DRXRC 

STGDSN: IXGLOGR.TCHOPRA.TEST.LOGSTRM1.SY1 

VOLUME=ALL001 SIZE=000300 (IN 4K) % IN-USE=002 

GROUP: PRODUCTION 

JOBNAME: MAINASD 

NUMBER OF LOGSTREAMS: 1 

ASID:001D 








Usage and Invocation (Report Output) 

GROUP specification is displayed in the IXCMIAPU DATA TYPE(LOGR) utility output when 

REPORT(YES) is specified 

LOGSTREAM NAME(USER.STREAM.EXAMPLE) STRUCTNAME(LOGGERSTR1) 

LS_DATACLAS()LS_MGMTCLAS()LS_STORCLAS() HLQ(NO_HLQ) MODEL(NO) 

LS_SIZE(0) STG_MGMTCLAS(MGMTDR) STG_STORCLAS(STORDR) 

STG_DATACLAS(STG2GIG) STG_SIZE(524288) LOWOFFLOAD(0) HIGHOFFLOAD(80) 

STG_DUPLEX(YES) DUPLEXMODE(DRXRC) RMNAME() DESCRIPTION() RETPD(0) 

AUTODELETE(NO) OFFLOADRECALL DASDONLY(NO) DIAG(NO) 

LOGGERDUPLEX(COND) EHLQ(IXGLOGR) GROUP(PRODUCTION) 

STRUCTURE NAME(LOGGERSTR1) LOGSNUM(10) 

MAXBUFSIZE(65532) AVGBUFSIZE(4092) 

EFFECTIVE AVERAGE BUFFER SIZE (4092) GROUP(PRODUCTION) 








Usage and Invocation (New Messages) 

IXG074I System Logger services disabled for GROUP: TEST 

IXG075E System Logger constrained for GROUP: PRODUCTION 

IXG076I System Logger constrained for GROUP: TEST 

IXG270I Directory extent records consumption point for test group 

Usage and Invocation (Changed Messages) 

IXG063I Logger abended and issued an SVC dump 

IXG233I Invalid release level 

IXG253I No longer recalling data sets for group: groupname 

IXG257I No DSEXTENTS defined or allocated for TEST pool 

IXG261E Change explanation and system programmer response 

IXG262A Change explanation and system programmer response 

IXG266I Identify production or test log stream service tasks 

IXG271I Identify production or test log stream service tasks 

IXG272E Identify production or test log stream service tasks 

IXG601I Display Logger command output 








Coexistence and Toleration Considerations 

PTFs for Compatibility APAR OA14009 are required on pre z/OS V1R8 systems in your sysplex 

Following Results will happen on a pre z/OS V1R8 if the PTF is applied 

� Log stream connection attempts on pre-z/OS V1R8 release level system are not honored, 

if the GROUP attribute is TEST 

� Connection request on pre-z/OS V1R8 release level will fail with return code 8 and reason 

code ’08E3’x (IXGRSNCODELOGSTREAMNOTSUPPORTED) 

� If a LIKE keyword is used to define a log stream that will have the TEST GROUP 

designation then this request will fail with return code 8 and reason code ’08E3’x 

(IXGRSNCODELOGSTREAMNOTSUPPORTED) 








Coexistence and Toleration Considerations… 

Following Results will happen on a pre z/OS V1R8 if the PTF is applied 

� Report on the GROUP 

o DISPLAY LOGGER,CONN,SYSPLEX 

o DISPLAY LOGGER,LOGSTREAM 

o DISPLAY LOGGER,STRUCTURE 

� Allow the deletion of GROUP(TEST) log streams on pre z/OSV1R8 systems if the log 

stream has never been connected to 

o The first offload data set will be orphaned if the log stream has never been 

connected to 

� Message IXG270I will be DOMable when group TEST log streams are force deleted on 

z/OS V1R7, or when any log stream deletion causes the TEST data set extent shortage 

to cease on pre z/OS V1R8 systems 

� SETLOGR FORCE,DELETE command will be able to delete log stream with GROUP(TEST) 

designation but System Logger will not connect to structure to free structure resources 







CFRM Performance Enhancements Stage 2 

Background 

Coupling Facility Resource Management (CFRM) manages coupling facility resources 

and is critical to the operation of a high-availability parallel sysplex environment 

� The CFRM couple data set (CDS) is the centralized “control point” used by CFRM to manage 

Coupling Facilities (CF) and CF Structures 

CFRM Performance Enhancements Stage 0 delivered in the service stream added 

support to optimize some of the sysplex failure cleanup processing for CF Structures 

CFRM Performance Enhancements Stage 1 delivered in z/OS V1R4 added processing 

optimizations to CF Structure rebuild processing and IXCQUERY processing 

This high degree of availability in a Parallel Sysplex is achieved by enabling surviving 

systems to recover rapidly for a failed system within the sysplex and allowing coupling 

facility (CF) structures that fail to be quickly rebuilt or recovered via duplexing 

failover 

Poor CFRM performance can adversely impact the availability of coupling facility 

structure data and thus the availability of products and subsystem using the structures 








Solution 


� Update the current implementation to avoid using the CFRM CDS as much as possible 

� Processing required to manage the coordination of CF Structure rebuild or duplexing 

failover and system recovery will use a message-based protocol to greatly reduce 

serialized access to the CFRM CDS 

� The message-based protocol defines a single system as manager and all other systems 

as participants 

� The manager system is responsible for coordinating the processes involved with the 

participating systems and updating the CFRM CDS when needed 

� The manager system does the I/O to the CFRM CDS which greatly reduces the number 

and frequency of serialized access 

� Communication between the manager system and participant systems uses XCF signaling 

to send messages between the systems 








Solution 

Exploiters: 

� CFRM Performance Enhancements Stage II is targeted to all zSeries customer environments 

which currently run a Parallel Sysplex 

o These environments require CFRM to manage CF Structure and Connector events that 

occur in the sysplex 

Benefit: 

� Larger production parallel sysplex configurations with a large number of CF Structures 

and Connectors should see a major improvement in sysplex availability, especially during 

occurrences of sysplex partitioning and CF recovery 








Usage Requirements 

CFRM Couple Dataset 

� A new version of the CFRM CDS will be required for systems to enable the message-based 

protocol 

o This allows installations to control the enablement of this function and only exploit it 

only when the CFRM CDS supports the new function 

z/OS Systems 

� All systems in the sysplex must be at a z/OS release V1R8 or higher 

o In order to use the new version of the CFRM CDS that supports message-based 

protocol, all systems in the sysplex must be at z/OS release 1.8 or higher 








Coexistence Considerations 

Systems that do not support message-based processing (z/OS 1.7 and below) will 

not be able to join a sysplex that is using a CFRM CDS that was formatted for 

message-based processing 

A CFRM CDS formatted for message-based processing cannot be brought into use 

by a sysplex while there are one or more downlevel systems (z/OS 1.7or lower) in 

the sysplex 

� This is consistent with CDS version changes that have been done in the past for 

updated functions 








Usage and Invocation 

CFRM Couple Dataset 

� A CFRM CDS must be formatted specifying 

ITEM NAME(MSGBASED) 

� This CFRM CDS must be specified in either a COUPLExx Parmlib member or in operator 

commands to bring into use as the primary CFRM CDS (SETXCF COUPLE,TYPE=CFRM…) 

� Format Utility (IXCL1DSU) 

//SYSIN DD * 

DEFINEDS SYSPLEX(PLEX1) 

DSN(SYS1.XCF.CFRM01) VOLSER(3390X01) 

NOCATALOG MAXSYSTEM(8) 

DATATYPE(CFRM) 

…… 

ITEM NAME(SMDUPLEX) NUMBER(1) 

ITEM NAME(MSGBASED) NUMBER(1) 









Display Commands 

� D XCF,COUPLE,TYPE=CFRM 

IXC358I 00.00.00 DISPLAY XCF FRAME 1 F E SYS=SYSA 

CFRM COUPLE DATA SETS 

PRIMARY DSN: SYS1.CFRM2.CDS 

VOLSER: volser DEVN: devn 

FORMAT TOD MAXSYSTEM 

03/01/2006 12:58:24 32 

ADDITIONAL INFORMATION: 

FORMAT DATA 

POLICY(6) CF(8) STR(128) CONNECT(128) 

SMREBLD(1) SMDUPLEX(1) MSGBASED(1) 









SETXCF Operator Command 

� SETXCF STOP, MSGBASED 

o Message-based processing may be stopped via a SETXCF STOP, MSGBASED command 

o The sysplex will change to policy-based processing 

o This allows an installation to “fallback” to policy-based processing 

� SETXCF START, MSGBASED 

o Message-based processing may become enabled via a SETXCF START, MSGBASED 

command 

o The sysplex must be running with a version of the CFRM couple dataset that supports 

message-based processing in order for this command to execute successfully 

o The system will choose the system where the SETXCF command was issued as the 

new manager system 









D XCF,STR (summary information for structures) 

� Message-based 

IXC359I 00.00.00 DISPLAY XCF FRAME LAST F E SYS=SYSB 

STRNAME ALLOCATION TIME STATUS TYPE 

DUPALLOWED04 03/01/2006 09:37:56 ALLOCATED CACHE 

IXCTL_SIGNAL 03/01/2006 13:52:54 ALLOCATED LIST 

EVENT MANAGEMENT: MESSAGE-BASED MANAGER SYSTEM NAME: SYSA 

� Policy-based 

IXC359I 00.00.00 DISPLAY XCF FRAME LAST F E SYS=SYSA 

STRNAME ALLOCATION TIME STATUS TYPE 

DUPALLOWED04 03/01/2006 16:13:17 ALLOCATED (NEW) CACHE 

DUPLEXING REBUILD 

METHOD: SYSTEM-MANAGED 

PHASE: DUPLEX ESTABLISHED 

DUPALLOWED04 03/01/2006 09:37:56 ALLOCATED (OLD) CACHE 

DUPLEXING REBUILD 

EVENT MANAGEMENT: POLICY-BASED 





Operating System 


Operating System Support for IBM System z9 

z/OS.e (1) Version 1 Release 4 (3) , 5 (3) , 6, 7, 8 

z/OS Version 1 Release 4 (3) , 5 (3) , 6, 7, 8 

Linux, 64-bit distribution 

Linux, 31-bit distribution 

z/VM Version 5 Release 1, 2 

z/VM Version 4 Release 4 (4) 

z/VSE (5) 3.1, VSE/ESA 2.7 (5)(6) 

z/VSE V4 (7) (Preview – no GA announced) 

z/TPF Version 1 

TPF Version 4 Release 1 (ESA mode only) 

ESA/390 

(31-bit) 

No (2) 

No (2) 

No 

Yes 

No 

Yes 

Yes 

No 

No 

Yes 




z/Architecture 

(64-bit) 

1 z/OS.e - z800, z890 and z9 BC only 

2 IBM Bimodal Accommodation Offering is available for 1.4. This offering is not available for z/OS 1.5 & later 

3 Support for z/OS V1.4 and 1.5 will end March 31, 2007 

4 Support for z/VM V4.4 will end September 30, 2006 

5 z/VSE V3 can execute in 31-bit mode only. It does not implement z/Architecture and specifically does not implement 64-bit mode 

capabilities. z/VSE V3 is designed to exploit select features of IBM System z hardware. 

6 Support for VSE 2.7 will end February 28, 2007 

7 z/VSE V4 is designed to exploit 64 bit real memory addressing, but will not support 64-bit virtual memory addressing 

Note: Please refer to the latest PSP bucket for latest PTFs for new functions/features. 

Yes 

Yes 

Yes 

No 

Yes 

Yes 

No 

Yes 

Yes 

No 


Minimum Operating System Support for System z9 Functions 

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) 


z/OS.e - z800, z890 and z9 BC only SLES = SUSE Linux Enterprise Server 

RHEL = Red Hat Enterprise Linux 






Minimum Operating System Support for System z9 Functions 

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) 

6.Linux and z/VM do not support it, the IBM Software Group products are enabled for it on all distributions 


z/OS.e - z800, z890 and z9 BC only 





SLES = SUSE Linux Enterprise Server 

RHEL = Red Hat Enterprise Linux 



z/OS Support Summary 

* All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these Statements of General Direction is at 

the relying party's sole risk and will not create liability or obligation for IBM. 





z/OS Planned Roadmap 

Architectural Level Set 


z/OS Planning Information 

* All statements regarding IBM's plans, directions, and intent are subject to change or withdrawal without notice. Any reliance on these Statements of General Direction is at 

the relying party's sole risk and will not create liability or obligation for IBM. 





z/OS Statements of Direction 

IBM plans to take the following actions in the future*: 



z/OS.e V1.8 (5655-G52), is planned to be the last release of z/OS.e 

� Marketing, ordering, support, and service for z/OS (5694-A01) 

remain unaffected 

� z/OS.e V1.8 planned to be orderable until October 2007 

� Service for z/OS.e V1.8 planned to be available until September 2009 

To replace both the z/OS.e operating system and the NALC pricingmetric with the 

zNALC pricing metric (zNALC is available on all z/Architecture systems) 

� zNALC will replace New Application License Charges (NALC) and z/OS.e, and is 

intended to be IBM's strategic z/OS offering for new workloads 

� zNALC is planned to be available March 16, 2007 

z/OSV1.9 is planned to be the lastrelease to support DFSORT ISPFpanels 

z/OSV1.9 is planned to be the last release of z/OS Communications Server tosupport the 

configuration of Traffic Regulation (TR) policy as part of the Quality of Service discipline 

� IBM recommends you implement TRconfiguration using IntrusionDetection Services 

(IDS) policy configuration (availablein z/OS V1.8) 

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





z/OS Statements of Direction… 

IBM plans to take the following actions in the future*: 



IBM intends to improve the availability date for z/OS R8 supportof JES3 NJE 

communications in using TCP/IP to March 30, 2007, rather than 1H2007 

� In order to enable JES3 NJE over TCP/IP in z/OS V1.8, you must install the PTF for 

APAR OA16527 and its prerequisites 

IBM intends to improve the availablity date of the optimized LDAP directory server, 

called IBM Tivoli Directory Server for z/OS, to March 30, 2007 from 1H2007 

� Designed to let you centralize distributed user registries z/OS 

� PTF for OA19286 required 

� Integrated Security Services -LDAP Server also available in V1.8 

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






New Application License Charges (NALC) 

IBM System z New Application License Charges (NALC) 

At a Glance 

Announced letter ENUS207006, January 9, 2007 

Offers a reduced price for z/OS to encourage Qualified Applications on the Platform 

Allows LPAR-level granularity 

Provides criteria for identifying a Qualified Application 

Is available when Qualified Applications are running under z/OS on IBM z/Architecture servers 

Can aggregate across servers belonging to a qualified Parallel Sysplex 

Planned availability date is March 16, 2007 

Overview 

System z New Application License Charges (zNALC) offers a reduced price for the z/OS® 

operating system on LPARs where you are running a qualified "new workload" application 

(Qualified Application) such as Java language business applications running under WebSphere® 

Application Server, Domino®, SAP, PeopleSoft, and Siebel 

zNALC extends IBM’s commitment to sub-capacity pricing, allowing customers with a Qualified 

Application to obtain a reduced price for z/OS where charges are based on the size of the 

LPAR(s) executing a Qualified Application, assuming all applicable terms and conditions are met 







IBM System z New Application License Charges (NALC)… 

Prerequisites 

zNALC is available only on IBM z/Architecture servers (z900, z990, z9 EC, z800, z890, z9 

BC, or later) running the z/OS (5694-A01) operating system 

z/OS middleware running on the IBM z/Architecture server which qualifies for Workload 

License Charges (WLC) or Entry Workload License Charges (EWLC) must be priced WLC/EWLC 

in order for z/OS to be eligible for zNALC charges 

Any Logical Partition (LPAR) that is designated as a zNALC LPAR must follow the naming 

convention "ZNALxxxx" where xxxx may be any letters or numbers 

Qualified Applications 

zNALC is available only on LPARs where a Qualified Application is present, among other 

requirements 

In general, Qualified Applications are those that IBM considers "new workload,“ such as 

Java language business applications running under WebSphere Application Server, Domino, 

SAP, PeopleSoft, or Siebel 








Qualified Applications… 

IBM has established the following criteria to determine which applications are Qualified 

Applications: 

1. An "Application" is a computer program that is used to accomplish specific business 

Tasks, such as Customer Relationship Management (CRM), Enterprise Resource Planning 

(ERP), Supply Chain Management (SCM), business information warehouse, accounting and 

inventory control programs, including the database server used for that task 

In this definition, an Application is not a stand-alone database management system or 

systems management tool (that is, related to the management or operation of the 

Computer itself or of other computer programs) 

2. An application may be considered a Qualified Application if: 

a) It is currently generally commercially available, supported by its manufacturer, and 

enabled to run under z/OS, and that same Application (with substantially the same 

functionality) is simultaneously generally commercially available, supported by its 

manufacturer on, and enabled to run under a UNIX® operating system (e.g. AIX®, 

HP-UX, Linux, or Solaris), or Microsoft Windows (collectively "Distributed Platforms") 









b) It is a database server running under z/OS and it is operating solely in support of a 

software program that is currently generally commercially available, supported by its 

manufacturer, and running in a client/server environment where the business logic (for 

example, application server) is running on a Distributed Platform; 

c) It is a Java language business application running under WebSphere Application Server 

(or equivalent). These do not include systems management tools 

3. z/OS is eligible for zNALC pricing when running in an LPAR where the Qualified Application 

is executing 

The only other products that may execute in this LPAR are those products that support the 

Qualified Application 

The only other products that may execute in this LPAR are those products that support the 

Qualified Application 

The LPAR must be used exclusively for the Qualified Application and for programs that 

support the Qualified Application and for no other purpose 

4. IBM will determine whether a particular program is a Qualified Application 









For a list of approved zNALC Qualified Applications, visit 

http://ibm.com/zseries/swprice/znalc.html 

Limitations and Restrictions 

zNALC is not available: 

� On any server where OS/390® or z/OS.e is licensed or running 

� On any server where the pricing metric for z/OS is NALC 

Sub-capacity zNALC is not available: 

� On any LPAR’s where z/OS is running as a guest of z/VM® 

For detailed Information on zNALC refer to the Announcement Letter 

IBM System z New Application License Charges, ENUS207006, January 9, 2007 




Provided as Part 

of Silvio's Corner 

Doc Jukebox 





Statement of general Direction 

In 2007, IBM intends: 

� For z/OS.e Version 1 Release 8 to be the final release of the z/OS.e operating system 

Previously announced marketing, ordering, support, and service for z/OS (5694-A01) 

remain unaffected 

� To allow ordering of z/OS.e V1.8 until the planned withdrawal from marketing in October 2007 

In accordance with IBM program service policy, IBM intends to provide service for z/OS.e V1.8 

until its planned end of service in September 2009 

� To continue marketing of the NALC pricing metric until fourth quarter 2007 

After fourth quarter 2007, you cannot request NALC pricing for any OS/390 or z/OS license, 

but you may keep your existing z/OS licenses with NALC charges or OS/390 licenses with NALC 

charges 

To replace both the z/OS.e operating system and the NALC pricing metric with the zNALC 

pricing metric, which is available on both IBM z/Architecture high-end and midrange systems 

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






z/OS 1.8 Auxiliary Storage Manager (ASM) 

z/OS ASM Support for large Page Datasets 

z/OS 1.8 DFSMS provides page dataset support which is not exploited by 

z/OS 1.8 

A page space is a system dataset that contains pages of virtual storage 

The pages are stored into and retrieved from the page space by the auxiliary storage 

manager (ASM) 

A page space is an entry-sequenced cluster which is preformatted (unlike other datasets) 

and is contained on a single volume 

In z/OS 1.8 DFSMS provided support to allow a page space to have a maximum size equal 

to 16,777,215 slots 

The support in z/OS has not been provided to allow a local page dataset to be greater than 

1,048,576 slots 

Though installations may define a page space larger than 1,048,576 slots the additional 

space will not be used by z/OS 

Installations need to ensure they provide sufficient local page space which is addressable by z/OS 

The z/OS restriction of 4GB of page space applies to all page datasets: PLPA, COMMON, 

and LOCALs 





RMF Spreadsheet Reporter Enhancements 


RMF Spreadsheet Reporter Update 

Current RMF Spreadsheet Reporter Version 5.2.3 Enhancement to LPAR 

Trend Reporter Macro RMFR9LP.xls: 

Utilization Reports for CP’s as well as Specialty Engines (ICF, IFL, zAAP and zIIP) 

New Version 5.2.4, which is still Beta-Testing, will provide a new XCF 

Trend Report Macro (RMFR9XCF.xls) 

Will allow a more efficient and faster interpretation of XCF performance the RMF postprocessor 

XCF report 

Supports various filterting options to select XCF performance data of interest 







RMF Spreadsheet Reporter Example 1: CP Utilization 

Note: above chart has been created eith RMF Spreadsheet Reporter Macro RMFR9LP.xls 







RMF Spreadsheet Reporter Example 2: zAAP Utilization 








RMF Spreadsheet Reporter Example 3: zIIP Utilization 








RMF Spreadsheet Reporter Example 4: XCF Trend Report 

Note: above chart has been created eith RMF Spreadsheet Reporter Macro RMFR9XCF.xls, which is planned to be shipped with new Version 5.2.4 





































115

APAR's and Red Alerts 

OA11382 z/OS 1.8 GRS Dynamic Functions SPE for z/OS 1.7 

OA13154 Enhancements to BPXWH2Z for Migration to zFS File Systems 

OA13994 (IPL) Loop In HASCHAM Start IO Appendage when Buffer points to itself 

OA14409 RSM Available Frame Queue (AFQ) Management Change 

OA14465 Missing or unexpected GESYSGON System gone XCF Group Event 

OA14593 IXC256A not responded to because it is not readily available 

OA15607 (IPL, FUNCTIONLOSS) Catalog Hang after ABEND71A in z/OS 1.4 and up 

OA16630 (Hiper) System Hang during XCF Takeover.pdf 

OA16704 (ATTENTION, XSYSTEM) IXCMIAPU Loop, corrupt or missing SFM Administration Policy 

OA17514 Message Flood Automation Support for z/OS 1.6 and up 





APAR's of Interest 

OA17264 (NEW FUNCTION) Issue a Warning Message when multiple I/O Timeouts occur during Device Initialization at NIP Time 

OA17306 (IPL) SYSZMCS CONSIDLATCH Latch never freed 

OA17652 (PERFORMANCE, FUNCTIONLOSS) Repeated ABEND026 RSN0C1C1012 IXLR1DIA for XCF Signalling Structure fills LOGREC 

OA17983 (IPL) z/OS DFSMS 1.8, Wait in IDA019SE+3C8 for deferred EOV Request 

OA18196 BPXWH2Z Support for Migration to SMS-managed multi-Volume zFS File Systems 

OA18345 STP Migration to mixed CTN Support 

OA18464 (FUNCTIONLOSS) Distributed File Service, z/OS 1.4+,includes Fixes for more than 30 zFS problems 


APAR's and Red Alerts... 

OA18511 (Hiper) RACF ABENDA78 after NETVIEW Request Auth Call 

OA18622 (FUNCTIONLOSS) SYS.BPX.A000.FSLIT.FILESYS.LSN Deadlock MMAP Buffer Write Pipe 

OA18898 ABEND0C4 PIC11 IDACAT11+X'688' UA17643 (Dynamic HCD and Catalog Volumes) 

OA18920 ABEND0C4 in IXCL1DSU when defining a Couple Dataset 

OA19310 (Hiper) IRA100E SQA Shortage after GDPS HyperSwap of 10000 PPRC Pairs 

OA19698 System Logger Connect and Inventory Delete Services may point to incorrect Data 

OA19783 (Hiper) XCF STP Support for reverse Migration 

OA19962 VLF Cache for Catalogs is not purged 

OA20180 zFS performance (Change of Default Value for dir_cache_size to 32M), z/OS 1.7+ 

OA20293 (Hiper) Potential tape dataset loss due to changes introduced by PE APAR OA17011 





APAR's of Interest 

OA19109 (IPL) z/OS 1.7+, Miscellaneous ABENDs in IOSAS due to IOSAS Storage Overlay following H/W Activate 

OA19239 (IPL) WAIT204 RC06 at IPL Time because of ABEND806 in ALLOCAS Address Space, z/OS 1.7+ 

OA19281 (IPL) Unpredictable Results due to Overlay of PSA at X'470‘, ABEND0C4-11 in CNZSIMPF+B4, z/OS 1.8 

OA19429 SYSIGGV2 ENQ Hang with Wait in Module IGG0CLEG ,z/OS DFSMS 1.4+ 

OA19462 SRB Service Units incorrect at JBB77S9, HBB772S and HBB7730, z/OS 1.6+ 

II14026 Performance Degradation after converting LLA Managed PDS to LLA Managed PDSE 

OA15473 New Function, LLA Performance Enhancement, z/OS DFSMS 1.7+ 

OA15473 New Function, LLA Performance Enhancement, z/OS DFSMS 1.7+ 









118

SFM for XCF Sympathy Sickness 

The Problem Area 

There are many users of XCF signalling services, and many of those are critical system 

components 

� This can hurt "innocent bystanders" on the same system 



All these users share a common set of resources (message buffers and paths) 

A problem in one XCF user can impact other components using XCF because they are all 

sharing the same resources 

� This can have a knock-on effect and hurt users in other systems 

� Known as "sympathy sickness" 






XCF Buffers and Transport Classes 








XCF Signalling Flow and Pressure Points 








The most common Causes of these Problems are: 

MsgExit SRB suspended 

� Local Lock 

� Latch 

MsgExit SRB not dispatched 

� Application dispatch priority too low 

� Single CPU dominated by higher priority work 

� Tight loop in unrelated work unit 

� LPAR weight too low 

� LPAR capping 








But, this is really two Problems: 

At the address space level: 

� Some address space is not processing his XCF messages 

� This might only be hurting that application 

At the system and/or sysplex level 



� If he isn't sending many messages, it may not impact anyone else 

� Existing stall detect code advertises this condition via the IXC430E and IXC431I messages 

� We are running out of buffer space for XCF messages for ALL users of that Transport Class 

� Now, other users are being impacted 

� Eventually the sending system will be unable to accept any more XCF messages in that 

Transport Class for that target system, potentially impacting any applications trying to 

send messages in that Transport Class 

It is the latter situation that this support targets..... 








The Solution… a new Role for SFM (Sysplex Failure Management) 

SFM – The Enforcer… 

Sacrificing one for the good of many..... 






Objective of new Function: 



Improve Availability for innocent Bystanders by automatically removing the stalled Task that 

owns the Messages that are filling the most PATHIN Buffers: 

� IF the new function is enabled, and IF the sender and target system agree that pain is 

being caused to both, SFM will cancel the stalled task that owns the largest number of 

buffers in the bufferpool 

� It does this by building on the existing stall detection capability 

Note that ANY task can be killed by this function 

If the hung task is GRS, CONSOLE, or XCF, this function will result in that system being 

partitioned out of the sysplex 

The Function is included in the z/OS 1.8 Base and rolled back to z/OS 1.6 

with APAR OA09194 






Implementation 



SFM policy must be defined with new MEMSTALLTIME parameter and activated with the 

SETXCF START,POL,TYPE=SFM,POLNM=xxxx command 

MEMSTALLTIME(NO) is default 

DATA TYPE(SFM) REPORT(YES) 

DEFINE POLICY NAME(SFM01) REPLACE(YES) 

CONNFAIL(YES) 

SYSTEM NAME(*) 

MEMSTALLTIME(900) 

WEIGHT(50) 

ISOLATETIME(0) 

SYSTEM NAME(FRED) 

MEMSTALLTIME(NO) 

WEIGHT(100) 






D XCF,C Command now shows MEMSTALLTIME… 








An example… 

First we stall the member… 

� This causes PATHIN buffers to fill 

� After a while, XCF tries restarting a path… 








Example… 



90 seconds later, XCF tries restarting all paths in that transport class (not at the same time)… 






Example… 



These signalling paths will not be used again until the stall is resolved.. 

Part of the process of restarting paths includes communication between target and sender about 

stalled members and whether they are causing sympathy sickness 






Example… 



Shortly afterwards… get new messages indicating sympathy sickness… 

Or, if MEMSTALLTIME not specified in SFM policy: 






Example… 



After the IXC631I message, D XCF,G command ON ANY system shows the group with the 

stalled member, together with an indication that it is causing sympathy sickness 






Example… 








Automation 

New Messages 

� IXC631I, IXC640E 

Summary 



Very focused function - intent is to save the sysplex by sacrificing one offender: 

� New function to identify if stalled member is actually causing pain for others 

� Enhanced D XCF,G command, so information can be obtained on any member of the plex 

plus new messages to inform you of the problem 

� New support in SFM to automatically address the problem: 

o Can be turned on or off system by system 

o Can control how long SFM waits before taking action 

� You must decide on an appropriate MEMSTALLTIME value 

o Long enough to give you a chance to fix it 

o But short enough to address problem before it escalates 

This situation can exist with both CF and CTC XCF connectivity 

� This new function addresses both 






Summary… 



Member will only be terminated if it is causing sympathy sickness – it will NOT be terminated 

purely because it is stalled 

DOES NOT address the root cause of the stall - critical that you raise an alert on the 

IXC631I and IXC640E messages and use the time to attempt to address the root cause 

� Might consider using automation to increase Service Class of member(s) causing the stall 

This is not intended to address general system hangs or stalls 

� But will effectively address the subset of stalls that are causing XCF buffers to fill 

AND are hurting other XCF users 

Member termination could hurt 

� Some exploiters don't recover well from task termination 

� Will terminate ANY task causing sympathy sickness, including CONSOLE, GRS, etc… 












136

z/OS Migration Checker Tool 

Starting with z/OS 1.8, IBM provides a new 

Migration Checker Tool 

It can be executed as a Batch Job on each 

of your individual z/OS LPAR’s and check for 

required Migration Actions 


z/OS Migration Assistance 

This easy to install and run Tool is available on the z/OS Downloads Web Site 

http://www-03.ibm.com/servers/eserver/zseries/zos/downloads/#mchecker 

Refer to the IBM Migration Checker for z/OS Installation and Use File for any 

incorporated Fixes 

Download Libraries and Doc: 

MIGCHECK.CLIST 

MIGCHECK.JCL 

MIGCHECK.LOAD 

z/OS Migration Checker Installation and User’s Guide 






The current Level B.1 of the Tool provides the following Checks: 

TN3270AS Run the TN3270E Telnet server as a separate address space 

HFSZFS Migrate from HFS file systems to zFS file systems 

ZFSMULT Discontinue use of multi-file system aggregates 

BTSIZE Use the new default for BLOCKTOKENSIZE in IGDSMSxx 

OLDVSAM Redefine existing VSAM data sets that contain the IMBED, 

MASTRCON Accommodate the removal of the master console 

ONEBCON Accommodate the removal of 1-byte console IDs 

LLSTCAT Catalog SYS1.SIEALNKE and SYS1.SIEAMIGE for the 

default system link list in z/OS V1R8 

NEWDS Add references to new data sets and paths 

OLDDS Remove references to old data sets and paths 

SMSLVL Ensure the integrity of SMS control data sets 

ETCUSS Update Communications Server and z/OS UNIX /etc 

configuration files 


REPLICATE, and KEYRANGE attributes 







Installation Steps 

1. 

Download z/OS 1.8 Migration Checker 



2. Upload the 3 binary Files to z/OS physical sequential (PS) RECFM=FB Datasets 

3. RECEIVE (unpack) the 3 PS-Datasets 

4. Customize HLQ.ZOSV1R8.MIGCHECK.CLIST($JOBCARD) 

Note: to prevent an ABEND S213-30 due to multiple Migration Checker Jobs from 

opening Library HLQ.ZOSV1R8.MIGCHECK.sysname.OUTPUT for Output in parallel, set 

the JOBNAME Variable to JOBNAME=ALLSAME 

5. Execute 'USM1115.ZOSV1R8.MIGCHECK.CLIST($SETUP)' 

This will create the following 2 Libraries: 

- HLQ.ZOSV1R8.MIGCHECK.sysname.JCL (Execution JCL) 

- HLQ.ZOSV1R8.MIGCHECK.sysname.OUTPUT (Migration Checker Reports) 

6. Run HLQ.ZOSV1R8.MIGCHECK.sysname.JCL($MIGALL) 

This exectutes all Checks and writes the Results to HLQ.ZOSV1R8.MIGCHECK.sysname.OUTPUT 






Migration Checker Reports 



The following Member contains a Summary of the Migration Checker Results: 

- HLQ.ZOSV1R8.MIGCHECK.sysname.OUTPUT($MIGALL) 

Detailed Information on the Results and recommended Migration Actions will be written to 

individual Component Members in HLQ.ZOSV1R8.MIGCHECK.sysname.OUTPUT 

Example of the Migration Checker Summary Report in Member $MIGALL: 

/*------------------------------------------------------------------*/ 

/* Summary status of the migration checker programs */ 

/*------------------------------------------------------------------*/ 

BTSIZE - EXCEPTION FOUND? Yes. MIGRATION ACTION REQUIRED? No but recommended 

ETCUSS - EXCEPTION FOUND? Yes. MIGRATION ACTION REQUIRED? Yes. 

HFSZFS - EXCEPTION FOUND? Yes. MIGRATION ACTION REQUIRED? No but recommended 

LLSTCAT - EXCEPTION FOUND? No. 

MASTRCON - EXCEPTION FOUND? No. 

NEWDS - EXCEPTION FOUND? Yes. MIGRATION ACTION REQUIRED? Yes. 

OLDDS - EXCEPTION FOUND? No. 

ONEBCON - EXCEPTION FOUND? Yes. MIGRATION ACTION REQUIRED? No but recommended 

TN3270AS - EXCEPTION FOUND? No. 

ZFSMULT - EXCEPTION FOUND? No. 

OLDVSAM - EXCEPTION FOUND? No. 

SMSLVL - EXCEPTION FOUND? No. 






Migration Checker Reports… 



The detailed Migration Actions required for the different z/OS Components will be written to 

individual Members in the OUTPUT Dataset 

These will contain the following Information: 

- Migration Actions being checked 

- Reason why this is a Migration Action 

- What is examined in this Check 

- Process Information 

- Exception found Yes/No 

- Steps to take 





SMP/E Change File Record Facility 





System Cloning 

SMP/E Change File Records can be produced and written to the SMPDATA1 

and SMPDATA2 Datasets as a Result of APPLY or RESTORE Processing 

These records can be used to propagate the libraries and members modified by SMP/E 

APPLY and RESTORE processing to other systems that require the same changes 

Normal SMP/E Reports, such as SMPOUT etc, do not contain complete Information on 

all Elements changed during APPLY or RESTORE 

To use Change File Recording, the CHANGEFILE Subentry in the OPTIONS Entry 

must be set to YES to instruct SMP/E to create these Records 

In Addition, the Datasets and the DDDEF’s for the SMPDATA1 and 

SMPDATA2 Datasets have to be created 

SMP/E provides macros containing the mappings of these records: 

- GIMMALC for Assembler 

- GIMMCLC for C 

- GIMMPLC for PL/I 



Library Change File Record Types 

The following are the valid Record Types produced by the 

Library Change Interface: 

Record Type Desription 

A0 Alias Record Type 0 

A1 Alias Record Type 1 

C0 Continuation Record Type 0 

E0 Element Record Type 0 

E1 Element Record Type 1 

H0 Header Record Type 0 

L1 Library Record Type 1 

L2 Library Record Type 2 

P0 SYSMOD Status Record Type 0 

S0 SMP/E Environment Record Type 0 

T0 Trailer Record Type 0 








Examples of Library Change File Records 

H0MVST1002007044135845000000000000000143000000000946 






S0APPLY 03040006SM154.SMPE.ZOSV17.TARGET.CSI MCAT.SM15.M4SYS 

P0AA19310APPLIED HDZ11K0APAR 

P0JBB772SAPPLIED HBB7720FUNCTION 

P0UA00015APPLIED HDZ11K0PTF 

P0UA23255APPLIED HDZ11K0PTF 

P0UA24565SUPD 

P0UA24582SUPD 

P0UA24667SUPD HDZ11K0PTF 

P0UA24671SUPD HDZ11K0PTF 

L0CMDLIB PDS S15R41SYS1.CMDLIB 

L0CNMCLST PDS S15R42NETVIEW.CNMCLST 

L0CSSLIB PDS S15R41SYS1.CSSLIB 

L1SBPXXMLS HFS /usr/lib/xml_schema/IBM/ 

L2SBPXXMLSPATHHFS SYS1.OMVS.ZOSV17.ROOT.ZFS 



Examples of Library Change File Records… 

L1SFSUMLIB HFS /usr/lib/IBM/ 

L2SFSUMLIBPATHHFS SYS1.OMVS.ZOSV17.ROOT.ZFS 

E0EEQINSTXDATA1 ADDREP SEEQINST 

E0IOSIOSENMSGENU ADDREP MSGENU 

E0IWMWLMENMSGENU ADDREP MSGENU 

A0IWMP2FDPLMOD ADDREP MIGLIB IWMPMFDP 

A0IWMZ2RTRLMOD ADDREP MIGLIB IWMZPRTR 

A0BLSU LMOD ADDREP MIGLIB BLSQPRMJ 

A0BLSU LMOD ADDREP MIGLIB BLSRADDD 

T0MVST1002007044135845000000000000000143000000000946 






For detailed Information and refer to the following Documentation: 

SMP/E for z/OS Reference, SA22-7772 









146

Redbooks and Redpapers 

� IBM System z Strengths and Values, SG24-7333-00 

� Server Time Protocol Planning Guide, SG24-7280-00 

� Server Time Protocol Implementation Guide, SG24-7281-00 





Recommended Readings 

� Introduction to the New Mainframe: Large-Scale Commercial Computing, SG24-7175-00 

� z/OS V1R8 RACF Implementation, SG24-7248-00 

� z/OS V1R8 Implementation, SG24-7265-00 

� System Programmer's Guide to Workload Manager, SG24-6472-03 

� z/OS UNIX Security Fundamentals, REDP-4193-00 

� ABCs of zOS System Programming Volume 8, SG24-6988-00 

� IBM System Storage Business Continuity: Part 1 Planning Guide, SG24-6547-00 

� IBM System Storage Business Continuity: Part 2 Solutions Guide, SG24-6548-00 

� IBM System Storage Business Continuity Solutions Overview, SG24-6684-00 

� Customizing and using IBM OMEGAMON zOS Management Console 4.1.0, REDP-4166-00 

� HiperSockets Implementation Guide, SG24-6816-01 


GSE z/OS Expertforum Switzerland # 66, 27.-28.^3.2007 







148


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 #16 (February 2007), GA22-7501-12 

� Transformation of zSeries to support new Workloads, WP100961A 

� Why new Workloads on System z9, WP100961B 

� Enterprise Copy Services Matrix, 20070131, TD103655) 

� FlashCopy for Open Environments, 20070215, PRS2458 

� FlashCopy in a zSeries Environment, 20070215, PRS2459, 20070215 

� Global Copy, Metro Mirror, Global Mirror, and Metro-Global Mirror Overview, 20070215, PRS2457 

� Managing CPU-intensive Work on Uniprocessor LPARs, 20061215, WP100925 

� z/OS V1R8 Parallel Sysplex Test Report, December 2006, SA22-7997-04 

� FlashCopy in a zOS Environment Quick Reference, TD103707, 20070315 

� FlashCopy in Open Environments Quick Reference, TD103706, 20070315 

� Global Copy, Metro Mirror, Global Mirror Quick Reference, TD103708, 20070315 

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... 







151 

Zürich, 27. März 2007 © 2007 IBM Corporation

Silvio's Corner - 400 Bad Request

Create successful ePaper yourself

Delete template?

Save as template?