MainframeZone.

com - Storage: z/Data Perspectives: Best Practices in DB2 Storage Management Page 1 of 3

Search MainframeZone.com Search!

Advanced Search

about us | advertising | contact

Latest issues

SPONSORS
Storage
Home > [Departments] Storage > z/Data Perspectives: Best Practices in DB2 Storage Management

SUB DEPTS
Backup / Recovery /
Business Continuity z/Data Perspectives: Best Practices in DB2
Data Warehousing / Storage Management
Storage
Connectivity /
Print this article
Infrastructure
SEARCH DEPTS
Performance &
Capacity Planning by Craig S. Mullins < Previous Page 1 2 Next Page > Go!

Advanced Search
April 6, 2011

For many DB2 professionals, storage management can be an afterthought, but it really
MAINFRAME JOBS
shouldn’t be. The cost of managing storage can be up to 10 times as much as the initial
Data Engineer z/OS
cost of acquiring the storage. Storage issues are vitally important, and unless managed Programmer Resources
appropriately, can be costly. International Inc (PRI Inc.)
St. Louis, MO, US

DB2 stores data in VSAM Linear Data Sets (LDSs). Each table space and index space DB2 for Z/OS
DBA/System
requires at least one VSAM data set. But there are many other storage-related objects Programmer
you will encounter with DB2 for z/OS, including storage groups (both DB2 and DFSMS), Flexjobs
MI, US
system data sets (logs, Boot Strap Datasets [BSDSs], etc.), image copy backups (stored
on disk or tape), DB2 library data Data Engineer III —
DB2 z/OS DBA
sets, temporary data sets, etc. HP
US

Storage-related information is IBM Mainframe

available from multiple sources, Engineer/Programmer -
z/OS
including the DB2 Catalog, Real-Time ITAC Solutions
Statistics (RTS), RUNSTATS, Birmingham, AL, US

STOSPACE, etc., but the details are z/OS DB2 Applications

scattered and it can be difficult to DBA
CTG
gain a complete, accurate, up-to-date Topeka, KS, US
picture. Furthermore, any historical Software Developer,
view into DB2 storage usage must be DB2 for z/OS
IBM Software Group
managed manually. San Jose, CA, US

DB2 z/OS DBA

A responsible DBA with a Apex Systems Inc
comprehensive storage strategy can Menomonee Falls, WI, US

ensure that all DB2 databases have #32614 | Mainframe

sufficient allocation to satisfy Programmer /
MVS ,COBOL, CICS, DB2
business requirements. They can Butler America
answer questions such as, “Why is DB2 storage growing when our business isn’t?” Raleigh, NC, US

http://www.mainframezone.com/storage/z-data-perspectives-best-practices-in-db2-storage-management 5/6/2011
MainframeZone.com - Storage: z/Data Perspectives: Best Practices in DB2 Storage Management Page 2 of 3

Wasted storage will be minimized and a proactive approach to adding more storage when Mainframe Developer :
COBOL, DB2 :
required will be adopted. Beechwood Computing Ltd
Madison, WI, US
Although mainframe disk is usually equated to a 3380 or 3390, the actual physical disk is more >>
no longer as simple. Today’s modern storage architecture uses disk arrays, or Redundant
Search Jobs
Arrays of Independent Disk (RAID). An array is the combination of two or more physical
disk devices in a single logical device or multiple logical devices. The array is perceived job title, keywords, company, location
by the system to be a single disk device.
Find Jobs
Jobs by Indeed
Another relatively recent change is the use of IBM’s Data Facility Storage Management
System (DFSMS) to manage DB2 data. As of DB2 9, DATACLAS, MGMTCLAS, and
STORCLAS can be specified in DB2 storage groups. Using DFSMS with DB2 is the sane
thing to do because the new disk architectures, with concepts such as log structured files
and gigabytes of cache, render conventional database design rules based on data set
placement less relevant. In most cases, placement isn’t an issue, and when it is, SMS
classes and ACS routines can be used. Keep in mind, too, that as of DB2 10, the system
catalog must be managed by DFSMS.

What about extents? Many believe that modern storage devices render extent
management obsolete, but that isn’t exactly true. For one thing, the latest extent
management features only work with SMS-managed data sets; if your data sets are user-
managed, then the old rules apply. For example, as of z/OS 1.7, system-managed data
sets can have up to 123 extents on each of 59 volumes for a total of 7,257 extents.
Otherwise, the limit remains 255. Also, extent consolidation, introduced in z/OS 1.5,
requires SMS-managed STOGROUPs. When a new extent is adjacent to old, the two will
be merged automatically. This can result in some extents being larger than the PRIQTY
or SECQTY specification.

< Previous Page 1 2 Next Page >

More info about the author:

Craig S. Mullins

This article has no comments. Be the first to comment!

Sign up Today for the CICS Spotlight:

In-depth CICS articles and information!

sign-up >>

Compression for CPRI

Reduce your fiber optic costs for CPRI transport by 50%
www.samplify.com/wireless

COMMENT ENTRY

Name:

Email:

Location:

Website: http://

Comments:
Remember my personal information

Notify me of follow-up comments?

http://www.mainframezone.com/storage/z-data-perspectives-best-practices-in-db2-storage-management 5/6/2011
MainframeZone.com - Storage: z/Data Perspectives: Best Practices in DB2 Storage Management Page 3 of 3

Please enter the word

you see in the image below:

Preview Submit

General Legal Departments From TCI Publications:

• About Us • Privacy Policy • Applications & Databases • Operating Systems • Mainframe Executive
• Contact • Case Studies • Storage • z/Journal
• Site Map • CICS / WebSphere • Security • Spotlights
• Site Search • IT Management • Operations • Newsletters
• bpm.com

© MainframeZone, Inc. 2011

http://www.mainframezone.com/storage/z-data-perspectives-best-practices-in-db2-storage-management 5/6/2011