×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Do you consider it a design weakness/limitation that all other libraries are one level deep under QSYS? QSYS is the only library that can contain other libraries. This is by IBM's design.
If you want to mimic the structure of other libraries nested within libraries, e.g. QTEMP, SECURITY, PRODATA, PRODCOMMON, CUSTOMOBJ, PRISTINEOBJ, QGPL, just use library lists. The library list provides that capability, up to 250 libraries in a list.
Specify one list of libraries for production, another list of libraries for Test, another list of libraries for Development.
Many single-LPAR machines provide Production, Test, and Development environments by using different library lists.
If IBM's design of QSYS and its child libraries is a limitation, what examples of application software providers can you point to that have said, "we gotta have libraries nested within libraries and therefore we choose [name-the-operating-system-and-database]
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: separate DEV, TEST, & PROD environments survey, (continued)
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.
midrange.com
