Re: 250 libraries again (was V3R1 QUSRTOOL, *PRDLOD)

["James W. Kilgore" <eMail@xxxxxxxxxxxxxxxxxxx>]

Joe,

When you mention: legacy, no source code, no support, in one sentence
then state: new software from vendors forcing the use of longer library
lists, I have to ask:  are you in the sad situation where you have one
very old application from a road kill vendor, in conjunction with a
newer, supported, application that is "forcing" the use of longer lists?

Maybe this should be a topic for a survey.

How many folks are out there with missing source code where the vendor
(or an in house accident) prevents you from retrieving the source,
modifying the source -and- the application is doing something "cute"
with the library lists?

I'm really ignorant about application suites like JBA, never had the
pleasure of meeting their acquaintance, but what prevents an
installation from taking their gazillion libraries and just doing a
MOVOBJ into a single consolidated library?  Do they qualify the object
names?  Did they bury and continuously repeat the "cute" library list
code in a whole bunch of CL programs so that you could not replace a
single command with a "no-op"?

How bad is it out there?
+---
| 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
+---