RE: DSPDBR

["David Schopp" <dschopp@xxxxxxx>]

What you want is Craig Rutledge's utility EXPDBR.  Expanded Database
Relations.
What a wonder tool this is.  You need it.  Give it a PF name and it shows
all
related LFs.  Give it an LF and you get the "based-on" PF plus associated
LFs.

Trust me.  Download and install it.  You'll be glad you did.

One heckuva satisifed customer,
Dave



-- Original Message --
  From: MacWheel99@aol.com
  Date: Fri, 29 Mar 2002 15:13:00 EST
  Subject: DSPDBR
  To: MIDRANGE-L@midrange.com (AS400 & iSeries & family discussion group)
  Reply-To: midrange-l@midrange.com

  We can use DSPDBR for some physical file to get a list of all logicals
that
  point at it.

  Is there something we can use for some logical to see what physical it
points
  at?

  My interest is with library crossings, since we have several versions of
each
  physical file (one per BPCS environment) & I want to make sure I have no
  inappropriate links of a logical to the wrong physical.

  I happened to be comparing list of logicals against the physical in one
  environment with list of logicals against physical of same name in another
  environment & noticing names on one list not on the other.  It would be
nice
  if there was other ways to display this data so the discrepancies more
  obvious & also which not really being used.

  I was recently surprised by PRTDSKINF RPTTYPE(*OBJ) OBJ(*ALL)
MINSIZE(4000)
  SORT(*LSTUSE) that we have some rather large data logicals that we are not
  using.  I will be using GO CMDREF to *OUTFILE to extract what software
they
  are intended for, if any.