V'0)<FACDIFF

FACDIFF



&

July 1991





FThe Facility differences utility (FACDIFF) is used to compare element Egenerations contained in one VMS version against element generations !contained in another VMS version.

&Software Version: FACDIFF Version X0.1



D

FACDIFF



F Activates the FACDIFF utility. The FACDIFF utility is run from DCL. 7 Compares CMS element generations for any differences.



Format

6

FACDIFF library-spec base-class target-class

                              
Command QualifiersDefaults
 /[NO]COMPARE  /NOCOMPARE
 /[NO]FORMAT  /NOFORMAT
 /[NO]HEADER  /HEADER=library
 /[NO]LOG /LOG
 /OUTPUT=file-spec None.
 /PROCESS  /PROCESS=flagfree
 /[NO]STATISTICS  /NOSTATISTICS


prompts

            
 LIB_SPEC:  library-spec
 BASE_CLASS:  base-class
 TARGET_CLASS:  target-class



Description

HThe FACDIFF command activates the utility from DCL and then acts on the library(s) specified.

FThe FACDIFF utility performs a number of functions. First it verifies Cthat both class names specified are in fact part of the library(s) Hspecified. If there are any errors, FACDIFF reports them. An example of Ean error would be one of the classes specified is not present in the library.

HFACDIFF then uses CMS to get a list of all elements in each class. From Hthis list it determines which elements have changed generations between Gthe two classes specified and displays this information. Optionally, a @user can instruct FACDIFF to not only display information about Edifferent generations but it can also go in and verify that the code did in fact change.

COutput can be formatted to the users needs. The output can contain Epagination headers, or simply one header for each library processed. EAlso FACDIFF has the ability to put the output in a form that can be Deasily parsed by a user written utility (see the /FORMAT qualifier).




Parameters



library-spec

G Specifies the CMS library that is to be acted on. This specification F can contain wildcards, but it must be a valid CMS library directory J specification (i.e. VMS$:[YELLOW_TEST.CMS]). An example of a wildcarded J specification would be: VMS$:[Y*.CMS]. This specification would process / all libraries that start with the letter "Y".

base-class

F Specifies the CMS class name that will be used as the basis for the comparison.

target-class

G Specifies the CMS class name that will be compared to the base class.



Command Qualifiers



/[NO]COMPARE

J Indicates that not only should the CMS generations be checked, but that H also the source code should be checked. This is useful when trying to G locate code that has changed generations, but the actual source code  has not changed.

/[NO]FORMAT

: Indicates that the user wants the output in the form of:
F /libraryspec/elementname/baseclassgeneration/targetclassgeneration/4

/[NO]HEADER=(header_type[,header_type,...])

E Indicates what the user wants for header displays. The choices are:

/[NO]LOG

H Specifies that the FACDIFF utility should display a message for every  LIBRARY that is processed.#

/OUTPUT=file-specification

A Specifies the name of a file that is to contain all the output.

ENote: error messages and informational messages will not be put into the output file.-

/PROCESS=(attribute[,attribute,...])

E The PROCESS qualifier is used to identify what libraries are to be J processed. Some libraries have special attributes associated with them, I VMSCMS$NO_PROPAGATE.FLAG is an example of an attribute. This attribute B indicates that this library is not to have any code propagation D performed within it. The process qualifier is used to selectively H process or skip libraries marked with certain attributes. The list of  acceptable attributes is:

/STATISTICS

A Specifies that statistical information should be collected and displayed.


 .
_ Contents