Gilles wrote:
<<DBADGALT @[log in to unmask](DBSETTYPE<>"D" AND DBSETENTRIES>1 &
AND DBSETFULLNESS>0.8),0.6>>
This is a small point. We used to have a similar check in a regular database
monitoring job. However if you have any Jumbo datasets DBSETTYPE<>"D" will get
you more than just master datasets. It will get you useless listings of all of
the chunks of the Jumbo datasets that you have. Instead we use the following to
focus on master datasets:
LISTF @[log in to unmask]@( (DBSETTYPE = "A" OR &
DBSETTYPE = "M") AND &
DBSETFULLNESS > .65 AND &
DBSETCAPACITY > 1), DB
Since we want to keep masters from reaching 80%, we check for 65%.
===================
Leonard S. Berkowitz
Perot Health Care Systems
(Harvard Pilgrim Health Care account)
voice: 617-509-1212
fax: 617-509-3737
pager: 781-226-2431
Gilles Schipper <[log in to unmask]> on 11/27/2000 04:04:56 PM
Please respond to Gilles Schipper <[log in to unmask]>
To: [log in to unmask]
cc: (bcc: Leonard Berkowitz/CORP/HPHC)
Subject: Re: [HP3000-L] Adager
In general, 80% is a good rule, but ....
You probably want to fine-tune that rule a bit so that it better handles
the different requirements for different kinds of datasets.
For example, in general, it's much better to allow more "free space" for
masters, since performance could be a serious issue for undersized masters.
For details, it is much more important that you can always add one more
entry. The larger the number of entries in the detail, the smaller the
percentage of "free space" necessary.
The combination of Adager and Vesoft allows to create an intelligent job
that sizes your datasets according to it's characteristics.
For example,
!JOB DBMCAPJ,MGR.SYSTEM;INPRI=13
!RUN MPEX.PUB.VESOFT
DBADGALT @[log in to unmask](DBSETTYPE<>"D" AND DBSETENTRIES>1 &
AND DBSETFULLNESS>0.8),0.6
DBADGALT @[log in to unmask](DBSETTYPE="D" AND DBSETFULLNESS>0.8 &
AND BETWEEN(DBSETENTRIES,2,19999)),0.75
DBADGALT @[log in to unmask](DBSETTYPE="D" AND DBSETFULLNESS>0.85 &
AND BETWEEN(DBSETENTRIES,20000,199999)),0.8
DBADGALT @[log in to unmask](DBSETTYPE="D" AND DBSETFULLNESS>0.95 &
AND DBSETENTRIES>=200000),0.9
EXIT
!EOJ
Replace PROD with the appropriate account containing your production data
bases.
Of course you may need to adjust this job to deal with any specific
circumustances according to your needs.
In other words, YMMV.
At 10:16 AM 2000-11-27 -0500, STEPHEN HUNTER wrote:
>Hello all, I would like some help with some info on the Database Tool called
>ADAGER.. I am familar with a product called Flexibase, but this is my 1st
>exposure to ADAGER. My question is this: Currently, the operators that I
>have just taken over, will run an Adager on ANY dataset that shows up as 76
>to 80 % full(They get these figures from running a capacity program that
>shows the percentage of each dataset)
>
>This HP system is running MANMAN as a front-end.. I find this very curious
>that one would run Adager on ANY Dataset that is 76 to 80% full. Is this
>comment practice?? If not, what is a good measuring tool as to when to run
>the Adagers on these datasets??
>
>Any help is greatly appreciated...
>
>Thanks...
>_____________________________________________________________________________________
>Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com
---------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP3000 & HP9000 System Administration Specialists
300 John Street, Box 87651 Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000 Fax: 905.889.3001
Internet: [log in to unmask]
---------------------------------------------------------------------------
|
