My approach to scanning software for potential year-2000 problems.
 

1. As I recieve software, I'll store the "programs" in a folder,
   e.g. the Weekly Petroleum has been move to .\WPSRS.


2. If there are any files that cannot be processed as ASCII files,
   e.g. XYZ.WRI, then I'll store these in a subordiante folder after
   saving a equivalent ASCII version in a TXT file. Similarly, any
   files that are .BAK backupfiles etc, will also be stored in that folder.


3. Next I'll run following command to build the LIST file.
 

           for %%x in (.\WPSRS\*.*) do call mfprt %%x
 

   The LIST file is a comprehensive listing of all the programs etc. Since
   this could be fairly chunkie file, it has been formatted to be listed
   on the mainframe printer. Note that each line of code has a unique
   line number and a system and module name associated with it. LIST will
   be renamed to reflect the system it belongs to, e.g. WPSRS.LST.


4. Next run the Y2KFLTR.BAT. After looking at the output, Y2KHITS, the
   Y2KFLTR.BST program may have to be modified to tag lines that may not
   be coded as the program is written. Similarly, the program may need to
   be updated to eliminate the false positives by UNTAGging lines. The LIST
   file can then be used to make a better estimate of how much effort is 
   involved in fixing and testing the code and to aid in the remediation
   process.
  

   
