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



Nonetheless, that it an IBM supplied library that has to be in the System
portion of the library list. IBM owns the object names in there so if your
applications use the same names, then the application needs to be corrected.
It's likely the source of the problem was the DB/2 group. QSYS2 is where
quite a bit of the enhancements and new functions that IBM delivers for DB/2
goes.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Gqcy
Sent: Monday, February 09, 2015 10:17 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: should QSYS2 be in system portion of Library list?

I don't think this is a memo to users issue...
I am on 7.1 (been here for 2 years), and this occurred this month when I put
on TR8 or DB2 group level 32.



On 2/9/2015 9:58 AM, rob@xxxxxxxxx wrote:
QSYS2 should be in the system portion of the library list.

I am sure that somewhere WAY BACK there would have been a Memo To Users
that would have warned you that this was going to be added to the system
portion of the library list when you upgraded to release x.y.z and you
should plan accordingly.

Yes, there will be a lot of objects that do not begin with Q. You can see
many of them here:

http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_72/db2/rbafzcatalog.
htm?lang=en-us


Rob Berendt


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.