Extended address volume eav
Download
1 / 76

Extended Address Volume (EAV) - PowerPoint PPT Presentation


  • 63 Views
  • Uploaded on

Extended Address Volume (EAV). zArchitecture Data Scalability. Why is EAV needed. Problem: Running out of z/OS addressable disk storage Rapid data growth pushing 4-digit device number limit Solution: Defining larger volumes by increasing the number of cylinders New track address format

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Extended Address Volume (EAV)' - guy-pruitt


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript


Why is eav needed
Why is EAV needed

  • Problem:

    • Running out of z/OS addressable disk storage

      • Rapid data growth pushing 4-digit device number limit

  • Solution:

    • Defining larger volumes by increasing the number of cylinders

      • New track address format

        • 28 bit cylinder track address (CCCCcccH)

      • Space managed in multi-cylinder units

        • Cylinder-managed space (EAS)

  • Benefit:

    • Increase z/OS addressable disk storage by supporting additional data set types that are EAS eligible

      • z/OS V1R12 provides the third iteration of this support


Overview what is an eav

Breaking the 65,520 cylinder limit

Overview - What is an EAV

  • What is an Extended Address Volume (EAV)?

    • A volume with more than 65,520 cylinders

    • Size limited to 223 GB (262,668 Max cylinders)

    • Supported in z/OS V1R10 and higher

z/OS

V1R12

z/OS

V1R10

z/OS

V1R11


Overview ds8000 support
Overview - DS8000 Support

  • 3390 Model A

    • A device configured to have 1 to 268,434,453 cylinders

      • 223 GB

    • DS8000 Release 4 Licensed Internal Code

  • An EAV is configured as an 3390 Model A in the DS8000

Theoretically up to

268,434,453 Cylinders

3390-A

“EAV”

Size limited to 223 GB (262,668 Max cylinders)

in z/OS V1R10 and higher

3390-9

3390-9

3390-9

3390-3

Theoretical

Up to 225 TB

3 GB

Max cyls: 3,339

9 GB

Max cyls: 10,017

27 GB

Max cyls: 32,760

54 GB

Max cyls: 65,520


Overview eav key design points

cylinder-managed

space

Cylinders

Beyond first

65,520

Cylinders

First

65,520

Cylinders

track-managed

space

EAV

Overview – EAV Key Design Points

How the space

is managed

  • Maintains 3390 track format

  • Track-managed space: the area on an EAV located within the first 65,520 cylinders

    • Space is allocated in track and cylinder units

    • Storage for “small” data sets

  • Cylinder-managed space: the area on an EAV located above the first 65,520 cylinders

    • Space is allocated in multicylinder units

      • A fixed unit of disk space that is larger than a cylinder. Currently on an EAV it is 21 cylinders

      • System may round space requests up

    • Storage for “large” data sets

  • Track-managed space comparable to same space on non-EAVs


Multi unit cylinders
Multi-unit cylinders

  • The 21 cylinder value for the MCU is derived from being the smallest unit that can map out the largest possible EAV volume and stay within the index architecture (with a block size of 8192 bytes), as follows:

    • Value that divides evenly into the 1GB storage segments of an IBM DS8000

    • These 1GB segments are the allocation unit in the IBM DS8000 and are equivalent to 1113 cylinders.

    • These segments are allocated in multiples of 1113 cylinders starting at cylinder 65520


Overview eav key design points1

Extended addressing

Space (EAS)

Base addressing

space

EAV

Overview – EAV Key Design Points

Extended addressing space (EAS): the area on an EAV located above the first 65,536 cylinders.

  • 28-bit cylinder addressing (CCCCcccH)

How the space

is addressed

  • Base addressing space: the area on an EAV located within the first 65,536 cylinders.

    • 16-bit cylinder addressing (CCHH)

    • Comparable to same addressing space on a non-EAV

Cylinders

beyond first 65,536

cylinders

New track address format needed to access tracks in EAS

The first 65,536

cylinders







Overview access to eas eligible data sets on eav

Format-8

Format-3

Extended addressing

space

Format-3

F3

F3

Format-9

Format-3

F3

F3

Up to 10

Format-3

Base addressing

space

EAV

Overview – Access to EAS eligible data sets on EAV

New DSCB

types provides a method of

protecting existing programs from

seeing an unexpected new track

address format

  • EAS eligible data sets can reside anywhere on an EAV

    • Format 8/9 DSCBs

EAS eligible data sets include VSAM, Sequential, Direct, and Partitioned in z/OS V1R12

Format-1

Format-3

Up to 10

Format-3


Format 4 dscb
Format 4 DSCB

  • Number of cylinders on volume

    • Existing two-byte field DS4DSCYL in the F4 DSCB will contain the value of x’FFFE’ (65534). This Identifies the volume as an EAV.

      • DS4EAV defined as constant value of X’FFFE’

    • New four-byte field DS4DCYL will contain the number of cylinders on the volume.

  • New allocation unit for cylinders above 65,520

    • New two-byte field DS4LCYL will contain a code value of x’0010’ to indicate that the cylinder-managed space after the first 65,520 cylinders must be allocated in units that are larger than one cylinder.

      • This value represents 65520 cylinders divided by 4095. For a non-EAV this will be zero.

    • New field DS4MCU (“minimum allocation unit”) will contain the number of cylinders that each extent in the cylinder-managed area must be a multiple of.

      • For an EAV this will be 21. For a non-EAV this will be zero. It is valid only when the value in DS4DSCYL is DS4EAV.


