Compliance to what?  Compliance to some established standard.  Some types of standards you might be considering:
   -  Module Naming Standards.
   -  Y2K Implementation Assurance.
   -  Version Update and Upgrade Assurance (Change Control).
   -  Module Library Location Standards.

        Module Naming Standards.  Our product can help you verify that a given library or group of libraries contains specifically named members. Those specifically named members may be identified to the program as a generic group through the use of wildcard search arguments.

        Y2K Implementation Assurance.  Hopefully you know the name of the programs and/or subroutines which have been affected by the code remediation effort.  Our program can help you by reporting the current level of all of those programs and subroutines across multiple libraries.  You simply confirm that those levels are up to date with your requirements.

        Version Update and Upgrade Assurance (Change Control).  Our program helps you by reporting the current level of the programs and subroutines you designate across multiple libraries.  You indicate the affected user program names and affected libraries, and our program does the rest.  You simply confirm that those levels are up to date with your requirements.

    Note that you must update the OIC data base after user program maintenance so that the reporting will be accurate.  If you make a copy of the older OIC data base, you can run your reports from that data to see a "before" maintenance snapshot of your programs. This can be a useful debugging aid if maintenance problems occur.

        Module Library Location Standards.  Because our product can scan multiple libraries and consolidate the report data, we are able to provide you with the location of a module name (or group of names) from every scanned library in one report.  Through the use of these reports you can determine that the modules of concern are located in the proper library.  This can help spot misplaced or rogue members.