RE: 250 libraries. a solution?

["York, Albert" <albert.york@xxxxxxxxxxxxxx>]

Actually, the scenario you are describing is a good argument for the way IBM
designed it.

The legacy application would still work fine (since it still has less than
26 libraries)  and the new application (with more than 25 libraries) would
work too. The library lists could be controlled with job descriptions, if
needed.  The only problem would be if the legacy application needed to
interface with the new application. However, that would require programming,
which would eliminate the original problem.

Albert York     


        -----Original Message-----
        From:   barsa@barsaconsulting.com [SMTP:barsa@barsaconsulting.com]
        Sent:   Wednesday, May 30, 2001 8:40 AM
        To:     MIDRANGE-L@midrange.com
        Subject:        RE: 250 libraries. a solution?


        >If you stick with 25 or fewer libraries in the user portion of the
library
        list
        >you won't have an issue.

        And if one of your vendors decides to move to 26+ libraries?

        >There is also a serious question regarding application design if
you need
        more
        >than 25 user libraries.

        Ain't THAT the truth!

        All in all, I can't envision any other way IBM could have approached
this
        change.  All library list related code is broken and needs to be
fixed and
        that's that.  Y2K has weeded out most of the companies without
source code
        and there just aren't that many places in a normal application where
you
        manipulate the library list.

        I respect Al Barsa, but I don't understand the level of his alarm on
this
        topic.

        Here's the problem.  You have software that works perfectly well
today, but
        you have any of the following conditions:
           No access to source (i.e.: the source is not retrievable)
           No SEU
           No skills or time to fix the problem
           A design that calls for putting the library list in a data area
(as I
           have seen many vendors do).  The maximum size for a data area is
2000
           bytes.
           A design that calls for putting the library list, library by
library in
           fields in a physical file.  (Hey, it's not my design, I just fix
it for
           a client.)

        Now you purchase package that requires that you turn off the switch.

        New you're @#$%ed.

        This is the reason that I have asked IBM for a job level switch.
Large
        customers and good vendors have all of their source.  In the real
world,
        that's another situation.

        Al

        Al Barsa, Jr.
        Barsa Consulting Group, LLC

        400>390

        914-251-1234
        914-251-9406 fax

        http://www.barsaconsulting.com
        http://www.taatool.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
        +---
+---
| 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
+---