This document describes the use of the SLP file processing utilities
SUM, EXTRACT, and REAUDIT.
.hl1	Installation
All three utilities run as foreign commands. Copy the .EXE's into
SYS$SYSTEM. Each user must define a foreign command for each utility,
as follows:
.literal

	$ SUM :== $SUM
	$ EXTRACT :== $EXTRACT
	$ REAUDIT :== $REAUDIT
.end literal
.hl1	SUM: Merge SLP Updates
Invocation:
.literal

	$ SUM input-file,input-file,... output-file

.end literal
The SUM utility takes as input any number of SLP update files and
merges them into one SLP file. All updates are arranged in line number
order. Collisions between updates are reported, and handled as follows:
.s1
If the updates that collide are all inserts, they are concatenated
in the order in which their respective input files were given.
.s1
If any of the colliding updates are deletes or replacements, the update
from the SLP file given last in the SUM command takes precedence; the
other updates are discarded.
.hl1	EXTRACT: Remove Common SLP Updates
Invocation:
.literal

	$ EXTRACT input-file-1 input-file-2 /OUTPUT=output-file

.end literal
The EXTRACT utility does the inverse of SUM. It compares the two
update files given, and produces a new update file that contains
only the edits from input-file-1 that are not also in input-file-2.
Any edits encountered in input-file-2 that are not present in
input-file-1 are reported.
.s1
This utility is useful in extracting the edits of a SLP file
that are unique, as compared to some other SLP file.
.hl1	REAUDIT: Apply Old Audit Trails
Invocation:
.literal

	$ REAUDIT input-file-1 input-file-2 /OUTPUT=output-file

.end literal
The reaudit utility is used to apply the SLP audit trails from an
old update file to their corresponding edits in the new file.
Wherever an edit from input-file-2 is found in input-file-1, the
output file is written with the audit trail from input-file-2.
Edits in input-file-1 that have no matching edit in input-file-2
are written with the last audit trail encountered in input-file-1.