z/os v2r2 enhancements

ibm.com

www.ibm.com/redbooks

< Introduction>

z/OS V2R2 Enhancements

© 2015 IBM CorporationITSO-2

Topics Covered

Welcome

DAY 1

z/OS V2R2


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

The following are trademarks or registered trademarks of other companies.

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

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.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both.Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.

For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml:

*BladeCenter®, DB2®, e business(logo)®, DataPower®, ESCON, eServer, FICON, IBM®, IBM (logo)®, MVS, OS/390®, POWER6®, POWER6+, POWER7®, Power Architecture®, PowerVM®, S/390®, System p®, System p5, System x®, System z®, System z9®, System z10®, WebSphere®, X-Architecture®, zEnterprise, z9®, z10, z/Architecture®, z/OS®, z/VM®, z/VSE®, zSeries®

Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market.

Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.

Trademarks


Topics Covered

• Welcome to ITSO Workshop

• Considerations for z/OS V2R2 Content Development

• Expectations

• IBM Redbooks materials


Considerations for z/OS V2R2 Content Development– Materials to be delivered at z/OS V2R2 GA time. 95%

– Content to be more modular. 75%

– Content to be more relevant. 75%

– More use of video. Your opinion? What works for you?

– Content to be more consumable. 60%

– Minimize Duplication . 90%

– Content should be more navigable. 80%

– Include the DFSMS related products. 100%

It’s a journey!


IBM Redbooks Materials for z/OS V2R2

• Benefits:

– Expectations set early for readership

– Improved promotion of content

– Improved management of content

– Topic based content

– Community effort


Expectations

• What do you want to take from today’s workshop?

• Discussion topics with each other.

• Relevance?


IBM Redbooks z/OS V2R2 Content

SG24-8287-00 IBM z/OS V2R2: Job Entry Subsystems and SDSF SG24-8288-00 IBM z/OS V2R2: Security SG24-8289-00 IBM z/OS V2R2: Storage Management and Utilities SG24-8290-00 IBM z/OS V2R2: Availability Management SG24-8292-00 IBM z/OS V2R2: Performance SG24-8305-00 IBM z/OS V2R2: Operations SG24-8306-00 IBM z/OS V2R2: Diagnostics SG24-8307-00 IBM z/OS V2R2: SysplexSG24-8500-00 IBM z/OS V2R2: ServerpacSG24-8310-00 IBM z/OS V2R2: Unix Systems Services SG24-8311-00 IBM z/OS V2R2: User Interfaces

Email: [email protected] with your comments.

ibm.com


< User Interfaces>

z/OS V2R2 Enhancements IBM Redbooks: SG24-8311-00 IBM z/OS V2R2: User Interfaces


Topics Covered

• TSO/E Logon

• TSO/E OPERSEWAIT

• Non-Unix related ISPF functions


TSO/E Logon

A new option, named PASSWORDPREPROMPT is provided in z/OS

V2R2 to improve the protection of user id information.

• When the function is active, the user is required to enter userid and

password in line mode, before processing LOGON command and full-

screen processing.

• After successfully entering the logon information, the standard panel is

displayed with the userid and password fields being protected.

• Note: The new support is being provided in z/OS V1R13 and z/OS

V2R1 as well via APAR OA44855.


TSO/E Logon

Activating the option

• To activate the new function the system needs to be running with an

IKJTSOxx PARMLIB member indicating

PASSWORDPREPROMPT(ON).

• PASSWORDPREPROMPT is specified on the LOGON statement, for

example:

LOGON PASSWORDPREPROMPT(ON) PASSPHRASE(ON) VERIFYAPPL(ON)

• The default setting is OFF.

• Note: The intention is to set the default value to ON in the future


TSO/E Logon

Related points:

• Any incorrect data results in showing the new message IKJ56474I

IKJ56474I USERID OR PASSWORD IS INCORRECT OR NOT AUTHORIZED

• Exits IKJEFLN1 and IKJEFLN2 are not run on entry and exit of the pre-

prompt processing but are during standard logon panel processing

• After successfully entering the logon information, the standard panel is

displayed with the userid and password fields being protected

• The processing applies to IBM RACF® userids

• UADS users are only able to log on if RACF is inactive

• Line-mode has similar results


TSO/E OPERSEWAIT

The OPERSEWAIT setting on the SEND statement in PARMLIB member

IKJTSOxx determines whether WAIT or NOWAIT should be used for an

OPERATOR SEND command that is issued without explicitly setting

WAIT or NOWAIT.

• The old default setting of ON means that SEND commands wait for a

user's VTAM® buffer to be available, and for the message to be sent.

• In z/OS V2R2 the default for OPERSEWAIT has been changed to OFF


TSO/E OPERSEWAIT

A new health check, named TSOE_OPERSEWAIT_SETTINGS, has been

created that indicates whether the current setting matches the preferred

installation setting.

• The preferred setting will default to OFF, but the installation has the

ability to change it to ON via a parameter setting on the health check.

• A successful check results in the following message.

IKJH0401I OPERSEWAIT matches the preferred state.

• An unsuccessful check results in seeing the following information.

IKJH0402E OPERSEWAIT does not match the preferred state.


TSO/E OPERSEWAIT

Coexistence considerations.

• To maintain the equivalent function with previous releases of z/OS, add

OPERSEWAIT(ON) to the IKJTSOxx PARMLIB member.

• With the new default, SEND commands may fail more frequently and

show the following message.

IKJ008I USER(S) user-list AT BUSY TERMINAL(S), MESSAGE CANCELLED

• It is suggested you monitor the frequency of this message being issued

and determine the best option for your system.


Non-Unix related ISPF functions

Topics:• Interactive ISPF Gateway

• ISPF Browse enhancements

• ISPSTART command enhancement

• CONTROL for left and right scroll commands

• EDIF and VIIF enhancements

• Global configuration options

• Removals BookManager/Build and extraneous commands

• DTL compiler enhancement to use the system variable ZISPFRC

• ISPF configuration table


Non-Unix related ISPF functions – Interactive ISPF Gateway

Enhancements introduced with z/OS V2R2 for the ISPF Gateway API include:

• Using z/OS TSO CEA Address Space Services to create TSO address spaces

and provide communication between the remote client and the address space.

– This provides support for the reuse of TSO/E address spaces and so improves performance.

• Run interactive programs, issuing TSO/ISPF conversational mode commands.

• The TSO/E address spaces that are started by the Interactive ISPF Gateway

are started by using a TSO logon procedure.

• An attention interrupt can be sent to a TSO/E address space that was started by

the Interactive ISPF Gateway in order to terminate a command that is in process

in the address space.

• The Interactive ISPF Gateway provides both a native API and an XML API.


Non-Unix related ISPF functions – Interactive ISPF Gateway

API Request TypesAPI Description

NEWTSO Start a new TSO/E address space. Do not start ISPF.

NEWTSOISPF Start a new TSO/E address space and ISPF.

RECONNTSO Reconnect to a dormant TSO/E address space. No ISPF is supported.

RECONNTSOISPF Reconnect to a dormant TSO/E address space. ISPF is started.

REUSE Reuse a TSO/E address space for a new command.

RESPOND Respond to a prompt from a TSO/E address space.

PING Ping a TSO/E address space. Required every 15 minutes to keep the address space alive.

ATTN Send an attention interrupt to a TSO/E address space.

DORMANT Put a TSO/E address space in a dormant state. Activating a dormant address space is faster than starting a new address space.

LOGOFF Log off a TSO/E address space.

CANCEL Cancel a TSO/E address space.


Non-Unix related ISPF functions – Browse enhancements

Two Browse enhancements

• Increasing the Browse record number limit

– records that browse can process is increased to 2,147,483,646.

– The browse LOCATE command is enhanced to increase the maximum line number

value allowed.

– The BRIF service uses the new limit when the caller passes a new parameter

(EXTEND) and the READ routine is altered to accept the new maximum value.

• Browse enhancement to display the length of variable records

– The Browse primary DISPLAY command has been enhanced to show the record

descriptor word (RDW) for variable length records. Options RDW and NORDW have

been added to the command. NORDW is the default.


Non-Unix related ISPF functions – ISPSTART

The ISPSTART command enhancement supports an initial command

stack on the OPT parameter.

• OPT(ZSTART) is now the default in cases where the OPT parameter

can be specified but is omitted.

• The use of mixed and lowercase data is now allowed when the OPT

parameter is used to control the use of an initial command stack.

• The ISPSTART command documentation was updated to describe the

OPT parameter for controlling the use of an initial command stack.


Non-Unix related ISPF functions – CONTROL

The CONTROL service allows you to control the PASSTHRU of the LEFT

and RIGHT scroll commands.

• The dialog is now allowed to turn the PASSTHRU of these commands

on and off as needed.

• It also allows the dialog to query the current status of the PASSTHRU of

these commands.

Option Explanation

PASON LEFT and RIGHT scroll commands are passed to the dialog.

PASOFF LEFT and RIGHT scroll commands are not passed to the dialog.

PASQUERY Do a Query of the passthru status for LEFT and RIGHT scroll commands.


Non-Unix related ISPF functions – EDIF and VIIF

The EDIF and VIIF services enhancement supports an edit line command

table.

• A new parameter User Line Command Table can be passed now.

• It is a positional parameter, passed as last 9 characters and padded

with blanks.

Example:

CALL ISPLINK (’VIIF ’,’EDIFDSN’,’EDIFPROF’,

’F’,80,RDRTN,CMDRTN,MYDATA,LINECMTAB);


Non-Unix related ISPF functions – Global configuration options

• Support for globally specifying a Line Command Table has been

provided in z/OS V2R2.

– A new setting, GLOBAL_LINE_COMMAND_TABLE, defines a line command table

that will be active when not otherwise specified by the user or supplied as parameter

on the edit or view service call.

– This improves the usability for specifying a line command table.

• You can disable the PACK option for the Move and Copy utility.

– Also, this disables the Edit PACK primary command.

– A new setting, GLOBAL_DISABLE_PACK, disables the pack operation used by the

editor.


Non-Unix related ISPF functions – Removals

IBM BookManager® Build is no longer provided by IBM as of z/OS V2R2.

• Option 13.1, BookManager Build, has been removed.

• This provides the removal of an unsupported option from menu

structure.

• Even though the TSO Data Utilities product is no longer supported,

there are six commands related to that product that still exist in

ISPTCM, These are COPY, FORM, FORMAT, LIST, MERGE, and

PASCALVS. In z/OS V2R2, these six commands have been removed.


Non-Unix related ISPF functions – DTL Compiler

The final return code from the DTL compiler needs to be available to

influence the JCL step return codes.

• The final return code from the DTL compiler is stored into the ISPF

shared pool variable ZISPFRC.

• This allows a batch invocation of ISPDTLC to be aware of the success

or failure of the DTL compilation.


Non-Unix related ISPF functions – ISPF configuration table

An ISPF configuration load module can not be updated if the source

keyword file is not available.

• The ISPF Configuration Utility has been enhanced to provide a new

option 7 for converting the active configuration load module, or one

residing in a data set, to a keyword file.

• The generated keyword file can then be updated using existing option 1

or 2 of the ISPF Configuration Utility.

• A configuration load module can then be built from the updated keyword

file using existing option 4 of the ISPF Configuration Utility.

• This enhancement is also available for z/OS V2R1 via APAR OA42680


Non-Unix related ISPF functions – ISPF configuration table

ibm.com


< Serverpac>

z/OS V2R2 Enhancements IBM Redbooks: SG24-8500-00 IBM z/OS V2R2: Serverpac


Topics Covered

• ServerPac Download using HTTP

• SDSF Packaging change

• Support for z/OSMF in z/OS

• Usability Logstream

• Enhanced Support for SMS managed Datasets

• Enhanced Support for File System Merge operation

• Support for KC4z element configuration

• Internet Delivery of Customized offering Driver


ServerPac Download using HTTPS

• Support to enable the User download z/OS Products and Service

Orders (CBPDO, ServerPac and CustomPac) directly to z/OS host

using HTTPS protocol. Ability to download using FTP and FTPS is still

retained.

• Check your procedures for allowing external downloads.


SDSF Packaging change

• ServerPac now SMP/E installs SDSF into BCP zone.

• No option will be available to merge SDSF into BCP zone


Support for z/OSMF in z/OS

• Support for V2R2 z/OSMF configuration using PARMLIB member

• Support to migrate z/OSMF V2R1 and z/OSMF V1R13 configuration to

z/OSMF V2R2 using Sample job.


Usability Logstream

• Support to use either Logstream or Dataset as SMF option

in Full System replacement Path


Enhanced Support for SMS managed Datasets

• Added support to use Management Class in Data set allocation

• Added Support to use Data Class in Data set allocation

• Added Support to allocate Data set using ACS routines

• Enhanced Global Change Command CH SMS to support

Storage class Data Class and Management Class changes

• Two New Views added under ‘Select Data Set view Panel’ CPPP605R.

SMS ACS – Whether Dataset is managed by ACS routines (Yes Or No)

SMS Classes - SMS Data Class, Storage Class and Management Class


Enhanced Support for File System Merge operation

• V1R13 Driving System

If zFS Target File system size exceeds 4 GB, the User will be provided

with three options to handle the scenario

1. Reduce Target File System size by unmerging few Data sets

2. Change File System size to HFS

3. Make File System SMS Managed with a Data Class

• V2R1 Driving System

If zFS Target File system size exceeds 4 GB, the User will be provided

with two options to handle the scenario

1. Allocate Data Set using Data Class with Extended Addressability

2. Reduce Target File System size by unmerging few Data sets

•


Support for KC4z element configuration

• ServerPac supports KC4z Setup by providing two DOC jobs and two

Install jobs.


Internet Delivery of Customized offering Driver

• Customized Offering Driver(COD) is now orderable with Electronic

Delivery option


< JES2, JES3, and SDSF>

z/OS V2R2 EnhancementsIBM Redbooks: SG24-8287-00 IBM z/OS V2R2: JES2, JES3, and SDSF


JES2 Summary of changes• JOBGROUP

• EVENTLOG

• Deadline Scheduling

• JES3 JECL statements

• RAS enhancements

• Checkpoint Improvements

• Exits


JOBGROUPS

JOB 1STEP 5

JOB 1STEP 1

JOB 1STEP 2

JOB 1STEP 3

JOB 1STEP 4

JOB 1STEP 1

JOB 3STEP 3

JOB 2STEP 2

JOB 4STEP 4

JOB 5STEP 5

Reduced batchwindow by increased

parallelism


JOBGROUPS: DEFINING THE JOB GROUP

•Conditional logic•Concurrent processing•Familiar syntax


JOBGROUP DEFINITION

JOB 1STEP 5

JOB 1STEP 1

JOB 1STEP 2

JOB 1STEP 3

JOB 1STEP 4

JOB 1STEP 1

JOB 3STEP 3

JOB 2STEP 2

JOB 4STEP 4

JOB 5STEP 5


Job group pendingJob submission

NO JCL erroron JOB#0002

Running JOBGROUP


JOBGROUP Management


EVENTLOG• With increasing numbers of steps in a single JOB, JOB completion return code might not be enough to

decide a corrective action.

• z/OS V2R2 introduces a new data set called EVENTLOG, that will log data about each step for a JOB.

– EVENTLOG contains data about three subtypes of SMF type 30 records, being Job

start or start of other work unit (subtype 1), step total (subtype 4), and Job termination

or termination of other work unit (subtype 5).

– Data collection set by default. To suppress data collection, use:

$T JOBDEF,SUP_EVENTLOG_SMF=NO


DEADLINE Scheduling• Requirement of job processing that some jobs must start a certain time of the

day to perform critical tasks.

• z/OS V2R2 introduces new keywords for use with SCHEDULE JCL statement.

You can use new keywords to keep a JOB held until a certain time, a desired

time for a job to start, or that a job should run on the same system another

reference job is currently executing.


DEADLINE Scheduling• HOLDUNTL

– Syntax // SCHEDULE HOLDUNTL=('15:40',06/06/2016)

• WITH– Syntax // SCHEDULE WITH=(DB2AMSTR)

• STARTBY– Syntax // SCHEDULE STARTBY=('13:00')

– If the job does not start by specified time, JES2 will use the value set on PROMO_RATE on

JOBCLASS definition to move the job up on the execution queue each one minute cycle.


Introduction to JES3 JECL statements


RAS Enhancements• New $ACTIVATE level

– With the introduction of z22 level, old z2 level is no longer supported by JES2.

– Required for new features such as JOBGROUP and Increased number of jobs.

• Increased number of jobs– Support up to 1,000,000 active jobs, up to 2,500,000 job output elements, define up to 2,500,000

BERTs


RAS Enhancements• New DEBUG Option

– The option QVERIFY provides an option to drive regular job queue verifications.

• Updated $D PERFDATA(CKPTSTAT)– updated to provide additional performance metrics. These metrics can be used to monitor and tune

your environment accordingly


Checkpoint Enhancements• 64 bit CKPT processing

• JES2 checkpoint tuning– The z/OS V2R2 introduces a new managements capability of DORMANCY and HOLD parameters,

where JES2 is responsible for maintaining its values.

• Reconfigure CKPT data sets– The existing $T CKPTDEF has been updated to include DSNAME, VOLSER, STRNAME to define

the checkpoint data set being resized, and SIZE and SPACE attributes, to define the new

checkpoint size


Checkpoint Enhancements


JES3


JES3 Summary of changes• Support for OUTDISP option at the JCL OUTPUT

• JES3 support for symbols

• Data Set Integrity (DSI) for the JES3 data sets


Support for OUTDISP option at the JCL OUTPUT• At z/OS V2R2, JEs3 supports OUTDISP parameter on JES3 SYSOUT

initialization statement, as JES2 does.– Possible values are:

– WRITE

– KEEP

– HOLD

– LEAVE

– PURGE

• INQUIRY, and MODIFY JES3 commands updated to support OUTDISPkeyword.


SDSF


SDSF Summary of changes• System command improvements

• JOB Display enhancements

• Batch parallelism new panels

• JJE component elimination

• zIIP exploitation

• UI enhancements


System Commands Improvements System Command Extension pop-up is enhanced to provide a better user

experience, while increasing the number of saved commands, and allowing grouping and commenting commands. Default number of saved commands increased from 20 to 50, and can be

up to 2,000 if a PDS-e is defined to ISFTABL on logon procedure. Option to group, filter, and comment commands for a better management.


System Commands Improvements Sample usage of System Command Extension to group a command to D-CKTP group, with an

explanatory comment.


System Commands Improvements Hit PF4 on SHOW option to display existing groups for filtering. Select the desired group, and only

related commands are displayed on


System Commands Improvements There is also the option to clear the entire list, a selected group, or especific entries, by selecting

EDIT from the top menu, and CLEAR:

Additional options to control System Commands Panel


JOB Display enhancements Starting on z/OS V2R2, new display panels are added to provide a concise, yet meaningful way to

display relevant JOB information. New JOB Step panel eases the access to JOB Step execution information.

JOB Step completion is available thru option JS from various panels, including ST and DA.


JOB Display enhancements JOB detail panels added to provide additional JOB information regarding:

JOB Devices allocated by JOB (JD) JOB Memory utilization (JM) JOB related delays (JY)


JOB Display enhancements A new SNAPSHOT command is added to capture the contents of a tabular display into a browse/edit

session. All columns are captured, included the ones not displayed on screen. You can use PRINT command (from SDSF Browse) or COPY (from ISPF Edit) to move the captured

