Library QGPL Best Practice Usage

0 pts.
Tags:
DataCenter
Development
Should production Applications use QGPL to store objects and what should be put in QGPL ?
ASKED: December 14, 2006  2:31 PM
UPDATED: December 19, 2006  10:29 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

QGPL (General Purpose Library). I have been in shops that use it an others that don’t as a matter of course.
Upgrades can be an issue, but as a system administrator, my biggest concern is cleaning up old objects. And its not always clear what is system and what is user in QGPL.

So its a matter of personal preference.

Discuss This Question: 3  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • WickedWoman
    My opinion: no. Product applications and files should be in libraries identifying them as such. QGPL (general purpose library) should not contain product/application software, so that manipulation of the library list does not require removing QGPL. Some companies use it for outq's, profiles, stuff that needs to be accessible regardless of the application environment. Do note that if a bound ILE program is created and the library not specified it will default into QGPL, not CURLIB.
    0 pointsBadges:
    report
  • DHanneman
    I'm of the opinion to place common use objects (Output Queues, Page segments, overlays, commands, etc...) in QGPL. However, I would not put any locally developed code or data in QGPL to avoid versioning or leveling issues with legacy systems.
    200 pointsBadges:
    report
  • Jcvaug
    My best practice: leave it alone. You need to create your company's GPL (and name it that way). I usually also create a company's OPS (for operations) and dedicated company library per application. This way, you are in total control of the environment. IBM can change anything in QGPL, and you don't care. Your "compGPL" will contain profiles, outq, etc... that are general in nature for the system. The library "compOPS" will contain all program you develop for operations (like special saves, last IPL date, etc...). This is YOUR library. Then, each application will have its own libraries. Good luck in your projects.
    15 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following