RE: SYSLIBL for a SUB System

I think your best option here is a combination of things. First off, what
you are most likely after is any job that runs in this subsystem has a
modified system library list from the system value.

Remember that any job that comes into a subsystem needs a routing step.
Archetypically the routing program is QCMD but it can actually be any
program as long as it performs the three basic functions that are needed.
(1) Set the attention program if needed, 2) call the initial program on the
user profile (if interactive) 3) go to the initial menu on the user profile
(if interactive)).

The routing step also sets the subsystem memory pool, and class to be used.

Now if the routing step were to call a CL program that also reset the system
library list, then all the jobs running in that subsystem would then use
that system library list instead of the one supplied in the system value.
Clearly that program will need to run with adopted authority, but be careful
not to propagate it.

Problem solved without having to change a single program. Also the fix can
be applied to any subsystem thereafter and by using routing data you could
have hybrid subsystems that run both types of jobs.

Work management 101. See my PowerUP18 presentation: Optimizing IBM i Work
Management. (If you attended the conference)


--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Mohammad Tanveer
Sent: Friday, August 24, 2018 9:38 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Re: SYSLIBL for a SUB System

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.
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
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 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