data to a more permanent location.


BATCH Parallelism z/OS V2R2 the JES2 adds support for dependent job control and job groups, called batch

parallelism. Two new panels were added on SDSF for end users to manage the new functionality. The job group panel allows you to view and control your job groups. This panel contains information

about job group name, id, owner, status, system affinity, scheduling environment, and other. There are several display options available from JOBGROUP panel, including:

DE - Display the jobs in the job group that encountered an error DJ - Display jobs associated with a job group. DL - Display job group information. This command will include information about creation time,

spool usage, and other. DP - Display dependency. This includes job predecessors, and concurrent jobs.


BATCH Parallelism The job dependency panel lets you view:

For a selected Job Group, all of the dependency within the group. For a selected job:

Jobs that is dependent on Jobs that have dependencies on it


JJE Component Elimination• Starting on z/OS V2R2, the need for a second JJExxxS component has been

eliminated. The SDSF V2R2 is installed as a single FMID: HQX77A0. All JES data is now obtained via interfaces (such as the SSI) rather than by traversing JES2 control blocks.


ZIIP exploitation• Performing a sort on SDSF panels with tens of thousands jobs can increase CP

usage. Now, SDSF uses zIIP processor to perform some CPU-intensive tasks.

There is no user action necessary to use zIIP


UI Enhancements• Starting on z/OS V2R2, many user interfaces enhancements have been put in

place.• Perform actions against multiple jobs from command line.

• 2 D -> issues the Display action against the second row• 1-5 P -> issues the Purge action against rows 1 to 5• 1-3 6-10 14 C -> issues the Cancel action against rows 1 to 3, 6 to 10, and 14

• SET ROWNUM • The new SET ROWNUM command can be used to turn on row numbering on SDSF panels.

• Browse locate dataset action• Starting on z/OS V2R2, it is now possible to browse a specific data set number for a job direct

from DA, I, ST, O, H, and JS panels.• S5 –> positions to the fifth data set• S-2 -> positions to the next-to-last data set


UI Enhancements• NP column width

• NP column can be expanded to a specified width via +nn action, where nn is a value from 4 to 20.

• Use the ARRANGE command to expand the NP column and save the configuration

ibm.com


< Diagnostics>

z/OS V2R2 EnhancementsIBM Redbooks: SG24-8306-00 IBM z/OS V2R2: Diagnostics


Topics Covered

• DUMPS

–SDUMP CTRACE

–SDUMP User Token

• SLIP Traps

• LOGREC


Dumps

• z/OS Dump types:

– SYMPTOM

– SYSTEM USER (SYSUDUMP)

– SYSTEM ABNORMAL END (SYSABEND)

– SYSTEM MACHINE-READABLE (SYSMDUMP)

– SNAP

– TRANSACTION

– SVC (SDUMP)

– STAND-ALONE

• 64bit zArchitecture Virtual addressing may cause large dumps and may affect

performance and availability. Exclude unnecessary areas from dumps to reduce

resource requirements to execute the dumping process.


Traces

• Trace is a set of chronological sequential data located in memory describing

events. When this memory is full, there is a wrap-around. In z/OS there are

several types of traces:

– Component trace (CTRACE), where reported events are related and created by a

z/OS component, such as: IOS, GRS, XCF and others.

– Master trace, where events are related with console messages

– System trace, where events are related to CPU interruptions SSCH instruction, z/OS

task switches and more.

– GTF Trace, where the events are similar with the System Trace but they are

externalized to magnetic media.


SDUMP

• SDUMP is a non formatted dump generated by macros SDUMP and SDUMPX,

issued when a z/OS component fails. Dump is stored in a system data sets

SYS1.DUMPxx.

• Memory dumps and traces decrease the Mean Time to Repair (MTTR) of a

software error.

• SDUMP improvements at z/OS V2R2 are:

– SDUMP CTRACE

– SDUMP User Token support


SDUMP(CTRACE)

• Prior to z/OS V2R2 some SDUMP lack of availability problems are reported:

– Detected SDUMP hung conditions

– SDUMP may take long dump times due to extensive delays.

• In z/OS V2R2 SDUMP has a Component Trace (CTRACE) of its own.

• CTRACE SDUMP options CTIDMPxx member or by CTRACE CT command:

– ON / OFF to switch On or Off the SDUMP CTRACE. Default is On.

– OPTIONS ALL traces all SDUMP events (suggested) / MIN: traces key events

– BUFSIZE (from 4 M to 32 M)

– WTRSTART where to collect optionally trace records out of memory buffers: SVC

dump or Trace data sets.

• TRACE CT command to start, stop, or modify the SDUMP CTRACE.


SDUMP User Token

Prior to z/OS V2R2 Name/Token cannot be used to locate dynamic storage area

to use because its only interfaces require dynamic storage.

Solution provides name/token retrieve variants that use register only interfaces,

improving usability. The major intended exploiter is DB2.

IEANTRTR macro, that has same environment as for IEANTRTS / IEAN4RTS,

you may declare:

IEANTRTR LEVEL=l,NAME=n[,TOKEN=t]

• On successful return:

– Output 64-bit GR0 contains bytes 0-7 of returned token

– Output 64-bit GR1 contains bytes 8-15 of returned token.

• However, you must not use IEANTRTR unless you are on z/OS V2R2 or later

(check bit CVTZOS_V2R2 in byte CVTOSLV6 being on)


SLIP ACTION=CMD

• The z/OS V2R2 enhancements have added the COMMAND option as a new

option on the ACTION parameter for a SLIP trap event. The option is available

to all types of slip traps.

SLIP SET,...,ACTION=CMD,CMD=('command1','command2',...),END

SLIP SET,...,ACTION=CMD,CMD=('D CF','D GRS',),ML=1,END

– CMD is allowed on all types of traps including PER and error events

– CMD is allowed with other actions except WAIT and IGNORE

– CMD is not allowed as a REMOTE option (however ROUTE can be used as a command)

– Up to 8 commands can be specified as such.

– Commands can be up to 126 characters long; Consoles may restrict the number of characters to

less than 126 so you may have to use the SET SLIP=xx command to enter longer commands.

– Commands can be broken into parts with a second set of parenthesis.


SLIP DESCription option

• DESC= :Optional parameter of the STDUMP,SVCD<SYNCSVCD,TRDUMP,

and WAIT actions..

• DESC allows you to add text to the dump title or wait state

– Up to 65 characters

SLIP SET,C=0C1,ID=ITSO,A=(SVCD,CMD),CMD=('D SLIP','D GRS'),DESC=‘ITSO Test dump',END

D SLIP=ITSO

– IEE735I 15.15.04 SLIP DISPLAY 523

– ID=ITSO,NONPER,ENABLED

– ACTION=SVCD,CMD,SET BY CONS CON3E0Y1,RBLEVEL=ERROR

– MATCHLIM=1,0,COMP=0C1 CMD=('D SLIP', 'D GRS')

– DESC=ITSO Test dump


Dynamic Logrec

Logrec is a set of records (stored in data set or log stream) containing hardware

and software error related records.

• With Dynamic Logrec there is no need to IPL, when executing following actions:

– Maintenance on the 3390 volume keeping the SYS1.LOGREC data set

– Switch from LOGSTREAM to DATASET after a System Logger outage, without having

the LOGREC data set pre-allocated.

– Resize the SYS1.Logrec data set

– Save an old Sys1.Logrec data set and switch to a new data set.


Dynamic Logrec

Dynamic Logrec is implemented through two modifications:

– New options at the SETLOGRC command, that allows the specification of DATASET

(data set name) or LOGSTREAM (log stream name) resource.

– Parameter LOGREC at IEASYSxx PARMLIB member, which allows the specification

of log stream name.

• Examples of SETLOGRC command:

– SETLOGRC LOGSTREAM=NEW.LOGSTREAM.NAME

– SETLOGRC DATASET=TEST.LOGREC

• Examples of LOGREC parameter in IEASYSxx:

– LOGREC=LOGSTREAM=LOGREC.TEST1

– LOGREC=LS=SYS1.LOGREC.TEST2

–


Dynamic Logrec

• Examples of LOGREC parameter in IEASYSxx:

– LOGREC=SYSA.LOGREC The data set SYSA.LOGREC is used.

– LOGREC=SYSTEMA.LOGREC The data set SYSTEMA.LOGREC is used.

– LOGREC=&SYSNAME..LOGREC Assuming the value that is specified on the

– SYSNAME= parameter is SYSTEMA, the data set SYSTEMA.LOGREC is used.

– LOGREC=LOGSTREAM The LOGREC log stream, SYSPLEX.LOGREC.ALLRECS, is used by

SVC 76 (LOGREC) to record error and environmental records.

– LOGREC=LS SVC 76 (LOGREC) uses the LOGREC log stream SYSPLEX.LOGREC.ALLRECS to

record error andenvironmental records.

– LOGREC=LOGSTREAM=LOGREC.TEST1 SVC 76 (LOGREC) uses the log stream

LOGREC.TEST1 to record error and environmental

– LOGREC=IGNORE No error or environmental recording by SVC 76 will occur.


< Operations>

z/OS V2R2 EnhancementsIBM Redbooks: SG24-8305-00 IBM z/OS V2R2: Operations


Topics Covered• REGIONX Support

• SMFLIMxx

• 2 Million Open Data Sets

• Dynamic APF SMF Record

• IPL Device Number and Volume

• GRS EQDQ Monitor Enhancements

• BCPii SMF Recording

• CPM Provisioning based on CPU consumption


REGIONX Support

• REGION does not allow users to specify values for below and above the line storage• REGIONX JCL keyword supports two storage specifications and allows the user to explicitly specify

values for their below-the-line storage and above-the-line storage needs.


REGIONX Support

• REGIONX is mutually-exclusive with existing REGION keyword. • REGIONX values used on STEP statements override JOB statements.


SMFLIMxx Support

• z/OS V2R2 provides support for a new PARMLIB member SMFLIMxx to set up job cancel decisions, REGION, and MEMLIMIT values.

• Reduce the need for updates to IEFUSI exit• SMFLIM values can be activated ad IPL time, or SET SMFLIM=(xx,yy,zz) operator command.

• Optional syntax check with “,C” - SET SMFLIM=(xx,C)


SMFLIMxx Support

• Each statement starts with REGION keyword, and a set of filter keywords that indicate to which jobs/jobsteps to apply the settings.

• Wildcards allowed.REGION JOBNAME(CPM*,SUPT*)REGIONBELOW(4M) REGIONABOVE(1G) MEMLIMIT(4T)

• Multiple values within a single keyword treated as OR, while values across keywords AND'd together.REGION JOBNAME(CPM*,SUPT*)STEPNAME(COPY*)REGIONBELOW(4M) REGIONABOVE(1G) MEMLIMIT(4T)


SMFLIMxx Support

• The following values are accepted for EXECUTE keyword:• YES – Override any earlier CANCEL• CANCEL – Cancel the step (and job)• CANCELFROMIEFUSI – Use the decision of IEFUSI• NOCHANGE – Default


SMFLIMxx Support

• Final set of values could come from application of several rules.

JOBNAME(IEF*,SBJ*,)STEPNAME(STEP*,ASM*,) PGMNAME(ASMA90) REGIONBELOW(4M) EXECUTE(CANCEL)

JOBNAME(IEFPRT1)PGMNAME(ASMA90)EXECUTE(YES)• JOB IEFPRT1 will use REGIONBELOW(4) from first match, and will execute,

according to second match.

• IEFUSI decision can be overridden or accepted.• Not planned at this time support for limits on data spaces/hiperspaces/shared memory.


SMFLIMxx Support

• When SMFLIMxx applies a limit, it will write a multi-line message to the joblog, indicating what changed and where the rule for it originated


Dynamic APF SMF Record

• Dynamic APF changes are not tracked by SMF• Starting on z/OS V2R2, a new SMF type 90, subtype 37 record will be created every time a dynamic

APF change takes place after IPL.

SMF record fields include: Function Origin (CSVAPF, SET PROG, SETPROG with PROGxx suffix) Data set name Volume ID Timestamp of the operation Jobname of the requester CHKEY (for example, stepname) of the requester Console ID of the requester Security product user token (Utoken) of the requester


IPL Device Number and Volume message

• IPLing an incorrect volume is hard to detect, can cause errors, and slow down the IPL process.• A new message is provided in z/OS V2R2 containing the desired device number and volser information.

IOS128I IPL DEVICE: sdddd VOLUME: vvvvvv


GRS EQDQ Monitor Enhancements

• GRS EQDQ Monitor enhanced to capture ENQ/DEQ diagnostics for problem determination while minimizing impact to system performance.

• Uses SMF 87• More cohesive, understandable filtering than EQDQ Monitor



• Activate via SETGRS command, or using MONITOR keyword from GRSCNFxx member.• SETGRS MONITOR=YES• SETGRS GRSMON=xx• MONITOR(YES) -> in GRSCNFxx

• SMF type 87 record must be included in SMFPRMxx member.• Specify SYS(TYPE(87(1))) for only subtype 1 – QSCAN• Specify SYS(TYPE(87(2))) for only subtype 2 – ENQ/DEQ• Specify SYS(TYPE(87)) for all subtypes



• Two logical FILTER lists: Include list and Exclude list like RNLs. Exclude list trumps Include list.• Avoid FILTER INCLUDE ENQ QNAME(*) RNAME(*) without other modifiers – too much data!

FILTER INCLUDE ENQDEQ QNAME(SYSDSN) RNAME(*)SCOPE(SYSTEMS)

FILTER EXCLUDE ENQDEQ QNAME(*) RNAME(*)JOBNAME(MYJOB)

FILTER INCLUDE QSCAN GENERIC(YES) XSYS(YES)

• SYS1.SAMPLIB(ISGMON00) contains more hints and examples


BCPii SMF Recording

• Whenever a BCPii application issues an API that modifies hardware resources, there are not sufficient audit trails to keep track of which application/user modified the resources

• On z/OS V2R2, BCPii now cuts SMF 106 records for successful HWISET and HWICMD API calls

• Subtype 1 (HWISET) SYS(TYPE(106(1)))Cuts detailed information about each successful HWISET call

• Subtype 2 (HWICMD) SYS(TYPE(106(2)))Cuts detailed information about each successful HWICMD call


CPM Provisioning based on CPU

• Provisioning Manager monitors systems for CPC-wide CPU consumption, tracking potential processor bottlenecks.

• Enhanced Capacity Provisioning Policy allows to define conditions, which qualify for provisioning of additional processor capacity if a certain CPU consumption is exceeded

• Provisioning Manager can change autonomically or advise to change General Purpose, zIIP or zAAPProcessor Capacity based on the settings of the Capacity Provisioning Policy



• Specifications how Provisioning Manager should react to high CPC-wide CPU consumption, require definitions in Capacity Provisioning

• Domain Configuration• Policy

• New Policy supporting Utilization Based Provisioning can only be defined in z/OSMF for z/OS V2R2



• The Domain Configuration defines a Capacity Provisioning management domain specifying• CPCs with processor capacity to be managed• Systems in those CPCs, used to observe the CPU consumption

• The Policy defines scopes and rules for changes of Processor Capacity• Processor Scopes define the total amount of allowed changes• Time Conditions define when increases and decreases of capacity should, in combination with• Utilization Conditions specify when a CPC is constraint and should initiate a step-by-step

increase and decrease of processor capacity.



• Define:• How much additional processor capacity can be provisioned at most• Where and what kind of capacity should be managed• When and in which situations should be provisioned

• Provisioning Manager will automatically relate observed systems to their hosting CPC



• Utilization and Policy Reports are available from console:



• Provisioning Manager informs on console about processor capacity changes it initiates and of their successful implementation, not about the initiating action or policy element

ibm.com


< UNIX System Services>

z/OS V2R2 EnhancementsIBM Redbooks: SG24-8310-00 IBM z/OS V2R2: Unix System Services


Topics Covered

• 64-bit z/OS UNIX stacks above the bar

• z/OS UNIX Shell and Utilities MAN pages

• z/OS UNIX file system support in ISPF

• zFS enhancements

• OPenSSH enhancements

• z/OS UNIX tools and solutions


64-bit z/OS UNIX stacks above the bar

• New BPXPRMxx PARMLIB statement

• OMVS Modify command

• Displaying OMVS storage information


64-bit z/OS UNIX stacks above the bar – BPXPRMxx

• Internal dynamic stacks can be moved above the bar.

• The thread capacity is increased.

• New BPXPRMxx PARMLIB statement introduced.

KERNELSTACKS(ABOVE|BELOW)

– ABOVE All kernel stacks are allocated above the bar. This increases the thread limit to a

maximum of 500,000.

– BELOW All kernel stacks are allocated below the bar. This is the default.

– Note: The value cannot be changed dynamically.


64-bit z/OS UNIX stacks above the bar – OMVS Modify command

• New interface to send Physical File System (PFS) commands to a PFS

either within the OMVS address space or in a colony address space.

F OMVS,PFS=pfsname,command-string

– Note: This new interface is needed by a 64-bit zFS when it runs in the OMVS address space, since

the existing MODIFY ZFS commands no longer works.

Pfsname This is the name of the PFS that receivesthe command.

command-string This the command string to be passed from the Logical File System (LFS) to the PFS


64-bit z/OS UNIX stacks above the bar – OMVS Modify command

• Example:– $> cn "f zfs,query,level"

– IOEZ00639I zFS kernel: z/OS zFS

– Version 02.02.00 Service Level OA47906 - HZFS420.

– Created on Fri May 29 11:49:19 EDT 2015.

– sysplex(filesys,rwshare) interface(4)

– IOEZ00025I zFS kernel: MODIFY command - QUERY,LEVEL completed successfully.

– $> cn "f omvs,pfs=zfs,query,level"

– IOEZ00639I zFS kernel: z/OS zFS

– Version 02.02.00 Service Level OA47906 - HZFS420.

– Created on Fri May 29 11:49:19 EDT 2015.

– sysplex(filesys,rwshare) interface(4)

– IOEZ00025I zFS kernel: MODIFY command - QUERY,LEVEL completed successfully.


64-bit z/OS UNIX stacks above the bar – Display OMVS storage

• OMVS storage display output enhancement

• If KERNELSTACKS(ABOVE) has been specified in the BPXPRMxx

PARMLIB member, the output of command D OMVS,STORAGE shows

thread information instead of stack cell information.



• Displaying OMVS storage information. KERNELSTACKS set to BELOW

$> cn "d omvs,o" | grep KERNELSTACKSKERNELSTACKS = BELOW

$> cn "d omvs,storage"BPXO075I 20.44.51 DISPLAY OMVS 395OMVS 0011 ACTIVE OMVS=(2A)

KERNEL STORAGE USAGEPRIVATE STORAGE:CURRENT USAGE MAXIMUM AVAILABLE HIGH WATER REGION SIZE

59740158 363046502 59748350 1830789120STACK CELLS:CURRENT USAGE MAXIMUM CELLS HIGH WATER

36 35453 46PROCESS STACK CELL USAGE

USER JOBNAME ASID PID PPID STATE THREADS STACKSNO PROCESSES FOUND USING 50 OR MORE SPACE SWITCHED STACK CELLS.



• Displaying OMVS storage information. KERNELSTACKS set to BELOW

$> cn "d omvs,o" | grep KERNELSTACKSKERNELSTACKS = ABOVE

$> cn "d omvs,storage"BPXO075I 13.01.46 DISPLAY OMVS 919OMVS 0011 ACTIVE OMVS=(74,2A)

