J4Release Project Leader Menu (PLMENU) B

Release Project Leader Menu (PLMENU)

Chapter 7
Comparing VDE to CMS

=This options allows you to check the consistency of a stream Frepresentation between VDE and CMS. The module generations in the VDE Cdatabase are compared to the module generations in the CMS library.

ARequired Privileges

GThe process rights identifiers (VMS_SOURCE or VMS_SOURCE_READ) )and VMS_ENABLE_CMS are required.c

7.1 Invoking the compare stream procedure

HThe VDE to CMS comparison utility is invoked by selecting option 6 from the project leader main menu.

"
7What action do you want to perform? (1-6,EXIT,HELP): 6 Compare 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$]:

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

BThe next prompt asks you for the stream you want to compare. This -prompt defaults to the value of logical name PLMENU$DEFAULT_SOURCE_STREAM.

"
Stream to compare [V5.4]:

HEnter the work directory where you want the utility's file(s) to reside.

"
5Directory for log files [WORK212:[SWEENEY.SCRATCH]]:

=Enter the queue in which to run the compare stream batch job.

"
1Queue to submit compare job [CLUSTER_LONGBATCH]:

FIndicate if you want the report of stream differences to be displayed Gin the log file (default) or written to a separate report file. If you Hdo not give a directory specification to the file name, the report will @be located in the work directory. The default file type is .LIS.

"
Report file name ? [LOG]: TEST

HEnter the facility to process. By default, the procedure submitted will Hcompare VDE to CMS for all non-archived facilities in the product root. GArchived facilities are skipped by the procedure. Facilities marked no Apropagation are compared by this procedure. You may enter a full Efacility name or a partial facility name with wildcards. For example @you may enter SYS* to process all facilities beginning with SYS.

"
!Facility to process [ALL]: SYS*

FThe procedure prompts you for the time to begin the compare job. This Doption is a read only function so there is no warning notice on any entered time.

"
)Time to submit compare job? [NOW]:+00:01

1You are asked to confirm your comparison request.

"
E If you proceed you will submit a job to compare stream V5.4 for all = facilities matching the file specification VMS$:[SYS*.CMS]. 4 Differences in the stream will be reported to file $ WORK212:[SWEENEY.SCRATCH]TEST.LIS; Do you wish to proceed? [Yes]: !Validating stream V5.4 in VDE... UJob V54_COMPARE (queue CLUSTER_LONGBATCH, entry 526) holding until 13-APR-1992 09:17

V

7.2 Compare Stream Processing

AThe compare stream utility compares the stream for each facility Dmatching the entered specification. For each facility, a message is Hdisplayed to the log file indicating whether the VDE stream and the CMS Dclass differed or matched. Differences are reported to the location $specified in the report file prompt.c

7.3 Suggestions for Comparing Streams

There are some known differences between CMS and VDE that can be ! ignored. These differences are:
1. BASE_LEVEL.MAR in facility SYS. This module is updated in CMS only ! by the system building tools.K
2. Facilities AAA_VDE_TEST and YELLOW_TEST are testing facilities for L the tools group. Any differences encountered in these facilities may be ignored.
J
A difference between VDE and CMS may be the result of a rolled back J VDE transaction. The difference is self-correcting once the transaction is run successfully.H
As mentioned in the populate stream section, if you allow changes H to a source stream during a population, you may encounter differences J in the target stream after the population. This is due to the fact that C the CMS populations take place after the VDE stream is populated.

Chapter 8
Creating a New Facility

