Manual resolution for COBOL programs when there are multiple PDS members having the same name in the COBOL source as PROGRAM-ID

For an ordinary COBOL compiler in z/OS, there can be mismatch between member name in the PDS and program name (PROGRAM-ID name) in the source. Like in our case we have have 4 programs that are:
PDS member name is PROG1 and PROGRAM-ID name PROG0
PDS member name is PROG2 and PROGRAM-ID name PROG0
PDS member name is PROG3 and PROGRAM-ID name PROG0
PDS member name is PROG4 and PROGRAM-ID name PROG0
All these programs are compiled (to an object code on z/OS, not load module) with their real program names (all same PROG0), but during linkage it has set module name using link card f.e. PROG1 program:
IDENTIFY PROG0('PROG1/1A2B3C4D/ABC 000123')
  NAME  PROG1(R)
And respectively for other programs the same (PROG2/PROG3/PROG4).
We are fully aware that ADDI is static source code analysis tool and it scans source code only and has no information about the binder/linkage of the program, however in this case maybe using some resolution feature would help to handle this problem.
As in such situation programs are not being built and we cannot see such programs in the AD Analyze client.
Idea would be to have some manual resolution pointing PDS member to be resolved with some another name, than we do have in the program source as PROGRAM-ID. Like f.e.:
MY.OWN.PDS(PROG1) PROG1
MY.OWN.PDS(PROG2) PROG2
MY.OWN.PDS(PROG3) PROG3
MY.OWN.PDS(PROG4) PROG4
So in that case AD compiler could take PDS member name and set name (in AD processes) that is coded in such (or simmilar) resolution file, but not take PROGRAM-ID PROG0 as from program source.