If you are having this problem it may be possible to isolate the particular application and, more importantly, the component which is giving you problems, in a special directory like /opt/<essential package name> which MAY fix the problem since the aplications which are generating errors will HOPEFULLY no longer be aware of its existence. This depends on several factors, most particularly how well these applications were designed. If you can control how the various load modules are located through environment variables or a configuration script of some kind you're probably home free. If, however, locations of needed files are hard-coded you will need your vendor's support on this issue.
As to whether your vendor is wrong, it depends on what question you're asking about. If you mean: Is my vendor wrong about this being the only supported solution? The answer is NO, they aren't, they know what they support and undoubtedly have their reasons. If you're asking whether the reasons are any good, the question is harder to answer. You might want to ask your vendor for some explanation about why they are using an outdated package that conflicts with current configurations from your z/Linux distribution. You may also wish to consider looking for a vendor who provides a product which uses up-to-date components. Especially if you're paying. Erik Johnson On Tue, Feb 3, 2009 at 9:53 AM, David Boyes <[email protected]> wrote: > Background: > > Upgrading a system to current level. Have a vendor product that insists on > the installation of a backlevel component application that causes the > configuration and service management system to report errors in the > configuration. Vendor insists that the backlevel component is the only way, > but the errors cause problems with future upgrades and overall configuration > management by reporting false positives when checked for whether the system > is up to date and has all service applied. > > Question: > > I believe the maker of the vendor product is in error here. Am I wrong? > > -- db > > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
