Free or relatively cheap ones may be an option though (I'm just not aware of any). I know third-party tools exist for this, but they are not viable options at the moment due to cost. be displayed by the Display Program References (DSPPGMREF) command. It could be in a comment and return a false positive. When a file is used by a program, it is referred to by name, which identifies both. So far, I've tried using DSPPGMREF, but that only returns the overall object (IE: MYLIB/MYSRVPGM), not the individual sub-procedures used.Īnother route I've ventured was using FNDSTRPDM but that's just scanning the source for the string PROC1. However a search for PROC2 should not return a result. ![]() I'm looking for a way to search for PROC1 or PROC3 and see the result of MYLIB/MYPGM returned. ![]() MYLIB/MYPGM <- My ILE program object which uses PROC1 and PROC3 Then I have an ILE program which uses PROC1 and PROC3 but not PROC2. So something like this: MYLIB/MYSRVPGM <- My service program object I've been trying to move away from anything which dumps into files to use APIs instead (for example using QDBRTVFD instead of closing/clearing a file, doing DSPFFD to that output file then opening/reading the file) but I can't find an equivalent API to get the program references. ![]() Is there a way to programmatically find the usages of the individual sub-procedures within a library/file? I'm looking for an API which gets me the same info as doing DSPPGMREF to an output file. If I have a service program with a single module which contains three sub-procedures.
0 Comments
Leave a Reply. |