KERNEL STORAGE USAGEPRIVATE STORAGE:CURRENT USAGE MAXIMUM AVAILABLE HIGH WATER REGION SIZE

147451904 1815228416 163024896 1830789120THREADS:CURRENT USAGE MAXIMUM THREADS HIGH WATER

87 500000 108PROCESS THREAD USAGE

USER JOBNAME ASID PID PPID STATE THREADSNO PROCESSES FOUND USING 50 OR MORE THREADS

.


z/OS UNIX Shell and Utilities MAN pages

• Cached pages no longer supported

• Man command updated to support Single Tagged pre-

Formatted Plain Text (stfpt)


z/OS UNIX man command: Cached pages no longer supported

• The new z/OS UNIX man command does no longer supports cached

versions of manual pages.– The old man command used cached versions of manual pages in the USS file system even if it

was a zero-byte file. This was invalid


z/OS UNIX man command: Support for stfpt

• The manual of UNIX System Services Command is converted from

DITA to .stfpt format and displayed by the man command transparently.

– The BookManager format manual is still supported, but has low priority in comparison

to the new format .stfpt manual file.

– The BookManager manual page of UNIX System Services Command bpxa5mst.book

will not be delivered.

Example: using option -k to search for information about keywords.$> man -k ownerchgrp - Change the group owner of a file or directorychown - Change the owner or group of a file or directorygetfacl - Display owner, group and ACL$> man -k groupchgrp - Change the group owner of a file or directorychown - Change the owner or group of a file or directorygetfacl - Display owner, group and ACLnewgrp - Change to a new group


z/OS UNIX file system support in ISPF

• New functions added to ISPF option 3.17– The z/OS UNIX ISPF Shell (ISHELL) file system functions have been added.

– Enhanced displays for mounted file systems.

– Lists can be shown ordered by either file system name or mount point name.

– Lists can be expanded and collapsed to improve usability.

• Benefits of the changes:– File system functions are consolidated in a single location.

– Before, there were several ways for working with UNIX file systems:

– Mount Table functions in the z/OS UNIX ISPF Shell (ISHELL)– z/OS UNIX Directory List Utility (udlist) of ISPF option 3.17

– The usability for displaying mounted file systems has been improved.

– There are practical usability issues when many file systems have to be displayed and managed in

the ISHELL mount table.


z/OS UNIX file system support in ISPF• ISPF Option 3.17


z/OS UNIX file system support in ISPF• Example: Expand/contract list entries for access to file systems.


zFS – cache Enhancements

• zFS 64-bit support–zFS cache enhancements

–Health Check for zFS cache removals

–Statistics Storage information

–Running zFS within the OMVS address space

–Specifying larger values with the 64-bit zFS support

• zFS enhanced and new functions–New 8-byte counter support

–New sysplex related APIs

–z/OS UNIX command zfsadmfsinfo

–zFS API ZFSCALL_FSINFO

–Moving zFS into the OMVS address space


zFS – cache Enhancements

• In z/OS V2R2, a new log caching facility is used and statistics are available in a

new format.

– The statistics log cache information is available via the zFS API service command

ZFSCALL_STATS (0x40000007), opcode 247.

– Specifying Version 1 returns the old structure API_LOG_STAT data.

– Specifying Version 2 returns the new structure API_NL_STATS data.

– z/OS UNIX command zfsadm query -logcache and MVS system command MODIFY

ZFS,QUERY,LOG support the new statistical data.

• Several types of caches are no longer available.

– The Transaction cache has been removed.

– With improved logging method, it is no longer needed.

– The Client cache has been removed.

– z/OS V1R12 cannot coexist with z/OS V2R2 so it is no longer needed.


zFS - cache enhancements

• Toleration APAR OA46026 must be installed and active on all z/OS V1R13 and

z/OS V2R1 systems prior to introducing z/OS V2R2. Chck PSP bucket.

• Considerations:

– Down level systems can recognize the new logging method and run the new log recovery and

return Version 1 output, although most of the API_LOG_STAT values are 0.

– Applications that use STATOP_LOG_CACHE (opcode 247) to request Version 1 output should be

updated to use Version 2 output.

– z/OS UNIX command zfsadm query -logcache and MVS system command MODIFY

ZFS,QUERY,LOG return the new statistics already.

• Removal of transaction cache and client cache– If using the zFS parmlib configuration option tran_cache_size or client_cache_size, the

specifications are. ignored


zFS - cache enhancements

• Elimination of the metadata backing cache– As 64bit support allows zFS to obtain caches above the bar, there is no longer a need to define a

metaback cache in data spaces.

– Considerations:

– The zFS parmlib member option metaback_cache_size is used for compatibility

– zFS internally combines meta cache and metaback cache and allocates 1 cache in zFS address

space storage

– It is suggested that where appropriate to remove metaback_cache_size option from your zFS

PARMLIB members and add its value to the meta_cache_size option


zFS - Health Checks for zFS cache removals

• There is an health check named ZFS_CACHE_REMOVALS to monitor this.

– It determines if zFS is running with PARMLIB configuration options metaback_cache_size,

client_cache_size and tran_cache_size.

– Specifying any of the options causes an exception.

– It is therefore suggested not to specify these three options.

– There are the following override check parms keywords:

– METABACK

– CLIENT

– TRANS

– The possible values are ABSENCE or EXISTENCE

– PARM('METABACK(EXISTENCE), CLIENT(EXISTENCE), TRANS(EXISTENCE)')


zFS - Statistics Storage information

• New Statistics Above 2G Storage Information API. available via zFS API service

command ZFSCALL_STATS (0x40000007), opcode 255 STATOP_STORAGE_ABOVE.• Command MODIFY ZFS,QUERY,STORAGE,DETAILS provides a heap free list.


zFS - Statistics Storage information

• The following points are provided regarding usage of Statistics APIs.

– On using STATOP_USER_CACHE (opcode 242) remote VM_STATS are shown as all zero for

Version 1 requests. No remote VM_STATs are provided for Version 2 requests.

– Version 1 requests should be updated to Version 2 to receive the new output.

– When using STATOP_TRAN_CACHE (opcode 250) all zeros are returned for Version 1 requests

and nothing for Version 2 requests.

– You should use STATOP_LOG_CACHE (opcode 247) with a Version 2 request for new output.

– Using one of the following APIs Query Config Option tran_cache_size setting (opcode 208),

client_cache_size setting (231) or Set Config Option tran_cache_size (opcode 160),

client_cache_size (opcode 230) has no effect.

– Commands zfsadm config or zfsadm configquery with options -tran_cache_size or -

client_cache_size have no effect.

– Command zfsadm query -trancache now displays all zeros. It is suggested to remove it

– Be aware that in the MODIFY ZFS,QUERY,LFS report transaction cache data has been removed.


zFS - Running zFS within the OMVS address space

• In z/OS V2R2, zFS can run in the OMVS address space. Depending on the

workload circumstances this might provide CPU reduction based on the shorter

path lengths.

– You can remove the ASNAME keyword in the FILESYSTYPE statement for zFS in the

BPXPRMxx PARMLIB member.

– If you still use the IOEZPRM DD statement in the zFS STC to point to the zFS configuration

parameters, Add this DD statement to the OMVS STC.

– If OMVS does not use the value defined in IBM-supplied PPT (Program Properties Table), ensure

that the OMVS id has the necessary privileges as the zFS STC user id had.

– This might not be an issue because the OMVS user id is set up also with high authority as you

do for zFS.

– You must exploit the new MODIFY OMVS,PFS=ZFS command to address zFS MODIFY

commands to zFS as there is no extra zFS STC active.


zFS - Moving zFS into the OMVS address space

• Ensure that the KERNELSTACKS is set to above the bar already or prepare to

after the next IPL.

• Show the BPXPRMxx PARMLIB settings for KERNELSTACKS and zFS

$> cn "d omvs,o" | grep KERNELSTACKSKERNELSTACKS = ABOVE

$>

echo "The local sysclone value is:" $(sysvar SYSCLONE)The local sysclone value is: 74$> cat "//'SYS1.PARMLIB(IEASYS00)'" | grep OMVSOMVS=(&SYSCLONE.,&OMVSPARM.),

$> cat "//'SYS1.PARMLIB(BPXPRM74)'"KERNELSTACKS(ABOVE)

FILESYSTYPE TYPE(ZFS)ENTRYPOINT(IOEFSCM)PARM('PRM=(&SYSCLONE.,00)')


zFS - Moving zFS into the OMVS address space

• To check if the move has happened use the new MODIFY MVS,PFS=ZFS

interface because the MODIFY ZFS command is no longer available.

$> cn "d omvs,p" | grep ZFSZFS IOEFSCMZFS PRM=(74,00)

$> cn "f zfs,query,level"IEE341I ZFS NOT ACTIVE

$> cn "f omvs,pfs=zfs,query,level"IOEZ00639I zFS kernel: z/OS zFSVersion 02.02.00 Service Level OA47915 - HZFS420.Created on Fri May 29 13:31:44 EDT 2015.sysplex(filesys,rwshare) interface(4)IOEZ00025I zFS kernel: MODIFY command - QUERY,LEVEL completed

successfully.


zFS - Specifying larger values with the 64-bit zFS support

• The new 64bit support provides support for larger caches

zFS configuration options Old range New range

vnode_cache_size 32 - 500,000 1000 - 10,000,000

meta_cache_size 1M – 1024M 1M – 64G

token_cache_size 20480 – 2,621,440 20480 – 20,000,000

trace_table_size 1M – 2048M 1M - 65535M

xcf_trace_table_size 1M – 2048M 1M - 65535M


zFS - New 8 byte counter support

• The 4-byte counters (V2R1) have been replaced by 8-byte counters (V2R2).

• Existing APIs dealing with statistic numbers now supporting 8-byte counters.

– STATOP_LOCKING (opcode 240)

– STATOP_STORAGE (opcode 241)

– STATOP_USER_CACHE (opcode 242)

– STATOP_IOCOUNTS (opcode 243)

– STATOP_IOBYAGGR (opcode 244)

– STATOP_IOBYDASD (opcode 245)

– STATOP_KNPFS (opcode 246)

– STATOP_META_CACHE (opcode 248)

– STATOP_VNODE_CACHE (opcode 251)

• The zfsadm query and MODIFY QUERY commands are affected by this, so check any

automation or scripts that parse or reference the output from the commands.


zFS - New Sysplex related APIs

• There are three new Sysplex related APIs:

– Statistics Sysplex Client Operation Info, named STATOP_CTKC (opcode 253)

– This returns information about the number of local operations that required the sending of a

message to another system.

– Server Token management Info, named STATOP_STKM (opcode 252)

– This returns the server token manager statistics.

– Statistics Sysplex Owner Operation, named STATOP_SVI (opcode 254)

– This returns information about the number of calls processed on the local system as a result of a

message sent from another system.

• This is used by the following new zfsadm query options.

– zfsadm query -ctkc

– zfsadm query -stkm

– zfsadm query -svi


zFS - New Sysplex related APIs

• Existing MODIFY ZFS,QUERY commands now support 8-byte counters.

– MODIFY ZFS,QUERY,CTKC

– MODIFY ZFS,QUERY,STKM

– MODIFY ZFS,QUERY,SVI

• New powerful FSINFO interface– A zfsadm command

– A detailed file system API command, named ZFSCALL_FSINFO ( 0x40000013)

– A zFS MODIFY command

– It always supports 8-byte counters.

• TIP: use FSINFO now instead of List Aggregate Status (opcode 135 or 140) or

List File system status (opcode 142).


zFS - z/OS UNIX command zfsadm fsinfo

Command Syntaxzfsadm fsinfo [-aggregate name | -path path_name | -all]

[-basic |-owner | -full |-reset][-select criteria | -exceptions][-sort sort_name][-level][-help]

-aggregate name This is used to specify the name of the aggregate. Use an asterisk (*) at the beginning, at the end, or both at the beginning and the end of name as a wildcard. On using wildcards, the default display mode is -basic. Otherwise, the default display is -owner

-path path_name This specifies the path name of a file or directory that is contained in the file system. The default information display is -owner.

-all This displays information for all aggregates in the sysplex. The default information display is -owner.

-basic This displays a line of basic file system information for each specified file system.

-owner This displays only information that is maintained by the system owning each specified file system.

-full This displays information that is maintained by the system owning each specified file system. It also displays information that is locally maintained by each system in the sysplex that has each specified file system locally mounted

-reset This resets zFS statistics relating to each specified file system. This option requires system administrator authority.



zfsadm fsinfo selection criteria Criteria Description of the criteriaCE XCF communication failures between clients systems and owning systems

DA Marked damaged by the zFS salvager

DI Disabled for reading and writing

GD Disabled for dynamic grow

GF Failurs on dynamic grow attempts

GR Currently being grown

IE Returned ENOSPC errors to applications

L Less than 1 MB of free space; forces increased XCF traffic for writing files

NS Mounted NORWSHARE

OV Extended (v5) directories that are using overflow pages contained

Q Currently quiesced

RQ Had application activity

RO Mounted read-only

RW Mounted read-write

RS Mounted RWSHARE (sysplex-aware)

SE Returned ENOSPC errors to applications

TH Having sysplex thrashing objects in them

V4 Aggregates that are version 1.4

V5 Aggregates that are version 1.5

V5D Aggregates that are disabled for conversion to version 1.5

WR Had application write activity



zfsadm fsinfo exceptions

Exceptions Description

CE XCF communication failures between clients systems and owning systems

DA Marked damaged by the zFS salvager

DI Disabled for reading and writing

GD Disabled for dynamic grow

GF Failurs on dynamic grow attempts

IE Disk IO errors

L Less than 1 MB of free space; forces increased XCF traffic for writing files

Q Currently quiesced

SE Returned ENOSPC errors to applications

V5D Shown for aggregates that are disabled for conversion to version 1.5



zfsadm fsinfo examples

Example 1: provide a path name

Example 2: List all zFS aggregates that are quiesced or not mounted sysplex-aware

$> zfsadm fsinfo -path test -basicUSER01.TEST.ZFS SC74 RW,NS,L

Legend: RW=Read-write, L=Low on space, NS=Mounted NORWSHARE

$> zfsadm fsinfo -select q,nsUSER01.TEST.DUMMY.ZFS SC74 RW,RS,Q,LUSER01.TEST.ZFS SC74 RW,NS,L

Legend: RW=Read-write,Q=Quiesced,L=Low on space,RS=Mounted RWSHARE

NS=Mounted NORWSHARE


zFS - New zFS API ZFSCALL_FSINFO (0x40000013)

The pfsctl (BPX1PCT) API is used to send requests to the zFS physical file

system for most zFS API calls

• FSINFO has two subcommands:

– Query file system info (opcode 153)

– This requires a minimum buffer size of 10K for a single-aggregate query and 64K for a multi-

aggregate query.

– Reset file system stats (opcode 154)

– This requires a minimum buffer size of 10K.

BPX1PCT(“ZFS “, /* File system type followed by 5 blanks */0x40000013, /* ZFSCALL_FSINFO – fsinfo operation */

parmlen, /* Length of parameter buffer */parmbuf, /* Address of parameter buffer */&rv, /* return value */&rc, /* return code */&rsn) /* reason code */



Rexx example:

• A sample REXX named rxlstqsd exploiting the new fsinfo API has been created

for demonstration and reference.

– Sample rxlstqsd uses the new pfsctl() command ZFSCALL_FSINFO to list all quiesced zFS

aggregates in a sysplex sharing environment.

– It has been created to be run in z/OS UNIX, TSO and as a SYSREXX routine.

– The utility is provided in ASCII text mode as additional material in conjunction with the Redbook

SG24-8310-00 z/OS V2R2: Unix System Services. When transferring it from your workstation to

z/OS using FTP it is suggested that you:

– Transfer file "rxlstqsd.txt" it in text mode, not binary, to z/OS UNIX first.

– Use ftp sub-command quote site sbd=(1047,819) before you run the transfer and rename it to

"rxlstqsd".

– From UNIX you can copy it to a TSO REXX and a SYSREXX library.

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



Rexx example: Using the utility from different environments

. $> rxlstqsdUSER01.TEST.PRELE.ZFSUSER01.TEST.RW.ZFSUSER01.TEST.ZFS$> cn "f axr,rxlstqsd"ZFSQS004I RXLSTQSD on SC74 -USER01.TEST.PRELE.ZFSUSER01.TEST.RW.ZFSUSER01.TEST.ZFS

$> sudo zfsadm unquiesce USER01.TEST.PRELE.ZFSIOEZ00166I Aggregate USER01.TEST.PRELE.ZFS successfully unquiesced$> sudo zfsadm unquiesce USER01.TEST.RW.ZFSIOEZ00166I Aggregate USER01.TEST.RW.ZFS successfully unquiesced$> sudo zfsadm unquiesce USER01.TEST.ZFSIOEZ00166I Aggregate USER01.TEST.ZFS successfully unquiesced$> rxlstqsdZFSQS006I There are no quiesced aggregates.$> tsocmd "rxlstqsd"rxlstqsdZFSQS006I There are no quiesced aggregates.


zFS - FSINFO zFS Modify interface command

• The syntax of the FSINFO zFS Modify interface command is very similar to

corresponding zfsadm command.

. modify zFS_procname,fsinfo[,{aggrname | all}[,{full | basic | owner | reset} [,{select=criteria | exceptions}][,sort=sort_name]]]


zFS - Health Check Removal

• Two zFS health checks have been removed because they are no longer

needed.

– ZOSMIGV1R13_ZFS_FILESYS

– ZOSMIGREC_ZFS_RM_MULTIFS


OpenSSH enhancements

• z/OS OpenSSH has been upgraded to OpenSSH 6.4p1.– This provides a much more current OpenSSH version.

– Same versions of OpenSSL 1.0.1c and zlib 1.2.3 are used.

– The ssh-rand-helper tool is no longer supported in 6.4p1.

– Support for many new crypto algorithms are included.

– This provides compatibility with other OpenSSH or SSH implementations that prefer to use

these new algorithms.

• AES-CTR mode support was added to ICSF via APAR OA45548. It was added

to work like existing AES-CBC mode ICSF support. Affected OpenSSH

algorithm names:

– aes128-ctr

– aes192-ctr

– aes256-ctr



• Support has been added for better accounting and auditing of ssh connections.

– A new triplet has been added to the SFTP client transfer SMF record for the target pathname.

– The sftp client did not record the target pathname in the past.

– A new SMF 119 record has been created; it is written at the beginning of a successful ssh

connection, just after user authentication.

– The ssh client and sshd server will have their own new subtypes.

– Existing “Common TCPIP” and “SSH Common Security” triplets will be included.

• The ssh client can now be invoked under a TSO OMVS shell. Nevertheless,

entering of password credentials is still not allowed to prevent exposures and

displaying of passwords.

– This makes diagnosis of connection and handshake problems easier for many customers.

– It allows to verify a working network connection, acceptance of server host keys, and even a

completed connection if a password is not required.



• The IBM-added option IdentityKeyRingLabel was complex to use in a shell

script since literal double-quotes are required. This problem has been resolved.

– The syntax of IdentityKeyRingLabel has been relaxed so that double-quotes are optional when

entered from an ssh, sftp, or scp command line.

– They are still required when the keyword appears in the zos_ssh_config or authorized_keys

file.

– The HostKeyRingLabel is similarly relaxed so that double-quotes are not required when this

