?It is often useful to compare the contents of two streams (CMS DClasses). For instance, you may need to identify which modules have Hchanged between one stable build stream and a subsequent unstable build Hstream. You can use the compare CMS class option of the menu to compare Htwo CMS classes for one or more facilities (CMS libraries). The utility Eallows you to submit multiple batch jobs to produce reports of class differences.

HThe VDE database stream generations are not compared by this option. If Ayou want to compare the VDE generations you can use the VDE SHOW BGENERATION command with the /IF_DIFFERENT qualifier. See the "VDE HReference Manual" for a description of the SHOW GENERATION command. The GCompare CMS class utility and the VDE command should give you the same Hresult. If the VDE difference is not the same as the output produced by Fthis option, then you have uncovered a difference between VDE and CMS for one or both of the streams.

CRequired Privileges


HYou need the process rights identifiers VMS_ENABLE_CMS 5and (VMS_SOURCE_READ or VMS_SOURCE)._

10.1 Invoking the Compare Class Option

GTo compare two CMS classes, select option nine from the main menu. The )compare class command procedure executes.

 

" 8 What action do you want to perform? (1-6,EXIT,HELP): 9 Difference Stream Version X-1 /Enter ? or "HELP" at any prompt to obtain help 5Prompt default values (if any) appear in brackets [] :Enter <Ctrl>Z, "Quit" or "Exit" to exit immediately  Product Root [VMS$]: VMS  



dEnter the product root. See Chapter 2 for a definition of product root.

CYou are asked to supply one of the streams to compare. There is no +validation performed on the entered stream.

 

"  First Stream [V5.5]: V5.5  



@Enter the second stream to for the comparison. No validation is performed.

 

" ( Second Stream [V5.5_BUILD]: V5.5_BUILD  



:Enter the batch queue in which to run the difference jobs.

 

" 8 Queue to submit difference job(s) [CLUSTER_LONGBATCH]:  



AEnter a directory for the log file produced by this option. This Hdirectory specification is also the default directory specification for any report file produced.

 

" @ Directory for logs and work files [WORK212:[SWEENEY.SCRATCH]]:  



DOptionally enter a file name to contain a report of the differences Hbetween the two streams. By default the differences will be reported in ?the log file. The file type defaults to ".LIS" and the default ?directory is the work directory entered at the previous prompt.

 

" " Report file name ? [LOG]: bs.lis  



FEnter the facility specifications to process. You may enter wildcards @in the facility name. In the example below, the streams will be ;compared in all facilities which begin with the letter "B".

 

"  Facility to process [ALL]: B* @ If you proceed you will submit a job to difference stream V5.5 D to stream V5.5_BUILD for all facilities matching the specification 1 VMS$:[B*.CMS]. Differences will be reported in ( file WORK212:[SWEENEY.SCRATCH]BS.LIS;. $ Do you wish to proceed? [Yes]: yes IJob BS (queue CLUSTER_LONGBATCH, entry 1483) started on GALAXY_LONGBATCH  



HYou are asked if you wish to process any more facilities. If you answer Faffirmatively to the prompt, you are asked for a new report file name Fand a facility specification to process. A batch job is submitted for Geach facility specification entered. The procedure terminates when you enter "NO" to this prompt.

 

" 4 Do you want to process any more facilities? [Yes]: ! Report file name ? [BS.LIS]: cs  Facility to process [ALL]: c* @ If you proceed you will submit a job to difference stream V5.5 D to stream V5.5_BUILD for all facilities matching the specification 1 VMS$:[C*.CMS]. Differences will be reported in ( file WORK212:[SWEENEY.SCRATCH]CS.LIS;. Do you wish to proceed? [Yes]: IJob CS (queue CLUSTER_LONGBATCH, entry 1484) started on DELPHI_LONGBATCH 7 Do you want to process any more facilities? [Yes]: no  

U

10.2 Compare Class Processing

EFor each facility specification entered, a batch job is submitted to Gproduce a report of differences between the two streams. The batch job Edisplays a message for each facility processed. A sample session and 5the log file produced by the session's input follows.

 

