|
>Peter, Dean, (et al), > >In a message dated 98-04-16 11:06:34 EDT, you write: > >> Having a library in front of QSYS is not a big problem. However, a >> software provider has to provide the ability to remove the objects in this >> library if the user desires by taking an option from a menu. The product >> still should be able to function, maybe not all functions but should give >> you the major portion. That should be documentated. > >Have _NONE_ of these vendors heard of the "Product Library" option for >commands and menus? It puts the library in question either above or below the >current library (can't remember which), but _below_ QSYSLIBL. If the vendor >requires multiple libraries, and is obnoxious enough to force them into >QSYSLIBL, they could just as easily hardcode anything in the product library >to specifically refer to the other library names... > Product library only works if the commands are not also in QSYS. While I am not familiar with Help Systems product, I assume they put a library in front of QSYS to intercept certain commands with their own copy. The problem is not the modification of QSYSLIBL. The problem is not telling the customer BEFORE installation that QSYSLIBL would be modified. Even worse, putting a library in front of QSYS to which the public has *CHANGE authority creates a very serious security exposure. This should NEVER be permitted. Charlie Massoglia, Massoglia Technical Consulting, Inc. PO Box 1065, Okemos, MI 48854, USA 517-676-9700 Fax: 517-676-1006 EMAIL: cmassoglia@voyager.net +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.