MAINFRAME: What's New with VMAX for Mainframe? · MAINFRAME: What's New with VMAX for Mainframe?...

MAINFRAME: What's New with VMAX for Mainframe?

Bruce Klenk & Justin Bastin

© Copyright 2017 Dell Inc.2

Topics• What’s new with VMAX All Flash for Mainframe

• What’s new in HYPERMAX for Mainframe

• Newest Features in Mainframe Enablers (MFE) 8.2– SECURE Snapshots– TimeFinder SnapVX

• What is new with the latest Hypermax– Data Protector for z Systems (zDP) Enhancements– SMF Enhancements– EAV– Dynamic Volume Expansion


VMAX: The mainframe of storage!

CONSISTENCY TECHNOLOGY

SUB-CONTROLLER FAULT ISOLATION

Mission CriticalAvailability

PARALLEL NDU

Data Protector for z Systems (zDP)

NON DISRUPTIVE UPGRADES

>99.9999%*

*Using SRDF/S replication

D@RE

T10 DIF+

Mirrored Writes; ongoing cache integrity checks, nonvolatile NVMe power loss protection

Protection

Multi-siteReplication, Automated failover

DATA AT REST ENCRYPTION

END-TO-END DATA INTEGRITY

Effortless

Advanced error detection

Advanced cache protectionDeployed in more mission critical

environments than any other storage platform

VMAX Platform Update


VMAX 450F/FXVMAX 850F/FX

Same HYPERMAX operating system for all VMAX All Flash systems

VMAX All Flash family expands!

Q2-17

VMAX 950F/FX

1-4 zBricks, 2 racks8 Core Ivy Bridge CPUs

6Gb/s SAS back end120 Drive DAE/960 Max

1-8 zBricks 4 racks12 Core Ivy Bridge CPUs

6Gb/s SAS back end120 Drive DAE/1,920 Max

1-8 zBricks 4 racks18 Core Broadwell CPUs

6Gb/s SAS back end120 Drive DAE/1,920 Max


VMAX & VMAX 950F for mainframes

ConsolidationOpen systems and Mainframes

zDP Data ProtectionImproved monitoring, reporting, resiliency

ScaleUp to 1.7PB usable Starts at 13TB usable

Z Systems SynergyzHPF Extended Distance IIDynamic Volume Expansion, 1TB EAVs

Performance50% more CPU coresUp to 40% response time improvement

PerformanceFlashboost supportImproved FICON emulation

New 950F New in HYPERMAX


VMAX All Flash engines850F

Ivy Bridge 12 Core CPU

Up to 8 Engines per System

Up to 384 CPU Cores per System

Up to 16 TB Cache per System

Up to 256 FICON Ports per System

6 Gb/s SAS Backend, Dual IB FDR 56 Gb/s Matrix, PCIe Gen3 I/O Slots

450F

Ivy Bridge 8 Core CPU





950F

Broadwell 18 Core CPU






950zF/zFX Directors

• 2x 18-core 2.3GHz Broadwell CPUs– 72 cores per zBrick

• 512GB or 1TB cache– Up to 2TB per zBrick– DDR4 memory

• 2x 6Gb SAS I/O modules

• 1x Compression I/O modules

• 3x Host & SRDF I/O modules


Chassis• 4U Enclosure• Supports 2 CPU Modules• Each Director board has its own redundant Power &

Cooling• 33” D x 7” H x 17.5” W

CPU Module• Dual socket, Up to 145W Broadwell EP CPUs

I/O Module• Supports 11 I/O Slots per Director

Front View

Rear View

950zF Engines


Highly efficient data center

• High Capacity SSDs- 960 GB 2.5”- 1.92 TB 2.5”- 3.84 TB 2.5”- 7.68 TB 2.5”- 15.36 TB 2.5”

DENSE DAEs- 120 Drive Slots - 4RU Deep Rack

11


Protocol Connectivity/Speed 450F/850F 950F

