Re: Controlling subsystem, Was: PTF install questions

I have not seen any issues with other installations. The OEM software outfits that require a change to the system library list make me really, really, really nervous since they clearly don't have processes that are well tested and rely on a very specific environment.

I have never seen an issue with an IBM upgrade, installation, or PTF application. IBM tests their stuff way to well to have something like a library in a library list get in the way.

Assuming you don't need a routing program, job queue, job description, etc in the installation that might be in those libraries I don't see a reason they could not be removed, that said, they are there for a reason and really should not inhibit any software install. BTW: I also tend to put all my security programs and registered exit point programs in those libraries as well.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 8/29/2013 8:33 AM, Jim Essinger wrote:

Jim,

Thanks for that explanation. I will have to contemplate this for our
installs. I like some of the ramifications and advantages this brings.

I have looked at installs that ask to have removed any libraries in the
system library list other than qsys and qtemp. Have you seen issues with
those type of installs, or are they mostly IBM upgrades?

Jim Essinger
--
Western Power Sports


On Thu, Aug 29, 2013 at 6:14 AM, Jim Oberholtzer<
midrangel@xxxxxxxxxxxxxxxxx> wrote:

> Regularly. Disadvantage: you have to create it. OK that's three
> minutes and about five commands. Advantage: Call it what you will, and
> if you have other things you want the controlling subsystem to do you
> can do that without destroying the IBM supplied subsystem. At upgrade
> time it also avoids having to redo any customizations you made to the
> IBM supplied subsystem since it will not be over written by IBM.
>
> If you really want to, you can just create a duplicate of QCTL and call
> it what you want as well.
>
> Word of caution: It's best to create a library to hold all of your
> custom system level objects in it (such as a custom controlling
> subsystem, job descriptions, classes, routing programs etc...). I
> usually call the libraries PARTITION for partition level objects and
> SERVER for objects that are common to all partitions on the system.
> I'll change the system library list to have PARTITION and SERVER before
> QSYS at the top of the library list so your objects get picked up before
> the IBM objects do if you happen to name them the same. While your
> custom objects could go into QGPL or QUSRSYS why not keep those
> libraries clean and create your own?
>
> Remember at when doing an upgrade or initial install there are a couple
> of other IBM supplied subsystems that are temporarily used as
> controlling subsystems. DO NOT mess with them. First off there's no
> need and secondly you'll find installation processes don't run as expected.
>
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects
>
>
> On 8/29/2013 6:55 AM,rob@xxxxxxxxx wrote:

> > Well, I guess there's probably an infinite number of possibilities for
> > controlling subsystems. Well, not really. It's probably limited to the
> > number of legitimate subsystem names you can create with 10 characters or
> > less.
> >
> > Anyone use anything different for a controlling subsystem than QBASE or
> > QCTL?
> >
> >
> > Rob Berendt
> > --

> --