keyword is used on an sshd command line.

– The previous syntax still works as well.



• Using OpenSSH

• Key Exchange algorithms– Key exchange (also known as "key establishment") is any method in cryptography by which

cryptographic keys are exchanged between two parties, allowing use of a cryptographic algorithm.

– The following Key Exchange algorithms can now be specified via option -oKexAlgorithms.

– Old algorithms: diffie-hellman-group1-sha1, diffie-hellman-group14-sha1, diffie-hellman-group-

exchange-sha1, diffie-hellman-group-exchange-sha256

– New NIST Elliptic-curve algorithms: ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-

nistp521 (NIST is the National Institute of Standards and Technology)



• Key algorithms– The following Key algorithms are supported now.

– Old algorithms: ssh-rsa,ssh-dss

– New NIST Elliptic-curve DSA w/ SHA-2 algorithms added:

– ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521,

– [email protected], [email protected],

– [email protected],



– [email protected], [email protected]

– OpenSSH certificates have been added, too.



• Cipher algorithms– In cryptography, a cipher (or cypher) is an algorithm for performing encryption or decryption. This is

a series of well-defined steps that can be followed as a procedure.

– The following Cipher algorithms are supported. The default preference order is as shown. New

ciphers are hilighted, ICSF support is noted with "*" (already supported) or "**" (newly supported).

– aes128-ctr**, aes192-ctr**,aes256-ctr**, arcfour256,arcfour128,


– aes128-cbc*, 3des-cbc*, blowfish-cbc, cast128-cbc, aes192-cbc*,

– aes256-cbc*, arcfour, [email protected]*



• Mac algorithms– In cryptography, a message authentication code (MAC) is a short piece of information used to

authenticate a message and to provide integrity and authenticity assurances on the message.

– A keyed-hash message authentication code (HMAC) is a specific construction for calculating a

message authentication code (MAC) involving a cryptographic hash function in combination with a

secret cryptographic key.

– The following MAC algorithms are supported. The default preference order is as shown. New MAC

algorithms are hilighted, ICSF support is noted with "*" (already supported) or "**" (newly

supported).

– [email protected]*, [email protected]*,


– [email protected]**,

– [email protected]**,

– [email protected]*,





– hmac-md5*, hmac-sha1*,


– hmac-sha2-256**, hmac-sha2-512**,

– hmac-ripemd160*, [email protected]*,

– hmac-sha1-96*, hmac-md5-96*

• Dynamic port assignment for remote port forwarding – You can use command ssh -R 0:host:port. A remote port of 0 can be specified in which case a

dynamic port will be assigned on the server. The client will report a message with the specific

ephemeral port assigned.



• Support for public key (user and host) certificates– These are not X.509 certificates, but a simpler implementation that is unique to OpenSSH. A single

key (CA key) may sign (vouch for) the public keys of many users or servers. If a host or user trusts

the CA public key, then it implicitly accepts the keys that have been signed by it.

– For more information, see the User's Guide or man page for the ssh-keygen command. These

have been available for a few years.

• Multiple user authentication methods– The server (see AuthenticationMethods in the sshd_config file) may specify that more than one

authentication method is required for a user or for all users. For example, it can be requested to

need a key and to enter a password in addition.



• SFTP enhancements– There are the following SFTP enhancements.

– Support for recursively transferring files in a directory tree via get -r and put -r.

– sftp server read-only mode

– sftp df command for displaying filesystem attributes

– Improved performance of directory listings

– Support of the ls -h option - human readable file attribute units

• Eimination of ssh-rand-helper function– z/OS OpenSSH now requires a working /dev/random UNIX device.

– Function ssh-rand-helper was slow, not as secure, and often timed out.

– ICSF /dev/random support is now required to start ssh or sshd.

– If /dev/random is not available, then ssh and sshd start up will fail with an error message.

– FOTS1949 PRNG is not seeded. Please activate ICSF.



• SMF records– You should also refer to for new functions implemented.

– New algorithms are added into the related SMF records.

– The sftp client records target path name has been added in subtype 97.

– An additional triplet was added to this record which contains the target (remote) path name

for a SFTP client file transfer.

– Two new SMF 119 records have been added.

– Type 94 (x"5E") - Client connection started record

– Type 95 (x"5F") - Server connection started record

– The content of these records is identical, and a subset of other 119 SSH records.

– Standard SMF 119 header

– Common 119 TCP/IP identification section

– SSH common security section; this identifies which algorithms were used.



• Migration and coexistence considerations– Here are migration actions or coexistence considerations.

– As in previous releases, protocol 1 is disabled by default.

– Different as with the open source Version 6.4 of OpenSSH, sftp is changed so that non-error

messages are not printed to stdout if running a batch file (-b).

– In effect, the -q (quiet mode) option is turned on with -b and cannot be turned off. Since this will

impact many installations, it has been changed in the z/OS port so that -b does not force -q. The

-q option can be specified in addition to -b.

– Therefore this is not a migration action, but the behavior is not be consistent with other

implementations.



• Migration and coexistence considerations– Preferences for GlobalKnownHostsFile in ssh_config

– /etc/ssh/ssh_known_hosts, /etc/ssh/ssh_known_hosts2

– Preferences for IdentityFile in ssh_config

– For protocol version 2, the default is ~/.ssh/id_rsa, ~/.ssh/id_dsa, and ~/.ssh/id_ecdsa.

– Preferences for UserKnownHostsFile in ssh_config

– ~/.ssh/known_hosts, ~/.ssh/known_hosts2

– Preferences for AuthorizedKeysFile in sshd_config

– .ssh/authorized_keys, .ssh/authorized_keys2

– Preferences for HostKey in sshd_config

– /etc/ssh/ssh_host_rsa_key, /etc/ssh/ssh_host_dsa_key and /etc/ssh/ssh_host_ecdsa_key


z/OS Unix Tools and Solutions

• The tools mentioned here are available from the following ITSO page:

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

• Refer to file ITSO_Tools.pdf to get instructed how tools are provided and can be

retrieved and activated.


< Storage Management and Utilities>

• z/OS V2R2 Enhancements• IBM Redbooks: SG24-8307-00 IBM z/OS V2R2: Storage Management

and Utilities


Topics Covered• DFSMS Data Facility Product (DFP)

• DFSMS Hierarchical Storage Manager (HSM)

• DFSMS Removable Media Manager (RMM)

• DFSORT

• Catalog and IDCAMS

• VSAM


DFSMSdfp Updates• SMS Space Constraint Relief

• User Defined ACS Read-Only Variable

• SMS RAS Enhancements

• DEVSUPxx Enhancements

• Open/Close/EOV Enhancements


dfp: SMS Space Constraint Relief

• Currently for non-Guaranteed Space allocation, SMS Space Constraint Relief (SCR) processing reduces the requested space by the data class specified percentage, 'Reduce Space Up To (%)', if the originally requested space cannot be satisfied.

• A new sub-parameter, Guaranteed Space Reduction (Y | N), is added to the data class panel.

•SCR space reduction function is enhanced to allocate the largest possible space that satisfies the

specified reduction percentage for both guaranteed space and non-guaranteed space requests.

•Note: Space reduction will remain unsupported for striping allocation.


dfp: SMS Space Constraint Relief• Currently, during the allocation of a secondary extent on the current volume, if the requested free

space is not available, EOV will call SMS to switch volumes and try to extend onto a new volume. – This algorithm can be inefficient in leaving large amounts of free space behind on the current

volume which is less than what the user specified for secondary amount.• z/OS V2.2 Secondary Space Reduction allows the system to extend data sets by less than their

originally specified secondary space allocation amounts when doing so would avoid allocation of space on additional volumes

– DADSM provides a new minimum allocation on the DADSM Extend interface.

– The allocated space must be equal to or greater than the minimum quantity derived from the attribute Reduce Space Up To (%) on the ISMF data class definition under “Space Constraint Relief”..

–Reduce Space Up To means Remove up to that amount



– This support will be for SMS managed non-striped VSAM data sets and Non-VSAM data sets.– New SMF fields:

– SMF64SSR –if secondary space reduction was used

– SMF64NTA –size of extent returned in Tracks


dfp: User Defined ACS Read-Only Variable

• Currently the user cannot provide installation specific values to the ACS routines via existing ACS read-only variables.

• z/OS V2R2, SMS provides a new user defined ACS Read-only variable in SMS IGDSMSxx parmlibmember:

USER_ACSVAR(value1,value2,value3)• The new parameter has 3 positional values.• Each value is a user-defined 8 character string. • The positional values of the new parameter can be altered by the following SETSMS

command: SETSMS USER_ACSVAR(value1,value2, value3)



Production System

SYS1.PARMLIB(IGDSMSxx):USER_ACSVAR(PROD,,)

Test System

SYS1.PARMLIB(IGDSMSxx):USER_ACSVAR(TEST,,)

PROC DATACLAS /* DATA CLASS ACS ROUTINE */IF &USER_ACSVAR(1) = ‘PROD' THENSET &DATACLAS = ‘PROD_DC’

ELSEIF &USER_ACSVAR(1) = ‘TEST’ THENSET &DATACLAS = ‘TEST_DC’

ELSE WRITE ‘***** UNEXPECTED VALUE FOR USER_ACSVAR’

EXIT CODE(0)END /* END DATACLAS ROUTINE */


dfp: SMS RAS Enhancements

• Storage Group Space Alert Messages– Currently, SMS VTOC Data Set Services (VDSS) issues IGD17380I to notify a user that the

cumulative space allocated on the selected storage group has exceeded the high allocation

threshold.

IGD17380I STORAGE GROUP (sgname) IS ESTIMATED AT xx% OF CAPACITY, WHICH EXCEEDS ITS HIGH ALLOCATION THRESHOLD OF zz%

– z/OS V2R2 SMS allow yous to specify new storage group space warning thresholds separately

from the high allocation thresholds.



• Sample sreen to set up alerts

– Create new alert threshold attributes in the storage group panel

– If the alert threshold value is not specified, it defaults to zero and no alert messages will be

issued.



• Storage Group Space Alert Messages

– New alert messages, IGD400I and IGD401I, will be issued to the console when the alert thresholds have been reached.

IGD400I TOTAL SPACE ALERT ON STORAGE GROUP (sgname) CURRENT USAGE (xx%), ALERT THRESHOLD (yy%)

IGD401I TRACK-MANAGED SPACE ALERT ON STORAGE GROUP (sgname)CURRENT USAGE (xx%), ALERT THRESHOLD (yy%)

– The alert messages will be issued at an incremental interval. – IGD401I is issued only for the pool storage group containing one or more EAV volumes.



• Storage Group Space Alert Messages

– A new optional keyword, ALERT, is introduced for the DISPLAY SMS command.

