|
1) Ok, now I get your comparison to RTVDDSSRC. 2) Yes, you can get SQL to generate a file created from DDS. After all, once the file is created who cares how it was created? The cool thing about the SQL is when you do the DSPFD you actually see the SQL statement used to create the statement. 3) Bummer about you supporting so many old releases. I did a summer at a printing company. People were proud of their 40 year old presses. No new equipment anywhere. Seems that other divisions got the new stuff to the point that this division was closed down. They're scheduled to implode the building. 4) As far as I know any IBM customer can submit a design change request. Some get accepted, some do not. That SQL precompiler is a special issue and currently I am going over the heads of the people who deny any fixes. I'd like to leave that quiet for now. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Dan Bale" <dbale@samsa.com> To: <midrange-l@midrange.com> Sent by: cc: midrange-l-admin@mi Fax to: drange.com Subject: RE: QUERY TO SQL 03/19/2002 01:52 PM Please respond to midrange-l Rob, sorry I've been running my mouth, errr I mean, fingers, for most of the day today. Someone cut me off on the way in today, so I must be venting (or something). To answer your questions, the RTVDDSSRC reference was Buck's, as he was comparing his home-grown RTVDDSSRC to IBM's RTVQMQRY, in terms of the output only being a starting point and not necessarily a final product. My opinion is that IBM should have put forth the effort to generate equivalent SQL from RTVQMQRY. Regarding OpsNav, sure, when I get to V4Rsomething. Still, that's great to know. Does the file you generate the SQL from need to be created from SQL? Or can it be a DDS file? >submit a design change request You seem to be the reigning master at this, Rob! Seriously, can *any* AS/400 customer submit these? I seem to recall a time when you had to be a Consultline (?) subscriber or somesuch before IBM would listen to you. The link you provide seems to ask only for an IBM customer number. Also, I guess it would help if I weren't stuck on V3, eh? Rob, I'd be curious to know how many design change requests you've made and, of those, how many IBM has implemented. It seems to me the the SQLRPG preprocessor has been an issue for ages now, and I've not heard that IBM has addressed it yet. Surely more than a few people have issued design change requests for that? Dan Bale SAMSA, Inc. 989-790-0507 DBale@SAMSA.com <mailto:DBale@SAMSA.com> Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of rob@dekko.com Sent: Tuesday, March 19, 2002 1:29 PM To: midrange-l@midrange.com Subject: RE: QUERY TO SQL Dan, I spot several meanderings here. 1) RTVDDSSRC a) What does that have to do with *QRYDFN's? b) There is a tool in Op's Nav called 'Generate SQL' which will give you the sql to recreate the file. Also, if you just want to add a field or something you can do it there. 2) RTVQMQRY As someone suggested - submit a design change request, don't preach to the choir http://www-912.ibm.com/s_dir/slkbase.nsf/1ac66549a21402188625680b0002037e/3c a7d5dfc681aa86862565c500526323?OpenDocument&Highlight=0,5314847 Rob Berendt _______________________________________________ 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/cgi-bin/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.