Re: Easy way to get file documentation

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

Must be part of Performance Tools. As shipped these were restricted to
QSECOFR or someone with *ALLOBJ authority. I was just looking at the V4R5
manuals.

You could do a DSPDBR, then DSPFD TYPE(*ACCPTH), then run an SQL join
against the 2 outfiles. That's basically what these commands do.

The first one runs DSPDBR for each of the libraries listed, to an outfile,
then runs reports against it, one from parent file perspective, the other
from dependent file perspective.

The second command takes files from libraries, according to the criteria,
and, I assume, runs DSPFD against each with the type(*accpth) parameter,
again to an outfile. This outfile does not get saved, so far as I know.
Then a couple reports are written, one with more detail and from the
perspective of the deoendent files, the other from the view of the parent file.

At 09:11 AM 4/19/02 -0400, you wrote:
>Vernon - we are at v4r5, and the commands you suggested do not exist.
>However, these could be interesting and useful. Anyone any ideas?
>
> >>> Vernon Hamberg <vhamberg@attbi.com> 04/18/02 08:08PM >>>
>Native on the 400 - ANZDBF and ANZDBFKEY.
>
>Help text for ANZDBF:
>
> >The Analyze Database File (ANZDBF) command produces two reports that
> >show the physical and logical files in a set of libraries and the
> >relationships between the files.  It saves the information in a
> >database file for further analysis by the Analyze Database File Keys
> >(ANZDBFKEY) command.  Both reports (physical to logical file
> >relationships and logical to physical file relationships) are
> >written to the printer file QPPTANZD.  Two printer files with the
> >same name are produced.  The data is saved in member QAPTAZDR of the
> >database file QPFRDATA/QAPTAZDR.
>
>Help text for ANZDBFKEY:
>
> >The Analyze Database File Keys (ANZDBFKEY) command produces, from
> >the data generated by the Analyze Database File (ANZDBF) command,
> >two reports showing the key structure of the database files.
> >
> >One report is written to the printer file QPPTALNK.  The other
> >report is written to the printer file QPPTKEYMTX.
>
>On this command I use *NUMLF special value for physical file and 1 for
>number of logicals. This gives me everything, I think. Or you can name a
>specific physical.
>
>At 03:50 PM 4/18/02 -0500, you wrote:
> >What is the easiest way to get file documentation with documentation on the
> >logics and what the keys are?
> >_______________________________________________
> >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> >To post a message email: MIDRANGE-L@midrange.com
> >To subscribe, unsubscribe, or change list options,
> >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> >or email: MIDRANGE-L-request@midrange.com
> >Before posting, please take a moment to review the archives
> >at http://archive.midrange.com/midrange-l.
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.
>
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.