|
It's my opinion that those who asked for this are: 3. CUSTOMERS dealing with third-party applications that each assume that they're the only software on the system. Vendors have been writing their library list hogs for years and haven't felt any pressure to clean things up. As a customer, if I run afoul of the 25 library limit because I'm trying to integrate two or more software packages (as well as in-house development) I'm stuck because the vendors won't support my integration issues. They'll only guarantee that their applications will stay within the 25 library limit while running "vanilla". Yep, application design is the problem. Still, AS/400 customers want or need more than 25 libraries in the user library list because they can't get all their applications to run well together. Or, they can't get them to run without hacking out a whole bunch of CL's to swap library lists and explicitly override files. Most of us bought third-party solutions because we didn't want to do a lot of programming. I wonder how many of these RTVJOBA CL's are actually being used to circumvent the 25 library limitation. My first choice for a solution would be to get every application vendor to use intelligent, graceful library structures. It would be nice to see one data library, one executable library, and one source library per application. It would also be nice to see intelligent and consistent use of the product library. Perhaps we could see more applications use the equivalent of an Oracle SID, so that the data library is defined into an application variable (data area or LDA?) and retrieved for qualified file overrides. I'm obviously not going to get my first choice. I'm glad IBM gave me my second choice. -Jim James Damato Manager - Technical Administration Dollar General Corporation <mailto:jdamato@dollargeneral.com> +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@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-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.