Format 8 and 9 dscb
Format 8 and 9 DSCB

  • Format 8 DSCB similar to Format 1 DSCB except

    • Identifier F8 instead of F1

    • Points to format-9 DSCB instead of a format-3 DSCB

    • Cylinder numbers in the extent descriptions can include large cylinder numbers

  • Format 9 DSCB

    • New as of z/OS V1R10

    • Points to one or more format-3 DSCB


Format 8 dscb
Format 8 DSCB

  • Identical to F1 DSCB with following exceptions

    • The format identifier (DS1FMTID) will be x’F8’ instead of x’F1’ . New symbols defined:

      • DS1IDC constant value of X’F1’ in DS1FMTID

      • DS8IDC constant value of X’F8’ in DS1FMTID

    • Track addresses in the extent descriptors starting in DS1EXT1 will use new track address format (that is, may contain 28-bit cylinder numbers)

    • The ‘next DSCB’ address (DS1PTRDS) will always point to a F9 DSCB (new type of DSCB) instead of a possible first F3 DSCB.


Format 9 dscb
Format 9 DSCB

  • F9 DSCB will exist only for EAS eligible data sets (VSAM in first release)

  • Will contain the following

    • The format identifier will be x’F9’

    • A subtype field

      • In the first EAV release, the subtype will be 1.

      • In future releases, additional subtypes may be added.

    • Track addresses which point directly to up to ten F3 DSCBs

      • All the format 3 DSCBs can be read with one channel program.

    • A 20-byte field DS9ATRV1 that IBM is reserving for vendors. IBM will not specify or monitor its content.

    • A ‘next DSCB’ address will point to a possible F3 DSCB. The F3 DSCBs will continue to be chained.

      • In future releases, additional F9 DSCBs may be chained between the subtype 1 and any F3 DSCBs


Overview access to extended attribute dscbs
Overview - access to extended attribute DSCBs

  • Code EADSCB=OK to access extended attribute data set control blocks (DSCBs)

    • EADSCB=OK indicates that program understands 28-bit cylinder numbers and format 8 and 9 DSCBs.

    • OBTAIN (CAMLST), CVAFDIR, CVAFFILT, CVAFSEQ, DCBE (open for EXCP processing, open VTOC), CVAFDSM

      • Not specifying EADSCB=OK will cause these services to fail

    • Keyword on 1.10 programs ignored on pre 1.10 systems & on volumes not supporting extended attribute DSCBs

      • Recommendation: code keyword on all invocations

EADSCB=OK keyword must be specified to access EAV VTOC records!

Not all applications

can access EAS eligible

data sets!

Use the tracking

facility to assist

in finding

programs


Migration assistance tracker
Migration Assistance Tracker

  • The EAV migration assistance tracker can help with:

    • Finding programs that you might need to change if you want to support extended address volumes (EAVs)

    • The EAV migration assistance tracker is an extension of the console ID tracking facility

  • Functions:

    • Identify select systems services by job and program name

    • Identify possible instances of improper use of returned information in programs, like parsing 28-bit cylinder numbers in output as 16-bit cylindernumbers

    • Identify instances of programs that will either fail or run with an informational message if they run on an EAV





Cnidtrxx parmlib member
CNIDTRxx Parmlib member

set cnidtr=7t

IEE536I CNIDTR VALUE 7T NOW IN EFFECT



Eas eligible data set sets in z os
EAS Eligible data set sets in z/OS

  • EAS Eligible: A data set on an EAV that is eligible to have extents in the extended addressing space and described by extended attribute DSCBs (format 8/9)

  • Can reside in track or cylinder-managed space

  • SMS-managed or non-SMS managed

  • Any data set type can reside in track-managed space

  • Data set types supported

    • VSAM data types (KSDS, RRDS, ESDS and linear)

      • This covers DB2, IMS, CICS, zFS and NFS

      • CA sizes: 1, 3, 5, 7, 9 and 15 tracks

    • Sequential (Extended Format)

    • Sequential (Basic and Large Format)

    • Direct (BDAM)

    • Partitioned (PDS, PDSE)

    • Catalog (VVDS and BCS)

V1R10

VSAM

V1R11

VSAM

EF SEQ

z/OS

V1R12

ALL



Non eas eligible data set list
Non-EAS-eligible data set list

  • A data set that may exist on an EAV but is not eligible to have extents (through create or extend) in the extended addressing space or have extended attribute DSCBs (format 8/9)

    • The following data sets are not EAS-eligible:

      • VSAM data sets with incompatible CA sizes

      • VTOC (continues to be restricted to within first 64K-1 tracks)

      • VTOC index

      • Page data sets

      • VSAM data sets with imbed or keyrange attributes

      • HFS file system

      • XRC Control, Master or Cluster non-VSAM data sets

        • State data set EAS eligible in z/OS V1R12

        • Journal data set EAS eligible in z/OS V1R11 and V1R12

      • Certain system data sets such as SYS1.NUCLEUS


Eattr data set attribute
EATTR data set attribute

