The Facility differences utility (FACDIFF) is used to compare element generations contained in one VMS version against element generations contained in another VMS version.
Software Version: FACDIFF Version X0.1
Activates the FACDIFF utility. The FACDIFF utility is run from DCL. Compares CMS element generations for any differences.
FACDIFF library-spec base-class target-class
Command Qualifiers Defaults /[NO]COMPARE /NOCOMPARE /[NO]FORMAT /NOFORMAT /[NO]HEADER /HEADER=library /[NO]LOG /LOG /OUTPUT=file-spec None. /PROCESS /PROCESS=flagfree /[NO]STATISTICS /NOSTATISTICS
| LIB_SPEC: | library-spec |
| BASE_CLASS: | base-class |
| TARGET_CLASS: | target-class |
The FACDIFF command activates the utility from DCL and then acts on the library(s) specified.The FACDIFF utility performs a number of functions. First it verifies that both class names specified are in fact part of the library(s) specified. If there are any errors, FACDIFF reports them. An example of an error would be one of the classes specified is not present in the library.
FACDIFF then uses CMS to get a list of all elements in each class. From this list it determines which elements have changed generations between the two classes specified and displays this information. Optionally, a user can instruct FACDIFF to not only display information about different generations but it can also go in and verify that the code did in fact change.
Output can be formatted to the users needs. The output can contain pagination headers, or simply one header for each library processed. Also FACDIFF has the ability to put the output in a form that can be easily parsed by a user written utility (see the /FORMAT qualifier).
library-spec
Specifies the CMS library that is to be acted on. This specification can contain wildcards, but it must be a valid CMS library directory specification (i.e. VMS$:[YELLOW_TEST.CMS]). An example of a wildcarded specification would be: VMS$:[Y*.CMS]. This specification would process all libraries that start with the letter "Y".base-class
Specifies the CMS class name that will be used as the basis for the comparison.target-class
Specifies the CMS class name that will be compared to the base class.
/[NO]COMPARE
Indicates that not only should the CMS generations be checked, but that also the source code should be checked. This is useful when trying to 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:
/libraryspec/elementname/baseclassgeneration/targetclassgeneration//[NO]HEADER=(header_type[,header_type,...])
Indicates what the user wants for header displays. The choices are:
- [NO]LIBRARY - Specifies that the user wants to see a header only when a new library is being processed.
- [NO]PAGE = Specifies that the user wants to see a header at the beginning of each new page.
Note: for terminals a page is defined as the size of the display screen./[NO]LOG
Specifies that the FACDIFF utility should display a message for every LIBRARY that is processed./OUTPUT=file-specification
Specifies the name of a file that is to contain all the output.Note: error messages and informational messages will not be put into the output file.
/PROCESS=(attribute[,attribute,...])
The PROCESS qualifier is used to identify what libraries are to be processed. Some libraries have special attributes associated with them, VMSCMS$NO_PROPAGATE.FLAG is an example of an attribute. This attribute indicates that this library is not to have any code propagation performed within it. The process qualifier is used to selectively process or skip libraries marked with certain attributes. The list of acceptable attributes is:
- [NO]ALL - process all libraries no matter what attribute it may have
- [NO]ARCHIVEDFACILITY - process all archived libraries
- [NO]FLAGFREE - process libraries with not attributes
- [NO]NOPROPAGATE - process libraries marked no propagate
/STATISTICS
Specifies that statistical information should be collected and displayed.
| Contents |