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