× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hello all,

Have come across situation on a 6.1 box where the database members for the
performance collection files does not match the the collections shown in
DLTPFRCOL

Performance collection is creating the management collection objects
*MGTCOL and the data is being copied to the performance data files with a
new member for each collection period.

If I look at the member list for these files I can see one member for each
date going back a couple of months.

If I use the DLTPFRCOL command with *SELECT I can see a list of
performance collections for each day.

My problem is this list does not match the actual members in the database
files. And no, the members have not been removed from the database
manually.

If I try and delete a performance collection using the DLTPFRCOL command,
I receive the message that the collection cannot be found and the
collection for that date is not removed.

Also there are some collections from years ago showing as ** IN USE **
which I am fairly sure is not true.

I would expect there is some way to rebuild the database files or
preferably re synchronise the performance collections to what is actually
in the performance files.

I searched the archive on DLTPFRCOL and found nothing.

Can't log a PMR as they do not have extended 6.1 support BUT upgrade to
7.3 is now approved for earlyish next year.

Any suggestions ?

TIA

Don Brown


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.