" Difference Stream Version X-1 /Enter ? or "HELP" at any prompt to obtain help 5Prompt default values (if any) appear in brackets [] :Enter <Ctrl>Z, "Quit" or "Exit" to exit immediately  Product Root [VMS$]:  First Stream [V5.5]: # Second Stream [V5.5_BUILD]: AMBER 8 Queue to submit difference job(s) [CLUSTER_LONGBATCH]: @ Directory for logs and work files [WORK212:[SWEENEY.SCRATCH]]:  Report file name ? [LOG]:  Facility to process [ALL]: H* @ If you proceed you will submit a job to difference stream V5.5 ? to stream AMBER for all facilities matching the specification 1 VMS$:[H*.CMS]. Differences will be reported in  the log file. Do you wish to proceed? [Yes]: TJob V55_AMBER_DIFF (queue CLUSTER_LONGBATCH, entry 591) started on GALAXY_LONGBATCH 3$ type WORK212:[SWEENEY.SCRATCH]V55_AMBER_DIFF.log . "SYS$NODE" = "GALAXY::" (LNM$SYSTEM_TABLE) 0%FAC-I-PROC, Processing library VMS$:[HELP.CMS] + Library: VMS$:[HELP.CMS] 2 Base class: V5.5 Target class: AMBER 3 Element name V5.5 AMBER <----------------------------------------------------------- 2 ACCOUNTIN.HLP 2 3 2 LEXICAL.HLP 6 7 2 SET.HLP 12 14 2 SHOW.HLP 9 10 2 START.HLP 6 7 2 STOP.HLP 6 9 2 V55_NEWFEATURES.HLP 2 3 /%FAC-I-PROC, Processing library VMS$:[HLD.CMS] 2 TEST job terminated at 29-APR-1992 09:01:45.67  Accounting information: M Buffered I/O count: 139 Peak working set size: 4178 M Direct I/O count: 77 Peak page file size: 11696 M Page faults: 5831 Mounted volumes: 0 N Charged CPU time: 0 00:00:03.34 Elapsed time: 0 00:00:13.16  

c

10.3 Suggestions for Comparing Classes

HThis option uses the masterpack CMS libraries in readonly mode so there .are no restrictions in the use of the utility.

HThe need to archive or obsolete an entire facility occasionally arises. BMost commonly, a facility used for holding the update files for a ;particular VMS release is archived after the release ships.

GObsoleting a facility refers to deactivating a facility beginning at a Gparticular stream. The deactivation is achieved by removing all of the Cfacility's module generations for a specific stream and all of the Egenerations of the stream's successors. For example, assume facility BDECW$LIBS is active in stream AMBER and obsolete in stream BLADE. FSuppose both streams are still open for source code changes and BLADE Bis a successor of AMBER . The BLADE stream does not want the four Chundred modules in the facility to be used when creating new build Estreams and populating existing build streams, but, the AMBER stream Eneeds the four hundred module generations. The BLADE release project Dleader can obsolete the facility and remove the four hundred module @generations from the VDE stream and CMS library. Obsoleting the Efacility will mean faster, more efficient stream populations for the >BLADE project. The AMBER project is unaffected by this action.

FArchiving a facility obsoletes the facility beginning at a particular Gstream, and sets a flag to prevent further stream creations and stream Fpopulations for ALL streams in the facility.+ If the Ffacility to archive spans multiple releases, it is important that the Afacility not be archived until all mainline streams in which the facility is active are closed.

BRequired Privileges


@The archive facility option requires that the user hold the VDE Fprivilege PERFREP and the process rights identifiers EVMS_ENABLE_CMS and VMS_SOURCE. If the user does not 9hold these privileges, the submitted batch job will fail.



e

11.1 Invoking the Archive Facility Procedure

CTo archive or obsolete a facility, select option ten from the main 6menu. The archive facility command procedure executes.

 

