EStream population refers to producing a snapshot of a stream at some Fpoint in time. VMS build streams are populated from a VMS development Astream and then used as input to a system build. The overhead of Gpopulating a build stream varies depending upon how "close" the target Ebuild stream module generations are to the development stream module Dgenerations. If there are only a few differences between the target @build stream and the development stream, then a populate can be =completed in a matter of minutes. If the two streams diverge Fsignificantly, then the populate stream overhead degenerates close to Cthe create stream overhead. The populate stream option of the menu Gprompts you for all the information necessary to successfully populate Aa stream in the VSC database and in the masterpack CMS libraries.

K The populate build stream option of the project leader menu is updated D to process build streams which do not maintain CMS classes. The L option's current behaviour to populate build streams maintained in both G VDE and CMS is retained. The value of the logical VDE$FETCH_METHOD 6 determines how the build stream will be populated.

G The VDE$FETCH_METHOD logical is used by the menu option AND by the K batch stream submitted to determine how to populate the stream. If the J VDE$FETCH_METHOD logical value is VDE, the stream is populated in the K VDE database only. If the VDE$FETCH_METHOD logical value is not VDE or K undefined, the job tries to populate the stream in VDE and CMS. If the J VDE$FETCH_METHOD logical is set to VDE, there is no time warnings for I when a VDE only stream populate should run. If CMS classes are to be I populated, the option will warn the user about populating the stream during normal working hours.

I If your build streams do not maintain CMS classes, you may choose to J use the VDE POPULATE STREAM command directly from VSC to populate you I build stream. The POPULATE STREAM command requires the user hold the I VDE privilege PERFREP. The VDE FROZEN privilege must also be held by H the user if the build stream state is frozen. See the VDE reference F manual for a description of the POPULATE STREAM command. The file E VMSCMS$:POPSTRM.COM contains the populate stream command used to < currently populate build streams. The command format is:

 

" K$ VDE SET PRIV FROZEN;POPULATE STREAM/FROM='parent_stream' 'target_stream' which could be used in VSC as: VSC>SET PRIV FROZEN <VSC>POPULATE STREAM/FROM='parent_stream' 'target_stream'  



BRequired Privileges


EThe populate build stream option requires that the user hold the VDE Fprivileges FROZEN and PERFREP and the process rights Hidentifiers VMS_ENABLE_CMS and VMS_SOURCE. If the user Bdoes not hold these privileges, the submitted batch job will fail.c

4.1 Invoking the populate stream procedure

@To populate a stream, select option two from the main menu. The +populate stream command procedure executes.

 

" 8 What action do you want to perform? (1-6,EXIT,HELP): 2  Populate Stream Version X-1 0 Enter ? or "HELP" at any prompt to obtain help 6 Prompt 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 Fstream is the stream to populate from, or, if you like, the stream to Fcopy. Usually the source stream is a VMS development stream, but this His not a requirement. The source stream is similar to the parent stream Hof 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 populate stream job now prompts you for the queue to submit the populate jobs.

 

" 3Queue to submit populate jobs [CLUSTER_LONGBATCH]:  



EYou are now asked for the work directory into which to place the log Ffile 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.

 

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



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

 

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



9You are finally asked to confirm your population request.

 

" 3 Populate stream V5.5_BLD_Z from stream V5.5? [Y]: !Validating stream V5.5 in VDE... 'Validating stream V5.5_BLD_Z in VDE... ZJob V55_BLD_Z_POP (queue CLUSTER_LONGBATCH, entry 633) started on queue CLUSTER_LONGBATCH  

V

4.2 Populate Stream Processing

FThe populate stream batch job maintains a status file to indicate the ?current state of the stream population. Any warnings or errors Hencountered 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:

I
1. The target VDE stream is populated from the source VDE stream. The I population is broken down into many small RDB transactions to avoiding D locking out other update usage on the masterpack. If any error is 6 detected at this point the batch job will terminate.B
2. The procedure submits a batch job to perform the CMS insert J generation commands for every non-archived facility which allows change  propagation.G
3. Each CMS insert generation procedure checks if the source stream D exists in the facility CMS library. If the source stream does not G exist, a warning message will be output in the log file and into the H procedure status file. If the source stream exists, the target stream ! is populated from the source. +J
4. The procedure waits for the hundreds of CMS insert generation batch J jobs to complete. When all jobs are complete the status file is checked I for errors. The user who submitted the job will receive a mail message * indicating the status of the population.



i

4.3 Suggestions for populating build streams

