KEMBAR78
Understanding EAV in z/OS Systems | PDF | Computer Science | Computers
0% found this document useful (0 votes)
43 views25 pages

Understanding EAV in z/OS Systems

Implementing and Using Extended-Addressing Volumes

Uploaded by

meisterdausi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
43 views25 pages

Understanding EAV in z/OS Systems

Implementing and Using Extended-Addressing Volumes

Uploaded by

meisterdausi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 25

Implementing and Using

Extended-Addressing Volumes
(EAV)
Session 15904

Steve Pryor
DTS Software, Inc.

steve@dtssoftware.com
Agenda

What are EAV Volumes?
 History and current status
 Architecture and addressing

z/OS changes for EAV
 DSCBs, program support, DFSMS
 SRS, ACC, and vendor support of EAV

How to Create and Use EAV

Advantages and Disadvantages
Why EAV?

Running out of addressable disks
 4-digit device number limits total available devices


Larger Volumes
 More data under one roof

Fewer total volsers to manage
What is an EAV Volume?

More than 65,520 cylinders on a single volser
 IBM 3390-A (DS8000) or equiv (Hit UVM, VMAX, etc)
 Introduced in z/OS 1.10 for up to 223 GB
 Track format and tracks/cyl identical to current 3390
 SMS or non-SMS
 Volume divided into two areas:

Track-managed space

Cylinder-managed space


What Data Can Reside on an EAV?
 varies depending upon z/OS release
Maximum Volume Sizes
EAV introduced in z/OS R1.10

Theoretical max size of 268,434,453 cyls (225TB)

3390-A
“EAV”

3390-54
3390-27
3390-3 3390-9

223GB – 1TB
3 GB 9 GB 27 GB 54 GB Max Cyls 262,688
Max cyls: 3,339 Max cyls: 10,017 Max cyls: 32,760 Max cyls: 65,520 to 1,182,006
EAV Architecture Terms

Multicylinder Unit
(MCU/MAU) = 21
cylinders
Cylinders
Beyond first
Extended-addressing space 
(Cylinder-Managed space) BreakPointValue
65,520
Cylinders
EAS
(BPV)

EAS-eligible – can
65K 'line'
reside anywhere on
Cylinders Base Addressing space
EAV
0 – 65,519 (Track-Managed Space)

EAV
Changes due to EAV

Changes in DSCBs

Changes in size of VTOC, VTOCIX, VVDS

Changes in track addressing format

Changes in program parameters and processing

Changes in report field sizes
EAS-Eligible Datasets

1TB vol
EAV 3
EAV 2 V1R13
EAV 1 V1R12
V1R11

z /O S V1R10
2010
2009
2008
EAS:
EAS: S e q u e n tia l
EAS:
e x te n d e d PDS, PDSE
VSAM fo r m a t
o b je c ts BDAM
s e q u e n tia l
F o rm a t 8 BCS, VVDS
E A T T R a ttr ib u t e
DSCBs S p o o l d a ta s e ts
A u to m a tic V T O C
M ig r a tio n r e b u ild
tra c k e r
Non-EAS-Eligible Data

May still reside in track-managed space
 VTOC, VTOCIX, HFS, page datasets
 Certain XRC and SYS1
 VSAM imbed/keyrange, or incompatible CA
size (old alloc not 1,3,5,7,9,or 15)


Just about all user data is now EAS-eligible
 Including DB2, IMS, CICS, zFS, NFS
 FTP allocation is no longer a barrier to EAS use
DSCB Changes

Format-4

EAV indicator, cylinder count, MAU

Extended-Attribute DSCBs (EADSCBs)
 Format-8

Similar to F1DSCB, chains to F9DSCB
 Format-9

Similar to F3DSCB, but:
 Can point to additional F3DSCB or F9DSCB
 Direct pointers to F3DSCBs
 Additional metadata: jobname, stepname, crtime, vendor.
DSCB Changes

Format-8 Format-3

F3 Format-3

Format-9
Extended addressing F3
space F3
Format-3

F3
Up to 10
VVDS
Format-3

Base addressing
space
VTOC Format-1 Format-3
VTOCIX Up to 10
8K blocks Format-3
EAV
EAV Addressing

Old 16-bit Cylinder Addressing Format
Max cyl
65,520
 CC HH
maximum value x'FF F0 00 0F'
C C H H


New 28-bit Cylinder Addressing Format
 The '000' in the HH field becomes high order
