Subject: | |
From: | |
Reply To: | [log in to unmask][log in to unmask], 9 Jun 1998 18:54:16 +0200435_us-ascii Today I created a web interface to extract the data out of Scope/UX (the Scope/iX ported to HP9000's). Currently I have three reports: * Global CPU Utilization, * the same but as Histogramm ... and coloured (!), * Application report. The setup & definition of the reports is very site-specific (=matches our Unix needs) but if somebody is interested in the scripts behind please let me know. [...]37_9Jun199818:54: [log in to unmask] |
Date: | Mon, 8 Jun 1998 08:05:21 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
I have used RoadRunner for years and I can not believe what I am reading.
You have documentated that these issues work and yet they don't ? I also
will be using the Jumbo datasets and b-trees, but now it looks like I will
have to find another back up utility other than RoadRunner. I see that the
support that we pay is not going to the support of the product.
-------------
Original Text
From "Paul H. Christidis" <[log in to unmask]>, on 6/5/98 10:26
PM:
To: iSMTP Gateway@City_Hall_1@Servers[<[log in to unmask]>]
Fellow Listers,
I just installed RoadRunner 4.7.1 and tried to see if the 'dbstore'
parameter had been 'fixed' to include 'jumbo' and 'b-tree' datasets when
selecting a database. To my disappointment it has not. I placed a call to
Tivoli and I must say that the responses were not very encouraging. They
indicated that they had my request for enhancement but they only had 2 more
sites that are using 'jumbo' datasets and thus not enough 'pressure' was
being exerted to 'invest' in the enhancement.
Based on the mail traffic that I've observed I've concluded that there
is
a substantial number of list members that are using RR. I must also
conclude that many of them are not aware of the problem with the 'dbstore'
parameter. Perhaps not many sites are using 'jumbo' datasets but many
sites
will be using 'b-tree' sets since now they are available on turboIMAGE.
Now missing a 'b-tree' dataset is not as serious as missing a 'jumbo'
dataset, since the 'b-tree' can be rebuilt from the existing data, but
still
one has the potential inconvenience and waste of time while trying to debug
problems caused by a missing dataset or while regenerating the 'b-tree'
sets.
I'd like to enlist the support of every RoadRunner user in this list and
'flood' [log in to unmask] or their 1-800-848-6548 number with demands on
'fixing' the 'dbstore' parameter to function in a manner consistent with
their documentation.
Regards
Paul H. Christidis
|
|
|