– D SMS[,{STORGRP|SG}{(sgname|ALERT|ALL)}[,LISTVOL]

– The new optional keyword, ALERT, is used to display any pool storage groups which have

already reached either the total space alert threshold or the track-managed alert threshold.

– The existing message, IGD002I, will be enhanced to include space information.

– The space information is shown for pool storage groups only.


dfp: DEVSUPxx Enhancements• Improved DEVSUPxx Processing

– All keywords will be treated in a consistent manner so that none will be initially reset to their default values both during IPL and with processing SET DEVSUP command.

– The SET DEVSUP=xx target can specify only the keyword(s) that need to be changed.• Continued processing of the DEVSUP member after syntax error

– If syntax error is detected, the system continues processing and IEA252E message is issued:IEA252E DEVSUPxx: INVALID SYNTAX ON LINE yyyy. MEMBER PROCESSING

CONTINUES• Improved DEVSUPxx Processing

– Allow you to specify more than one DEVSUPxx member in a single SET command.– SET DEVSUP=(xx,yy,zz…)IEASYSxx PARMLIB member now supports multiple values for DEVSUP keyword:

DEVSUP=(xx,yy,zz…)• Additional information about tape-related DEVSUPxx parameters

– A new DEVSERV QLIB operand will display settings for TAPEAUTHDSN, TAPEAUTHF1, TAPEAUTHRC4, and TAPEAUTHRC8.


Dfp: Open/Close/EOV Enhancements

• Abend code Elimination– Eliminate abend code A13, reason code 18 by automatically selecting the correct volume during

Open processing for multivolume tape data sets.• Add JOBID & SYSPLEXID to SMF 14/15

– JOBID and SYSPLEXID are now added to SMF 14/15 (non-VSAM data set activity) records.

Rollback to V2.1 with OA43798.


DFSMShsm Updates• Classic Migration, Storage Tiers, and Data Migration

• ARCMDEXT Support for Transition

• Introduction of DFSMShsm Common Dump Queue

• Other DFSMShsm Dump Enhancements

• Fast Replication Enhancements


hsm: Classic Migration, Storage Tiers, and Data Migration• With z/OS V2R1, DFSMS Storage Tiers introduced automated, policy-based space management that

moves SMS-managed data from tier to tier within the Primary (Level 0) Hierarchy, allowing for policy-based management of “active” data.

• Automated movement provided via DFSMShsm Space Management function; movement is referred to

as a 'Class Transition‘ and is based on management class criteria.

• Data remains in its original format and can be immediately accessed after the movement is complete.

• Enhanced support for DB2, CICS and zFS data


Classic Migration, Storage Tiers, and Data Migration


hsm: Classic Migration, Storage Tiers, and Data Migration • z/OS V2R2 enables Class Transitions to be initiated with the various Migration commands.

– New keywords: BOTH, MIGRATIONONLY, TRANSITIONONLY

– The default behavior is to perform both migration and transition processing for VOLUME and

STORAGEGROUP operations.

– The default for MIGRATE DATASET is to perform a migration. The TRANSITION keyword indicates

that a transition should be performed.



With z/OS V2R2, a new STORAGEGROUP keyword can be used to initiate migration for all volumes within a storage group in parallel.

• Primary Space Management processing will be performed for the storage groups, as opposed to the

standard volume-by-volume processing performed by MIGRATE VOLUME.

– Use Case: Clients create DB2 image copies (using FlashCopy) to a specific storage group and then

invoke DFSMShsm MIGRATE to move the copies to tape.

– This enhancement enables a single command to process all of the volumes in the storage group in

parallel.



• New MOVE keyword enables DFSMS Class Transition function to move data laterally to the same tier of storage, in addition to the ability of moving data to different tiers storage.

• MOVE keyword added to the MIGRATE DSNAME, VOLUME and STORAGEGROUP commands.

– Every data set will be processed, regardless of management class policy or threshold, and ACS

routines will be invoked to determine the new storage class and/or storage group.

– Use Case: Move DB2 data from existing smaller volumes to the new larger, newly defined EAVs.


ARCMDEXT support for Class Transition

• In z/OS V2R2, ARCMDEXT enables RC 20-40 to be used to override the destination, so the Transition may be converted to a Migration.


Introduction of DFSMShsm Common Dump Queue

Today, Dump commands (Command, Auto, Fast Replication) today must be processed on the same DFSMShsm host that initiated the request.

The resources of a single DFSMShsm host do not scale to the large copy pool sizes that need to be

processed.



Distribute dump work across all hosts in a sysplex-wide Common Dump Queue (CDQ).

Introduces an architecture to distribute workload across host members in an HSMPlex, and the new

architecture allows for flexible configurations.

Invoked and controlled via SETSYS commands.



There are 3 roles that a host can assume:

Master Scheduler: Responsible for receiving, managing, and distributing Dump

requests within the XCF group. There can be only one Master Scheduler at a given

time within the group.

– Submitting Host: Receive requests from USERs or Automatic Functions and send to

Master Scheduler by XCF messaging, and Processing command complete message

from Master Scheduler and posts user complete. Any hosts connected to CDQ are

considered as submitting hosts, including Master scheduler.

– Processing Host: Receive requests from Master Scheduler, process, and send return

a response about completion to Master Scheduler. To become a Processing host, it is

necessary to be connected to CDQ with DUMP function not set to HOLD and with

DUMPTASKS greater than 0.



• Disconnect DFSMShsm hosts from CDQ before shutting down DFSMShsm.

– Prevent receiving Dump requests;

– Allows Master Scheduler (MS) to redirect the MS role to another eligible host;


Other DFSMShsm Dump Enhancements

• New MINSTACK and MAXSTACK keywords

Provide a minimum stack option to indicate that fully utilizing the available dump tasks is

more desirable than optimizing stacking.

– Added a new MINSTACK, minimum stack, parameter and an MAXSTACK alias for

the STACK parameter.

– Depending on the value of MINISTACK, it may be possible that the use of multi-

tasking will use more tapes.



• Sample of NEWSTACK difference



• Allow multiple Copy pools to be stacked onto the same tape

– This will occur when the copy pools are dumped at the same time and use the

same dump classes. Today this only occurs with Automatic Dump.

• New command UPDTCDS to update expiration date for a copy pool dump copy.

– New UPDTCDS command updates ALL of the CDS records that need to be

updated to reflect the new expiration date.

– Avoid using hundreds of FIXCDS commands.


DFSMS Fast Replication Enhancements

Today, finding messages related to a Fast Replication command is very difficult because they are written to shared logs.

First, find the correct log and then search through all of the messages for all HSM activity


DFSMS Fast Replication Enhancements

• z/OS V2R2 provides an option to dynamically allocate a unique message data set and write all DFSMShsm and DFSMSdss messages for a specific FRBACKUP or copy pool Automatic Dump to that data set.

– Invoked via SETSYS command

SETSYS FASTREPLICATION(MESSAGEDATASET(YES|NO HLQ(hlq)))

– Indicates that all Fast Replication messages should go to a unique data set with a unique HLQ.

– Each message is prefixed with the date and timestamp, along with the ID of the host that wrote

the message.

– Message Data Sets must be SMS managed.


DFSMSrmm Updates• WHILECATALOG attribute and EXPDT retention method

• DFSMSrmm RAS Enhancements


WHILECATALOG attribute and EXPDT retention method• WHILECATALOG Support

Until z/OS V2R2 it was impossible to let the catalog status of a dataset control its retention without

using a VRS policy. Now, the user can directly specify "WHILECATALOG" for data sets managed by

their Expiration Date.

– Especially useful for GDG datasets – use WHILECATALOG to keep cataloged GDGs available until they’re uncataloged as new generations are created.

– Can be set as a default, or can be changed using CHANGEDATASET. – Can be defined PARMLIB with separate defaults specified for GDG and non-GDG

datasets.


WHILECATALOG attribute and EXPDT retention method• WHILECATALOG(ON) processing


DFSMSrmm Enhancements

• WHILECATALOG(UntilExpired) processing


DFSMSrmm RAS Enhancements

• Use of Expiration Time– Beginning on z/OS V2R2, scratch processing will also include expiration time when

deciding on whether or not to expire a tape. This will prevent tapes from being scratched before the required time

• SEARCHDATASET / SEARCHVOLUME Enhancements– Search volumes and data sets by date/time ranges.

RMM SEARCHDATASET OWNER(*) LIMIT(*) CRDATE(START(2013/110,220000) END(2013/111,040000)) CLIST('RMM CHANGEDATASET ',')EXPDT(2013/120)')

• CHANGEVOLUME / CHANGEDATASET Enhancements– The CHANGEVOLUME has been enhanced to provide a better performance when

used to change only EXPDT attribute from the records– Update expiration time of volumes and data sets.

RMM CHANGEDATASET 'USER1.DUMP' VOLUME(THM000) EXPTM(153000)


DFSORT Updates• zHPF Exploitation

• AGE Function

• WEEKNUM Function

• Other DFSORT Enhancements


zHPF Exploitation

• Currently DFSORT does not exploit zHPF.– zHPF increases the maximum I/O rate possible on the channel by providing Transport Control

Word (TCW) that facilitates the processing of aan I/O request by the channel and the control unit.

– DFSORT normally uses EXCP for processing of basic and large format sequential input and output data sets (SORTIN, SORTOUT, OUTFIL).

– DFSORT already uses BSAM for extended format sequential input and output data sets (SORTIN, SORTOUT and OUTFIL). BSAM already supports zHPF.

• Update DFSORT to prefer BSAM for SORTIN/SORTOUT/OUTFIL when zHPF is available.– DFSORT will automatically take advantage of zHPF if it is available on your system; no user actions

are necessary.– You will be able to identify the use of BSAM access method for your work by searching message

ICE084I. There is no DFSORT messages related to zHPF usage on any logs or sysouts


AGE Function

• Date conversion AGE function– A date conversion function AGE for the BUILD and OVERLAY operands of DFSORT’s INREC,

OUTREC and OUTFIL statements can now be used to calculate the date duration (ie time between a given date and the current date):

– AGE=YMD produces a 8 byte result which has duration in years (0-9999), months (00-12), and days (00-31).

– AGE=YM produces a 6 byte result which has duration in years (0-9999), months (00-12).– AGE=YD produces a 7 byte result which has duration in years (0-9999), days (00-366).


AGE Function


WEEKNUM Function

• Date conversion WEEKNUM function– A date conversion function WEEKNUM for the BUILD and OVERLAY operands of DFSORT’s

INREC, OUTREC and OUTFIL statements can now be used to calculate the week number that represents the week of the year.

– WEEKNUM=USA returns an integer in the range of 1 to 54 that represents the week of the year. The week starts with Sunday, and January 1 is always in the first week.

– WEEKNUM=ISO function returns an integer in the range of 1 to 53 that represents the week of the year. The week starts with Monday and includes 7 days.


WEEKNUM Function


Catalog and IDCAMS Updates• GDG Enhancements

• Catalog RAS Enhancements

• Miscellaneous IDCAMS Enhancements


GDG Enhancements

• New DEFINE EXTENDED keyword allows up to 999 GDS to be active within 1 GDG.

– DEFINE SMS.GDG GDG EXTENDED LIMIT(999)

– ALTER LIMIT(limit) is provided to modify the max number (between 1 and now 999)

– Enabled via SYS1.PARMLIB member IGGCATxx

– New GDGEXTENDED variable set to “YES” (default is “NO”).


GDG Enhancements

– Coexistence considerations

– ALL systems in an installation should be at z/OS V2.2 or higher before enabling

GDGEs, and it’s expected that there will be no attempt to fall back a prior release.

– Coexistence APAR OA46009 (Catalog) and OA46116 (DSS) prevents access to

GDGEs on lower level systems.


GDG Enhancements

– New GDGSCRATCH (YES|NO) parmlib variable overrides IDCAMS keyword on GDG DEFINE.

– If not set or parmlib variable is GDGSCRATCH(NO), the keyword specified on the

DEFINE GDG takes precedence.

– New PURGE keyword added to IDCAMS DEFINE and ALTER GDG which allows user to specify what happens to unexpired GDSs during roll-off.

– Specifies that when the SCRATCH is set, unexpired generation data sets (GDSs)

are to be deleted during roll off processing. Default is NOPURGE.

– New variable, GDGPURGE (YES|NO), for SYS1.PARMLIB member IGGCATxx.

Default is “NO”. Overrides DEFINE GDG setting when PURGE is set.


Catalog RAS Enhancements

• Catalog Attributes Healthcheck

– A shared catalog must be defined with SHAREOPTIONS(3 4) and must reside on a

shared volume.

– Catalogs that reside on shared volumes will become damaged if referred to by another

system and the shareoptions are inconsistently set.

– A new healthcheck will be designed to identify catalogs residing on volumes whose

devices are defined as shared in the active IODF that might have their

SHAREOPTIONS set incorrectly.


Catalog RAS Enhancements

• DFSMSdss restore of User Catalog to Any Volume

– Allows logical catalogs restored to be performed to any volumes, as long as device

capacity matches (3390 vs 3390).

– Catalog Modify Command Security

– Provides additional controls to enable users to perform only report related catalog

activities.

– New Catalog Search Interface fields

– CAXWA control blocks moved to CAS private storage. CSI now can be used to retrieve

dynamic catalog data.

– Connect Multi-line WTO

– Large multi-line operator messages (> 255 lines) will now display to completion.


Miscellaneous IDCAMS Enhancements

• VERIFY RECOVER Enhanced

– Running VERIFY RECOVER command after an EXAMINE (on the same STEP) will cause

EXAMINE to pass error information to VERIFY command, and it will attempt to repair any error that

it can.

• REPRO MERGECAT reduced output

– New MESSAGELEVEL keyword added to REPRO to reduce the number of output lines for REPRO

commands. Using MESSAGELEVEL(SHORT) option will replace IDC0639I and IDC01402I by new

IDC01401I:

– IDC01401I SUCCESSFUL MERGE FOR GILTST1.TEST.V000001


Miscellaneous IDCAMS Enhancements

• New CIMODE to PRINT and REPRO functions

– New keyword CIMODE, which PRINTs or REPROs by CI rather than by record. Opens VSAM data

set in CIMODE and is primarily for use with ESDS, but could be used to access a KSDS data

component directly.

• TSO LISTCAT NOPREFIX keyword

– A new parameter PREFIX/NOPREFIX has been introduced to LISTCAT. This new parameter allows

the user to add/remove the TSO user id when running LISTCAT


VSAM Updates• RLS Index Level Locking• VSAM LSR Dynamic Buffer Addition• Faster search for Access Method Block List• Support for DB2 greater than 2M Opened clusters


VSAM Enhancements

• RLS Index Level Locking– Today when processing VSAM data sets, there is a single point of contention (DIWA) preventing

concurrent VSAM RLS data CI splits in different CAs, CI reclaims, and spanned-record insertions and updates.

– z/OS V2R2 introduces a new level of serialization at the sequence set index CI level.– New locks used during CI SPLIT, CI RECLAIM, spanned record activity.– CA split / reclaim activity will still use data-set level lock.– New SMF fields were added to MVS System Management Facilities (SMF) for the new index

record locks.– Toleration Considerations:

– Toleration APAR OA42676 is required to be installed on all V1R13 and V2R1 systems across the sysplex prior to bringing a V2R2 system into the sysplex.


VSAM nhancements

• VSAM LSR Dynamic Buffer Addition– Currently with LSR buffering, if there are no available buffers to process a request (ie they’re in use

by other requests), the request will fail with a logic error indicating “no buffers”.– Dynamically add buffers to LSR pool as needed.

– The current buffer pool is expanded with the same settings.– If successful, an informational RC = x'44' is returned in the RPL feedback word; otherwise,

the “no buffers” logic error will still be returned.– Not supported for GSR buffer processing, Cross memory mode, SRB mode or

TCB's running in Key 9. – New message:

IDA9990I VSAM DBA ADDED xxxx DATA|INDEX BUFFERS of yyyyy BYTES EACH TO SHRPOOL zzz BECAUSE THERE WERE INSUFFICIENT BUFFERS TO PROCESS THE REQUEST.RECOMMENDATION: FOR PERFORMANCE, REBUILD THE SHARED POOL WITH AN INCREASE IN SIZE.


VSAM Enhancements

• Faster search for Access Method Block List• AMBL is a VSAM internal control block associated with opened clusters. Having thousand data sets

opened by an application such as DB2 will result in large AMBL chains.• z/OS V2R2 improves AMBL chain searches by introducing a binary tree to keep track of the opens and

closes for each cluster


VSAM Enhancements

• Support for DB2 greater than 2M Opened clusters• A large number of opened clusters leads to large amounts of virtual storage for VSAM control blocks,

that must reside in 31 bit addressable private storage.• In z/OS V2R2 some of the control blocks for linear clusters (VSAM LDS) are moved above the bar, if

requested so by the Media Manager caller.

ibm.com


< Sysplex>

z/OS V2R2 EnhancementsIBM Redbooks: SG24-8307-00 IBM z/OS V2R2: Sysplex


Topics Covered

• CF Site Preference List

• Message Isolation

• Gaining CF Ownership

• Server Time Protocol

• Log Stream Offload Process


CF Site Preference List

• CF Duplexed Structures and Keywords

• Enhanced Messages

• Health Check on Structure Duplexing


CF Site Preference List - CF Duplexed Structures and Keywords

Prior to z/OS V2R2 XES picks up a CF by:

• Locating the CF name in the CFRM preference list

• Connectivity to the system trying to allocate the structure

• The CFLEVEL greater than or equal to the requested CFLEVEL as declared at

IXLCONN macro

• There is available space equal to or greater than the requested structure size

• The volatility requirement is met as declared at IXLCONN macro

• The failure-independent requirement requested at IXLCONN macro is met

• Does not contain structures in the exclusion list as declared at CFRM couple

data set.



Structure duplex rebuild:

Structure duplexing rebuild aims to provide continuous availability in the event of

the primary structure experiencing an outage.

There are 2 types of duplexing as chosen by the structure exploiter:

• User Managed Duplex based on performance

– Secondary structure may reside local

• System Managed Duplex based on availability

– Secondary structure may reside remotely



Prior to z/OS V2R2, structure PREFLIST parameter in CFRM policy provides

insufficient XES information to determine best CF for each duplexed structure.

Solution is to use the former SITE keyword plus new CFRM keywords:

• SAMESITEONLY Only duplex structure, if both CFs are at the same site

• SAMESITE Creates a preference to duplex structure in CFs at the same site

• CROSSITE Creates a preference to duplex structure in CFs at a different site

• ANYSITE CF SITE specification is not used to determine CF importance and

eligibility for duplexed CF structure allocation.


CF Site Preference List - CF Duplexed Structures and KeywordsCF NAME(CF1SITE1) SITE(SITE1)MFG(IBM)...CF NAME(CF2SITE1) SITE(SITE1)MFG(IBM)...CF NAME(CF1SITE2) SITE(SITE2)MFG(IBM)...CF NAME(CF2SITE2) SITE(SITE2)MFG(IBM)...

STRUCTURE NAME(STR1) SIZE(10M) DUPLEX(ALLOWED) PREFLIST(CF1SITE1,CF2SITE1,CF1SITE2,CF2SITE2)STRUCTURE NAME(STR2) SIZE(10M) DUPLEX(ALLOWED,SAMESITEONLY)PREFLIST(CF1SITE1,CF2SITE1,CF1SITE2,CF2SITE2)STRUCTURE NAME(STR3) SIZE(10M) DUPLEX(ENABLED,SAMESITE)PREFLIST(CF1SITE1,CF2SITE1,CF1SITE2,CF2SITE2)STRUCTURE NAME(STR4) SIZE(10M) DUPLEX(ENABLED,CROSSSITE)PREFLIST(CF1SITE1,CF2SITE1,CF1SITE2,CF2SITE2)


CF Site Preference List – Enhanced Messages

D XCF,STR,STRNAMEIXC360I 14.11.06 DISPLAY XCF STRNAME: DUPALLOWED01STATUS: ALLOCATEDEVENT MANAGEMENT: MESSAGE-BASEDTYPE: CACHEPOLICY INFORMATION:

POLICY SIZE: 204 MPOLICY INITSIZE: 104 MPOLICY MINSIZE: 90 MFULLTHRESHOLD: 80ALLOWAUTOALT: NOREBUILD PERCENT: N/ADUPLEX: ALLOWED SAMESITEONLYALLOWREALLOCATE: YESPREFERENCE LIST: LF01 LF02 A TESTCF SUPERSESENFORCEORDER: NOEXCLUSION LIST IS EMPTY


CF Site Preference List – Enhanced Messages

IXC745I enhancementsTHE PREFLIST MUST CONTAIN TWO OR MORE FACILITIES

The value of the DUPLEX keyword requires that two or more coupling facilities be specified in the preference list for the structure.

THE PREFLIST MUST CONTAIN TWO OR MORE FACILITIES WITH DIFFERENT SITE VALUES

The CROSSSITE keyword specified on the DUPLEX parameter requires that two or more coupling facilities be specified in the preference list for the structure with different SITE values.

THE PREFLIST MUST CONTAIN TWO OR MORE FACILITIES WITH THE SAME SITE VALUE

The SAMESITE or SAMESITEONLY keyword specified on the DUPLEX parameter requires that two or more coupling facilities be specified in the preference list for the structure with the same SITE value.

The new message IXCH0226I is displayed when DUPLEX SITE preference is used. The new message IXCH0227I is displayed if DUPLEX SITE preference not met. The messages IXCH0202I and IXCH0206E are changed.


CF Site Preference List – Health Check on Structure Duplexing

• The IBM Health Check XCF_CF_STR_PREFLIST check shows exceptions for

duplexed structures based on DUPLEX parameter. The most preferred CF

depends on DUPLEX SITE preference:

• ANYSITE (specified or defaulted)

– Primary in first CF in PREFLIST

– Secondary in second CF in PREFLIST

• SAMESITE or SAMESITEONLY

– Primary in first CF with SITE specified

– Secondary in next CF with same SITE

• CROSSSITE

– Primary in first CF with SITE specified

– Secondary in next CF with other SITE


XCF Signalling Transport Class Simplification

• Messaging

• Operational Considerations

• Message Isolation


Messaging

XCF is a z/OS component that passes messages between a group of

members in a Parallel Sysplex.

• Messages are held in buffers; there are 3 kinds:

– Outbound message buffers - used to store the message on the sending system

– Inbound Message buffers - used to receive the message on the target system

– Local message buffers - used to send and receive messages within the same system


Operational Considerations

• The successful delivery of messages and responses between members

is reliant on:

– The configuration of components and operational processes required to perform

messaging traffic are available and sufficiently functional.

– The performance of all the related parts are balanced, and achieving their goals

without dominating a resource or disrupting the capacity apportionment across the

sysplex.

• If the target system is experiencing issues and is not recycling its

inbound message buffers, the buffers may fill up and the system

becomes stalled.


Operational Considerations

• A stalled system can have a further impact on other members because

the other members attempting to send messages to the stalled system

will still have their outbound message buffers in use as they wait for the

stalled system to become available again. If the situation persists, the

sending system's outbound message buffers will become saturated

because of the delay, and any further IXCMSGO requests will be

denied. The sending systems may then experience a secondary impact

and stall because of the issue with the target system which is still

experiencing difficulties and has already stalled. This secondary impact

may spread to other members.


Impact of a stalled system

• Operational Message IXC631I:

– When a stalled system affects other members it issues the message IXC6311 to inform

the operator that a local stalled XCF member may be having an effect on other

members. This message is also displayed once for each of the other members affected

by the stalled member.

IXC631I GROUP grpname MEMBER membername JOB jobname ASID asidSTALLED, IMPACTING SYSTEM sysname {WHICH IS IN PARTITIONING }Explanation: The indicated XCF Group Member is not processing its XCF work in a timely manner. The stall is considered critical because it is impacting the indicated system. For example, the indicated system may not be able to send signals to the local system because the stalled member is holding XCF signal buffers that would be needed to receive such signals.


Impact of a stalled system

• Operational Message IXC640EI:

– The stalled system will issue message IXC640E once to indicate the stalled situation

has arisen and a possible resolution, see . The situation will become more complicated

if the consoles on the offending system are unable to process the IXC631I and

IXC640E messages.

– .IXC640E type XCF GROUP MEMBERS ON SYSTEM sysname IMPACTING SYSPLEXtextExplanation: One of the following conditions exists:System sysname has at least one XCF group member that appears to be stalled, and is not processing its XCF work in a timely manner. Failure to process this work appears to be impacting the sysplex. System sysname has at least one critical XCF group member that appears to be impaired. See the explanation of message IXC633I for a description of situations that can make a member appear impaired.


Message Isolation Enhancements

• Message isolation is the process by which XCF monitoring identifies a member

which is not processing its inbound buffers in a timely manner and subsequently

arranges to have sending XCF systems reject or delay messages targeted to

that member.

– IXCJOIN macro has new MSGISO keyword MSGORSN to request the isolated status.

– IXCMSGO and IXCMSGOX new isolation reason code:

– Hex Return code 0C Hex Reason code 3C

– Equate Symbol: ixcMsgRsnTargetIsolated

– Query services IXCQUERY, IXCYQUAA, IXCMG, IXCYAMDA: to determine the

member status and recognize the Impacted and Isolated status.

– DISPLAY XCF: MVS display command to show status information.



– IXC637I: system message displaying the impact window for a given member.

IXC637I GROUP grp_name MEMBER isolated_memname JOB jobname ASID asidMEMTOKEN memtoken1 memtoken2 ON SYSTEM isosysnm ISO#: isosysslot.sysiso#MESSAGE ISOLATION IMPACT FOR SYSTEM impsysnm RPT#: report#IMPACTED : impactdate impacttime IXC637ISEQ#: impactiso# whyclosed: closedateclosetimeRESUMED : SEQ#: closeiso#DELAYED : delayeddate delayedtime #MSG: #msgdelayedREJECTED : rejecteddate rejectedtime #MSG: #msgrejected

Explanation: Member isolated_memname of group grp_name on system isosysnm is “message isolated”. XCF delays or rejects messages targeted to a member that is message isolated. When a sending member has a message delayed or rejected because the target member appears to be isolated, the sending member is said to be “impacted”. System impsysnm issues message IXC637I to summarize the isolation impact experienced by the members of group grp_name residing on system impsysnm. Message IXC637I indicates the time when the impact started, the number of messagesthat were delayed or rejected, and the time when messages were most recently delayed or rejected.



– NEW MESSAGE IXC637I: system message displaying the impact window for a given member.

IXC637I GROUP grp_name MEMBER isolated_memname JOB jobname ASID asidMEMTOKEN memtoken1 memtoken2 ON SYSTEM isosysnm ISO#: isosysslot.sysiso#MESSAGE ISOLATION IMPACT FOR SYSTEM impsysnm RPT#: report#IMPACTED : impactdate impacttime IXC637ISEQ#: impactiso# whyclosed: closedateclosetimeRESUMED : SEQ#: closeiso#DELAYED : delayeddate delayedtime #MSG: #msgdelayedREJECTED : rejecteddate rejectedtime #MSG: #msgrejected

Explanation: Member isolated_memname of group grp_name on system isosysnm is “message isolated”. XCF delays or rejects messages targeted to a member that is message isolated. When a sending member has a message delayed or rejected because the target member appears to be isolated, the sending member is said to be “impacted”. System impsysnm issues message IXC637I to summarize the isolation impact experienced by the members of group grp_name residing on system impsysnm. Message IXC637I indicates the time when the impact started, the number of messagesthat were delayed or rejected, and the time when messages were most recently delayed or rejected.



– NEW MESSAGE IXC638I: system message displaying the isolation window for a given member.

IXC638I GROUP grp_name MEMBER member_name JOB jobname ASID asidMEMTOKEN memtoken1 memtoken2 ON SYSTEM sysname ISO#: isosysslot.sysiso#MESSAGE ISOLATION STATUS FOR SYSTEM sysname RPT#: report#ISOLATED : isolatedate isolatetime : SEQ#: memberiso# whyclosed: closedate closetimeRESUMED : SEQ#: resumeiso#DELIVERYQ : deliveryqdate deliveryqtime #MSG: #msgqueuedLAST MSGX : activedatesi activetimesi SEQ#: signalqueueseq#

Explanation: Member member_name of group grp_name on system sysname is “message isolated”. XCF isolates a member when it fails to make adequate progress with respect to the processing of its messages. Message isolation helps keep problematic group members from impeding the delivery of messages to other members. Message IXC638I indicates the time when XCF isolated the member and provides information about the XCF work pending for themember, as well as information about the progress of the signal exit routines that are expected to process that work.



– NEW MESSAGE IXC645E: alerting the operator to the existence of isolated members..

IXC645E SYSTEM sysname HAS ISOLATED XCF GROUP MEMBERS

Explanation: One or more XCF group members on system sysname are “message isolated”. XCF isolates a member when it fails to make adequate progress with respect to the processing of its messages. Message isolation helps keepproblematic group members from impeding the delivery of messages to other members.



– DISPLAY XCF,GROUP uses the new query services for status information..


Migration and coexistence considerations

• The new enhancements only apply to systems running z/OS V2R2 however be considerate of the following points:

• Does apply to local message traffic, though we seldom see issues there• So not likely to see any new behavior until there are at least two systems running z/OS V2R2 in

the sysplex• IPLing system with z/OS V2R2 activates the new behavior. However, when communicating with

down level system, the old behaviors apply and so derive no benefit.• Down level systems do not require any compatibility support.• z/OS V2R2, XCF might now selectively indicate “no buffer” for messages targeted to an

isolated member.• Some XCF exploiters issue messages to complain when their msgout request is rejected for a

“no buffer” condition• In the past, you might then go look at your MAXMSG specifications• But with z/OS V2R2, those exploiter messages might be the result of the target

member being “message isolated”• So with z/OS V2R2, you should first look to see whether message isolation might

apply• XCF query services (and therefore measurement products such as RMF) only indicate “no

buffer” for true MAXMSG constraints.


Gaining CF Ownership

• A z/OS instance joining a Sysplex

• Definition Enhancements


Gaining CF Ownership - A z/OS instance joining a Sysplex

The XCF of the z/OS system joining the Syplex uses Pathout information to try to

establish a conversation with other z/OS systems’ XCF already in the Sysplex.

Verification requires:

• The Sysplex name in the COUPLExx is the same as the other z/OS systems in

the Sysplex.

• The symbol &Sysclone is unique per z/OS in the Sysplex

• GRS RNL is the same as in other previous z/OS Sysplex members

• MAXSYSTEM parameter counter of z/OS systems in the Sysplex is not

exceeded.

If everything is correct, then the XES component tries to connect with the CF.



Prior to z/OS V2R2 CF Authority was introduced.

• The CF Authority is a string of bytes located in the CF. It is formed by the

Sysplex name plus the contents of the current TOD. The first z/OS XES joining

the Sysplex (first connecting) asks the CF to store the CF Authority. The

Sysplex name in the CF Authority comes from the COUPLExx Parmlib member,

as defined by the installation. The act of storing a new CF Authority in the CF is

termed “gaining ownership”.

• The CF is located by XES through its name and attributes (Name, Type, MFG,

Partition, CECID, and other information) as described at the CFRM couple data

set.

.



Every time the first XES in a z/OS succeeds is connecting to a CF, this XES also

copies the CF Authority into the CFRM couple data set (CDS). Then, every time

that a gaining ownership process is executed, the CF Authority at the CFRM is

compared with the CF Authority in the CF to avoid the same CF in several

Sysplexes. CF Authority is cleared (zeroed) at the CF when it is removed from the

Sysplex.

.


Gaining CF Ownership – Definition Enhancements

Prior to z/OS V2R2, hardware definition and configuration errors may cause

issues when XES from the IPLing z/OS tries to connect to a CF already being

used by z/OS systems from other Sysplexes. In this case, messages are shown at

the console and the operator must decide on what action to take. If the information

is insufficient, an incorrect decision may cause a full Sysplex outage.

CFRMTAKOVERFCF is a new COUPLExx keyword. The default is (NO).

.



When a Sysplex tries to gain ownership to the CF via the first IPL of one of its

z/OS systems, it will attempt to store a new CF Authority in a CF. :

• If CF Authority of the CF matches the old CF Authority in the CFRM CDS. It

means that this CF was used lately by this Sysplex.

– Why would an old CF Authority in the CFRM CDS match the one in CF?

– The Sysplex is being IPLed in the previous CF. It appears that there are no problems with this

so it would be okay to use CF

– IPL another z/OS with a different Sysplex couple data set, with another Sysplex name, but using

a copy (from mirroring or otherwise) of the same CFRM CDS. This is not recommended

because other z/OS systems are still using the current copy of CFRM CDS, that is, running in

other Sysplex and using this CF.



• The action here depends of the COUPLExx member keyword:

– CFRMOWNEDCFPROMPT(NO) - default. Sysplex gains ownership automatically

– CFRMOWNEDCFPROMPT(YES). Operator is prompted and needs to decide

This keyword was introduced prior to z/OS V2R2.

.



• CF Authority mismatches. Why would an CF Authority in the CFRM CDS

mismatch the one in CF?

– Sysplex-wide IPL with a different CFRM CDS. There is no problem to use such CF

– IPL a z/OS from different Sysplex couple data set but using an old copy (from mirroring or

otherwise) of the CFRM CDS. This situation has many potential issues if the Sysplex using

current copy of CFRM CDS still using CF

– IPL another sysplex (different sysplex CDS) with a CFRM policy that has a CF that does not

belong to it. This is also not recommended and putting the systems at risk.



• The action here depends of the COUPLExx member keyword:

– CFRMTAKEOVERCF(NO) - the default and recommended. XES rejects use of a CF that may

be in use by another Sysplex. Using this option, the installation avoids potential errors and

forces the installation to reactivate the CF being wrongly accessed, in order to pass it from one

Sysplex to another Sysplex if required.

– CFRMTAKEOVERCF(PROMPT) - old behavior. The operator is prompted and needs to make a

decision based on understanding the request and implications.

.


Server Time Protocol

• STP Roles

• Message Enhancements

• Migration and Coexistence


Server Time Protocol – STP Roles

STP provides the capability for multiple servers and CFs to maintain time

synchronization without requiring an IBM Sysplex Timer.

• The Current Time Server (CTS) is known as the Stratus 1 Server and this

provides time messages to the rest of the time related network.

– Preferred Time Server (PTS): is the preferred server to be the CTS, It uses timing information sent

by Support Elements or External Time Source to define synchronization between hosts.

– Backup Time Server (BTS): takes over as the CTS in the event of planned or unplanned outages,

without disrupting synchronization.

– Arbiter - Optionally configured on sysplexes with three or more servers and is used to determine

whether the BTS should take over the role of the CTS when communication with the PTS is lost.

Only a PTS and BTS can be assigned as the CTS, the arbiter is instrumental in the transition of the

BTS taking over the role as the CTS from the PTS. A failure or connection on the PTS will cause

the Arbiter-assisted recovery to be used when available.


Server Time Protocol – STP Roles

CTS (Stratum 1)PTS

Stratum 2BTS

Stratum 2Arbiter

Stratum 2

STP- Only Coordnated Timing Network


Server Time Protocol – Message EnhancementsWhen a state change is detected on STP role servers, the IEA398I message will

be issued indicating the change, and the reason.

IEA398I STP ROLE SERVER ATTACHMENT STATE CHANGE. STATE =

cccccccc REASON=H

• cccccccc is one of:

– FULL - Full connectivity between the role servers; the 3 role servers are each connected directly

to each other.

– Partial - A loss of connectivity exist between any 2 role servers, but not sufficient to fall to a

degraded state.

– Degraded - Any one of the role servers is unreachable from the other two. This implies that a

loss of connectivity exists sufficient to cause the disablement of arbiter-assisted recovery.

• H is the code which identifies the servers affected by the loss of connectivity.


Server Time Protocol – Message EnhancementsIf the IEA398I message is displayed as a result of a partial or degraded state, the

related IEA396E a WTO will be issued indicating the Arbiter-assisted recovery is

disabled.

IEA396E ARBITER ASSISTED RECOVERY IS DISABLED FOR THE CTN.

REASON = hh

The reason codes include:

• 11 - Arbiter not attached to primary or backup.

• 12 - Backup not attached to primary or arbiter.

• 13 - Primary not attached to backup or arbiter.

• 21 thru 23 - Role server entered imminent server disruption state.

• 31 thru 33 - Role server operating on internal battery feature.


Server Time Protocol – Message EnhancementsThe IEA396E WTO will not be cleared until the Arbiter-assisted recovery is

enabled. Message IEA397I is displayed as shown in to confirms the recover is

enabled.

IEA397I ARBITER ASSISTED RECOVERY IS ENABLED FOR THE CTN


Server Time Protocol – Migration and coexistence• There is a hardware dependency that must be met in order to use new STP

state change messages. The hardware and microcode level necessary to use

this feature are shown on .

Driver/Server MCL Bundle Release DateD79F/z10 N24406.094 50 Sep 28, 2011D86E/z196 N29799.110 44 Aug 24, 2011D93G/z114 & z196 GA2

Integrated N/A Sep 9, 2011


Log Stream Offload Process

• There is a new keyword available when defining or updating log streams on

z/OS V2R2 called LS_ALLOCAHEAD to pro-actively allocate up to 3 "advance-

current" offload data sets.

• Before you use LS_ALLOCAHEAD for defining log streams, you need to make

sure this feature is enabled in your environment. The default is to have this

feature enabled. You can enable/disable ALLOCAHEAD in IXGCNFxx

PARMLIB. You can also enable/disable ALLOCAHEAD dynamically

SETLOGR MANAGE,OFFLOAD,ALLOCAHEAD(YES|NO)


Log Stream Offload Process

• You can allocate up to 3 "advance-current" offload data sets when defining or

updating log streams. If defining a new log stream, the offload data sets will be

opened when a data set switch is necessary from the actual offload data set

being written into for the log stream.

• When first "advance-current" offload data set becomes the current one, logger

will automatically trigger another allocation to get a new "advance-current"

offload data set to meet the target.

ibm.com


<Security>

z/OS V2R2 EnhancementsIBM Redbooks: SG24-8288-00 IBM z/OS V2R2: Security


Topics Covered

• RACF

• LDAP

• PKI


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

The following are trademarks or registered trademarks of other companies.

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

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.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft Corporation in the United States, other countries, or both.Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.

For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml:

*BladeCenter®, DB2®, e business(logo)®, DataPower®, ESCON, eServer, FICON, IBM®, IBM (logo)®, MVS, OS/390®, POWER6®, POWER6+, POWER7®, Power Architecture®, PowerVM®, S/390®, System p®, System p5, System x®, System z®, System z9®, System z10®, WebSphere®, X-Architecture®, zEnterprise, z9®, z10, z/Architecture®, z/OS®, z/VM®, z/VSE®, zSeries®

Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market.

Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.

Trademarks


Read-Only Auditor Attribute

• Allows users to list profiles and users, permit the same ability to list information

that would be allowed to users with the AUDITOR attribute, but no access to

alter any system controls.

ADDUSER DIANA ROAUDIT TSO(PROC(ISPFPROC)...) ...


Default password removal for ADDUSER

• ADDUSER command no longer assigns a default password. If no phrase is

specified, the user is defined as PROTECTED.

ADDUSER NEWUSER

ICH01024I User NEWUSER is defined as PROTECTED.


Default password removal for ADDUSER

• The RACF exit ICHDEX01 is not needed anymore unless you are implementing

your own encryption. In the absence of the exit, RACF's default password

evaluation behavior is to try first assuming DES, and if no match is found, it

uses masking.


Password phrase support for RACLINK

• The RACLINK DEFINE command now supports password phrases.

• The RACLINK DEFINE command allows specification of target user's

password/phrase for implicit approval of the user ID association:

RACLINK ID(thisuser) DEFINE(thatnode.thatuser/thatpwd) PEER(PWSYNC)


GRANULAR CERTIFICATE ADMINISTRATION

• RACDCERT command is used to install and maintain digital certificates, key

rings, and digital certificates mappings in RACF.

• The command can be granular once you turn it on by the presence of the profile

IRR.RACDCERT.GRANULAR in the RDATALIB class

• Define a profile to control who can delete the certificate with label

FTPSERVER1 owned by user ID ftpid:

RDEFINE RDATALIB IRR.DIGTCERT.FTPID.FTPSERVER1.UPD.DELETE UACC(NONE)

PERMIT IRR.DIGTCERT.FTPID.FTPSERVER1.UPD.DELETE CLASS(RDATALIB) ID(USERA)

ACCESS(READ)


RACF Remote Sharing Facility

• Dynamic Main Switching is the ability to change your Main System Node (MSN)

to another LPAR without having to use the current complex process.

• Enable non-MAIN systems to become MAIN. They must now have checkpoint

files for, and communication channels to remote non-MAIN systems, and those

remote non-MAINs must be enabled as well


RACF Remote Sharing Facility

1) From the old (current) MAIN system issue:

