RE: System library list

IMHO putting any user library in the system library list is a very bad idea.

The user library list is not really that limited any more (up to 250 entries), so that should not be a concern. The system library list is only allowed 15 entries.

Of more concern is the fact that you cannot change the system portion of a job's library list on the fly, so if you have a need to remove a library for whatever reason you can't do it if in is in the system library list.

You also can't put another library above anything in the system portion of a job's library list. This can be important if you have a multiple versions of an object in different libraries. An example of this is our third party software where we have done some customizing of programs. We put those customized programs in a "custom" library that has to be placed above the vendor's program library so that the customized program is the one that is run when a user selects it. (That's also assuming you don't have the library name hard-coded in the program calls.)

--
Thank you,
Ron Zimmerman


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Morgan, Paul
Sent: Thursday, November 17, 2011 9:54 AM
To: Midrange Systems Technical Discussion
Subject: RE: System library list

Richard,

Every job shares the system library list. If you have a library that must be in every job's library list then put it on the system library list.

If you have many job descriptions with library lists it can become difficult to modify every job description to add a new library. It's easier to add the library to the system library list. It could be an authority problem where someone can modify the system library list but can't modify the job descriptions.

The user library list is limited in length. You might have to add a library to the system library list to get around this limitation.

The system library list is above the user library list. Adding a library it to the system library list puts it above any other library on the user library list.

Paul Morgan

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Reeve
Sent: Thursday, November 17, 2011 10:02 AM
To: midrange-l@xxxxxxxxxxxx
Subject: System library list

     Does anyone have a good explanation of the ramifications and possibly the why's and why nots of placing user libraries in the system portion of the library list?  I just signed on to a client box and noticed many user libraries in the system portion of the list.  While it looked odd, I don't know enough about it to say that it's a bad (or possibly a good) practice.

     Any thoughts?
 
Warmest Regards,

Richard Reeve
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.