|
John, Al, FRFs, REF, REFFLD: While I agree with the concept, I will admit that I am not a big fan of these as they are implemented on the AS/400. I have ranted on this topic before here on this list. It basically boils down to this: When editing the DDS for a physical file, I have to scan the FRF/REF source to see the "real" definition. Not a big deal for one or two fields you have to modify or add, but for entire files, it can be extremely time consuming. I have never seen a well-designed FRF. Multiple field definitions that define essentially the same element, hierarchy defined by placement in the source, inability to keep all field definitions in a single FRF because of PF restrictions of number of fields (see JDEdwards). I have a concept that I should have developed a little earlier in the AS/400's life cycle: There should be no edit-able source for PF and LF file definitions (and I'm not talking SQL QMQRY source here either). One table would exist in an environment that would define ALL files & fields - this would not be an FRF, but rather a file like, um, well think along the lines of the QWHDRFFD format that IBM supplies for the DSPFFD outfile. This would be maintained by an interactive application that would make it easy to use REFFLDs so you can see the definition, kind of like the JDEdwards DD application. Still a rough draft, but doable, I think. I'll invite you all to my grand opening when I get it done. <g> Dan Bale IT - AS/400 Handleman Company 248-362-4400 Ext. 4952 -------------------------- Original Message -------------------------- D.BALE@handleman.com wrote: > Is it my impression that SQL can define a database file with all the > attributes available to us in DDS, both PF & LF? I understand that DDS has > only a subset of the attributes that can be defined in SQL (as of V4R5?). So > my question is whether I lose any functionality by defining a database file > using SQL vs. DDS? Dan REFFLD(xxxx), REF(xxxxx) Thoses are big omissions in my opinion. John Carr +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.