|
Hi, I copied an IBMer on the note, and apparently QSYS2 changed from an *IBM library to an *ALLUSR library over at V5R2. I don't understand. What are these yahoo's thinking. This will @#$% up everybody's custom save/restore code, including mine. This is a system that's supposed to preserve your investment in code. This isn't as bad as changing the length of the library list, but it does suck. What they should have done was to have added an attribute to a library with DSPLIBD to an output file (which DSPLIBD doesn't currently exist) to indicate if it's an IBM or a USER library. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com "Chuck Lewis" <clewis@iquest.net> To: "'Midrange Systems Technical Discussion'" <midrange-l@midrange.com> Sent by: cc: midrange-l-bounces@m Subject: RE: QSYS2 idrange.com 02/06/2003 08:02 PM Please respond to Midrange Systems Technical Discussion Al, At my last job we had gone from a S/38 through a TON of AS/400 models, finally on a 530 and a 500 (510 ?) when I left 5 years ago. QSYS2 was on there but I have NO IDEA at what point it "came aboard" or from whom. We were using many modules for S2K and I know they did some stuff with it. But it seems like some of SSA's Alliance Partners did too (?) We are on a 620 where I am now and there is no QSYS2... If YOU don't know Al, I'm really worried :-) Chuck -----Original Message----- From: midrange-l-bounces@midrange.com [mailto:midrange-l-bounces@midrange.com] On Behalf Of Al Barsa Sent: Thursday, February 06, 2003 7:26 PM To: midrange-L@midrange.com Subject: QSYS2 Hi, In my last note, I determined from the help from SAVLIB *IBM that QSYS2 is not an IBM library. This comes to me as a surprise. Any comments? Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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
