ADSM-L

Re: Limitation of TSM DB Volumes

2003-04-14 10:01:11
Subject: Re: Limitation of TSM DB Volumes
From: Matt Simpson <matt AT UKY DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 14 Apr 2003 10:00:49 -0400
At 8:16 AM -0005 4/14/03, Richard L. Rhodes wrote:
Our current TSM server uses Shark storage.  We run a 80gb TSM db on 2
shark raidsets (8 packs) of 18gb drives.   All 20 db volumes are in
this same filesystem along with the
log(5gb), spread across all 18 spindles.

A lot of this stuff is still pretty hazy to me, but does that mean
you're not using raw volumes for the DB?  IBM recommended that we use
raw volumes for performance reasons.  We're also running on a Shark.
We have a 60gb database spread across 9 dbvolumes, all raw.
Considering how much Shark I/O is virtual, would we be better off
defining file systems on those partitions and defining multiple DB
vols per partition?
--


Matt Simpson --  OS/390 Support
219 McVey Hall  -- (859) 257-2900 x300
University Of Kentucky, Lexington, KY 40506
<mailto:matt AT uky DOT edu>
mainframe --   An obsolete device still used by thousands of obsolete
companies serving billions of obsolete customers and making huge obsolete
profits for their obsolete shareholders.  And this year's run twice as fast
as last year's.