VERIFY Utility Software

                                Karl M. Kemp

                              August 20, 1988


This document describes 3 files which can be used to simplify the use of 
VERIFY.  They are intended as examples to be customized.  Many improvements 
could be made to further enhance the software's usefulness in a particular 
application. 


The utility files are:

   MAKVER.DO   to create the MDL
   CHKVER.DO   to simplify running VERIFY
   CHKVER.BAS  run by CHKVER.DO


These files are all on the AMUS Network in account [100,111].  




The purpose of this utility is to prompt the user through the process of 
making and using Master Directory Listings (MDLs) and the VERIFY.LIT program 
(available with AMOS/L 1.3 and later releases).  MAKVER assists you in 
creating an MDL.  CHKVER helps you to check the MDL against existing files.  
Each process will be explained in detail below.  Both .DO files give you a 
chance to back out if you change your mind.


MAKVER.DO
   
This DO file should be placed in DSK0:[2,2].  When invoked with no 
arguments, it prompts you for file specifications to create an MDL by, and 
names it LOCAL.DIR (placed in the account you are currently working in).
Optionally, you can specify a name (up to 6 characters) for your .DIR file 
by entering: 

      .MAKVER filename 

You will see a screen full of explanation text and be asked for the
filespecs to  be placed into the MDL.  Pressing [ENTER] with no file
specifications when  prompted for them will cause an MDL to be made of all
files in the account  you are logged into.



CHKVER.DO

This DO file should be placed in DSK0:[2,2].  When invoked with no 
arguments, it attempts to VERIFY the MDL named LOCAL.DIR in the account 
your are logged into.  Optionally, you can specify a name (up to 6 
characters) for a .DIR file to VERIFY by entering: 

      .CHKVER filename 


CHKVER runs VERIFY with the /F option (to produce VERIFY.LST) and runs 
a program called CHKVER.RUN to spot and report only those lines with errors.

This feature saves you the trouble of having to watch umpteen lines of 
program names and the word 'VERIFIED' go past your screen while you hover
tensely over the [Ctrl-S].








CHKVER.BAS

This program should be placed wherever you keep source code and then 
compiled into DSK0:[7,6].  To do this, enter the following:

       .LOG BAS:
       .COMPIL dskxx:CHKVER.BAS[xxx,xxx]


CHKVER.RUN will be created but is never run by the user.  The CHKVER.DO 
process chains to this program after creating the VERIFY.LST file.  
CHKVER.RUN reads VERIFY.LST, one line at a time, and prints onto your 
screen the lines that contain a dash (-) or a question mark (?).  These 
characters should occur only on lines with errors.  All files that are 
VERIFIED will be skipped.  The last 2 lines output by the VERIFY procedure 
tell you the number of errors and missing files.  The program also adds a 
line telling you how many files were processed.  



.