FWhen you need to create a new facility on the masterpack, you can use @this option to create the facility. This option creates the new Gfacility in the VDE database and creates the facility CMS library. The Gutility creates three modules in the facility which are template files Hto be used for system building. The utility also sets up no propagation (facilities in the most efficient manner.

CThe facility is created interactively. There is no batch procedure submitted by this option.

ARequired Privileges

BThe VDE privilege CREFAC is required to run this >option. The process rights identifiers VMS_SOURCE and %VMS_ENABLE_CMS are required.c

8.1 Invoking the create facility procedure

CTo run the create facility procedure, choose option seven from the project leader main menu.

"
7What action do you want to perform? (1-7,EXIT,HELP): 7 Create 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 [TOOLS$]:

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

HA stream needs to be defined for the facility. The stream should be the Dfirst development stream in which you expect the components of this Ffacility to ship. For example, if you are creating a facility to hold Gthe update files for version V5.5, you would enter V5.5 to this prompt.

"
7 Facility begins with what development stream? [MAIN]:

EEnter the new facility name. The product root is checked to see if a HCMS library for this facility already exists. If a CMS library is found you will receive an error.

"
Facility Name?: VIC ? %CREFAC-E-ALREXISTS, facility VIC CMS library already exists! Facility Name?: wrench

EEnter a remark for the new facility. This remark is displayed by the VDE show facility command.

"
B Remark string for wrench [wrench FACILITY]: Wrench test facility

EIf the facility will accept change propagation enter yes to the next Bprompt. If you are creating a facility to hold update files for a 9particular release you should answer no to this question.

"
? Will facility wrench accept module change propagation? [YES]:

GYou are asked to confirm your input to proceed and create the facility.

"
@ If you proceed you will create facility wrench in root TOOLS$. G Stream MAIN will be populated with three system build template files. H The facility is created by this procedure. No batch job is submitted. & Do you wish to proceed? [Yes]:yes !Validating stream MAIN in VDE... 0%CREFAC-I-CREATING, Creating facility wrench... +%CREFAC-S-CREATED, facility wrench created

V

8.2 Create Facility Processing

9The create facility processing is broken down as follows:

The VDE facility and CMS library are created using the VDE create facility command.A
If the new facility is a no propagation facility, the file @ VMSCMS$NO_PROPAGATE.FLAG is created in the facility directory.G
Three modules are created in the facility. These three files are F templates you edit to perform a facility build. The three files are:
1. 'facility name'BLD.COM - This file contains a template of a command E procedure to perform all the steps of a VMS system build. In the @ example used in this chapter the file name is WRENCHBLD.COM.I
2. 'facility name'ASM.DAT - This is a specially formatted data file E that is used to contain information on which files to compile or L assemble in the facility. In the example used in this chapter, the file name is WRENCHASM.DAT.G
3. 'facility name'LNK.COM - This is a command file where all link < commands needed to build the facility should be located.
J
The CMS group BUILD is created. The three build files created above $ are inserted into the build group.

8.3 Suggestions for Creating Facilities

Be sure the propagation attribute for the facility is set J correctly. Unnecessarily propagating changes in a facility is expensive.I
Remember, facilities used for holding a release's update files are nopropagate facilities.H
If the create facility procedure is abnormally terminated, it may @ require manual intervention to correctly cleanup the facility.

Chapter 9
Populating a Stream in Selected Facilities

HThis option is virtually identical to the populate stream option. While Fthe populate stream option populates the stream in all CMS libraries, @this option only populates the facility CMS libraries which are Bspecified in a data file, or in a user entered list. The populate Ffacilities utility gives you the flexibility to populate both the CMS @libraries and VDE database, the CMS libraries only, or, the VDE Gdatabase only. The prompts are identical to the populate stream option Hexcept there are three additional questions. This option is useful when ?you know only a few facilities have changed since the previous Epopulation. It is important to realize that, if you populate the VDE Hstream, the population covers ALL facilities. The list Bof facilities to populate is used for controlling the CMS library 1populations and is ignored by the VDE population.

CRequired Privileges

HThe populate selected facilities option requires that the user hold the CVDE privileges FROZEN and PERFREP and the process Frights identifiers VMS_ENABLE_CMS and VMS_SOURCE. If Fthe user does not hold these privileges, the submitted batch job will fail.g

9.1 Invoking the populate facilities procedure

GTo populate a stream in selected facilities, use option eight from the >main menu. The populate facilities command procedure executes.

"
8 What action do you want to perform? (1-6,EXIT,HELP): 8 Populate Facilities 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.

HNext you are asked for the source stream for the population. The source Gstream is the stream to populate from, or, if you like, the stream for ?which to create a snapshot. Usually the source stream is a VMS Gdevelopment stream but this is not a requirement. The source stream is Esimilar to the parent stream of the create stream option. The source -stream defaults to the value of logical name PLMENU$DEFAULT_SOURCE_STREAM.

"
Source Stream [V5.4]: V5.5

HUpon entering the source stream you will be asked for the target stream Gto populate. This is usually a build stream for a development project. HThe target stream must have the VDE stream population attribute set for Cthis procedure to work. The target stream defaults to the value of *logical name PLMENU$DEFAULT_TARGET_STREAM.

"
Target Stream: V5.5_BLD_Z

DThe next question is used to determine if you want to interactively Fenter a list of facilities to process. If you answer affirmatively to Hthis question, you are prompted for a list of facilities. If you answer B"N"o to this question, you are asked to supply a file listing the facilities to process.

"
; Do you want to enter the facilities to process? [Y]: help P Answer "Y"es if you want to interactively enter the facilities to process. I If you answer no, you will be expected to supply the name of a file M which lists the facilities to process. Enter BACK or PREV to return to the target stream prompt. E Do you want to enter the facilities to process? [Y]:<RET>

)Enter the list of facilities to populate.

