RE: Large library lists...

> You could have set up an "extended library"  that
> would have sat below the user portion of the library
> list.  This would have broken no code, and given
> everybody exactly what they wanted.

How would this work exactly? Would it be an object that contained an
extension to the library list? I can see that this would stop the legacy
code from actually falling over, but the code wouldn't be able to touch the
extended library, so it might proceed under the incorrect assumption that
it has a strictly limited library list. Arguably this is worse than making
it fall over.

Today you have five library lists (believe it or not)

1).  Language library (1 library - specified with the [secret] SYSLIBLE
parameter of CRTSBSD/CHGSBSD)
2).  System portion of the library list (15 libraries - specified by the
system value QSYSLIBL or the CHGSYSLIBL command)
3).  Product libraries (2 libraries - propagated in a "pop the stack"
method PRDLIB parameter of CRTCMD/CHGCMD)
4).  Current library (1 library - specified by CHGCURLIB command or the
CURLIB parameter of CRTCMD/CHGCMD)
5).  User portion of the library list (25 libraries - specified by the
system value QUSRLIBL, by INLLIBL parameter of CRTJOBD/CHGJOBD,
ADDLIBLE/RMVLIBLE commands or by the CHGLIBL command)

My proposed "extended library list" would have been a sixth library list
tacked onto the bottom.

HO, HO, HO

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