EATTR is a new data set attribute in z/OS R11 to specify whether extended attributes can be created for a data set

  • NO - No extended attributes.

    • The data set cannot have extended attributes (Format 8 and 9 DSCBs) or optionally reside in EAS.

    • This is the default behavior for non-VSAM data sets in z/OS V1R11 and higher.

    • In z/OS V1R10 in the absence of EATTR this is equivalent to what the system uses for non-VSAM.

  • OPT - Extended attributes are optional.

    • The data set can have extended attributes and can optionally reside in EAS.

    • This is the default behavior for VSAM data sets in z/OS V1R11 and higher.

    • In z/OS V1R10 in the absence of EATTR this is equivalent to what the system uses for VSAM.

  • Used to override system-determined EAS eligibility

    Specifiable in AMS DEFINE CLUSTER and ALLOCATE, JCL,

    dynamic allocation, data class and ISPF

    Recorded in Format 1/8 DSCB for all data set types and volume types

    Recorded in VVDS for VSAM cluster name

    Listed by IEHLIST, ISPF, ISMF, LISTCAT, Catalog Search Interface (CSI), DCOLLECT

z/OS

V1R11


Eattr data set attribute in z os v1r11
EATTR data set attribute in z/OS V1R11

  • Miscellaneous

    • Volume selection based on EATTR values

      • SMS volume selection

      • HSM non-SMS volume selection

    • EATTR will be determined as follows

      • In the JCL interface by merging EATTR from the JCL, LIKE= and data class in that order

z/OS

V1R11


Eattr and format 9 data set attributes iehlist
EATTR and format 9 data set attributes – IEHLIST

CONTENTS OF VTOC ON VOL 1P9802 <THIS IS AN SMS MANAGED VOLUME>

FORMAT 4 DSCB NO AVAIL/MAX DSCB /MAX DIRECT NO AVAIL NEXT ALT FORMAT 6 LAST FMT 1 VTOC EXTENT THIS DSCB

VI DSCBS PER TRK BLK PER TRK ALT TRK TRK(C-H) (C-H-R) DSCB(C-H-R)/LOW(C-H) HIGH(C-H) (C-H-R)

81 65499 50 45 0 0 0 1279 14 50 0 1 1279 14 0 1 1

NUMBER OF MULTICYLINDER UNITS

CYLINDERS FIRST CYL ADDR SPACE

262668 65520 21

---------------DATA SET NAME---------------- SER NO SEQNO DATE.CRE DATE.EXP DATE.REF EXT DSORG RECFM OPTCD BLKSIZE

BRS8AM02.HANDLIN.V1P9802.NVSAM.FILL.CB1 1P9802 1 2008.176 00.000 00.000 1 PS FB 00 6320

SMS.IND LRECL KEYLEN INITIAL ALLOC 2ND ALLOC EXTEND LAST BLK(T-R-L) DIR.REM F2 OR F3(C-H-R) DSCB(C-H-R)

S 80 TRKS 1 0 0 58786 0 2 29

EXTENTS NO LOW(C-H) HIGH(C-H)

0 50901 9 50901 14

----ON THE ABOVE DATA SET,THERE ARE 6 EMPTY TRACK(S)

---------------DATA SET NAME---------------- SER NO SEQNO DATE.CRE DATE.EXP DATE.REF EXT DSORG RECFM OPTCD BLKSIZE

BRS8AM02.HANDLIN.V1P9802.VSAM.FILL.D1.DATA 1P9802 1 2008.176 00.000 00.000 1 VS U 80 4096

