× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi

We use an empty PF for our data dictionary.
All our other PFs use this one file in its REFFLD declaration.


There are very srict rules. The dictionary is modified only by certain users
and a new zone or modification can only be done by a written request to
these users.

A zone has 5 letters : 2 syllables of 3 and 2.

In the referencing file we add a prefix for example :

A CMAJDT R REFFLD(MAJDT)


The same dictionary is used in our RPGLE. Each module imports the
definitions of the dictionary zones in a DS like this from a copy book.
D gDictionary E DS EXTNAME ( DICTIONARY )
D PREFIX ( DFN_ )
D BASED ( DFN_Ptr )
D DFN_Ptr S *


To declare a new zone in an RPGLE all that is needed is
D gStsMt S LIKE ( DFN_STSMT )

Which means gStsMt is the same as the zone STSMT in the dictionary.

This is very easy to use but makes for very long program compile lists and
increases the weight of the program object since the dictionary is declared
in every module.

The problem now is, the dictionary is full ! We can no longer add any zones
!

The solution proposed is to create a second PF ( like a volume 2 )

Replace the file DICTIONARY by a LF with the same name which points to two
PFs ( volumes 1 and 2). We will still be limited to using names of 6
characters.

Any other ideas ? How do others get round this? As we are gradually moving
towards SQL, I wonder how should we be referencing columns in SQL tables?

Thaks.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.