" 9What action do you want to perform? (1-10,EXIT,HELP): 10 (Archive/Obsolete A Facility Version X-1 /Enter ? or "HELP" at any prompt to obtain help 5Prompt default values (if any) appear in brackets [] :Enter <Ctrl>Z, "Quit" or "Exit" to exit immediately  Product Root [VMS$]:  



dEnter the product root. See Chapter 2 for a definition of product root.

EYou are asked for the facility to archive or obsolete. The procedure Hvalidates the existence of the facility. The procedure issues a warning Bmessage if the VMSCMS$ARCHIVED_FACILITY.FLAG file is found in the Efacility masterpack directory. This flag indicates that the facility Bwas archived in the past. You are allowed to continue even if the 'VMSCMS$ARCHIVED_FACILITY file is found.

 

" # Facility To Obsolete?: DECW$LIBS  



HNow indicate if you want the facility to be archived or to be obsolete. 9Your entry must be substring of "ARCHIVED" or "OBSOLETE".

 

" .Archive or Obsolete DECW$LIBS? [OBSOLETE]: Ob  



HThe next prompt asks you for the stream where the facility is obsolete. EThe facility should not be active for the stream entered. All module Egenerations for the entered stream and all of it's successor streams Dare removed from the VDE database stream and the facility CMS class.

 

" 9Stream at which to OBSOLETE the facility? [AMBER]: BLADE  



CEnter the batch queue in which to submit the obsolete facility job.

 

" 9 Queue to submit obsolete batch job [CLUSTER_LONGBATCH]:  



?Enter the directory for the log file produced by the batch job.

 

" > Directory for logs and work files [WORK9:[SYSBLDTEST.JUNK]]:  



@At the next prompt, indicate the time to begin execution of the Eobsolete a facility batch job. The entry defaults to execute the job Fimmediately. If the facility you are archiving or obsoleting contains Gmany modules, it is advisable to defer processing until after "normal" working hours.

 

" - Time to begin obsolete facility job? [NOW]:  



+Confirm your input to submit the batch job.

 

" Do you wish to proceed? [Yes]: Y Job Obsolete_decw$libs (queue CLUSTER_LONGBATCH, entry 808) started on GALAXY_LONGBATCH  

a

11.2 Archive/Obsolete Facility Processing

AThe processing performed by the obsolete a facility batch job is summarized as follows:

?
1. If the ARCHIVE option was selected by the user, the file J VMSCMS$ARCHIVED_FACILITY.FLAG is created in the facility directory. For J the DECW$LIBS facility in the VMS product, the file would be located in  directory VMS$:[DECW$LIBS].J
2. The procedure determines all of the streams for which the facility D is obsolete. The result is the stream entered by the user and all ( successor streams in the VDE database.C
3. For each stream determined in the previous step, all module I generations in the facility that are members of the stream are removed 6 from the stream via a VDE REMOVE GENERATION command.E
4. For each stream, the associated CMS class is deleted from the  facility CMS library.

J
• Remember, only use the ARCHIVE option when the facility is inactive F for all, non-remedial development streams. All mainline streams for 1 which the facility was active should be closed.F
• Try to execute the obsolete facility batch job after hours. The > batch job executes a VDE REMOVE GENERATION command for each G module/stream combination determined to be obsolete in the facility. aJ For instance, suppose the facility contains one hundred modules and the G streams AMBER and BLADE each contain generations for all one hundred gH modules. Suppose BLADE is a successor stream to AMBER. Obsoleting the I facility at AMBER requires two hundred remove generation transactions. _J Obsoleting the facility at BLADE requires one hundred remove generation  transactions.aG
• If you are archiving a facility which holds one release's update J files, make sure you enter the release's successor stream to the stream E prompt. For example, to archive the AMBER facility you would enter h BLADE to the stream prompt.e

n

c.
1. Prepare a result disk for a system build
2. Start a system build
3. Check system build results3
4. Reserve a baselevel number for a future builda0
5. Permanently close a stream against changes%
6. Perform a stream's replacements

s m

PrevioussW

Contents>W

Contentss

E_