TARGET NODE(msn-name) SYSNAME(new-main) NEWMAIN

IRRM098I DRAINING SYSTEM OF INBOUND WORK. DO NOT INITIATE THE MAIN

SWITCH ON THE NEW MAIN SYSTEM UNTIL MESSAGE IRRM099I IS ISSUED.

IRRM099I ALL INBOUND WORK HAS COMPLETED. IT IS NOW SAFE TO INITIATE

THE MAIN SWITCH ON THE NEW MAIN SYSTEM.

2) From the new MAIN system, issue:


IRRM102I SYSTEM new-main IS NOW THE MAIN SYSTEM IN LOCAL NODE msn-

name.

3) From the remaining peer systems, issue:



Other changes

• The RACF_ENCRYPTION_ALGORITHM Health Check raises an exception if

KDFAES is not the active algorithm.

• New UNIXPRIV resource SUPERUSER.FILESYS.DIRSRCH controls read

and/or search accesses to all directories in RACF.

• New FSEXEC class in RACF prevents the execution of a specific file system, or

all files in a file system, similar to a 'NOEXEC' mount option.


Activity Log Enhancements

• In z/OS V2R2, LDAP allows you to specify a number of additional events to be

recorded in the LDAP activity log and in SMF type 83 records.

• Some New Activity Log features include, but are not limited to:

– New records for connection start and end events

– Merged and non-merged record types are supported.

– Existing add request records changed to include the attribute names in the request

– Existing modify request records changed to include the attribute name and an indication of it being

added, deleted or replaced

– Existing compare request records changed to include pwdpolicy update indicator

– New record for abandon requests

– Existing request records changed to include the msgid so that abandon requests can be related to

the request they affect

– New record for unknown requests


Compatibility Level Upgrade Without LDAP Outage

• LDAP support a new transition mode for a sysplex owning LDAP server. It

allows other LDAP servers in a Parallel Sysplex to be shut down and restart at a

new compatibility level, or with additional back ends without shutting down all

LDAP services in the Sysplex.

• Transition server operates at sysplex owner's level until it becomes the sysplex

owner. Terminating all the other instances in the sysplex triggers transition

server to complete transition by applying the new compatibility level and

refreshing backends. Finally, transition server becomes a normal sysplex owner,

making sysplex available for replicas with the same setting to join.


Dynamic Group Performance Enhancements

• In the past, determining a user's groups for dynamic groups required matching

the user entry against each URL in the directory. This is costly and does not

scale.

• This enhancement introduces a partial index. Dynamic group memberURLs are

indexed, when possible, on filter predicates:

– equal and present filter predicates within the URL are eligible for indexing.

– AND filters with at least one eligible predicate are also eligible for indexing.

– OR filters are only eligible for indexing if all predicates are eligible.

– Other filter types are not eligible: substring, greater or equal, less or equal, and NOT

filters.


Replication of Password Policy Attributes from a read-only Replica• In z/OS V2R2, LDAP propagate password policy operational attributes from the read only

replica to the supplier by sending a bind request.


PKI Enhancements

• PKINIT is a pre authentication mechanism for Kerberos 5, which uses X.509

certificates to authenticate the KDC to clients and vice versa.

• In this release, it is not required the use of UID 0 for the started tasks for

Kerberos, it supports new PKINIT parameters for the kinit command, and adds

some new PKINIT APIs.

• In this new release, PKI Services will enhance the administrator approval mode

to support multiple number of approvers. A configuration option with be provided

in the CGI templates file and JSP templates xml file to set the number of

administrators required to approve a certificate request.

• In V2R2, PKI Services enables to sign the OCSP response with the client

specified signing algorithm through an extension in the request.

ibm.com


z/OS – Availability Management

z/OS V2R2 EnhancementsIBM Redbooks: SG24-8290-00 IBM z/OS V2R2: Availability Management


Agenda

• z/OS Management Facility

• Common Event Adapter (CEA)

• z/OS Health Checker

• Predictive Failure Analysis (PFA)

• Runtime Diagnostics (RTD)

• Subsystem Initialization and Management


z/OSMF Agenda

• What is z/OS Management Facility (z/OSMF)

• New functionality in z/OSMF V2R2

– Integration into z/OS

– New way of configuration

– New z/OSMF look and feel (IBM „One UI“)

– Multiple Sysplex Support

– Configuration Assistant (CA), TCP/IP Stack Configuration


Overview• With z/OS V2R2, z/OSMF now

is part of the base operatingsystem.

• It provides support for a modern, Web-browser based management console for different z/OS functionality.

• It helps system programmers manage their z/OS environment by simplifying daily operations.

• z/OSMF is more than a graphical user interface. It isdesigned to maximize thesystem programmersproductivity:

• Automated tasks can helpreduce the learning curve andimprove productivity

• Embedded active userassistance through the use ofwizards provide guidance forthe tasks


z/OSMF: Base Services• Security integration with SAF (z/OSMF V1.13)

• ISPF Web UI (z/OSMF V1.13)

• REST API for Jobs (z/OSMF V1.13)

• REST API for Data Sets and Files (z/OSMF V2.1 with PTF UI16044)

• REST API for z/OSMF Information Retrieval (z/OSMF V2.1 with PTF UI90005)

• REST API for z/OSMF Systems (z/OSMF V2.1 with PTF for APAR PI32148)

• REST API for Software Management (z/OSMF V2.1 with PTF for APAR PI32158)

• REST API for z/OSMF Workflow (z/OSMF V2.1 with PTF for APAR PI32163)• Notifications (z/OSMF V2.1) View and act on the z/OSMF notifications that have been assigned to you• Use of WebSphere Liberty Profile (z/OSMF V2.1) faster startup, uses less resources• Workflow (z/OSMF V2.1) Perform a guided set of steps, for example, to configure components or

products in your installation. With PTF UI90005, A workflow step can use output from another workflow step; also a workflow step can be performed conditionally.

• Import Manager (z/OSMF V2.1 with PTF UI16044) Import plug-ins, event types, event handlers, and links into z/OSMF.

• System Setting - Discover the system definition that hosts the z/OSMF instance (z/OSMF V2.1 with PTF UI90005)


z/OSMF: Problem Management and Analysis

• Incident Log (z/OSMF V1.11) provides a consolidated list of SVC Dump related problems, along with details and diagnostic data captured with each incident. It also facilitates sending the data for further diagnostics.

• SDSF (z/OSMF V2.1 with PTF UI15294) provides a browser-based SDSF application designed to run in a z/OSMF environment that takes advantage of a graphical user interface.


