Re: qgpl

QGPL has many IBM objects in it that get used by processes that run on behalf of your applications by IBM. While it's not impossible to remove it from the library list, it might be troublesome to do even if your application does not use it. You'll have to get all the job descriptions set up so they can find it, effectively putting it back into the list anyway.

If you keep QUSRSYS and QGPL in it's IBM delivered state, meaning only objects IBM creates (and not all the junk that usually winds up there) then what's the objection to having it in the library list? First try putting it at the very bottom of the user portion of the list. If that continues to work without issues then you can try to remove it, but I keep going back to why.

One process that most likely will not work with out QUSRSYS and QGPL in the library list, PTF application, particularly if your using image catalogs. True you as an admin can add it as needed but it still sounds problematic to me.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 2/20/2013 6:27 PM, Porterfield, Sean wrote:

I won't answer "should", but we have it in our library list regardless of test/prod/whatever. It's below our application libraries, to make sure we have the correct test/prod/whatever objects first.
--
Sean Porterfield
________________________________________
From:midrange-l-bounces@xxxxxxxxxxxx [midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of A Paul [amandapaul1@xxxxxxxxxxx]
Sent: Wednesday, February 20, 2013 19:23
To: Midrange Systems Technical Discussion
Subject: qgpl

Just looking for some opinion here whether QGPL should be part of the user library list(for test environment), I believe it can invalidate tests and can have other impacts.
I know IBM created QGPL to contain some objects that are necessary for the system to perform effectively.
--