Is the VSAM Extended Addressability (EA) supported?

Products

• Bind Analyzer for DB2 for z/OS
• SQL-Ease for DB2 for z/OS
• SYSVIEW Performance Management Option for DB2 for z/OS
• Plan Analyzer for DB2 for z/OS
• Subsystem Analyzer for DB2 for z/OS
• Database Management for DB2 for z/OS - Performance Suite
• Database Management for DB2 for z/OS - SQL Performance Suite

Issue/Introduction

Is the VSAM Extended Addressability (EA) supported for a SYSVIEW history file and a Detector Datastore file. 

If it is supported for the history and datastore files, are there any considerations when the VSAM EA is used for those files?

Environment

Release : 20.0

Component : CA Insight Database Performance Monitor for DB for z/OS

Resolution

There is not any consideration for CA SYSVIEW for DB2 or Detector to work with Extended Addressability data sets, the only consideration is to specify a SMS Data Class when you define the data set. 

For reference, there is following links as the explanations for Extended Addressability.

- Extended Format and Extended Addressability.

<http://idcp.marist.edu/pdfs/ztidbitz/VSAM_ExtendedFormat_ExtendedAddressibility.pdf>

- IBM Redbooks - VSAM Demystified 

<http://www.redbooks.ibm.com/abstracts/sg246105.html?Open>

The SMS Data Class has to be defined by a SMS expert, depending on volumes available. 

Once you have the SMS Class then you have to specify it when you define the VSAM data set. 

- CA SYSVIEW for DB2. 

See a sample JCL in R200.CDBAAMP(ssid0550) member, this member is created for each SSID by the Post-Install Install Tsaks. 

- Detector. Option '7 Create/Initialize datastore' and specify 'SMS DATA class ===>' on each data set. 

Please see the attached document for several screen shots for reviewing. EXTEA is SMS Data Class that SMS administrator defined to run this samples.