Flat files can have multiple members - just created one like that. Does that affect how you might do this?

DSPFD will give the members for flat files or otherwise. Is the customer already using the *OUTFILE option of DSPFD?


On 8/4/2014 10:51 PM, Richard Schoen wrote:
Thanks all for the feedback.

Part of the reason for this request was we had a customer asking about listing PF members because they store EDI multimember physical files and said it takes hours to list them out.

If they are flat, then the question sounds moot.

If not it sounds like Robs technique might work.

It seemed to me there had to be a better way than DSPFD.

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-736-5800
F: + 1 952-736-5801
RJS Software Systems | A Division of HelpSystems


message: 6
date: Mon, 04 Aug 2014 17:45:41 -0500
from: CRPence <CRPbottle@xxxxxxxxx>
subject: Re: Need to get quick database member list for multimember

On 04-Aug-2014 17:05 -0500, Richard Schoen wrote:
Interesting though that a PF created by CRTPF with no DDS source
member doesn't register in the list.

With no DDS source, then Record Length (RCDLEN) is specified and the
File Type (FILETYPE) is either Data (PF-DTA) or Source (PF-SRC). The
former type is a flat-file, and the latter is a special variant of a
flat-file with an actual [rather than pseudo] external description that
is called a Source Physical File.

The SQL catalogs are for the SQL so they need not track that which
the SQL does not support; /flat files/ have very limited support, and no
support via the catalogs. The SQL supports only that which is
considered "relational", and what is in a permanent library [SCHEMA].
The DSPFD SYSPSTAT likely shows some selection criteria, similar to
SYSTABLES, whereby there is a predicate in the WHERE clause explicitly
including rows only where DBXREL='Y'.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page