Improve messages when the debug source is not compatible with the load module

We often get questions regarding "missing source" in the source window. The following errors are issued by language:
Enterprise COBOL: The Debug File creation date does not match the object for SAM1. The Debug file can not be used.
Assembler: Source or Listing data is not available, or the CU was not compiled with the correct compile options.

LDD ASAM1 ;
The EQALANGX file does not match the object for CU. The EQALANGX file cannot be used.
The length of CSECT ASAM1 in memory is X'00000726
' which does not match the length of X'000006D6
' found in the EQALANGX data.
EQALANGX debug file cannot be found for ASAM1. Use the SET SOURCE command to indicate the new location of the EQALANGX debug file.

OSVS COBOL: Source or Listing data is not available, or the CU was not compiled with the correct compile options.
SET DEFAULT LISTINGS DNET424.ADLAB.EQALANGX ;
Source or Listing data is not available, or the CU was not compiled with the correct compile options.
LDD SAMOS1 ;

More information is needed to resolve the issue. This occurs often when the load library has a different load module than the one prepared for debug tool, or the source information is different. For each type of language, and side file, (Enterprise COBOL, PL/I, older COBOL and PL/I, C/C++ and assembler), when the source is not available, identify the following information, if possible:
A) - Source information:
1) The debug source libraries searched
2) What libraries the member was found
3) The time/date of the compile/assemble
4) The size of the load module when the source was created
B) Load module information
1) The library from where the load module was fetched
2) The time/date the load module was assembled/compiled
3) The size of the load module