B
• NEVER DELETE AN EXECUTING CMS POPULATE JOB FROM THE E QUEUE. An improper termination of a CMS insert generation D 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 H problem. If you need to stop CMS population jobs from processing, the H jobs can be stopped by defining the logical name FAC$ABORT_POPLIBS in ; the system logical name table on all relevant nodes. The E FAC$ABORT_POPLIBS logical stops ALL populate jobs from processing. J After your jobs have stopped, be sure to deassign this logical to allow ) future populations to run successfully.I
• If the stream you are populating is very different from the source J 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 ( applicable to your development stream.F
• If you are going to do a build with the target stream, it's not G wise to allow changes to the source stream during the population. If @ you allow replacements into the development stream during the J 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 ' the stream that is used to build VMS.I
• If your populate stream job fails, rerun the populate stream using  the same input.

DRenaming a stream requires updating the VDE stream name and the CMS Gfacility class names. Rename stream processing can be performed during Enormal working hours because it does not lock up the VDE database or ,CMS libraries for prolonged periods of time.

F The rename stream option of the project leader menu is updated to I process streams which do not maintain CMS classes as well as streams L that do maintain CMS classes. The option determines whether CMS classes > are maintained for the stream by the value of the logical G VDE$FETCH_METHOD. The VDE$FETCH_METHOD logical is used by the menu L option AND by the batch stream submitted to determine how to rename the H stream. If the VDE$FETCH_METHOD logical value is VDE, the stream is G renamed in the VDE database and the VMS$ SYS facility only. If the J VDE$FETCH_METHOD logical value is not VDE or undefined, the job tries > to rename the stream in VDE and all product CMS libraries.

K If your build streams do not maintain CMS classes, you can use the VDE I MODIFY STREAM/NAME= command directly from VSC to rename your stream. G The MODIFY STREAM command requires the user hold the VDE privilege J MODSTRM. See the VDE reference manual for a description of the MODIFY H STREAM command. Remeber if you are modifying a VMS stream, you will K still need to rename the CMS class in the SYS facility because the CMS L class still needs to be maintained for the system baselevel procedures. F However, if you do not plan to use the stream for building in the F future, you may omit the CMS rename. The file VMSCMS$:RENSTRM.COM I contains the MODIFY STREAM command used to currently rename streams.  The command format is:

 

" R$ VDE Set priv MODSTRM; Modify stream'remark_qual'/name='new_name' 'stream_name' which could be used in VSC as: VSC>SET PRIV MODSTRM TVSC>modify stream/remark="BLADE Baselevel X999"/name=BLADE_X999_BLDN BLADE_BLD_N .DON'T FORGET THIS WHEN RENAMING A VMS STREAM. $ Set command VMSCMS$:FACRENAME N$! facrename will prompt you for the stream to rename and the new name if you $! omit the parameter values ^$ facrename/log=all/remark="BLADE Baselevel X999" VMS$:[SYS.cms] BLADE_BLD_N BLADE_X999_BLDN  



BRequired Privileges


GThe rename stream option requires that the user hold the VDE privilege <MODSTRM 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.a

5.1 Invoking the rename stream procedure

GTo rename a stream, select option three from the main menu. The rename "stream command procedure executes.

 

" 7What action do you want to perform? (1-6,EXIT,HELP): 3 Rename Stream Version X-1 %Enter ? 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.

HThe next prompt asks you for the stream you want to rename. This prompt Cdefaults to the value of logical name PLMENU$DEFAULT_SOURCE_STREAM.

 

" % Stream to rename [V5.4]: V5.5_BLD_Z  



HYou are asked to supply a new name for the stream. This prompt defaults :to the value of logical name PLMENU$DEFAULT_TARGET_STREAM.

 

" New Stream Name [V5.5_BLD_10]:  



HYou can now enter a new remark string to be associated with the renamed Estream. The stream's current remark string is retained if you do not enter a value to this prompt.

 

" @ New remark string for stream V5.5_BLD_10 [Use current remark]:  



FEnter the work directory where you want the rename stream log file to reside.P

0 

> " 4Directory for log file [WORK212:[SWEENEY.SCRATCH]]:  o



c<Enter the queue in which to run the rename stream batch job.

t 

g " 0Queue to submit rename job [CLUSTER_LONGBATCH]:  0



hGYou are asked to confirm your input and proceed with the stream rename.i

 

> " B If you proceed you will rename stream V5.5_BLD_Z to V5.5_BLD_10. Do you wish to proceed? [Yes]: 'Validating stream V5.5_BLD_Z in VDE... (Validating stream V5.5_BLD_10 in VDE... ]Job RENAME_V55_BLD_Z (queue CLUSTER_LONGBATCH, entry 633) started on queue CLUSTER_LONGBATCH g  d

T

5.2 Rename Stream Processing

b8The processing steps of the rename stream batch job are:

bG
1. The old CMS class name in all non-archived, propagating facility fG libraries is modified to the new stream name. A new stream remark is a: attached to the class if the user supplied a new remark.G
2. After all the CMS library classes are renamed, the VDE stream is 8 modified to the new stream name and new stream remark.

H
• If a rename stream job fails, it is sufficient to restart the job < assuming the failure was not due to a privilege violation.J
• Try to retain a consistent naming convention when renaming streams. J This will provide for easier interpretation of what a stream represents ' after you've gone on to other things. C
• Make sure you read the confirmation prompt to insure you are F renaming the correct stream. You don't want to rename a VMS version  development stream! 

o

_HThe create baselevel stream function is another way to rename a stream. HThis option is available as a convenience to maintain consistent stream Hnaming conventions. A baselevel is a milestone in the development cycle Gthat should be preserved for future reference. The baselevel stream is iEassociated with a baselevel result disk which is the output from the m@stream system build. An important difference between creating a Fbaselevel and renaming a stream is that creating a baselevel modifies @the new stream to prevent future populations of the new stream. +Creating a baselevel "freezes" the stream.+ 

eBRequired Privileges


GThe create baselevel stream option requires that the user hold the VDE Fprivilege CRESTRM and MODSTRM and the process rights Hidentifiers VMS_ENABLE_CMS and VMS_SOURCE. If the user Bdoes not hold these privileges, the submitted batch job will fail.

a

pl

6.1 Invoking the create baselevel stream procedure

eETo create a baselevel stream, select option five from the main menu. d7The create baselevel stream command procedure executes. 

= 

< " 7What action do you want to perform? (1-6,EXIT,HELP): 5 E r$Create Baselevel Stream Version X-1 /Enter ? or "Help" at any prompt to obtain help e5Prompt default values (if any) appear in brackets [] ;Enter <Ctrl Z>, "Quit" or "Exit" to exit immediately a Product Root [VMS$]:   



tdEnter the product root. See Chapter 2 for a definition of product root.e

tGThe next prompt asks you for the build stream you want to rename. This -prompt defaults to the value of logical name rPLMENU$DEFAULT_SOURCE_STREAM.s

b 

r "  s$ Build stream to rename: V5.5_BLD_Z  M



EBAfter you input the stream to rename you are asked for the system Fbaselevel number associated with the result disk for the build stream.

 

h " $ Result disk baselevel number: X999  o



rHThe next prompt encountered is used to indicate if this baselevel is an Ginternal field test(IFT) version or external field test (EFT) version. EIf this baselevel is not an IFT or EFT version enter "other" to this =prompt.>

t 

e " 1 Baselevel type (EFT, IFT or OTHER) [OTHER]: EFT a  



EYou are asked if you wish to append a suffix to the baselevel stream tname.o

h 

" 7Suffix to append to stream V5.5_X999_EFT [NONE]:_BLD_Z e r



FYou can now enter a remark string to be associated with the baselevel.

d 

r " B Remark string for V5.5_X999_EFT_BLD_Z [V5.5 EFT baselevel X999]:  n



eFEnter the work directory where you want the rename log file to reside.

> 

" 4Directory for log file [WORK212:[SWEENEY.SCRATCH]]:  o



<Enter the queue in which to run the rename stream batch job.

o 

t " 0Queue to submit rename job [CLUSTER_LONGBATCH]:  



@You are asked to confirm your input and proceed with the stream renaming.-

2 

t " PJ If you proceed you will rename stream V5.5_BLD_Z to V5.5_X999_EFT_BLD_Z. C Stream V5.5_X999_EFT_BLD_Z will be frozen and cannot be populated c. from the populate stream option of the menu. . Do you wish to proceed? [Yes]: 'Validating stream V5.5_BLD_Z in VDE... 0Validating stream V5.5_X999_EFT_BLD_Z in VDE... K%VDE-I-STRMMOD, information for stream V5.5_BLD_Z modified in the database t?%VDE-I-COMMIT, database transaction has successfully committed oWJob RENAME_V55_BLD_Z (queue CLUSTER_LONGBATCH, entry 329) started on CLUSTER_LONGBATCH a 

_

6.2 Create Baselevel Stream Processing

LCThe create baselevel stream procedure modifies the build stream to

6.3 Suggestions for Creating Baselevel Streams

G
• If a rename stream job fails it is sufficient to restart the job u5 assuming it did not fail for a privilege violation.tH
• This option is available to retain a consistent naming convention E across development streams. If you prefer to use the rename stream >D option please try to adhere to the naming convention used in this  procedure.C
• Make sure you read the confirmation prompt to insure you are F renaming the correct stream. You don't want to rename a VMS version  development stream!i

o