If a program does have errors then the date created, date last used and usage count will be listed to help identify redundant programs. The report can list all programs covered or just those with errors. point it at a specific environment setup). The routine can be run with the current library list, the current user's *JOBD library list or a specific *JOBD library list (ie. You can check against a list of referenced objects (or starting characters of objects) or *ALL. You can check a single program, a generic group, or *ALL in a specific library.

There's help text with the command, but here's a brief summary. If there was a format level mismatch, or a referenced object couldn't be found, then that was an error we wanted to know about. If the level identifier at program compilation time (from DSPPGMREF) matched that of the first occurance of the referenced file (from DSPFD) it was okay. I decided to automate the checking process by merging the output from a DSPPGMREF over a library with a DSPFD for each referenced object. Our cross reference tool had identified what needed changing, but we needed to be sure before going live. The format level identifier on the affected physicals had changed, along with most of their dependant logicals. We had been working on changes to some of our major files which required the recompilation of a hundred programs or so, and could impact a good many more. The object information repository data is stored with the *QRYDFN object.CHKLVLCHK is a routine I wrote around 1994 to save a lot of time and headaches. This would not need to be ran again, unless the query definitions were re-restored. However, any *QRYDFN object save/restored from V6R1 or V7R1 may require program QQUIWHOI to be run. V7R2 (no PTF necessary) - Any newly created query definitions will have accurate file usage information.

The program must be called every time a new query definition is added or query definition changes its file references, or you may see file references of '8' (Not specified). V&R1 (SI46908) - PTF supplies the support listed above, but you must run the following program to update the OIR information for file usage:ĬALL PGM(QSYS/QQUIWHOI) PARM(-library name-) It does NOT supply the file usage and does not have outfile support. Find all input file references for query definition TESTQRY in library QGPL: You can use the WHERE clause to filter out results: instead of a / as in library.outfile in FROM clause)ĭSPFFD of the outfile will give you the field names and text descriptions if you wish to craft your own queries. SELECT WHPNAM, WHLIB, WHFNAM, WHLNAM, WHFUSG Once the command completes, you can run a query over the outfile you just created Use Display Program References (DSPPGMREF) with *OUTFILE supportĭSPPGMREF PGM(*ALL/*ALL) OUTPUT(*OUTFILE) OBJTYPE(*QRYDFN) OUTFILE(-your library-/-your outfile-)

Dsppgmref file usage