cylinder number

X'CCCCcccH' – as stored

X'cccCCCCH – as used

cccCCCC:H – normalized (i.e, as printed)
EAV Addressing

Track-managed space
 The high-order cylinder no. is zero


Sample addresses
 X'FF F0 00 0E' – cylinder 65,520, track 14
 X'00 00 00 1E' – cylinder 65,536, track 14


TRKADDR macro or IECTRKAD routine
 Converts, compares, and calculates track addresses
 Possible, but not necessary, for programs to do 28-bit
calculations
28-bit Cylinder Addressing Format

EAV

Extended
addressing space
x CCCCcccH
cylinder-managed
CCHH space

(xCCCC000H)

track-managed
space
32760 Cyl 65520 Cyl
10017 Cyl Base addressing
3339 Cyl
space

Model 3 Model 9 Model 9 Model 9 Model A


3 GB 9 GB 27 GB 54 GB 100's of TB
EAV Programming Support

Changes for new DSCBs, cylinder addressing

EADSCB=OK keyword
 Indicates program understands F8/F9/28-bit cyls
 OBTAIN, CVAF macros (CVAFDIR/FILT/SEQ, etc.)
 DCBE (for EXCP open, VTOC open)
EAV Programming Support

Other programs
 Any channel program without OPEN

Usually, VTOC readers
 Size calculations or track addresses with CCHHR
 LSPACE, DEVTYPE – new keywords and plists
 Any readers of VVDS, or DEB extents
EAV Programming Support

New SMF fields
 SMF14EADSCB → EADSCB=OK on DCBE
 SMF14EXCPBPAM → BSAM/QSAM and EXCP
 SMF19 → LSPACE statistics expanded
 SMF6x → VSAM cylinder numbers expanded
 SMF74-1 → new RMF device capacity field
Migration Assistance Tracker

Uses Console ID tracking facility (APAR II113752)
 SETCON and D OPTDATA, TRACKING commands


Identify VTOC access errors needing
EADSCB=OK

OBTAIN, CVAFxxx, OPEN VTOC, OPEN EXCP

Identify programs that may need new services

LSPACE, DEVTYPE, IDCAMS DCOLLECT

Warn of possible errors parsing 28-bit cyls

IEHLIST LISTVTOC, IDCAMS LISTCAT, LISTDATA
PINNED
EAS Attribute

EATTR= NO/OPT/blank
 Added in z/OS 1.11, recorded in F1DSCB
 Use to prevent downlevel (1.10, 1.11) systems from
failing when restoring EAS datasets
 Available via JCL, dynalloc, DEFINE, dataclas, etc.
EAS Dataset Allocation
No
EAS-eligible type
of dataset?

Yes Allocate in
TRK-managed
space
No
EATTR=OPT?

Yes
No

Space req > BPV?


Allocate in
Yes CYL-managed
space
Setting Up EAV

SYS1.PARMLIB(IGDSMSxx)
 USEEAV = YES/NO
 BreakPointValue=cyls

May be specified in SG definition

ICKDSF INIT volume or use Dynamic Volume
Expansion

DEVSUPxx REFVTOC=ENABLE automatically expands
VTOC for DVE

Set dataclas EATTR=OPT if needed

Allocate and copy/move data
Vendor Products and EAV

Allocation Control Center
 Dataset allocation management

SET EATTR

Device selection and pooling


Storage Control Center MONitor
 Dataset and device reporting and monitoring
Cautions

Insure sufficient DSCBs when INITializing EAV

max DSNs = EAV cyls / (VTOC trks*50)

ICKDSF REFORMAT EXTVTOC or NEWVTOC

IGGCATxx VVDSSPACE sets VVDS size

Max VVDS size 5460 trk → 5825 cyl

Enable HyperPAV to prevent queuing on 1 UCB

Use EATTR=NO to prevent restore problems
with EAS datasets restored to pre-z/OS 1.12
systems
Further Reading and Documentation

Redbooks
 z/OS V1.13 Technical Update SG24-7961
 z/OS V1.13 Implementation SG24-7946


Manuals
 DFSMSdfp Advanced Services SC26-7400

Chapter 7.6 – TRKADDR macro

Appendix C – Using the EAV Migration Assistance Tracker
 DFSMS Using the New Functions SC26-7473
Questions?
Steve@dtssoftware.com
770.922.2444 x162

Share Technology Exchange


Booth 409

You might also like