RE: **How to find display file program relation**

Program references?  You're not thinking of database cross-reference files
(QADB* files), are you?  I don't think the system keeps track of program
references, though.  But, feel free to teach an old dog a new trick!

- Dan Bale
(I am *NOT* "Dale"
http://archive.midrange.com/midrange-l/200105/msg00281.html )
SAMSA, Inc.
989-790-0507
DBale@SAMSA.com <mailto:DBale@SAMSA.com>
  Quiquid latine dictum sit altum viditur.
  (Whatever is said in Latin seems profound.)

-----Original Message-----
From: rpg400-l-admin@midrange.com [mailto:rpg400-l-admin@midrange.com]On
Behalf Of Dave
Sent: Thursday, June 06, 2002 11:36 AM
To: rpg400-l@midrange.com
Subject: Re: **How to find display file program relation**


I thought there were system files that could be queried that already did
this?


"Dan Bale" <dbale@samsa.com> wrote in message
NGBBLKOIELICEFBCHOBCKEPPCFAA.dbale@samsa.com">news:NGBBLKOIELICEFBCHOBCKEPPCFAA.dbale@samsa.com...
> Every night, from the job scheduler, I run a:
>  DSPPGMREF PGM(*ALL/*ALL) OBJTYPE(*ALL) OUTPUT(*OUTFILE)
>
> I have three logicals built on the outfile:
>  1) Logical by referenced object name, library name
>       Key fields: WHFNAM, WHLNAM, WHPNAM, WHLIB
>
>  2) Logical by program name, library name, ref'd obj.
>       Key fields: WHPNAM, WHLIB, WHFNAM, WHLNAM
>
>  3) Logical by library name, program name, ref'd obj.
>       Key fields: WHLIB, WHPNAM, WHFNAM, WHLNAM
>
> Using the #1 logical, you would be able to instantly find the information
> you are looking for.  If you would like the source for this logical, or
all
> of them, let me know.  (I added meaningful COLHDG's as well, suitable for
> the file utility apps like WRKDBF or DBU.)
>
> - Dan Bale
> (I am *NOT* "Dale"
> http://archive.midrange.com/midrange-l/200105/msg00281.html )
> SAMSA, Inc.
> 989-790-0507
> DBale@SAMSA.com <mailto:DBale@SAMSA.com>
>   Quiquid latine dictum sit altum viditur.
>   (Whatever is said in Latin seems profound.)