z/OSMF: Configuration,and Performance• Configuration Assistant for z/OS Communications Server (z/OSMF V1.11) Simplified

configuration and setup of TCP/IP policy-based networking functions• WLM Policy Editor (z/OSMF V1.12) Simplified management of WLM service

definitions and policies. Facilitate the creation and editing of WLM service definitions, installation of WLM service definitions, and activation of WLM service policies

• Resource Monitoring (z/OSMF V1.12) Provides dynamic real time metrics for system performance

• Capacity Provisioning (z/OSMF V1.13) simplify the work of a z/OS CP administrator to manage connections to CPMs, view reports for domain status, active configuration and active policy.


z/OSMF: Installation, Migration, and Maintenance

• Software Management (z/OSMF V1.13) provides a simple, structured approach to deploying SMP/E installed software, In addition, it allows for inspection of a software instance to view the product, feature, FMID content, SYSMODS, as well as the physical datasets that comprise a particular software instance. It also enables you to perform actions to analyze and report on software instances (such as identifying installed products with an announced end of service date).


z/OSMF: The Application Stack

z/OS Components

• Communications Server IP• SAF• and others for specific plug-ins

Browser

z/OSMF Server

• WAS Liberty profile

•z/OSMF plug-ins

IBM 64-bit SDK for z/OSJava Technology Edition V7.1

HTTP(s)

• The z/OS Management Facility applications run on z/OS enabling you to manage z/OS from z/OS

– Information is presented on a PC using a browser• The z/OS Management Facility requires:

– z/OS Communications Server– Security definitions (SAF)– Other components are required for specific z/OSMF plug-ins– IBM 64-bit SDK for z/OS Java Technology Edition V7.1


Integration into zOS• z/OSMF is now part of z/OS!!!

– It is a base element of z/OS V2.2

– It’s documentation is part of z/OS

– e.g., migration actions are in z/OS Migration manual

– Comes as part of every z/OS order

– You no longer have to order it separately

– You can not remove it, or not install it

– You are NOT required to configure or start z/OSMF

– ServerPac delivers z/OSMF as part of the z/OS root file system using the directory of

/usr/lpp/zosmf

– VxRy is now removed.


z/OSMF V2R2 Configuration• Objective

– Configure z/OSMF like other z/OS functions – Eliminate the use of z/OS UNIX shellscripts to configure z/OSMF– Use PARMLIB to specify configuration parameters– Provide sample members for

– PARMLIB specification– Security definitions– Creation/migration of z/OS UNIX filesystem

– Utilize z/OSMF Workflows to provide a graphical interface, step the user through plug-in prerequisite configuration

– Planned 4Q2015*

– Documented in the IBM z/OS Management Facility Configuration Guide

V2.2 (SC27-8419)

– Additional documentation in DOC APAR PI46099

– The PTF will be installed in all z/OS V2.2 ServerPacs!!!

Enabled by PTF UI90027 (available August 5, 2015)


z/OSMF V2R2 Configuration

• Eliminate use of z/OS UNIX Shellscripts and REXX EXECs

– izumigrate.sh will still be used to assist in migration

• Eliminate the use of generated customized REXX EXECs for RACF

security definitions

– Eliminate configuration parameters only needed to customize security

definitions

• Eliminate the use of z/OS UNIX Shellscripts and generated customized

REXX EXECs to authorize users to use z/OSMF


z/OSMF V2R2 Configuration• Use PARMLIB to specify configuration parameters

– PARMLIB member IZUPRMxx contains remaining configuration parameters– Members can contain comments /* comment */– Members can use of system symbols– Member can be in any data set in the logical PARMLIB concatenation

– IZUPRMxx is optional.– Not needed if all defaults are used

– Sample PARMLIB member provided– SYS1.SAMPLIB(IZUPRM00)

– Tip: Specify values only for those defaults that you want to override (that is, omit any statement for which the default value is acceptable). – Doing so will ensure that you always obtain the default values, even if they

happen to change in a future release.• New parameter added to the IZUSVR1 started procedure to identify

PARMLIB member(s) to use– Concatenation of members is supported

– IZUPRM=‘(xx,yy,zz)’– Default is IZUPRM=NONE


z/OSMF Configuration – Sample Parmlib member IZUPRM00

Details: IBM z/OS Management Facility Configuration Guide (SC27-8419)


z/OSMF V2R2 – Security Definitions• SYS1.SAMPLIB(IZUxxSEC)

– IZUSEC – defines base (“Core”) z/OSMF security definitions– IZUCASEC – defines security definitions for Configuration Assistant– IZUCPSEC – defines security definitions for Capacity Provisioning– IZUDMSEC – defines security definitions for Software Management– IZUILSEC – defines security definitions for Incident Log– IZUISSEC – defines security definitions for ISPF– IZURMSEC – defines security definitions for Resource Monitoring– IZUWLSEC – defines security definitions for Workload Management

• SYS1.SAMPLIB(IZUAUTH) – security definitions to authorize a user to use z/OSMF

• There are no longer RACF REXXexecs, that have to be run.


z/OSMF V2R2 – Startup and Misc.• SYS1.SAMPLIB(IZUANG1 & IZUSVR1)

– Procedures that are supplied by IBM for server startup:– Please use IZUANG1 and IZUSVR1 from z/OS V2R2 SAMPLIB and do

not re-use V2R1 procedures to circumvent failures at startup time– Startup is the same as in V2R1

– Step1: S IZUANG1– Step 2: S IZUSVR1

• Misc:– /etc/zosmf is no longer used

– For some pre-check steps in configuration workflow, it is necessary toactivate RACF class SDSF and give users access to profileISFOPER.SYSTEM; ISFPRMxx settings do not help

• Maintenance is now included into regular z/OS maintenancestreams


z/OSMF V2R2 – Compliance with „One UI“ Standard• z/OSMF V2.2 now is compliant with IBM’s One UI standard

–IBM One UI standard delivers consistent user experience to IBM clients

• The UI style is has changed to be compliant with One UI standard.–Existing users will notice several changes:

–The colors scheme is black and white (links in blue)–The Welcome page has a Log in action to bring up a pop-up

window to enter user ID and password– Once logged on, the Log in action is replaced by a pull down to either:

– Log out– Switch User– Change Password

–New Help pull down identified by – The “About z/OSMF” function is a pull down action– Once logged on, “Help Contents” is the other pull down action


z/OSMF V2R2 Welcome Page

Log in Action

New Help Pull Down


z/OSMF V2R2 Log in Window

Secure authentication to z/OS host using regular z/OS User ID and

password.


z/OSMF V2R2 – Change Password Option


z/OSMF V2R2 Welcome Page after Logon

Pull down to:•Log Out•Switch User•Change Password

Help Contents now available

After logging on, you can click on What’s New to see new functions


z/OSMF V2R2 – What‘s New Page


z/OSMF V2R2 – Multiple Sysplex Support• Previously z/OSMF was single sysplex scope

– Some plug-ins have the capability to manage multiple sysplex– e.g., Resource Monitoring or Software Management

– It was also possible to have multiple z/OSMF instances within a sysplex( it is possible, but has some disadvantages)

• z/OSMF V2R2 supports managing multiple sysplexes from single z/OSMF– This framework enables managing multiple sysplexes from single user interface (one

z/OSMF tab in browser). – The first exploiter is Incident Log. You can now manage incidents from:

– multiple sysplexes (Group), or – multiple systems on a CEC, or – the existing multiple systems in a sysplex

Note: Software Management supported managing software instances residing in multiple sysplexes using one z/OSMF tab in a browser since z/OSMF V1.13

• Each sysplex must have at least one z/OSMF instance running– The z/OSMF instance which is connected by the user interface is known as “primary

z/OSMF”. – Other z/OSMF instances which are managed by “primary z/OSMF” are known as

“remote or secondary z/OSMF”.


z/OSMF V2R2 – Multiple Sysplex Support• The multiple sysplex support includes:

–z/OSMF Systems task is improved to be able to manage the topology information of systems, sysplex, CPC and group. – Supports graphic view of topology information and exporting the graphic

view. – Incident Log can now be invoked with a scope of a single sysplex,

single CEC, or specific group which is defined by user and could contain any systems.

–A “Topology REST interface” is provided for working with topology information such as groups, sysplexes through REST API invocation.

–A “Multisystem routing REST service” is provided for communicating with single remote system or group of remote systems.

–Single Sign On (SSO) can be set up to avoid the need to logon each remote/secondary z/OSMF when managing them from primary z/OSMF

• The z/OSMF Primary system must be z/OS V2.2–The remote/secondary systems can be z/OS V2.1 or z/OS V2.2


z/OSMF V2R2-Managing Multiple Sysplex Environments


z/OSMF V2R2 – Systems Task

• View topology by Sysplex, Group, or CPC


z/OSMF V2R2 – Systems Task

• Graphic view support (Systems on a CPC)

Export is supported


z/OSMF V2R2 – Incident Log Selection Options• The Incident Log task has been enhanced to provide multi-sysplex support,

which allows the user select the scope that they want to use (Group, CPC (CEC), or Sysplex)


z/OSMF V2R2 – Incident Log Aggregation■ Incident Log plugin now supports two modes in terms of the

managed scope: Basic-Proxy mode: Incident Log is opened on a single sysplex Aggregation mode: Incident Log is opened on a group which can contain

multiple sysplexes


z/OSMF V2R2 – Single Sign On• Single sign-on (SSO) enables users to log into one z/OSMF instance and to

access other z/OSMF instances without getting prompted to log in again. • z/OSMF uses the Lightweight Third Party Authentication (LTPA) security

protocol to enable a secure single sign-on environment among z/OSMF instances.– The LTPA protocol uses an LTPA token to authenticate a user with the

z/OSMF servers that are enabled for single sign-on.– The LTPA token contains information about the user and is encrypted using a

cryptographic key. – The z/OSMF servers pass the LTPA token to other z/OSMF servers through

cookies for web resources. – If the receiving server uses the same key as the primary z/OSMF server --

the server that generated the key to be used for SSO, the receiving server – decrypts the token to obtain the user information, – verifies that the token has not expired, and – confirms that the user ID exists in its user registry.

– After the receiving server validates the LTPA token, the server authenticates the user with that z/OSMF instance, and allows the user to access any resource to which the user is authorized.


z/OSMF V2R2 – Multisystem Routing REST Service■ Multisystem routing REST service is provided for communicating with single

system/group of systems via HTTP API invocation.■ Requires the target systems to be running■ Can be z/OS V2.1 or z/OS V2.2 systems

Operation HTTP Method

Retrieve data from one system, a list of systems or all the systems in a group

GET

Update data for one system, a list of systems or all the systems in a group

POST or PUT

Delete data from one system, a list of systems or all the systems in a group

DELETE

Authenticate with a secondary z/OSMF instance POST


z/OSMF V2R2 – Topology REST Service■ Topology REST service is provided for working with topology information

managed by z/OSMF via HTTP API invocation.

Operation HTTP MethodList the system defined to z/OSMF GET

List the groups defined to z/OSMF GET

List the systems included in a group GET

List the sysplexes defined to z/OSMF GET

List the systems included in a sysplex GET


z/OSMF V2R2 – Configuration Assistant, TCP/IP Stack• Configuration Assistant (CA) only supports configuration of z/OS CS

policy-based networking functions, such as IPSec, AT-TLS, and IDS.• While TCP/IP configuration is not that complex, some aspects are not

intuitive.• User must look through a lot of documentation.• Some statements are not easy to configure.


z/OSMF V2R2 – Configuration Assistant, TCP/IP Stack• z/OSMF V2.2 will provide a new

“TCP/IP” configuration perspective in the CA

• Support will be provided for both novice and more experiencedusers.

• CA will include integrated health checks for best practices configuration, including migration health checks for deprecated functions.

• The configuration model will support “levels of configuration” which include a sysplex level, image level, and a stack level with the goal to allow for configuration to be applied for grouping of stacks that require related configuration.

• CA will assist with “install” of the generated configuration files as it does with policy configuration.


Common Event Adapter Overview• CEA was first introduced with z/OS V1R9. It enables CIM providers to identify, receive,

and process selected z/OS events. These can be:– WTO, ENF.

– Program-initiated events.• CEA is a non-cancelable address space, that runs under z/OS. It is automatically started

during Master Scheduler initialization. Current exploiters for CEA are z/OSMF for its Incident Log task, and Base Control Program internal interface (BCPii) for event Processing.

• CEA has its own parmlib member, CEAPRMxx, and can modified through operator commands, like

– F CEA,D,PARMS


CEA Enhancement in z/OS V2R2

• CEA is enhanced to control TSO address spaces, that are programatically

launched.

– New keywords are added to CEAPRMxx parmlib member

– This enhancement controls the number of TSO sessions. It is used by the z/OSMF ISPF classic

interface.


Health Checker Oveview• IBM Health Checker for z/OS is a system component that identifies potential

problems before they impact your installation's availability or, in worst cases, would cause outages.

• Health Checker works in the context with other components like– Predictive Failure Analysis (PFA)– Runtime Diagnostics (RTD)– IBM zAware (IBM z Advanced Workload Analysis Reporter)

• These components are designed to circumvent problems in different ways.


New and updated Health Checks in z/OS V2R2• New and updated health checks in z/OS V2R2 apply to the following topics:

– Catalog,– Communication Server for z/OS– Component Trace (CTRACE),– Device Manager,– Hardware Accelerator Manager,– Integrated Cryptographic Support Facility for z/OS,– IOS,– JES2 and JES3,– PFA,– RACF,– System Symbols,– TSO/E,– UNIX System Services,– XCF,– zFS,– HTTP server migration.


Catalog related Health Check• (IBMCATALOG, CATALOG_ATTRIBUTE_CHECK): Looks for catalogs with

inconsistent share options


Hardware Accelerator related Health Check• (IBMHWAM, HWAM_ZEDC_DEVICE_AVAILIBILITY):

– This check looks at the current zEDC (zEnterprise Data Compression) device configurations.– The check gives an exception, if the available devices are in the same failure domain, or if fewer

devices than expected are available and active. This is to avoid single point of failures.


JES2 related Health Check• (IBMJES2, JES2_UPGRADE_CKPT_LEVEL_JES2):

– This check verifies the status of the JES2 $ACTIVATE level.– It is a renamed and updated version of the previous CHECK(IBMJES2,

JES2_Z11_UPGRADE_CK_JES2).– It issues exceptions if required pre-conditions are not met for upgrading to the new JES2 z22

checkpoint level. One example is, that the z22 mode requires EAV support (3390 extended address volumes).


PFA related Health Check• (IBMPFA, PFA_PRIVATE_STORAGE_EXHAUSTION):

– This check examines if there is a potential for private virtual storage to be exhausted by any address space in the future.

– It replaces an already removed slots and frames check.


RACF related Health Checks• (IBMRACF, RACF_CSFKEYS_ACTIVE)• (IBMRACF, RACF_CSFSERV_ACTIVE)• (IBMRACF, RACF_ENCRYPTION_ALGORITHM)• (IBMRACF, RACF_PASSWORD_CONTROLS)• (IBMRACF, RACF_RRSF_RESOURCES)• (IBMRACF, RACF_SENSITIVE_RESOURCES)


XCF related Health Checks• (IBMXCF, XCF_CF_SCM_UTILIZATION)• (IBMXCF, XCF_CF_STR_MAXSCM)• (IBMXCF, XCF_CF_STR_MAXSPACE)• (IBMXCF, XCF_CF_STR_SCM_UTILIZATION)• (IBMXCF, XCF_CF_STR_SCMMAXSIZE)• (IBMXCF, XCF_CF_STR_SCMMAXSIZE)• (IBMXCF, XCF_CF_STR_SCM_AUGMENTED)


HTTP Server Migration related Health Checks• (IBMZMIG, ZOSMIG_HTTP_SERVER_DOMINO_CHECK):

– This checks examines which HTTP server is in use, if you have one running in your system.– The “IBM HTTP Server Powered by Domino” is being removed in z/OS V2R2.– IBM recommends to migrate to the “IBM HTTP Server Powered by Apache”.– Please note that this check is not automatically shipped with z/OS V2R2 or any additional APAR.

Instead, you must download it from the following web site: – http://www-03.ibm.com/systems/z/os/zos/installation/HTTP_Health_Checker.html


Health Checker REXX Support for persistant data• z/OS V2R2 Health Checker provides REXX programming language support to

allow health checks to store and retrieve persistent data (saved across IPLs), as is already supported for checks written using High Level Assembler.

• This new function makes it easier to write health checks.• There are health checks from different sources:

– from individual IBM components, ISVs, and general users– each check is supposed to focus on one scenario only

• Health checks are named (CheckOwner, CheckName)


Overview of PFA• There are three general categories of software detected system failures:

– Masked failures: These are software detected system failures, which are detected and corrected by the software component

– Hard failures: This happens, when the software fails completely. An example is, when an operating kills a process

– Failures caused by abnormal behaviour: These are unexpected, or unusual situations which cause the software component to not provide the requested service.

• The idea behind Predictive Failure Analysis (PFA) is to predict potential problems, that might arise in your z/OS environment in the near future.

– These potential problems are not really hard failures, but rather soft failures, that can be categorized into four areas:

– Exhaustion of shared resources– Recurring failures caused by damage to critical control structures– Serialization problems such as classic deadlocks and priority inversions– Unexpected state transitions


Private Storage Exhaustion Check• In z/OS V2R2, Predictive Failure Analysis (PFA) monitors several ranges of

private area virtual storage for multiple address spaces and warns you when one or more address spaces exceed criteria that can indicate eventual private area virtual storage exhaustion.

• The PFA_PRIVATE_STORAGE_EXHAUSTION check detects future exhaustion of private storage under 2G in 6 storage locations within individual address spaces:

– Private user region – USER– Private authorized area – AUTH– Private user + private authorized – BELOW the line– Extended private user region – EUSER– Extended private authorized area – EAUTH– Extended private user + extended private authorized - ABOVE the line

• This check improves system availability by providing information you can use in advance of storage exhaustion, as long as the rate of storage consumption is not too rapid.


Overview of Runtime Diagnostics• Runtime Diagnostics (RTD) was originally introduced in z/OS V1R12.• It is also designed to analyze sick but not dead systems in a short time and it

looks for the evidence of soft failures.• You can use RTD to quickly analyze a sick system for the following kind of

problems:

– Component problems entitled as critical messages in OPERLOG

– ENQ, GRS latch contention for system address spaces, and z/OS UINX file system contention

– Address spaces using high CPU

– Address spaces that appear to be in a TCB enabled loop

– Local lock conditions

– JES2 health exceptions

– Server address space health exceptions


RTD Enhancement in z/OS V2R2• In z/OS V2R2 health based routing is an enhancement to WLM dynamic

workload routing. The focus here is further reducing impact due to middleware or transaction manager server health issues.

• WLM provides a health service called IWM4HLTH to enable multiple callers to report on a server’s health. The server will identify themselves and can provide reasons for their health ratings.

• The benefits for this new functionality are improved routing recommendations and diagnostic reporting about server health states.


Subsystem Initialization and Management• Prior to z/OS V2R2, when a new subsystem is defined to your z/OS, the

Subsystem name is reserved, regardless of whether it could be successfully initialized or not.

• If an error occurs, like at the INITRTN routine, you are not able to re-define the Subsystem, or create another Subsystem using the same name.

• Starting on z/OS V2R2, multiple changes were performed to allow you to deleteand re-define Subsystems.

