|
On 10/31/05, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx> wrote: > > Why not just run the CLRPFM CL command prior to the SQL statement? Yep, can definitely do that. Just nice to know if it can be done in SQL. I'm running multiple SQL statements in a source member via RUNSQLSTM and it would just help to ensure that the files are cleared before the SQL runs. If someone were to use the RUNSQLSTM standalone without clearing these particular files first, it'd be like running Al's MAKEAMESS command. Alternately, you could use OPNQRYF/CPYFRMQRYF, which does have > CRTFILE(*YES) and MBROPT(*REPLACE) options. Surely you jest! OPNQRYF when you've got SQL?!?!?!? No, just kidding. I'm a big fan of OPNQRYF and I remember thinking what an awesome tool it was when I migrated from the s/36 eons ago. Thanks for the suggestion, but I'd probably go with your first suggestion. - Dab
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
