Re: System library list

One common complaint is that it's easier to put a trojan in there.
Perhaps, but not having it in the system library list doesn't make your
system inherently secure.

Many people get around this by using "initial programs" to set their
library list. This worked well in the days of 5250, but doesn't do dink
for scheduled batch jobs, client server and other type of connections. A
job description with a valid library list, assigned to each user, might be
better.

Others mentioned the lock issue. Ok, if 95% of your users are using
ERPLIB anyway then you're probably not going to be able to do an update
midday regardless if it's in their user library or system library portion.
The rub is with add on products. For example, ZipCity. Having their
library in the library list of all jobs will prevent you from putting on
an upgrade midday (I used to do upgrades midday when we were running it).

Rob Berendt