FC4 x 16Gb FC/SRDF 4 x 8Gb FC/SRDF

FICON 4 X 16Gb FICON

Ethernet

4 x 10GbE iSCSI/SRDF 2 x 10GbE iSCSI/SRDF N/A2 x GbE Cu/2GbE Opt SRDF

eNAS

2 x 10Gbe Opt eNAS 2 x 10GbE Cu eNAS 4 x GbE Cu eNAS N/A4 x 8Gb FC Tape BU eNAS

I/O Modules by platform & protocol


VMAX All Flash tech refresh example

VMAX 20K 9 BAY

VMAX ALL FLASHSINGLE BAY

10X MOREPERFORMANCE

40% LOWERTCO

87% LESSENERGY

92% LESSFOOTPRINT

98% FEWER DRIVEREPLACEMENTS


950F for mainframe-only workloads

zCapacity Pack13 TBu


SCALE-OUT

SCALE

UP

zBrickEng + 13TBu




zCapacity Pack13 TBuBEST DENSITY FOR MAINFRAME

EASY TO PLAN, DEPLOY, MANAGE

zBrickEng + 13TBu

zBrickEng + 13TBu

zF Suite:• HyperMax OS & Embedded

management• Local replication• Mainframe Essentials

zF Options• Remote Replication*• Unisphere 360• D@RE• zDP• AutoSwap• GDDR• Mainframe Essentials Plus

zFX Suite: zF Suite plus• Unisphere 360• D@RE• zDP• AutoSwap• Remote Replication (SRDF

/S/A/STAR*)

zFX Options• GDDR• Mainframe Essentials Plus• Use of SRDF/STAR requires GDDR

• 13 TB zBrick requires R5 (7+1)


950F maximum system configuration(Two-engine system bay)

System Bay 2

System Bay 1

System Bay 3

System Bay 4


More flexible deploymentAgile system bay dispersion

25UP TO

METERSAPART

• Hot aisle / cold aisle cooling• Overhead cabling option• 3rd Party racking option


System power options

• 3-phase delta – most common– 2 drops/ bay

• 3-phase wye – 2 drops/bay

• Single-phase – Up to 6 drops/bay

• 2200W SPS


Vault to flash

Before• Reduced Environmental Cost• Smaller Li-Ion SPS in every cabinet only

powers the directors• Can have more drives per cabinet• More usable capacity per raw TB

• Reduced space and weight• Fewer cabs per TBu

• Improved performance and Usability• Larger memory space that can be saved

within 5 minutes• Simplified configuration

After

Vault toFlash


amodulevegetationwant to protect mythe small dog jumped over thetechnology allows for futureplants are able to retain morelong-term planning for majorindefinite retention terms mayspider bites may cause variousswimming under those conditionslarger capacity flash drivessecurity directiveinformationpersonalto

VMAX D@RE enabled

• Encrypts all user data on the array• Including vault drives

• All VMAX data services supported• No compromises

• Advanced Encryption Standard• AES 256

• Secure keys• Generation and deletion

