|
Issue is SYSLIBL was setup by native people ages ago and they added some
libraries in it which were not supposed to be in it. Now we cannot change
it but there is a need to remove them; for setting up a new environment
(without creating a new partition)
We took care of it for green screen sessions by using TAATOOL command to
remove libraries from SYSLIBL.
For JDBC/ODBC connections we are thinking to write some database exit
programs to do the same but was wondering if there is a better/easy way at
SBS level, meaning whenever a user makes a connection they will be assigned
a different SBS and in that subsystem we can have a different SYSLIBL.
Regards
On Fri, Aug 24, 2018 at 9:26 AM Rob Berendt <rob@xxxxxxxxx> wrote:
SYSLIBL is system wide.list
USRLIBL is what you'll have to use. Or set up a job description for jobs
in that subsystem.
Now, if you want to spin up a new partition of IBM i and have the whole
subsystem run in that, that is a different story.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Mohammad Tanveer" <surgum@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx
Date: 08/24/2018 10:09 AM
Subject: SYSLIBL for a SUB System
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Can we have a different SYSLIBL for a SBS? We are creating a new SBS and
wondering if we can specify a different SYSLIBL for its jobs.
Regards
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.