Results are slightly different. These are some reasons:

1. Some programs need to be recompiled to include updated modules.

2. Some modules are not referenced.

3. Some modules are not available.

Source by Library

*MODULE:

SELECT count(*), SOURCE_LIB FROM jpltools.modi0100 GROUP BY SOURCE_LIB

Figure 6: These are the sources by library from modules.

*PGM & *SRVPGM:

SELECT count(*), SOURCE_LIB FROM jpltools.pgml0100 GROUP BY SOURCE_LIB

Figure 7: These are the sources by library from programs.

Sources by File

*MODULE:

SELECT count(*), SOURCE_NAME FROM jpltools.modi0100 GROUP BY SOURCE_NAME  

Figure 8: These are the sources by file from modules.

*PGM & *SRVPGM:

SELECT count(*), SOURCE_NAME FROM jpltools.pgml0100 GROUP BY SOURCE_NAME

Figure 9: These are the sources by file from programs.

Objects by Version

*MODULE:

SELECT count(*), RELEASE_MODULE_CREATED_FOR FROM jpltools.modi0100 GROUP BY RELEASE_MODULE_CREATED_FOR

Figure 10: These are the objects by version from modules.

*PGM & *SRVPGM:

SELECT count(*), RELEASE_FOR FROM jpltools.pgml0100 GROUP BY RELEASE_FOR      

Figure 11: These are the objects by version from programs.

Objects by Owner

*MODULE:

SELECT count(*), MODULE_OWNER FROM jpltools.modi0100 GROUP BY   MODULE_OWNER    

Figure 12: These are the objects by owner from modules.

*PGM:

SELECT count(*), PROGRAM_OWNER FROM jpltools.pgmi0100 GROUP BY PROGRAM_OWNER

Figure 13: These are the objects by owner from programs.

*SRVPGM:

SELECT count(*), OWNER FROM jpltools.spgi0100 GROUP BY OWNER  

Figure 14: These are the objects by owner from service programs.

Check the Date of the Source Code

Reminder: MODI0100 or PGML0100 give us the exact date of the source code when compiling the module. DSPFD MBRLIST gives us the exact date of last modification of the source code.

Step one: Simplify the reading of DSPFD-MBRLIST (remember, the code is the same as in the previous article).

For the modification date of the source code:

SELECT MLNAME, case when MLCHGc = '' then ' ' else trim(char(  

MLCHGC+ 19)) concat MLCHGD concat MLCHGt end Upddate,MLMTXT FROM

jpltools.mbrlist WHERE MLCHGc <> ''                            

Figure 15: Simplify reading DSPFD-MBRLIST.

Step two: Simplify the reading of MODI0100.

For the compilation date of the source code:

SELECT src, srcmbr , case when srcdate = '' then ' ' else      

trim(char(substr(srcdate,1 ,1) + 19) ) concat substr( srcdate,2)

end cpldate , modattr FROM jpltools.modi0100                        

Figure 16: Simplify the reading of MODI0100.

The join of the two previous results (with SQL CTE - Common Table Expression) gives the list of modules without source:

with obj as (                                                    

SELECT src, srcmbr , case when srcdate = '' then ' ' else        

trim(char(substr(srcdate,1 ,1) + 19) ) concat substr( srcdate,2)

end cpldate , modattr FROM jpltools.modi0100                        

) , src as (                                                    

SELECT MLNAME, case when MLCHGc = '' then ' ' else trim(char(    

MLCHGC+ 19)) concat MLCHGD concat MLCHGt end Upddate,MLMTXT FROM

jpltools.mbrlist WHERE MLCHGc <> ''                              

) select src   , srcmbr , cpldate, modattr from obj exception    

join src on srcmbr = mlname                                    

Figure 17: These are the modules without source.

Find the list of sources that do not build a program directly—for example, code description of a service program or code of an SQL procedure or uncompiled code (i.e., copied code):

with obj as (                                                      

SELECT srcfile, srcmbr , case when srcdate = '' then ' ' else      

trim(char(substr(srcdate,1 ,1) + 19) ) concat substr( srcdate,2)    

end cpldate , modattr FROM jpltools.pgml0100                          

) , src as (                                                        

SELECT MLNAME, case when MLCHGc = '' then ' ' else trim(char(      

MLCHGC+ 19)) concat MLCHGD concat MLCHGt end Upddate,MLMTXT FROM    

jpltools.mbrlist WHERE MLCHGc <> ''                                

) select src.* from src src exception join obj on srcmbr = mlname  

Figure 18: These are the sources without objects:

Get the list of sources modified but not recompiled:

with obj as (                                                    

SELECT src, srcmbr , case when srcdate = '' then ' ' else        

trim(char(substr(srcdate,1 ,1) + 19) ) concat substr( srcdate,2)

end cpldate , modattr , text FROM jpltools.modi0100                

)

, src as (                                                      

SELECT MLNAME, case when MLCHGc = '' then ' ' else trim(char(    

MLCHGC+ 19)) concat MLCHGD concat MLCHGt end Upddate,MLMTXT FROM

jpltools.mbrlist WHERE MLCHGc <> ''                              

) select src   "Object", srcmbr "Src Mbr",                      

cpldate concat case when upddate = cpldate then '' else ' was  

updated ' concat upddate end   "Compiled_date"                  

, case when mlmtxt = text   then '   ' concat text   else '>> '

concat text   concat ' changed to ' concat mlmtxt end   "Text"  

from obj join src on srcmbr   = mlname and (cpldate <> upddate    

or text   <> mlmtxt)                                                                    

Figure 19: These sources were modified but not recompiled.

I changed my machine; we see the traces dated 2010-11-12-20:41:42.

Program Cross-References

These are based on DSPPGMREF output; that is to say on objects themselves, not on the source. Therefore, there is nothing to add to DSPPGMREF from the 16 files of RTVPGM. These analyses, exposed in the second article, are already accurate. They are not replicated here.

ILE Cross-References

ILE Cross-references are focused on module, procedure, program, and service program information received from RTVPGM outfiles. Their goal is to complete the data got from DSPPGMREF. Here, you will find a starter: the two SQLs needed to get the missing information quoted in previous articles:

Program by Activation Group:

select activation_group_attribute, count(*) count from jpltools.pgmi0100 group by activation_group_attribute

Figure 20: Get information about programs by activation group.

Monitor the Rights Acquisition:

select USER_profile_option, use_adopted_authority, count(*) count from jpltools.pgmi0100 group by USER_profile_option, use_adopted_authority

Figure 21: Monitor rights acquisition.

None of the programs in this application uses the owner authority. I don't need to further analyze which program runs under owner profile authority and check whether this is compliant with my policy rules. But if you need that information, you may want to quickly run an analysis:

SELECT program_name, program_library_name, program_owner FROM

jpltools.pgmi0100 WHERE USER_profile_option <>'U'            

I'll stop here; there is so much information in these files! Depending on your own interests, you can now easily understand how your software is built. Now, it's up to you.