On Thursday, April 22, 1999 02:07, Shane Devereaux asks,

> I have noted the following some time ago. Our Solution providers still
> utilise KSAM/3000 and have indicated they feel that HP have labelled
> KSAM/3000 as non-compliant merely because HP do not want to
> go to effort of checking.

According to the HP database, KSAM/3000 is not and will not be made Y2K
compliant.  Whether this refers to CM KSAM, NM KSAM or both is not made
clear.  Comments from HP on this?

IMHO, there are several products which still utilize KSAM files instead of
an Image or Allbase database.  The number of products is dwindling however,
as more and more systems are moved over (or have been moved over) to use the
more robust Image database.

Until HP makes clear as to which KSAM is not being addressed (or are they
both not being addressed?), I don't wish to comment on your next course of
action... but if HP is not going to address either KSAM product (both
Compatibility and Native Modes), then I would be having some very serious
discissions with your software vendor and the management of your company
about what *might* occur less than 270 days from now, and possible
contingency plans.

Best Regards,
Joe Geiser

====================================================
Joe Geiser, President and Senior Partner
CSI Business Solutions, LLC
Phone: +1(215) 945.8100   Fax: +1(215) 943.8408
Toll Free (US/Canada): (877) 945.8100
====================================================