SMS.IND LRECL KEYLEN INITIAL ALLOC 2ND ALLOC EXTEND LAST BLK(T-R-L) DIR.REM PTR TO F3(C-H-R) DSCB(C-H-R

S 0 CYLS 0 2 3 13

VENDOR

EATTR JOB STEP CREATE TIME CODE DATA

OPT JOB1GALA STEP0001 01:28:58.673275 1 X'11223344' 2 X'556677' 255 X'88'

EXTENTS NO LOW(C-H) HIGH(C-H)

0 193704 0 193724 14

----UNABLE TO CALCULATE EMPTY SPACE.

VPSM A = NUMBER OF TRKS IN ADDITION TO FULL CYLS IN THE EXTENT

TRK FULL TRK FULL TRK FULL TRK FULL

ADDR CYLS A ADDR CYLS A ADDR CYLS A ADDR CYLS A

3784725 42 0 3785670 63 0 3786930 21 0 3787560 42 0

3788505 63 0 3789765 21 0 3790395 42 0 3791340 63 0

THERE ARE 52290 EMPTY CYLINDERS PLUS 4590 EMPTY TRACKS ON THIS VOLUME

THERE ARE 12852 EMPTY CYLINDERS PLUS 4590 EMPTY TRACKS FROM THE TRACK-MANAGED SPACE

THERE ARE 957221 BLANK DSCBS IN THE VTOC ON THIS VOLUME

New fields and extent descriptors for data and free space adjusted to support larger cylinder numbers


Eattr in listcat
EATTR in LISTCAT

LISTCAT ENT(CFDUPLEX.AA.CARDHOLD) ALL

CLUSTER ------- CFDUPLEX.AA.CARDHOLD

IN-CAT --- W93UCAT.TVS

HISTORY

DATASET-OWNER-----(NULL) CREATION--------2009.058

RELEASE----------------2 EXPIRATION------0000.000

SMSDATA

STORAGECLASS ---MLCLAS01 MANAGEMENTCLASS---(NULL)

DATACLASS ------EATTROPT LBACKUP ---0000.000.0000

EATTR--------------(OPT)

BWO STATUS------00000000 BWO TIMESTAMP---00000 00:00:00.0

BWO-------------------NO


Bcp support for eav in z os v1r11
BCP support for EAV in z/OS V1R11

z/OS

V1R11

  • Support for data sets that reside in EAS

    • SMF, TSO/E, ISPF, FTP support

    • Language Environment support for data sets with extended attributes, including those in EAS on an EAV, for C/C++ programs

    • RACF discrete profile support for non-VSAM data sets in EAS

      • ADDSD and ALTDSD commands have been updated to support datasets in the EAS

      • The RACF database is not supported if allocated in the EAS

      • RACF utilities will not support allocation of DB datasets in the EAS

        • EATTR=NO (default) should be used on allocations for these data sets

          IRRUT200 SYSUT1 DD

          IRRMIN00 SYSRACF DD

          IRRUT400 OUTDD DD

    • SVCDUMP, SYSMDUMP, SNAP, ABDUMP and IPCS support


Catalog idcams bcs in z os v1r12
Catalog/IDCAMS - BCS in z/OS V1R12

  • BCS (basic catalog structure) data sets EAS eligible

  • AMS will be changed to support EATTR as a keyword on the DEFINE UCAT as well as on DEFINE UCAT MODEL.

    • This applies to both ICFCATALOG and VOLCATALOG objects.

  • EATTR(NO) – Can not have extended attribute DSCBs or optionally reside in EAS

  • EATTR(OPT) – Can have extended attribute DSCBs and optionally reside in EAS

    • Both recorded in the VVDS for the catalog objects and in the DSCBs that get created in the VTOC

    • Catalog object restricted to track-managed space when EATTR is not specified. This is the action taken by the system today for catalog defines.

    • No EATTR option in pre z/OS V1R12 systems

    • EXPORT/IMPORT preserves EATTR value across systems


Catalog idcams vvds in z os v1r12
Catalog/IDCAMS - VVDS in z/OS V1R12

  • VVDS (VSAM volume data sets) data sets EAS eligible

  • AMS will be changed to support EATTR as a keyword on the DEFINE CLUSTER where the object is a VVDS data set.

  • EATTR(NO) – Can not have extended attribute DSCBs or optionally reside in EAS

  • EATTR(OPT) – Can have extended attribute DSCBs and optionally reside in EAS

    • Both recorded in the DSCBs that get created in the VTOC

    • VVDS objects restricted to track-managed space when EATTR is not specified. This is the action taken when VVDS is allocated by the system.

    • No EATTR option in pre z/OS V1R12 systems

    • Data Class/Model does not apply to a DEFINE of an VVDS

      • Only way is with the EATTR keyword


Dfsmshsm support in z os v1r12
DFSMShsm support in z/OS V1R12

  • The DFSMShsm owned backup and migration (ML1 / ML2) volumes can be EAV space

    • Manage use with new option

      • SETSYS USECYLINDERMANAGEDSPACE(Y|N)

  • DFSMShsm data sets that can be allocated in EAS

    • Journal (basic or large format sequential data sets)

    • Control data sets (CDS) and Journal backup data sets

    • Logging and PDA data sets

  • DFSMShsm will support the data set level attribute EATTR for all EAV eligible data sets and process SMS and non-SMS recalls/recovers/arecovers accordingly.


Dfsort v1r12 changes
DFSORT V1R12 changes

  • DFSORT data sets that can be allocated in EAS

    • SORTIN, SORTOUT, OUTFIL

      • Maximum size of large format sequential supported

    • SORTWK

      • If basic format sequential

        • Limited to 65534 tracks

      • If large format sequential

        • Limited to 1,048,574 tracks (blocks)

        • Larger can be allocated but excess will not be used

        • Less in a resource-constrained environment

  • Provided in DFSORT V1R12


Other changes
Other changes

  • Other changes to support the additional data set types that are now EAS eligible.

    • DFSMSdss

    • EREP

    • IBM utilities like IEBCOPY

  • LIKE= processing for PDS

    • Directory blocks calculation

  • SMS support for catalogs in EAS

    • Volume selection

      • When EATTR=OPT prefer EAV volumes when space >= BPV

    • Default EATTR processing

      • Catalogs – equivalent to EATTR=NO processing

        • Different from VSAM even though catalogs are VSAM files


Interactions dependencies
Interactions & Dependencies

  • Hardware Dependencies

    • None other than the 3390 Model A that has been supported since z/OS Release 10

  • Software Dependencies

    • Apply PTFs on pre-Release 12 systems that share DASD with Release 12. Described on later Coexistence Considerations pages.

  • Exploiters

    • Planned exploiters include DB2 and IMS

    • User and vendor application programs. Ask your vendors.



Ispf eav data set support
ISPF EAV Data Set Support

  • Option A (Allocate New Data Set) of the Data Set Utility (ISPF option 3.2) is enhanced with a new “Extended Attributes” field.

  • If OPT is specified in this field the data set can have extended attributes and reside in EAS.



Ispf eav data set support2
ISPF EAV Data Set Support

  • Extended Attribute - Any of the following:

    NO - data set cannot have extended attributes or reside in EAS.

    This is the default for non-VSAM data sets.

    OPT - data set can have extended attributes and reside in EAS.

    This is the default for VSAM data sets.

    blank - use default based on data type.


Ispf eav data set support3
ISPF EAV Data Set Support. . .

  • The “Data Set Information” panels available from the Data Set Utility (ISPF option 3.2) and the Data Set List Utility (ISPF option 3.4) line commands I and S are enhanced to display the “Extended Attributes” setting for a data set.


Ispf eav data set support4
ISPF EAV Data Set Support

  • ISPF services are enhanced to return the “Extended Attributes” setting for a dataset:

    • DSINFO service

      • Returned in variable ZDSEATR

    • LMDLIST service

      • Returned in variable ZDLEATR



Configure an eav automatic vtoc and index rebuild in z os v1r11
Configure an EAV – Automatic VTOC and index rebuild in z/OS V1R11

  • Dynamic Volume Expansion enhancements

    • Automatic VTOC and VTOC index rebuild

      • When a volume increase in size is detected by the system

        • Triggered by state change interrupts (SCIs)

      • Controlled with new DEVSUPxx PARMLIB option

        • ENABLE(REFVTOC)

        • DISABLE(REFVTOC) – default

      • The refresh of the index occurs under protection of an exclusive SYSTEMS ENQ macro for major name SYSZDMO, minor name DMO.REFVTOC.VOLSER.volser.

z/OS

V1R11


Automatic vtoc and vtoc index rebuild
Automatic VTOC and VTOC index rebuild z/OS V1R11

  • REFVTOC=ENABLE - Enables the automatic REFVTOC function of the device manager that when enabled, and a volume expansion is detected, the device manager causes the volume VTOC to be rebuilt

    • This allows the newly added space on the volume to be used by the system

  • REFVTOC=DISABLE - This is the default value. It disables the automatic REFVTOC function of the device manager

    • With the REFVTOC function disabled, when a volume expansion is detected: (Use R10 method)

  • The following message is issued:

    IEA019I DDDD,VVVVVV,VOLUME CAPACITY CHANGE,OLD=XXXXXXXX NEW=YYYYYYYY


Thank you! z/OS V1R11



Coexistence pre z os v1r10
Coexistence – Pre z/OS V1R10 z/OS V1R11

Pre

z/OS

V1R10

  • Pre z/OS 1.10 systems will not allow EAV online

    • Minimizes coexistence support

    • Must plan EAV use by applications

    • Define ‘shared’ EAV offline in HCD

  • DEVSERV command displays

    • QDASD, fields shifted to support larger #CYLS

    • PATHS, support for 3390 Model A (3390A)

  • LISTDATA PINNED UNITNUMBER – not allowed

  • LSPACE

    • Treat expanded requests as normal

      • EXPDATA, XEXPMSG becomes DATA and EXPMSG


  • Coexistence pre z os v1r10 cont
    Coexistence – Pre z/OS V1R10 (cont) z/OS V1R11

    Pre

    z/OS

    V1R10

    • HSM Recall/Recover considerations

      • Support virtual concurrent copy (VCC) keywords

      • Recall or recover of data sets with format 8/9 DSCBs that were migrated or backed up on z/OS V1.10

        • Converted to format 1 DSCBs

        • New message, ARC0784I, attribute data not retained, if applicable.

    • DSS Restore considerations

      • No full volume restore of a full volume dump with extended attribute DSCBs (EAV)

      • Tracks restore including track 0 will fail

        • No track 0, only track-managed space from an EAV

      • Logical and physical data set restores changed to convert F8/F9 to F1 DSCBs

        • Inability to restore a F9 where F9 attribute data would be lost will be indicated with new message, ADR556W

      • DFSMSdss standalone restore will not perform a full volume or tracks restore of an EAV to a non-EAV.


    Coexistence pre z os v1r10 cont1
    Coexistence – Pre z/OS V1R10 (cont) z/OS V1R11

    • DB2 V8 and V9

      • Admin Enablement and Log Manager

        • Keep BSDS and active logs on non-EAV and not using Admin Enablement functions, then no changes

          • Otherwise, the coexistence support to DB2 V8 and V9 will need to be applied


    Migration to eav considerations smf records r10
    Migration to EAV considerations – SMF Records (R10) z/OS V1R11

    • SMF Type 14/15 (non-VSAM data set EOV or close)

      • A new flag, SMF14EADSCB, indicates whether a program specified EADSCB=OK on the DCBE macro

        • Specific migration aid in z/OS V1R10 to identify programs that open the VTOC or VSAM data sets with EXCP (MACRF=E)

        • In z/OS V1R10 or later this data set may have a format 8 DSCB

          • IBM recommends that you upgrade the program to handle 28-bit cylinder numbers and code EADSCB=OK

      • A new flag, SMF14EXCPBAM, indicates that a program used a non-EXCP OPEN DCB (BSAM, QSAM, BPAM) and issued EXCP or XDAP

        • When SMF14EADSCB is off, it identifies programs that may need to be upgraded to handle 28-bit cylinder numbers and have EADSCB=OK coded

        • Preparation for future release

          Note: Use TRKADDR macro to upgrade programs


    Migration to eav considerations smf records cont
    Migration to EAV considerations – SMF Records (cont) z/OS V1R11

    • SMF Type 19 (volume statistics)

      • LSPACE statistics recorded. Expanded with track-managed free space stats and total volume/track-managed space sizes

    • SMF Type 60, 61, 64, 65, 66 (various VSAM events)

      • Each of these SMF records contains a copy of a catalog record for a VSAM data set. They may contain extent descriptors with cylinder numbers greater than 65535.

    • SMF Type 74, subtype 1 (RMF device activity)

      • New device capacity field saved


    Migration to eav considerations vtoc index r10
    Migration to EAV considerations – VTOC index (R10) z/OS V1R11

    • Index block size increased from 2048 bytes to 8192 bytes for devices with cylinder-managed space

      • Contents of index map records increased proportionally (more bits per record, offsets changed)

        • Extended header in VIXM for free space statistics

        • VPSM

          • Track-managed space. Small (tracks and cylinders) and large (cylinders) unit map. Same but more bits

          • Cylinder-managed space. Each bit in large unit map represents 21 cylinders (a MCU)

      • Programs that access index maps must use existing self-describing fields in the map records

    • Block size is in format 1 DSCB for the VTOC index and returned by DEVTYPE macro

    • Default index size computed by ICKDSF – might not be 15 tracks


    Migration to eav considerations vvds r10
    Migration to EAV considerations – VVDS (R10) z/OS V1R11

    • VVDS (VSAM volume data set) contains extent descriptors for VSAM data sets

      • VVR (VVDS record)

        • May contain 28-bit cylinder numbers

      • No interfaces provided to access the VVDS directly

        • Programs that access the extents in the VVR record must ensure that they support 28-bit cylinder numbers

          • Use TRKADDR macro or the IECTRKAD routine


    Eas eligible finding affected programs r10
    EAS eligible – Finding Affected Programs (R10) z/OS V1R11

    • A product or program might be affected by this project if it does any of these (this list might be incomplete) AND it supports processing a data set that is EAS-eligible:

      • Issuing an OBTAIN macro to read a DSCB for an EAS-eligible data set or issuing a macro whose name begins with "CVAF" for an EAS-eligible data set. You must code a new EADSCB=OK option. For performance reasons, you might want also to exploit a new option to read all the DSCBs for a specified data set with one call.

      • If your program bypasses OPEN, almost any channel program issued for an EAS-eligible data set will be affected. This includes both building it and monitoring it.

      • Use a track address for an EAS-eligible data set such as those in IOSEEK in the IOSB, IOBSEEK in the IOB or DS1EXT1 in the DSCB. As in the first release of EAV, these will contain 28-bit cylinder numbers. You can use the TRKADDR macro from z/OS V1R10 to assist with these manipulations.

      • Use the BBCCHHR field in the I/O error text returned by the SYNADAF macro. This is in EBCDIC form. It is similar to text returned by VSAM.

      • Calculating the size of an EAS-eligible VSAM or non-VSAM data set from the cylinder and track numbers of its extents. These cylinder and track numbers might be from a VTOC, DEB or from an access method internal control block. The TRKADDR macro or IECTRKAD routine can assist with this calculation.


    Eas eligible affected programs cont r10 r11
    EAS eligible – Affected Programs cont. (R10, R11) z/OS V1R11

    • Examine programs that read VTOCs or DSCBs. On R10, programs designed to read an EAV VTOC expect to see format 8 DSCBs for only VSAM data sets. On R11 those programs can also see format 8 DSCBs for extended format sequential data sets. If you share EAVs between R10 and R11, you must avoid opening the non-VSAM data sets that have format 8 DSCBs or you must prevent those data sets from being on those volumes.

    • Programs can read VTOCs or individual DSCBs with BSAM, QSAM, EXCP, OBTAIN, CVAFDIR and CVAFFILT. If your program opens an EAV VTOC, it must specify EADSCB=OK on the DCBE macro. This is the same as for EAV on R10. The following principles are the same as in R10 but now they apply also to extended format sequential data sets:

    • Examine these VTOC-reading programs to see whether they might be affected by seeing a format 8 DSCB when they expected a format 1 DSCB or they might be affected by seeing a format 9 DSCB when they expected a format 3 DSCB.

    • If your program issues the OBTAIN, CVAFDIR or CVAFFILT macro for a data set that has a format 8 DSCB, then the macro must have EADSCB=OK.

    • If you create a non-VSAM data set on Release 11 on an EAV and you might want to use it on an earlier release, you should avoid EATTR=OPT for that data set. If the non-VSAM data set has a format 8 DSCB, you cannot open it on a release before 11.

    • Examine programs that calculate the size of a data set on a volume. The value might be larger than the program has ever seen. The TRKADDR macro is available to assist with these calculations.

    • Although there are no intended programming interfaces for channel programs with extended format data sets, any such programs must take the 28-bit cylinder numbers into account as in R10. 28-bit cylinder numbers might be in a DSCB, IOB or channel program. The TRKADDR macro is available to assist with manipulating track addresses.


    Usage invocation vtoc access r10
    Usage & Invocation – VTOC Access (R10) z/OS V1R11

    • OBTAIN and CAMLST macros

      • New option, NUMBERDSCB=n on each macro

        • If n > 0 and the DSCB is a format 1 or 8 DSCB, then you wish to read the logical chain of DSCBs that begins with that DSCB. They are chained with the DS1PTRDS field, which contains the CCHHR type of address of the next DSCB.

        • Consecutive 140-byte areas must be passed

        • SEARCH requests return additional bytes

          • Possible migration item if program provides 101 bytes return area

    • CVAFDIR macro

      • New parameter MULTIPLEDSCBS=YES|NO

        • YES - Process multiple buffers in the first buffer list if there are any for reads and writes. They will contain as many of the whole chain of DSCBs for one data set as possible and must begin with a format 1 or 8 DSCB


    Usage invocation lspace macro r10
    Usage & Invocation – LSPACE Macro (R10) z/OS V1R11

    • The LSPACE macro returns information about a DASD volume

      • Returned info can be in character or binary format.

        • New keywords XEXPMSG=addr andEXPDATA=addr

          • Returns free space information for total volume and for track-managed space

            • For all volumes

        • Total volume size and size of track-managed space is also returned

    • New DATATYPE keyword

      {ALL } Return all of the following information

      {VOLUME } Return free space for volume

      {VTOC } Return free space for VTOC

      {INDEX } Return free space for index

      {FRAGINDEX} Return the fragmentation index

    • New PLISTVER keyword

      • To manage the use of the longer LSPACE parameter list


    Usage invocation devtype macro r10
    Usage & Invocation – DEVTYPE Macro (R10) z/OS V1R11

    • Obtains device characteristic information about I/O devices

      • DEVTYPE non-INFOLIST calls

        • Returns a 2-byte value for the number of cylinders

          • Not valid for an EAV

      • DEVTYPE INFO=DASD (INFOLIST calls)

        • Existing call

        • Returns a 4-byte value for the number of cylinders

        • In addition it now returns

          • Multicylinder unit value

          • First cylinder address where cylinder-managed space begins

          • Cylinder-managed space supported indicator

          • Extended attribute DSCBs supported indicator

          • Block size of index data set


    Migration considerations eattr
    Migration Considerations - EATTR z/OS V1R11

    • Can share EAVs with pre-z/OS V1R12 systems until explicit action is taken to begin allowing non-VSAM data sets to reside in the EAS of an EAV

      • Applies to basic and large sequential, partitioned and direct data sets

      • This is because EATTR will default to NO for non-VSAM data sets.

      • A non-VSAM data set allocated with extended attribute DSCBs on z/OS V1R12 will not be able to be opened on pre z/OS V1R12 systems

    • EATTR specifiable for non-EAS eligible data sets

      • EATTR=OPT could have been specified on pre z/OS V1R12 system and ignored

      • In z/OS V1R12 the EATTR=OPT setting will take effect

      • Be certain that applications can handle extended attribute DSCBs and 28-bit cylinder numbers as they may become EAS-eligible data sets in z/OS V1R12


    Migration considerations z os v1r12
    Migration Considerations – z/OS V1R12 z/OS V1R11

    Supports additional non-VSAM data set types, introduces support for sequential (basic, large), partitioned (PDS/PDSE), catalogs and BDAM data sets in the extended addressing space (EAS):

    • Prior to z/OS V1R12 system, any attempt to open one of these types of non-VSAM data sets which have been allocated with a format 8 DSCB (from a z/OS V1R12 system) will fail with existing abend IEC144I 313-0C.

    • Prior to z/OS V1R12 system, if the next data set in the concatenation is one of these types of non-VSAM data sets which have been allocated with a format 8 DSCB then EOV will fail with new abend IEC023I 237-24.

    • With z/OS V1R12, any attempt to open one of these types of non-VSAM data sets which have been allocated with a format 8 DSCB will succeed with standard BSAM, BPAM and QSAM access

      • DCBE with EADSCB=OK is not required

      • Cannot rely on open ABEND.

      • Data set extents in DEB may contain 28-bit cylinder numbers

        • Programs need to be changed to support 28-bit cylinder addressing.

        • The system has no way to detect whether an application program can tolerate 28-bit cylinder numbers.

      • EXCP access still requires EADSCB=OK and will continue to get the open ABEND if EADSCB=OK is not specified on the DCBE macro


    Migration considerations z os v1r121
    Migration Considerations – z/OS V1R12 z/OS V1R11

    • EOV Like concatenation

      • With data sets with extended attribute DSCBs

        • EOV for EXCP processing requires EADSCB=OK to be specified on the DCBE macro to switch to a data set with extended attribute DSCBs. If EADSCB=OK is not specified, new ABEND IEC023I 237-28 will be issued.

          IEC023I 237-28 During EOV concatenation, a format 8 DSCB was read for a data set that was EAS eligible but EADSCB=OK was not specified on the DCBE macro

    • OPEN

      • Since BDAM is eligible for EAS, an OPEN with DCB OPTCD=A (actual track addresses) of a BDAM data set described with extended attribute DSCBs will be failed with existing abend IEC142I 113-44 unless EADSCB=OK set on DCBE macro.


    Migration considerations z os v1r122
    Migration Considerations – z/OS V1R12 z/OS V1R11

    • DFSMShsm

      • HSM owned volumes (migration/backup volumes) that are EAV or HSM-owned data sets (Journal, Log, CDS backup, PDA) that are allocated with extended attribute DSCBs will not be able to be accessed on pre z/OS V1R12 systems

        • Existing support will detect these conditions.

      • Restrict these uses until all systems are at z/OS V1R12 or higher


    Migration considerations z os v1r123
    Migration Considerations – z/OS V1R12 z/OS V1R11

    • XRC

      • Control, Master and Cluster data sets if allocated with extended attribute DSCBs will cause these data sets to be inaccessible.

        • Because of size, little benefit is gained

        • Restrict their use to track-managed space

      • Journal data set can be allocated in EAS at z/OS V1R11 and higher

      • State data set may be allocated in EAS at z/OS V1R12 and higher.


    Migration considerations z os v1r124
    Migration Considerations – z/OS V1R12 z/OS V1R11

    You can test the following bits in DFAFEAT8 in the DFA, mapped by IHADFA, to learn which data set types can be opened with format 8 DSCBs:

    1... .... DFAVSAMFOREAS VSAM

    .1.. .... DFASEQFOREAS Basic & large format sequential

    ..1. .... DFAPDSEFOREAS PDSE

    ...1 .... DFAPDSFOREAS PDS

    .... 1... DFADIRFOREAS Direct (BDAM)

    .... .1.. DFAEFSEQFOREAS Extended format sequential

    .... ..1. DFAUNDEFFOREAS No DSORG

    In V1R10, only the VSAM bit will be on (with PTF on V1R10).

    In V1R11, the VSAM and extended format sequential bits will be on.

    In V1R12, all the bits will be on.

    z/OS

    V1R10

    &

    higher


    Migration considerations z os v1r125
    Migration Considerations – z/OS V1R12 z/OS V1R11

    • Tracking Facility

      • Finds programs that need changing without the use of an EAV

      • When run from z/OS V1R12 the tracking facility will report instances for basic and large sequential, partitioned and direct data sets where EADSCB=OK has not be specified on system services

        • See speaker notes for a list of system services

      • If the ‘error’ instances are not upgraded, the invocation of the service will fail on an EAV


    Coexistence considerations z os v1r12
    Coexistence Considerations – z/OS V1R12 z/OS V1R11

    • EOV Like concatenation

      • With data sets with extended attribute DSCBs

        • On a pre z/OS V1R12 system EOV will not allow a switch to a data set that was allocated with extended attribute DSCBs on z/OS V1R12 that is not EAS eligible on the pre z/OS V1R12 system.

        • New ABEND will be issued

        • Provided with fix for OA28651

          IEC023I 237-24. During EOV concatenation, a format 8 DSCB was read for a data set that was not EAS eligible


    Coexistence considerations z os v1r121
    Coexistence Considerations – z/OS V1R12 z/OS V1R11

    LIKE= processing

    • Support to allow z/OS V1R10 and z/OS V1R11 systems to process data set attributes for a:

      • PDS data set that resides in EAS

      • non-VSAM data set that has extended attribute DSCBs

    • Provided with fixes for OA29877 in z/OS V1R10 and V1R11


    Coexistence considerations z os v1r122
    Coexistence Considerations – z/OS V1R12 z/OS V1R11

    • BCS/VVDS (catalog) in EAS

      • Support to allow z/OS V1R10 and z/OS V1R11 access to master catalogs allocated with extended attribute DSCBs

      • Support in catalog, VSAM, IDCAMS and DADSM to allow the EATTR data set attribute to be preserved between releases and used for the new allocation (z/OS V1R10, V1R11 and V1R12) for a BCS during EXPORT/IMPORT processing

      • Provided with fixes for OA29932, OA31449, OA29933, and OA30161 in z/OS V1R10 and V1R11


    Coexistence considerations z os v1r123
    Coexistence Considerations – z/OS V1R12 z/OS V1R11

    • DFSMShsm

      • Recognize basic and large format sequential, partitioned and direct data sets with extended attribute DSCBs in order to prevent processing them by a DFSMShsm function from a pre z/OS V1R12 systems.

        • DFSMShsm support for these is z/OS V1R12.

          • See speaker notes for a list of functions

      • Provided with fixes for OA30606 on z/OS V1R10 and V1R11.


    Coexistence considerations z os v1r124
    Coexistence Considerations – z/OS V1R12 z/OS V1R11

    • DFSMSdss

      • Recognize VVDS, BCS, basic and large sequential, partitioned and direct data sets with extended attribute DSCBs in order to prevent processing them by a DFSMSdss COPY or DUMP operation from a pre z/OS V1R12 systems.

        • DFSMSdss for these is in z/OS V1R12

      • Provided with fixes for OA29471 on z/OS V1R10 and V1R11.


    Coexistence considerations z os v1r125
    Coexistence Considerations – z/OS V1R12 z/OS V1R11

    • DFSORT V1R10

      • Issue message ICE289A for a data set that is not supported for EAS on z/OS V1R10 or z/OS V1R11 systems

      • Provided with fix UK45047 for DFSORT V1R10 which runs on z/OS V1R10 and z/OS V1R11


    Coexistence considerations ptf summary
    Coexistence Considerations – PTF Summary z/OS V1R11

    • OA28651, OPEN/CLOSE/EOV (UA52685 for R10, UA52686 for R11)

    • OA30161, DADSM (UA52742 for R11)

    • OA29932, catalog

    • OA31449, VSAM

    • OA29933, IDCAMS

    • OA29877, SMS

    • OA29471, DFSMSdss

    • OA30606, DFSMShsm

    • PK77146, DFSORT (UK45047)


    ad