|
Hello Mark, You wrote: >1) Is there a way to "convert" a regular library into an SQL >collection? Yes, but it is a manual process. Make like CREATE COLLECTION: CRTJRNRCV lib/QSQJRN0001 CRTJRN lib/QSQJRN JRNRCV(lib/QSQJRN0001) STRJRNPF lib/file JRN(lib/QSQJRN) IMAGES(*BOTH) Create various SQL Views over the system catalogue files. See an existing collection for examples -- the only real difference is the library name in the SELECT clause of the view. Make like CREATE COLLECTION WITH DATA DICTIONARY: As above but also CRTDTADCT lib >2) If not, why not? Second-guessing IBM here: a) Because you should have thought about this when you created the library/collection. b) Because it doesn't really matter. Files can be processed using SQL or native I/O regardless of whether they are in a library or collection. c) You can easily write a tool to do this. Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 mailto: shc@flybynight.com.au \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
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.