• FIPS-140-2 validation (#2479, #2871)• New External Key Manager Support

including IBM SKLM!


World’s most trusted storage platform

No Encryption

I/Os per second

Res

pons

e tim

e (m

s)

0

0.4

0.8

1.2

0 20,000 40,000 60,000 80,000 100,000

No Encryption

With Encryption (D@RE)

No Performance Impact

700+ VMAX All Flash arrays sold with Encryption

Trusted by customers in Financial, Healthcare, Government Sectors to name a few


VMAX All Flash: true NDUUnique in the Industry

• < 10 seconds to upgrade array OS (FAST IML)

• No component downtime for an HYPERMAX NDU

• No rolling outage upgrade

• No Failover or Failback processes involved

• For mixed Mainframe/Open boxes, no switching LUN ownership (trespass) required

* Average cost of downtime via Enterprise Management Associates

DOWNTIME COST

$1.8 millionper day

$45,000 per hour

$750 per minute

“Thank you VMAX for giving me back my weekends”

“VMAX NDU is the gold standard for upgrades”

“Nobody knows its happening, It just works”


VMAX All Flash – mission critical availabilityThe mainframe of storage

• Redundancy at every level in the system– Active-Active controllers, RAID, Power, Battery Backups,

dual ported SSD’s, IB switches, DAE’s, management modules

• Advanced cache protection– Mirrored Writes; ongoing cache integrity checks, NVMe

power loss protection

• Advanced error detection– T10DIF+ and CRC coding to protect from data, control faults

• Preemptive event driver– Prioritized processes; optimize error handling and host IO

over internal processes

Deployed in more mission critical

environments than any other storage platform

https://www.emc.com/collateral/technical-documentation/h13807-emc-vmax3-reliability-availability-and-serviceability-tech-note.pdf

https://www.emc.com/collateral/technical-documentation/h13807-emc-vmax3-reliability-availability-and-serviceability-tech-note.pdf

VMAX Software Update


VMAX z Systems synergy• NEW:

– 1 TB EAV– Dynamic Volume Expansion– zHPF Extended Distance II– D@RE external key manager support - IBM

SKLM (Secure key Lifecycle Manager) & Gemalto

• Enhanced zHPF support– List Prefetch– Format Writes– Bi-Directional transfers– BSAM/QSAM support

• Query Host Access (ICKDSF VERIFY OFFLINE)

• z13 FICON Enhancements:

– FICON Dynamic Routing– 32K devices per FICON

channel– Forward Error Correction

Codes– Read Diagnostics

Parameters

• zHyperWrite

• zFBA support

• PPRC SoftFence

• Non-disruptive state save

EMC makes no representation and undertakes no obligations with regard to product planning information, anticipated product characteristics, performance specifications, or anticipated release dates (collectively, “Roadmap Information”). Roadmap Information is provided by EMC as an accommodation to the recipient solely for purposes of discussion and without intending to be bound thereby.


VMAX software enhancements

• FICON Performance improvements

• FLASHBOOST for CKD– Implements Optimized Read Miss in the FICON emulation (EF) to significantly improve throughput and

lower latency for Random Read Miss (RRM) workloads directed at flash drives

• zDP Enhancements – Monitor the RDP cache usage and issue messages and take user specified actions when thresholds

are reached– Provide SMF records for data in zDP query commands, including RDP space consumption information– Provide an option to Terminate Snapsets

• Secure Snaps– Customers who need to protect their snapshot data from deletion or data corruption (intentional or

unintentional) – Supports an Isolated Recovery Solution

VMAX software enhancement details


Software enhancement details

• Newest Features in Mainframe Enablers (MFE) 8.2– Secure Snapshots– TimeFinder SnapVX

• What is new with the latest Hypermax– Data Protector for z Systems (zDP) Enhancements– SMF Enhancements– EAV– Dynamic Volume Expansion

Secure snapshots


Secure snapshots

Overview

• Prevents a snapshot from being deleted by anyone– Think of it as a “Time-To-Must-Live”

• Why provide this feature? – Intentional or unintentional data loss

• Requires supported versions of HYPERMAX OS / SE /UVMAX / MFE

• Supported for both FBA and CKD devices

• Only applies to native SnapVX targetless snapshots– Not applicable to SnapVX Linked Targets– Not applicable to Emulation modes (Clone, Mirror, VP Snap)


Secure snapshots

Overview

• Care must be taken when implementing this feature!

• No user will be allowed to reduce or remove the Retention Time

• Secure Snapshots cannot be terminated to free-up SRP capacity

• Users may want to consider how to implement– Specific points-in-time– Specific number per day– etc...

• All other SnapVX operations are allowed:– Link / Relink / Unlink– Restore / Terminate restored– Set mode


Secure snapshots

Overview

• Retention Time can be extended but not reduced

• Standard Snapshot can be converted to Secure Snapshot– Not vice versa

• When the Retention Time expires:– If the snapshot has no linked targets or restore sessions it will be automatically terminated– If the snapshot has linked targets it will be automatically terminated when the targets are

unlinked– If the snapshot has a restore session it will be automatically terminated when the restore

session is terminated


Creating secure snapshots

• Accomplish in Solutions Enabler

• Accomplish in SnapVX ACTIVATE command

• Accomplish in Unisphere


Secure snapshots

Solutions Enabler

• symsnapvx -sg <sg> -name <snapshot_name> establish –Secure <-delta | absolute>– Create Secure snapshot

• symsnapvx -sg <sg> -snapshot_name <snapshot_name> set Secure <-delta | absolute>– Convert existing snapshot to Secure

• symsnapvx –sid ## list– List only Secure snapshots


Secure snapshots

TimeFinder SnapVX JCL

• ACTIVATE (CONSISTENT(YES) Secure(YES) EXPI(1))– Secure attribute associated to snapshot

• CONFIG (TARGET(UNIT(####)) NAME(‘<name>’) Secure(YES) EXPI(1))– Convert existing snapshot to Secure


Secure snapshots

• MULTI_LINE(YES) option enhanced

• New security checks added

• CONFIG command – Provides ability to change snapshot from not being Secured to Secure– Allows customer to add time to live parameter via the EXPI (expiration)


Secure snapshots

Unisphere for VMAX


Secure snapshots

From z/OS

SRC CUU VOLSER TGT CUU VOLSER NAME -----------------------------------------------------------------------000001FE(N/A ) *5496* FFFFFFFF(N/A ) SNAP_MF_Unisphere

UNIQUE TRACKS: 0000000000 SRC MODIFIED TRACKS (UNIQUE+SHARED): 0000000000 TGT MODIFIED TRACKS (UNIQUE+SHARED): 0000000000 TRACKS TO BE COPIED: 0000000000 TIME TO LIVE DDDD/HH:MM:SS: 0000/03:59:04 TIME SINCE CREATION DDDD/HH:MM:SS: 0000/00:00:55 SNAPSHOT ID: ADAD0001 Secure SNAPSHOT: YES

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


Unisphere showing secure• Source volume of snapshot must be in Storage Group!

• I created Secure snapshot in z/OS

TimeFinder SnapVX


SnapVX new options

• GA as of February 27th, 2017 via the MFE 8.1 Fixes package

• A new FREE command added to SnapVX UNLINK command– FREE command locks target devices.

• Enables customers to free the in memory track pointers on the target volume

• If an allocation on the target device – is unique, the FREE command will free all allocations– If shared, FREE will command not free space until all allocations are terminated

• A snapshot will only free tracks once the snapshot is terminated


SnapVX new options – FREE(YES) example• Below shows linking snapshot to target volume in NOCOPY mode

GLOBAL CONDITIONVOL(ALL) COPYVOLID(NO) REUSE(NO) REPLACE(YES) GLOBAL CHKO(NO ) REFVTOC(NO) GLOBAL MODE(NOCOPY) WAITFORCOMPLETION(YES,MSG) * LINK SNAPSHOT (NAME(SNAP_CKB100_TEST) -

SOURCE(UNIT(B100)) -TARGET(UNIT(B104)) -NEWVOLID(CKB104) -VARY_ONLINE(YES) -)

QUERY SNAPSHOT (UNIT(B100) CUU(B100) MULTI_LINE(YES)) QUERY SNAPSHOT (UNIT(B100) CUU(B100) MULTI_LINE(NO))

- Enter "/" to select action Message Volume -----------------------------------------------------------------------JBASTI1.TESTK3 CKB104 JBASTI1.TEST1 CKB104 JBASTI1.TEST2 CKB104 SYS1.VTOCIX.CKB104 CKB104 ********************* End of Data Set list ****************************


SnapVX new options - NOCOPY• Below shows unlink command with FREE(YES) – default is NO

• Output from UNLINK job has one statement extra for the FREE

• NEW: ESNP1J0I SETTING WAIT_FOR_DEFINITION(NO) DUE TO FREE(YES) PARM

//QCINPUT DD * UNLINK (TARGET(SYMDV#(28)) FREE(YES) LOCAL(UNIT(B50E))) QUERY SNAPSHOT (UNIT(B50E) CUU(B100-B107) ) QUERY SNAPSHOT (UNIT(B50E) CUU(B100-B107) MULTI_LINE(YES)) /*

Menu RefList RefMode Utilities Help ------------------------------------------------------------------------------

Data Set List Utility VTOC error Option ===>

blank Display data set list P Print data set list V Display VTOC information PV Print VTOC information

Enter one or both of the parameters below: Dsname Level . . . Volume serial . . CKB104

Data Protector for z Systems (zDP) enhancements


In a nut shell

• zDP provided updates to zDP ISPF Panels

• Replication Data Point (RDP) cache utilization notification– RDP – the subset of total cache that is for local replication

• Set and collect SMF records specific to zDP

• TERMINATE command enhanced to terminate a range of snapshots

• Automatically Terminate Invalid snapsets

• Automatically retry for snapshot errors


zDP ISPF panel additions

• In MFE SAMPLIB(EIPCLIST)

• New RACF controls exist

• EIP_RACF_SMF

• EIP_RACF_TERM_RANGE

• EIP_RACF_ECACLEAR

SCF_SUFFIX = "EMC" SCF_JOBNAME = "MFESCF82" UNIT = "3390" VOLUME = '' EIP_RACF_START = "EMC.ADMIN.CMD.ZDP.START" EIP_RACF_STOP = "EMC.ADMIN.CMD.ZDP.STOP" EIP_RACF_RELDLOCK = "EMC.ADMIN.CMD.ZDP.RELDLOCK" EIP_RACF_PAUSE = "EMC.ADMIN.CMD.ZDP.PAUSE" EIP_RACF_RESUME = "EMC.ADMIN.CMD.ZDP.RESUME" EIP_RACF_SMF = "EMC.ADMIN.CMD.ZDP.MODIFY" EIP_RACF_TERM_RANGE = "EMC.ADMIN.CMD.ZDP.TERMINATE.RANGE" EIP_RACF_ECACLEAR = "EMC.ADMIN.CMD.ZDP.ECACLEAR" EIP_LOAD_LIBRARY = "'JBASTI1.PD10.SSCF820B.LINKLIB'"


New options in ‘CV’ -> ‘CR’Specify Versioned Data Group Parameters Command=> Scroll=> CSR

VDG Name . . . _______________ Consistent . . Yes _ or No _ Cycle Time . . ____ , ______ Cycle OverFlow Immed _ or Next _ Debug ..Statuse _ Log Opt DDname ________ Max Snapsets .. ___ MaxRC . . . . __ Preserve Limit. ___ Saved Snapsets ___ , ____ SRP Warn . . . ___ SRP Term ___ SRP Snap ___ RDP Cache Util ___ , ___ Timeout . . . ___ Cont _ Stop _ Term Policy . . Oldest _ Stop _

SMF rec number ___ TRACKS . . . . _

********************* Primary Commands: EDit SAve PRomote **************************************************** Bottom of data ********************************

• RDP Cache Util (ww,cc) – default (60,95)– ww is at what % the warning messages begin– cc is at what % the critical messages begin

• SMF Rec Number – Specify SMF record number to be used

• TRACKS - will return the total Changed and Unique track counts for the devices defined in each VDG VMAX.


Terminate command • Once in the zDP ISPF panels, customers would select

– ‘1 Query’ – tab to VDG and ‘S’ -> tab to device and ‘S’ -> select ‘TR’– Notice the ‘Simulate is defaulted to ‘N’’ +------- Terminate a range of snapsets -------

| | From date 02 / 22 / 17 18 : 00 | | To date 02 / 22 / 17 20 : 00 | | Format mm / dd / yy hh : mm | | | | Simulate Y (Y=Yes/N=No) | | +---------------------------------------------

EIP0001I *** EMC zDP - V8.2.0.(000) - SCF V8.1.0 (000) ***

EMCP001I TERMINATE VDG(TESTVDG1),DATE(170531800-170532000),SIM EIP0090I SIMULATE mode, no Snapsets will be terminated EIP0050I SYMM B10F/0001967-01505, Terminating SNAPSET TESTVDG1.......170531801C00022EIP0002I All control statements processed, highest RC 00


Terminate command • Once in the zDP ISPF panels, customers would select

– ‘1 Query’ – tab to VDG and ‘S’ -> tab to device and ‘S’ -> select ‘TR’– Notice the ‘Simulate is defaulted to ‘N’’– Create snapsets and tried the following

Confirmation

+------- Terminate a range of snapsets -------+| || From date __ / __ / __ __ : __ || || To date __ / __ / __ __ : __ || || Format mm / dd / yy hh : mm || || || || Simulate N (Y=Yes/N=No) || || |+---------------------------------------------+

+-----------------------------------------------------+| Confirm Snapset Command || || You are about to terminate a range of snapsets for || || VDG TESTVDG1 || || Type TERMINATE to confirm the action || || TERMINATE || || |+-----------------------------------------------------+


Terminate command in batch • Look at the JCL

• Julian date used in JCL

• New WTOR message to terminate!

• After replying CONT, snapsets terminated and query proves it.

//SYSIN DD * GLOBAL MAX_RC(4) TERMINATE VDG TESTVDG1,DATE(170440000-170441230) QUERY VDG TESTVDG1,SNAPSET //

J0021822 $HASP373 JBASTI00 STARTED - WLM INIT -SRVCLASS PRDBATMD - SYS V11A J0021822 *63 EIP0107R Reply CONTinue or CANcel


New query fields with SNAPSET option

• Provides RDP Cache Utilization information with the SNAPSET option on query VDG. Only works when SNAPSET keyword is used in QUERY command

QUERY VDG TESTVDG1,SNAPSET

Snapset Query for VDG TESTVDG1

SYMM 0001967-01505, Microcode level 5977_0950, Type VMAX200K Gatekeeper B10F, Device Count: 5, Snapset Count: 35 RDP Cache Utilization: 1% SRP ID/Name: 0001/SRP_1, Reserved Capacity: 10%

Total Capacity: 517M, Total Allocated: 45M, Snap Allocated: 2134K

CREATE SOURCE_TRACKS EXPIRATION SNAPSET_NAME STATE DATE TIME CHANGED UNIQUE DATE TIME ______________________________ _____ ___________________ ______________ ___________________

TESTVDG1.......170531501C00004 ACT 02/22/2017 15:01:39 0 0 TESTVDG1.......170531511C00005 ACT 02/22/2017 15:11:39 0 0

SMF enhancements


Output from VDG define/modify

• Look at SMFREC and TRACKs in JCL

//SYSIN DD * GLOBAL MAX_RC(4) DEFINE VDG TESTVDG1,

CYCLE_TIME(10,35), SMFREC(215,TRACKS(YES)), RDP_CACHE_UTIL(50,80)

MODIFY VDG TESTVDG1,ADD, CCUU(B10F,

B140-B144)

VDG TESTVDG1 is Inactive, Cycle 3

Cycle_Time(10,35),Cycle_Overflow(IMMED),Consistent(YES),Timeout(15,CONT)

Terminate_Policy(OLDEST)

SRP_Warn%(80),SRP_Snap%(50),SRP_Term%(100),RDP_Cache_Util%(50,80) Max_Snapsets(256),Saved_Snapsets(0,1),Persistent_Copy_Limit(32) Log_Opt(SCF) SMF(215,TRACKS) MAXRC(0)

QUERY command completed


Dynamically alter SMF

• Use /F emcscf,ZDP MODIFY ,SMF(yes|no),vdgname

CREATE SNAPSET_NAME STATE DATE TIME ______________________________ _____ ___________________

TESTVDG1.......170531501C00004 ACT 02/22/2017 15:01:38

F MFESCF82,ZDP MODIFY,SMF(NO)TESTVDG1SCF0740I ZDP MODIFY,SMF(NO)TESTVDG1 SCF0741I ZDP MODIFY command accepted

VDG TESTVDG1 is Active, Cycle 5, next cycle at 15:21:39 Cycle_Time(10,35),Cycle_Overflow(IMMED),Consistent(YES),Timeout(15,CONT)Terminate_Policy(OLDEST) SRP_Warn%(80),SRP_Snap%(50),SRP_Term%(100),RDP_Cache_Util%(50,80) Max_Snapsets(256),Saved_Snapsets(0,1),Persistent_Copy_Limit(32) Log_Opt(SCF) SMF(NO) MAXRC(0)



Dynamically altering SMF • Turning SMF on and changing the SMFID to use

F MFESCF82,ZDP MODIFY,SMF(YES,228,TRACKS(YES)),TESTVDG1SCF0740I ZDP MODIFY,SMF(YES,228,TRACKS(YES)),TESTVDG1 SCF0741I ZDP MODIFY command accepted

VDG TESTVDG1 is Active, Cycle 5, next cycle at 15:21:39

Cycle_Time(10,35),Cycle_Overflow(IMMED),Consistent(YES),Timeout(15,CONT)Terminate_Policy(OLDEST) SRP_Warn%(80),SRP_Snap%(50),SRP_Term%(100),RDP_Cache_Util%(50,80) Max_Snapsets(256),Saved_Snapsets(0,1),Persistent_Copy_Limit(32) Log_Opt(SCF) SMF(215) MAXRC(0)

VDG TESTVDG1 is Active, Cycle 6, next cycle at 15:31:39 Cycle_Time(10,35),Cycle_Overflow(IMMED),Consistent(YES),Timeout(15,CONT)Terminate_Policy(OLDEST) SRP_Warn%(80),SRP_Snap%(50),SRP_Term%(100),RDP_Cache_Util%(50,80) Max_Snapsets(256),Saved_Snapsets(0,1),Persistent_Copy_Limit(32) Log_Opt(SCF) SMF(228,TRACKS) MAXRC(0)


Extended Addressable VolumesEAV


Extended Addressable Volume (EAV) background

• EAV restrictions due to host operating system

• Prior to this release, supported EAV up to 262,668 cylinders

• At GA, supported EAV totaling ~1TB or 1,182,006 cylinders

• Use DVE to expand volume

• EAV volumes supported on z/VM 6.3 and higher

• EAV Volumes supported on z/OS 1.13 and higher

• EAV volumes NOT supported for z/TPF

• Volumes over 65,520 cylinders will be labeled as 3390-A

Dynamic Volume Expansion & Unisphereenhancements


Understanding Dynamic Volume Expansion

Overview

• What does DVE do?

• Devices targeted for expansion can remain online

• Once increased, cannot reduce the size – Devices can be expanded multiple times

• At initial release, all Dell EMC and IBM copy operations to that volume must be stopped before expansion can take place

• Use case: As customers reach host device addressing limits, the ability to increase existing devices was needed

Before

After


DVE specifics

• DVE allows for 3390 CKD devices to be expanded

• Max cylinder size for expansion = 1,181,006 (A LOT) = ~1TB

• Expanding a device up to 65,520 will be done in one cylinder increments

• Expanding a device up from 65,521 – 1,181,006 will be done in increments of 1113 cylinders

• The model for an expanded device will be –A– Therefore 3390-3 expanded with a 10017 (which is a mod-9) will be displayed as a 3390-A


Dynamically expanding a volume

Unisphere View – Before Expansion

• Highlighted row shows the Capacity at 7.93 GB

• This is equal to a Mod-9



Right Click on Volume you want to expand



Unisphere Panel

• Type or use the arrow’s on the right to adjust new size

• Currently a 3390-9

Mod Cylinder Tracks

3390-3 3339 500853390-9 10017 1502553390-27 32760 491400



Unisphere Panel

• Let’s make it a 3390-27

Mod Cylinder Tracks

3390-3 3339 500853390-9 10017 1502553390-27 32760 491400



Unisphere Confirmation

• Success is great!


Using additional spaceICKDSF• Code in the DEVSUPxx SYS1.PARMLIB member REFVTOC=ENABLE

– This will cause ICKDSF VTOC reformat to run automatically once the volume is expanded

• Run ICKDSF REFORMAT with the NEWVTOC command.

• If you don’t do this, you will get jobs failing with ALLOCATION FAILED messages in the jobREFORMAT DDNAME(VOLDD) VERIFY(CK5494) REFVTOC ICK00700I DEVICE INFORMATION FOR 5494 IS CURRENTLY AS FOLLOWS:

PHYSICAL DEVICE = 3390 STORAGE CONTROLLER = 2107 STORAGE CONTROL DESCRIPTOR = E8 DEVICE DESCRIPTOR = 0E ADDITIONAL DEVICE INFORMATION = 4800003C TRKS/CYL = 15, # PRIMARY CYLS = 32760

ICK04000I DEVICE IS IN SIMPLEX STATE ICK03091I EXISTING VOLUME SERIAL READ = CK5494 ICK01520I THE VTOC-INDEX WAS DELETED ICK01314I VTOC IS LOCATED AT CCHH=X'0000 0001' AND IS 464 TRACKS. ICK01502I BUILDIX FUNCTION STARTED ICK01503I 5494 REQUEST RECEIVED TO CONVERT VTOC TO IXFORMAT ICK01504I 5494 VTOC FORMAT IS CURRENTLY OSFORMAT, REQUEST ACCEPTED ICK01508A 5494 SHOULD CONVERSION PROCEED? REPLY U TO CONTINUE, ELSE T ICK01513I 5494 BUILDIX PROCESSING COMPLETED: VTOC IS NOW IN IXFORMAT ICK01317I VTOC-INDEX IS LOCATED AT CCHH=X'001F 0000' AND IS 450 TRACKS.

Mod Cylinder Tracks

3390-3 3339 500853390-9 10017 1502553390-27 32760 491400

DVE Dynamic Volume ExpansionWhat if?


Expand volume past 1,181,006 cylinders

• Good!


Expand volume to 1,181,006 cylinders

• Wow!


What Unisphere shows!

• Oh Yeah!


Conclusions

• Dell EMC added significant functionality to Mainframe Enablers to get the most out of your storage environment

• Dell EMC continues to enhance Unisphere specifically for Mainframe

• Dell EMC added new SECURE Snapshots to protect your most critical data from traditional and new threats

• The new VMAX 950F is your ideal solution for Mainframe storage!

RELATED SESSIONSTITLE TIME

Mainframe: Availability For Your Most Demanding Environments Tuesday 8:30

Mainframe: Envisioning Your Future - Keys To Mainframe Storage Success Wednesday 8:30

Mainframe: Ensuring Recovery In An Uncertain World Thursday 10:00

VMAX: What's New With VMAX All Flash & What's Up With NVMe Monday 1:30

VMAX: What’s New With HYPERMAX - The Power Behind VMAX All Flash Arrays Monday 3:00

VMAX: Birds of a feather Tuesday 1:30

VMAX: Manage and Optimize Application Performance with Unisphere Tuesday 12:00

VMAX Performance: Best Practices For Optimal Local & Remote Replication Performance

Thursday 8:30

VMAX: Security Best Practices for the Modern Data Center Thursday 11:30

Thank you Questions & Answers

MAINFRAME: What's New with VMAX for Mainframe? · MAINFRAME: What's New with VMAX for Mainframe?...

Documents

Transcript of MAINFRAME: What's New with VMAX for Mainframe? · MAINFRAME: What's New with VMAX for Mainframe?...