Souping Parallel Monitor Developments Together Oct70

Order Number: XX-F9CBB-2B

This document, titled "SOUPING PARALLEL MONITOR DEVELOPMENTS TOGETHER (MULTI)," outlines a detailed procedure for integrating changes from multiple parallel monitor developments (user and manufacturer) into a single, updated version of a complex of files.

The process involves:

  1. Preparation:

    • Obtaining "FAILSAFE" tapes of the original "father" files, "user-son" (user-modified) files, and "manufacturer-son" (manufacturer-modified) files.
    • Designating five distinct disk areas for these files, correction files, and the final "grandson" (edited) files.
  2. Core Procedures:

    • Restoring Files: The father, user-son, and manufacturer-son files are restored from tapes (or DECtapes) onto their respective disk areas.
    • Producing Correction Files: Using the CAM program (specifically COMPAR), two correction files are generated: one comparing father files with user-son files (USRCOR), and another comparing father files with manufacturer-son files (MANCOR). It emphasizes the importance of using the unchanged father area for this step to ensure correct merging.
    • Merging Correction Files: The CAM program is then used again to merge these two correction files into a single master correction file (e.g., 50102.COR). This step detects errors and conflicts between the parallel modifications.
    • Resolving Conflicts: Any conflicts detected during the merge must be manually resolved by editing the merged correction file using TECO. Conflicts can be identical edits/deletions or "real" discrepancies, requiring careful manual intervention to produce the desired final code.
    • Producing Final Edited Version: The FED program applies the manually resolved, merged correction file to the original father files, creating the new, final edited version in the "grandson" disk area.
    • Post-Production: Optionally, any newly introduced user or manufacturer files are copied into the grandson area. Finally, the entire new complex of edited files is saved onto two "FAILSAFE" tapes for backup.

The document provides specific command examples for each step, particularly for the CAM, COMPAR, and FED operations, and highlights key considerations like careful handling of file naming conventions and disk assignments.

XX-F9CBB-2B
May 1970
9 pages
Quality

Original
0.2MB

Site structure and layout ©2025 Majenko Technologies