× 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.



You need the output of both DSPFD (Display File Description) and DSPFFD
(Display File Field Descriptions). The first will give you the key fields,
the latter will give you the fields in each based-on file.

Keys can be different between the files that make up the logical. The
requirement is that they are in the same order from left to right. You can
have gaps, using the *NONE keyword in the field name.

Each component physical can be defined with a subset of and with calculated
fields. Use DSPFFD on both the logical and its constituent physicals, to
see if they are the same. If the same, just leave out the fields in the
logical DDS. Derived fields will be identified and have the formula shown.

You could also use ANZDBF and ANZDBFKEY to get the key info into one
report, including the SELECT/OMIT, if any, and SORT order, etc.

Look at all the attributes of the key fields, in order to get everything
you need.

Luck on you.

At 09:41 AM 4/11/02 +0100, you wrote:
>Morning all,
>
>Is there an easy way to retrieve the source for a multi-format logical?  I
>need to change one of these but don't have the source and haven't created a
>multi-format logical before.  Do all the key fields have to exist in all
>record formats?  I know I can get the information on which formats and key
>fields are used from DSPFD and try recreate it that way, I just wondered if
>there was a shortcut.
>
>TIA
>
>Martin
>



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.