"
d Enter a list of facilities delimited by commas(,)(256 character maximum) Hit <RET> to finish : help b Q Enter a list of facility names delimited by commas "," or enter one facility uF name. Enter BACK or PREV to return to the facility input prompt. d Enter a list of facilities delimited by commas(,)(256 character maximum) Hit <RET> to finish ( : sys,sysloa,driver,starlet<RET> c
m

"FIf you did not indicate you wanted to enter a list of facilities, you Bare asked for the location of a file that lists the facilities to Aprocess. The file must be a text file with one facility name per cBrecord. For example, the file below is used to process facilities DRIVER, SYS and SYSLOA.D

a
a
"
%$ type work$:[Sweeney.tools]facs.dat SYS h SYSLOA DRIVER $
_

RG Enter the facility list file specification. Your default directory is s? searched for the file if you omit the directory from the file r specification.

"
3 Facility List File: work$:[Sweeney.tools]facs.dat n

nAThe next prompt is used to indicate how the VDE database and CMS EElibraries are to be populated. If you want to populate the stream in Aboth the VDE database and the CMS libraries enter "BOTH" to this aDprompt. If you want to update the VDE database only, enter "VDE" to Hthis prompt. If you want to populate only the facility "CMS" libraries, enter CMS.

"
( Populate CMS, VDE or BOTH [BOTH]: BOTH
i

tDThe populate stream job now prompts you for the queue to submit the populate jobs.

f
"
2Queue to submit populate jobs [CLUSTER_LONGBATCH]
y

hEYou are now asked for the work directory into which to place the log tFfile and work files produced by the procedure. The submitted job name Fis formatted as 'target_stream_name'_POP. In our example the job name is V55_BLD_Z_POP.p

e

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

TEThe procedure prompts you for the time to begin the populate job. On aHweekdays, you are warned of possible masterpack disk contentions if you Gchoose a time between 5:00AM and 5:00PM. You may submit the job at the tFentered time if you answer affirmatively to the "Do you still want to 3submit the job at the entered time? [N]:" question.

e

"
H Time to begin submission of populate jobs? [ 9-APR-1992 17:00:00]: NOW iL Due to locking contention on the master pack, this job should be submitted E after 5:00PM and before 5:00AM on weekdays. It is advised to avoid tI submitting populations during regular working hours unless you are sure o? the source stream and the target stream are almost identical. r pD Do you still want to submit the job at the entered time? [N]: YES
a

g1You are asked to confirm your population request.t

o
e
"
@ If you proceed you will populate stream V5.5_BLD_Z from stream B V5.5 for the facilities listed in work$:[Sweeney.tools]facs.dat. Do you wish to proceed? [Y]: !Validating stream V5.5 in VDE... b'Validating stream V5.5_BLD_Z in VDE... dZJob V55_BLD_Z_POP (queue CLUSTER_LONGBATCH, entry 633) started on queue CLUSTER_LONGBATCH

Z

9.2 Populate Facilities Processing

>FThe populate stream batch job maintains a status file to indicate the ?current state of the stream population. Any warnings or errors aHencountered during the population are marked in this file. A population Fstatus is mailed to the user upon completion of the populate job. The 7populate batch job processing is summarized as follows:[

The target VDE stream is populated from the source VDE stream. The lI population is broken down into many small RDB transactions to avoiding oD locking out other update usage on the masterpack. If any error is F detected at this point, the batch job will terminate. The stream is H populated for ALL facilities due to the current implementation of the VDE POPULATE STREAM command.B
The procedure submits a batch job to perform the CMS insert F generation commands for every non-archived facility which is in the J facility list file. You are not allowed to populate archived facilities.G
Each CMS insert generation procedure checks if the source stream oJ exists in the facility CMS library. If the source stream does not exist J a warning message will be output in the log file and into the procedure A status file. If the source stream exists, the target stream is populated from the source. +F
The procedure waits for the CMS insert generation batch jobs to F complete. When all jobs are complete the status file is checked for E errors. The user who submitted the job will receive a mail message d* indicating the status of the population.

/n o

N Note

r L

+ The target class will be created in the CMS 2 library if it does not already exist.

9.3 Suggestions for populating facilities

NEVER DELETE AN EXECUTING CMS POPULATE JOB FROM THE E QUEUE. An improper termination of a CMS insert generation tD command can corrupt a CMS library so, please don't delete the CMS G population jobs. A future version of CMS is supposed to correct this tG problem. If you need to stop CMS population jobs from processing the eH jobs can be stopped by defining the logical name FAC$ABORT_POPLIBS in ; the system logical name table on all relevant nodes. The lE FAC$ABORT_POPLIBS logical stops ALL populate jobs from processing. rI After your jobs have stopped be sure to deassign this logical to allow s) future populations to run successfully. I
If the stream you are populating is very different from the source oI stream please don't submit the populate during "regular" working hours.D
Don't panic if you receive warning messages in the population G status. There may be facilities for future VMS releases that are not g( applicable to your development stream.F
If you are going to do a build with the target stream, it's not I wise to allow changes to the development stream during the population. aC If you allow replacements into the development stream during the bJ population, the VDE representation of the build stream will differ from H the CMS representation of the build stream. This could be a source of G confusion after the build. Remember, it is the CMS representation of i' the stream that is used to build VMS.tI
If your populate stream job fails, rerun the populate stream using the same input.iH
If you fail to populate a facility in which the source stream has G changed since the previous population of the target stream, you will .= cause the VDE stream representation to differ from the CMS =" representation for the facility.

PreviousoT

NextW

Contents

Release Project Leader Menu (PLMENU) 

Chapter 7Comparing VDE to CMS