ca.portal.admin

DASD Upgrades

Discussion created by ca.portal.admin on Feb 4, 2009
Latest reply on Feb 4, 2009 by ca.portal.admin
Our service provider announced plans to upgrade DASD hardware from mod-3
(3,339 cyl) to mod-L (32,760 cyl). =20

Currently we have many multi-file areas with some exceeding 50 files.
The general approach is to keep allocation down to roughly 12,500 tracks
(quarter volume) for each file. I was told this allowed for flexibility
when having to perform these migrations (and there's probably other
reasons) but I'm not convinced this is a good way to manage our database
files.

Would it be practical to allocate DB files to the volume's maximum size
when necessary? Any general rules to follow when allocating large
areas?

TIA,
Brian Hirman
R16.0 SP4 z/OS 1.9

=20
"
IDMS 3rd-party providers forum
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP
IDMSVENDOR-L@LISTSERV.IUASSN.COM
IDMSVENDOR-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: DASD Upgrades
"One more area of concern is disaster recovery. If your recovery site
does not have the same dasd, you could be in a bind. By keeping to the
smaller sizes you can prevent a problem.


Will Hathcock
Database Administrator
(719) 495-6177

We are what we repeatedly do. Excellence then, is not an act but a
habit. - Aristotle

Outcomes