• These new features are:– INITRTN pre-processing– SETSSI DELETE command– EVENTRTN exit routine– DISPLAY SSI command


SSI INITRTN pre-processing• When a Subsystem with INITRTN is defined, the z/OS Subsystem initialization

function checks if the INITRTN routine is installed in a library, and it is APF authorized.

• If any errors are found, an error message is displayed.


SETSSI DELETE• Prior to z/OS V2R2, subsystems defined to the z/OS could not be deleted by

regular commands.• With z/OS V2R2, a new SETSSI DELETE command is introduced to allow

logical deletion of Subsystems.• This is very useful to the ones in error allowing the installation to reuse the

Subsystem names.• The SETSSI DELETE has the following syntax:

– SETSSI DELETE,SUBNAME=I9N2,FORCE• There is a RACF security profile in class OPERCMDS to control access to

DELETE and ADD commands.• Attention: SETSSI DELETE is a “force” command. Removing an active

subsystem can have dangerous side effects. Use with care!


EVENTRTN Exit Routine

• In addition to initialization error handling, the new parameter named EVENTRTNcan be added to IEFSSI macro. This parameter informs the address of an exit routine

• The EVENTRTN option is only available for dynamic Subsystems, and they need to be defined through the IEFSSI macro and not by the console command SETSSI ADD.


DISPLAY SSI Command• the DISPLAY SSI command has been enhanced to display the Subsystem

name in hexadecimal, and any EVENTRTN associated with the Subsystem• The output from the DISPLAY SSI,ALL command is shown below:

ibm.com


< Performance>

z/OS V2R2 EnhancementsIBM Redbooks: SG24-8290-00 IBM z/OS V2R2: Performance


Topics Covered

• IBM Resource Measurement Facility (RMF)

• Workload Manager (WLM)

• Real Storage Management (RSM) Scalability

• RMF zFS Monitoring Enhancements


IBM Resource Measurement Facility (RMF)

• RMF Monitor III PCIe Support

• RMF Support for Large Pages

• GRS Usage Statistics in RMF Monitor III


RMF –PCIE Support

• Peripheral Component Interconnect Express (PCIe) is a high-speed serial

computer bus extension used internally in a computer for connecting its parts.

On a z13, a PCIe I/O Drawer contains several optional features connected to

processor units (at CPC Drawers) through PCIe buses:

– FICON Express 16S

– OSA Express 5S

– 10GbE Remote Direct Memory Access (RDMA) over Converged Ethernet Express (RoCE) is

a new communication protocol aimed at providing transparent acceleration for a sockets-based

TCP/IP applications and middle ware.

– zEnterprise Data Compression Express (zEDC), a fast data compression/deflation outbound

processor, then not producing MSUs. There is still the CPACF inbound coprocessor. z/OS

component in charge of data compression (CMF) should favored zEDC depending on algorithms.

– Flash Memory Express


RMF –PCIE Support

• z/OS V2R2, introduces RMF Monitor III PCIe Activity report and the

RMF Distributed Data Server (DDS) to provide online optional short-

term support for RoCE/ zEDC. (Previously SMF 74.9 via post –

processor)

• Set the PCIE option at ERBRMF04.

Move cursor to PFID and press enter to get more useful information


Monitoring zEDC performance

• This display provides much more useful info. Note that all the info only relates

to this LPAR’s use of the card (Covered in Day 2).


RMF – Support for Large Pages

• Large 1M pages improves E-DAT virtual translation, thus reducing CPU time.

– reside above the bar, are fixed, so no page outs, only to Flash.

• Shared pageable large pages allows large 1M pages in high virtual storage be

shared between address spaces.

• A Shared page is not a Common page.

– A Common page is shared among all address spaces.

– A Shared page is shared among specific address spaces. There are Shared pages between two

DB2 address spaces, such as: DDF and DBM1. Performance increase in cross memory.

• The size of shared area is defined by HVSHARE at IEASYSxx.

• Virtual storage above the bar is allocated in units of 1M called objects. Do not

confuse 1M page objects with 1M large pages.

• Updated Post-processor paging activity changes.



Paging Activity Report sample 1



Monitor III STORM Report Changes


RMF – GRS Usage Statistics in RMF Monitor III

• Information taken from the Monitor II session.

• RMF Monitor III introduces JOB Oriented Usage Report with job

oriented GRS statistics. It tracks how certain address spaces are calling

the GRS APIs macros (at QSCAN columns) to obtain the contention

status of resources, and requestor of those resources.

• Request the Monitor III USAGE Report by selection 1 from the Primary

Menu & selection 4A from the Overview Report Selection Menu or enter

command: USAGE [job_class, service_class] or USG


RMF – GRS Usage Statistics in RMF Monitor III

RMF Monitor III Job Orientated Usage Report

RMF V2R2 Job Oriented Usage

Samples: 60 System: TRX1 Date: 04/18/15 Time: 10.56.00 Range: 60 Sec

Service --- I/O --- --- CPU --- - Storage - ----- QScan ----Jobname CX Class Conn EXCP Total TCB Total Fixed Total Resct Time

XCFAS S SYSTEM 0.446 1.97 0.25 0.11 7754 2384 0 0.0 0BHBE T TSOCLASS 0.103 3.90 0.07 0.07 21 623 1 0.0 2581*MASTER* S SYSTEM 0.042 0.00 0.02 0.00 6323 1107 0 0.0 0SMF S SYSTEM 0.028 0.00 0.00 0.00 900 210 0 0.0 0CATALOG S SYSTEM 0.027 0.17 0.03 0.03 1824 228 0 0.0 0GRS S SYSTEM 0.020 0.00 0.01 0.01 14136 451 0 0.0 0JES2 S SYSSTC 0.010 0.38 0.03 0.02 9277 1041 0 0.0 0NET S SYSSTC 0.010 0.00 0.01 0.00 3050 138 0 0.0 0DFSZFS S SYSSTC 0.008 0.60 0.00 0.00 30660 499 0 0.0 0OMVS S SYSTEM 0.006 0.17 0.00 0.00 16098 356 0 0.0 0SMS S SYSSTC 0.004 0.93 0.00 0.00 548 89 0 0.0 0PAGENT SO SYSSTC 0.003 9.45 0.01 0.01 2978 18072 0 0.0 0HZSPROC SO SYSSTC 0.000 0.00 0.00 0.00 5125 183 0 0.0 0

Identify Top Resource Consumers at a Glance


Workload Manager (WLM)

• WLM Large Memory Enhancements

• IEAOPTxx parameters available to monitoring products

• WLM Buffer pool Management

• WLM Health Based Routing


WLM - Large Memory Enhancements

• IBM z13 may have up to 10 TB of memory, z/OS lpar up to 4 TB.

• Improve CPU cycles by avoiding I/O operations. WLM modifications can

improve the use of such memory.

• A page fixed in memory cannot be stolen.

• Fixing a large number of 1M large pages may cause a serious memory

availability problem to z/OS. Those pages cannot be stolen if there is a

“pageable memory shortage” state. In this state, SRM:

– Rejects new AS creation by denying START, LOGON and MOUNT commands

– Avoid Job selection by initiators

– Swaps out the swappable AS with the greatest number of fixed pages.



WLM changes in z/OS V2R2 changes how some IEAOPTxx PARMLIB keywords

are processed in relation to levels of page fixing. They indicate when a pageable

memory shortage is to occur.

• MCCFXTPR=xxx Percent of online storage that might be fixed.

• RCCFXTT= (aaa,bbb) | AUTO Low and high thresholds of total fixed memory

• RCCFXET= (aaa,bbb) | AUTO Low and high thresholds of fixed memory < 16M



MCCFXTPR=xxx - Percentage of fixed memory.

Default of 80% requires that 20% of memory remain not fixed.

With large memory, 80% may cause a “pageable storage shortage” state, when there is plenty of

pageable memory.

In z/OS 2.2, the required pageable storage threshold for large memory LPs (larger than 320 GB) is

always equal to 64 GB. This allows to fix much more memory without running into a pageable storage

shortage state.1 TB800 GB

80%



• RCCFXTT=(xxxxx,yyyyy) – Low/high threshold % fixed memory. Used by SRM

to determine if MPL should increase or decrease. Defaults are 66% and 72%,

for small memory there is not a problem. On, 1TB LP, for example, when 660

GB of storage is fixed, memory is not longer under pressure and SRM stops

decreasing MPL. In z/OS V2R2 SRM calculates optimal RCCFXTT lower and

upper thresholds, if installation defines RCCFXTT=AUTO.

• RCCFXET=(xxxxx,yyyyy)- Low/high threshold % fixed memory below 16M. The

same idea, but for page fixing below 16 M line. Use RCCEXTT=AUTO, as well.

• Check out OA44688 for rollback to z/OS V2R1


WLM - IEAOPTxx parameters available to monitoring products

• Performance monitors such as RMF and Omegamon, in releases prior

to z/OS V2R2, use their own software interface to externalize the

IEAOPTxx parameters in the user screens and reports.

• z/OS V2R2, WLM does provide a new WLM Service IWM4OPTQ to

make IEAOPTxx parameters available to z/OS monitoring products


WLM - Buffer pool Management

• Buffer pools are used as a cache to help avoid I/O.

• WLM buffer pool Management goal in DB2 is to keep application data

available in memory and eliminate physical I/Os, reducing CPU

consumption and transaction response.

• WLM helps DB2 by deciding dynamically the amount of buffers per

buffer pool.

• This capability is activated for each DB2 buffer pool, by the ALTER

buffer pool command with the AUTOSIZE option set to YES.



• WLM buffer pool management process

Enclave Database Manager

Program--------------------------------

ApplicationTask

AccessMethod

Buffer Pool

Buffer PoolManager

DataCollect

Exit

AdjustExit

DASD

AdjustAlgorithmsSampling

Performance Block

BPMgmtOnlyPerformance Block

A.

B.

C. D.

WLM/SRMWLM gathering performance data to recignize whether a Buffer Pool size

chage is necessary



• Buffer pool size variation



• Prior to z/OS V2R1, WLM-managed DB2 buffer pools were rarely

shrunk.

• In z/OS V2.R1 a Housekeeping function was added to shrink buffer

pools when their usage and/or misses slow down. However, that version

of the Housekeeping function did not consequently consider the

importance of the SCP transactions that were using the buffer pool.



• The new z/OS V2R2 implementation works as follows:When the

command is issued: ALTER BUFFERPOOL [VPSIZE(s)]

AUTOSIZE(YES)

– DB2 registers the bufferpool to WLM

– MIN size = 0.75 x VPSIZE

– MAX size = 1.25 x VPSIZE

– Initial USED size between MIN size and MAX size, the size tha is actually used by DB2

when the buffer pol is registered

• WLM recommends to:

– Grow the size of the bufferpool when the Performance Index of a SCP is impacted and

buffer pool delays are a significant contributor. WLM grows the size of the buffer pool

up to at most MAX size.



• Shrink the size of the buffer pool:

– Due to memory donation to a suffering SCP

– Due to regular housekeeping cycles. Refer to Housekeeping function improvement for

more details.

• WLM shrinks the size of the bufferpool down to:

– Initial USED size during regular housekeeping

– MIN size if memory donation to a suffering SCP is needed, when system is memory

constraint.

• DB2 decides about how much of that recommended size it actually

uses, based on its own algorithms:

– The used (by DB2) size of a buffer pool can be below its WLM recommended size

– DB2 “getmains” up to the used size, not up to the recommended size.



• When the command is issued: ALTER BUFFERPOOL AUTOSIZE(NO)

– DB2 de-registers the bufferpool from WLM management:

– Size of buffer pool doesn't change and DB2 keeps the last recommended bufferpool

size. Will also be the new VPSIZE for reallocation.


WLM - Health Based Routing• Objective of WLM Dynamic Routing Services is to dynamically balance the load

among servers. This balancing is good for:

• Capacity – Route work according to capacity available

• Performance – WLM goal attainment due to:

– Less queue time

– Less PU time due to less transaction concurrency

– Less Transaction Manager overhead.

• Availability – Avoid shortages

• Reliability – Avoid not healthy servers to be routed.

These exploiters ask for guidance where to run on servers, arrival transaction,

online sessions and network connection ports. WLM responds with Weights.

Weight = Available LP Capacity Factor * PI Factor * Enclaves_Queue_Time_

Ratio * Health_Factor


WLM - Health Based Routing

• Dynamic Routing Services

Client

Client

Client

Client

Client

RoutingManager

Server

Server

Server

ServerWLM

Dynamic Workload Balancing

Server here means a z/OS or an specific Address Space within z/OS.Routing Manager is any Transaction Manager.


WLM - Health Based Routing• In z/OS V2R2, the notion of finger-pointing is introduced, which allows multiple

internal and external components to report on the health of a server.

– To keep track of different health values (for example, reported by XCF/XES and the server himself)

– The algorithm for determining the health indicator for an address space is changed. The health

indicator is the minimum value of all the current settings from the different callers of the service

since the last RESET. This changes the current operation where the server's health indicator is

simply the last value being reported.

– An additional function of IWM4HLTH refers to RAS considerations regarding a server's health state.

The RESET function restarts setting of a composite health value by specifying an initial value and

discarding the values reported by other callers before.

– Callers can identify themselves by a subsystem type and subsystem name. WLM uses these

parameters to recognize different callers of the service. If no subsystem type is passed, the job

name of the caller address space is used instead


WLM - Health Based Routing– Callers can specify the reason or cause of change of the health indicator

– Users of this service need to check their programs for sufficient program authorization

A Transaction Manager uses IWM4SRSC service to request a routing recommendation WLM returns a list of servers and weights (numbers between 1 and 64).The Transaction Manager (exploiter) can use the weights to distribute incoming work.

Server A

SYS 1

IWMSRSRS

SYS1: avail. CapacitiesSYS2: avail. CapacitiesSYS3: avail. Capacities

Server AServer BServer C

SYS 2

Server B


SYS 3

Server C


Server System Weight

A SYS 1 50

B SYS 2 30

C SYS 3 20

50%RoutingManager

30%

20%

Use of WLM Weights by a Transaction Manager


Real Storage Management (RSM) Scalability

• Large memory performance gains

• Four steps to improve performance

• Large memory study

• Dumping considerations

• Modify the LFAREA INCLUDE1MACF(YES)


RSM - Large memory performance gainsLarge memories can improve performance due to:

• Substantial latency (delay) reduction for OLTP workloads implying in significant

response time reductions and increased transaction rates.

• In-memory databases have dramatic gains in response time by avoiding

synchronous IO waits.

• Batch window reduction. Less queue time and consequently shorter elapsed

times for Jobs.

• Reduced time to insight for analytic workloads:

– Processes data more efficiently helping organizations keep pace with influx of data

– Reduces time it takes to get from raw data to business insight.


RSM - Four steps to improve performance

• Step 1: Page fix DB2 buffer pools at current number of

buffers.

• Step 2: Deploy 1M large pages for page fixed DB2 buffers

• Step 3: Deploy pageable shared 1M pages

• Step 4: Increase size of DB2 local buffer pools to up to

100GB.


RSM – Large Memory Study

• Significant performance improvements were seen when more memory

was used for larger DB2 buffer pools while running the SAP Banking

Services (SBS) Day Posting workload on an IBM zEnterprise EC12.

• A customer representative financial services workload with memory

intensive, large number of DB2 tables, and random I/O behavior. Test

Scenarios:

– DB2 11 Single System

– 256 GB / 512 GB / 1024 GB real storage. Start with 256 GB real storage

– DB2 V11 Single System – minimal # of BPs


RSM – Large Memory Study


RSM – Dumping ConsiderationsRSM was modified internally to increase concurrency of tasks:

• Multiple page faults are processed concurrently within AS or with common storage

• Page fixing and unfixing can occur concurrently within an AS or with common storage

• Getmain/Freemain of storage can occur concurrently with page fixing/freeing and page faults

• Less contention on available frame queues.

RSM introduces following new functions:

• Dumping Large Memory via Stand Alone utility program

• Initialization of memory is more efficient – running disabled (Ref OA44207)

• CF STOR,OFFLINE and D MATRIX more efficient (OA44207)

• Frame steal processing more efficient in scanning PFTEs by skipping over certain areas that

are not eligible for steal processing.


RSM – Dumping Considerations• As applications use more virtual memory, dumps become larger causing several

times an unplanned IPL due to exhaustion of real memory and page data sets.

• Perhaps avoid dumping common area

On z/OS V2R2 there is a new option REAL parameter for Standalone Dump:

• Default of REAL=ALL dumps all real storage

• REAL=USED dumps only used real storage skipping any unused real frames.

• Can be set with REAL=USED at generation of ADSADMP or at runtime with

SET REAL(USED)


RSM – Modify the LFAREA INCLUDE1MACF(YES)• At z/OS V2R2 the option INCLUDE1MAFC at LFAREA keyword at IEASYSxx

has a default equal to YES.

• This option includes in the Available Frame Count, the 1 MB set of contiguous 4

KB frames in the available queue.

• The option NO may result in significant paging stealing (due to the lack of 4 KB

available frames),even when there is an abundance of 4 KB frames grouped in

chunks of 1M available in the memory.


zFS Monitoring Enhancements• In z/OS V2R2 new RMF Monitor III Sysplex reports are provided with detailed

and aggregated zFS data for various aspects of zFS performance analysis.

– ZFSOVW provides wait and cache statistics.

– ZFSFS shows file system statistics.

– ZFSKN comes up with zFS kernel statistics.

– RMF utilizes new zFS APIs to gather zFS performance data.


zFS Monitoring Enhancements

/*****************************************************************************************************//* NAME: ERBRMF04 *//* DESCRIPTION: PARMLIB MEMBER WITH RMF MONITOR III GATHERER OPTIONS *//* (ALL OPTIONS ARE SET TO DEFAULTS) … *//*****************************************************************************************************/

CYCLE(1000) /* SAMPLE EVERY SECOND (1000 MSEC) */DATASET(STOP) /* NO DATASET SUPPORT */DATASET(NOSWITCH) /* APPEND TO LAST NON-FULL DATASET */DATASET(WHOLD(7)) /* CONTROLS BUFFER PAGES IN STORAGE */

...VSAMRLS /* ACTIVATE VSAM RLS GATHERING */OPD /* ACTIVATE OMVS PROCESS DATA GATHERING */PCIE /* ACTIVATE PCIE DATA GATHERING */SCM /* ACTIVATE SCM DATA GATHERING */ZFS /* ACTIVATE ZFS DATA GATHERING */

NOSGSPACE /* NO STORAGE GROUP SPACE GATHERING */NOLOCK /* NO LOCK DATA GATHERING */

Set up zFS data collection


zFS Monitoring Enhancements

To displays the RMF Sysplex Report Selection Menu select S from the RMF Monitor III Primary Menu.

To request the Monitor III ZFSOVW, ZFSFS and ZFSKN reports select option 13, 14 or 15.

As an alternative, enter one of these commands:ZFSOVW or ZFO zFS OverviewZFSFS or ZFF zFS FileSystemZFSKN or ZFK. zFS Kernel


zFS Monitoring Enhancements• ZFSOVW Report

– Summary of wait percentages and caches statistics in the current sysplex

– Useful for discovering bottlenecks and tuning cache behavior

Sensitive fields for pop up menus


zFS Monitoring Enhancements• ZFSOVW pop up reports


zFS Monitoring Enhancements• ZFSFS Report


zFS Monitoring Enhancements• ZFSKN Report