|
Such as:REF(REFFILE) UNIQUE R ARCONTABR TEXT('A/R Consolidation Codes') COCODE R TEXT('Consolidation Code') COLHDG('Con' 'Cde') REFFLD(CODECONS)
Data dictionaries were, even before the S/36 and IDDU, all de rigueur. The iSeries is replete with data dictionaries, such as QSYS/QADBIFLD. Among other things, they provide the means by which one can locate where a field, is defined - often in more than one table.
There is a difference between a reference file (above) and a data dictionary. The reference file is used to define the attributes of a field: "Make this field look like this other field." A dictionary is a repository of all field definitions; the reference file is a subset of this repository.
midrange.com
* Jerry C. Adams
*IBM System i5/iSeries Programmer/Analyst
B&W Wholesale Distributors, Inc.* *
voice
615.995.7024
fax
615.995.1201
email
jerry@xxxxxxxxxxxxxxx <mailto:jerry@xxxxxxxxxxxxxxx>
Michael Ryan wrote:
You reference a Field Reference File by using the REF DDS keyword. You specify the name of the field in your file, and specify the field to be referenced in the REF keyword. On 1/18/07, Mike Berman <mikeba777@xxxxxxxxx> wrote:Is it that no one uses Data Dictionary anymore,if so why? Once I have the Dictionary created, how do I apply it to a file, by using the REF keyword? Michael Ryan <michaelrtr@xxxxxxxxx> wrote: A Field Reference File? It's basically a file definition (regular old DDS) that doesn't contain data. You just reference the fields. Check the DDS manual. As far as a data dictionary...I haven't seen one in 20 years. I wouldn't have any idea how to use it. On 1/18/07, Mike Berman wrote:Michael, I am not sure how to use this. Lets say I want to create a file. MYFILE MYFORMAT Fields are Company, Cust#, PO#. I created a Data Dictionary for this library, created Myfile and Myformat. Now do i add these 3 fields obviously there are more than that, do add each and every field that we are going to be getting from our EDI partner? Michael Ryan wrote: I wouldn't use that. Here's from the help: The Create Data Dictionary (CRTDTADCT) command creates a data dictionary. A data dictionary must be created before the user can use the Interactive Data Definition Utility (IDDU) to describe and create database files. The user can create a data dictionary with IDDU or with the CRTDTADCT command. More information is in the IDDU Use book, SC41-5704. IDDU? Not in this century. Here's from Wikipedia: A data dictionary is a set of metadata that contains definitions and representations of data elements. Within the context of a DBMS, a data dictionary is a read-only set of tables and views. The data dictionary is database in its own dictionary. Amongst other things, a data dictionary holds the following information: * Precise definition of data elements * Usernames, roles and privileges * Schema objects * Integrity constraints * Stored procedures and triggers * General database structure * Space allocations So it's more than a Field Reference File, though that would be a start. It's basically documentation that you want, right? On 1/18/07, Mike Berman wrote:HI, We have new file layouts to use in our EDI process and I have been told to create them, along with a Data Dictionary. I have never created one before and only used one very very briefly many years ago. I did a search in the archives but did not find much. As I am stumbling along on the Create Data Dict. command, I would love to see any examples of how to set one up. THe data is EDI PO that is coming to us in 6 separate files from a 3rd party VAN. They are calling these flat files. The fields, are all alpha. Do I enter all of the potential fields into the Data Dictionary? Or only the unique fields that will be referenced? In what ways are the Data Dictionary different from a Field Ref. file? Any and all help would be tremendously appreciated. Thanks, Mike --------------------------------- Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.-- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. --------------------------------- No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.-- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. --------------------------------- Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-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.
