RE: /Qsys.lib/.lib/ path? -- MIDRANGE-L

Subject: RE: /Qsys.lib/.lib/ path?
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Wed, 27 May 2015 13:00:58 -0500
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I'll give that a go next month when I do PTF's.

Thanks guys

-----Original Message-----
From: rob@xxxxxxxxx [mailto:rob@xxxxxxxxx]
Sent: Wednesday, May 27, 2015 11:29 AM
To: Midrange Systems Technical Discussion
Subject: RE: /Qsys.lib/.lib/ path?

Ok, now we're getting somewhere.
So what we're looking at here is NOT just a difference between /qsys.lib objects and 'stream file' objects.

I'd start out with the RCLOBJOWN command as that would be the least disruptive.

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: /Qsys.lib/.lib/ path? , rob

This mailing list archive is Copyright 1997-2025 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.