Stream population refers to producing a snapshot of a stream at some point in time. VMS build streams are populated from a VMS development stream and then used as input to a system build. The overhead of populating a build stream varies depending upon how "close" the target build stream module generations are to the development stream module generations. 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 significantly, then the populate stream overhead degenerates close to the create stream overhead. The populate stream option of the menu prompts you for all the information necessary to successfully populate a stream in the VSC database and in the masterpack CMS libraries.

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

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

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

$ 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'

Required Privileges

The populate build stream option requires that the user hold the VDE privileges FROZEN and PERFREP and the process rights identifiers VMS_ENABLE_CMS and VMS_SOURCE. If the user does not hold these privileges, the submitted batch job will fail.

4.1 Invoking the populate stream procedure

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

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

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

Next you are asked for the source stream for the population. The source stream is the stream to populate from, or, if you like, the stream to copy. Usually the source stream is a VMS development stream, but this is not a requirement. The source stream is similar 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

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

Target Stream: V5.5_BLD_Z

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

Queue to submit populate jobs [CLUSTER_LONGBATCH]:

You are now asked for the work directory into which to place the log file and work files produced by the procedure. The submitted job name is 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]]:

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

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

You are finally asked to confirm your population request.

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... Job V55_BLD_Z_POP (queue CLUSTER_LONGBATCH, entry 633) started on queue CLUSTER_LONGBATCH

4.2 Populate Stream Processing

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

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

4.3 Suggestions for populating build streams

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

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

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

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

$ VDE Set priv MODSTRM; Modify stream'remark_qual'/name='new_name' 'stream_name' which could be used in VSC as: VSC>SET PRIV MODSTRM VSC>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 $! 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

Required Privileges

The rename stream option requires that the user hold the VDE privilege MODSTRM and the process rights identifiers VMS_ENABLE_CMS and VMS_SOURCE. If the user does not hold these privileges, the submitted batch job will fail.

5.1 Invoking the rename stream procedure

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

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

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

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

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

You 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]:

You can now enter a new remark string to be associated with the renamed stream. 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]:

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

Directory for log file [WORK212:[SWEENEY.SCRATCH]]:

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

Queue to submit rename job [CLUSTER_LONGBATCH]:

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

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

5.2 Rename Stream Processing

The processing steps of the rename stream batch job are:

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

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

The create baselevel stream function is another way to rename a stream. This option is available as a convenience to maintain consistent stream naming conventions. A baselevel is a milestone in the development cycle that should be preserved for future reference. The baselevel stream is associated with a baselevel result disk which is the output from the stream system build. An important difference between creating a baselevel 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.+

Required Privileges

The create baselevel stream option requires that the user hold the VDE privilege CRESTRM and MODSTRM and the process rights identifiers VMS_ENABLE_CMS and VMS_SOURCE. If the user does not hold these privileges, the submitted batch job will fail.

6.1 Invoking the create baselevel stream procedure

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

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

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

The next prompt asks you for the build stream you want to rename. This prompt defaults to the value of logical name PLMENU$DEFAULT_SOURCE_STREAM.

Build stream to rename: V5.5_BLD_Z

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

Result disk baselevel number: X999

The next prompt encountered is used to indicate if this baselevel is an internal field test(IFT) version or external field test (EFT) version. If this baselevel is not an IFT or EFT version enter "other" to this prompt.

Baselevel type (EFT, IFT or OTHER) [OTHER]: EFT

You are asked if you wish to append a suffix to the baselevel stream name.

Suffix to append to stream V5.5_X999_EFT [NONE]:_BLD_Z

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

Remark string for V5.5_X999_EFT_BLD_Z [V5.5 EFT baselevel X999]:

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

Directory for log file [WORK212:[SWEENEY.SCRATCH]]:

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

Queue to submit rename job [CLUSTER_LONGBATCH]:

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

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

6.2 Create Baselevel Stream Processing

The create baselevel stream procedure modifies the build stream to disallow the population of the VDE stream. The procedure then submits the same rename stream batch procedure as used in the rename stream option. The rename stream batch job first modifies all the CMS facility class names to the new stream name. After the CMS library classes are renamed, the VDE stream name is modified.

6.3 Suggestions for Creating Baselevel Streams

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