The promote function copies members from any group to the next
higher group.
Note: SCLM promote only copies a member over a member at the next
level if it has changed. Two members with the same name are considered
to be changed if the accounting data and the member statistics are
different. If you retrieve the most recent version of a member into
the hierarchy, the recovered member at the development group is considered
the same as the member residing in the hierarchy. If the member in
the hierarchy has been corrupted, but the statistics are still valid,
SCLM will not overwrite the existing member during promotion. The
promote report indicates that the member was purged but not copied.
If you recover the most recent version of a member in order to replace
a corrupted member, you must save the member at the development group
to refresh the accounting data. You can save the member using SCLM
edit, migrate in forced mode, or the SAVE service. Then build and
promote the member as usual.
The promote function:
- Determines which components are eligible for promotion
- Verifies that the application is complete and current
- Promotes the components that are at the current group and within
the scope of the promote
- Potentially purges the components from the current group (and
possibly lower key groups)
- Generates a promote report
- Rebuilds the promoted member at the 'to group', if requested in
the language definition
Promote gives you an easy and efficient method to move data through
a hierarchy. As you build software components, they become eligible
for promotion to the next group in the hierarchy. Promote is based
on architecture or source members; thus you must build software components
successfully before you can promote them to the next group. Using
architecture members, you can promote individual software components
or sets of software components during one promote. SCLM processes
all data types associated with a component as a unit.
When the promote is complete, the promote function generates a
report identifying the components promoted.
The Build function is invoked when the members are copied successfully
and any language definitions of members promoted into this group require
rebuilding. The promoted member is conditionally rebuilt at the to-group
level, as well as any components with the given languages. Other components
are not rebuilt. Build messages, listings, and reports are generated
based on the values on the SCLM Build - Entry Panel.
You also can specify that only a Promote Report be generated. The
Promote Report identifies those components in the hierarchy that would
be copied or moved if the promote function were to be invoked.
The panel shown in Figure 1 appears when
you select Option 5, Promote, from the SCLM Main Menu.
Figure 1. SCLM Promote (FLMP#P) Menu SCLM Utilities Jobcard Workstation Promote Help
SCLM Promote - Entry Panel
Promote input:
Project . . . : PDFTDEV
From group . : MOS
Type . . . . : SOURCE Enter "/" to select option
Member . . . : PROG01 _ Workstation Promote
Mode . . 1 1. Conditional Scope . . . 1 1. Normal
2. Unconditional 2. Subunit
3. Report 3. Extended
Output control:
Ex Sub Process . . _ 1. Execute
Messages . . 3 3 1. Terminal 2. Submit
Report . . . 3 3 2. Printer
3. Data set Printer . . H
4. None Volume . . ______
Command ===> _________________________________________________________________
F1=Help F2=Split F3=Exit F7=Backward F8=Forward F9=Swap
F10=Actions F12=Cancel
The fields on the SCLM Promote - Entry panel are:
- Project
- The project that you specified on the SCLM Main Menu. An Alternate
field also appears if you specified an alternate project.
- From group
- The group from which to promote the member
- Type
- The type of the member
- Member
- The name of the member to be promoted
- Scope
- Select
one of the following possibilities:
- Normal
- To
process the components and members directly referenced by the specified
architecture member. In addition, this scope processes upward dependencies
for all Ada-type source members referenced directly by the architecture
member and all source members referenced as upward dependencies.
- Subunit
- To
process the components and members processed in normal scope as well
as downward dependencies for all Ada-type source members referenced
directly by the architecture members.
- Extended
- To
process the components and members processed in normal scope as well
as downward dependencies for all source members within the normal
scope.
Note: You must specify a scope equal to or greater
than the scope specified with the SCOPE keyword in the FLMLANGL macro.
- Mode
- Select
one of the following possibilities:
- Conditional
- To
bypass the copy and purge steps if promote discovers a verification
error.
Promote
compares dates in the build maps against dates in the database for
all software components taking part in the promote. Software components
are not promoted if they are deemed out of date. Use this mode to
guarantee complete project integrity.
- Unconditional
- To
perform copy and purge processing of all members despite verification
errors of other members and to promote only those members with correct
build map information.
Use this mode to promote software components
for incomplete or partial applications. For example, if some software
components referenced by an architecture member are not complete but
are required in the next group of the hierarchy, you can use this
mode to promote those software components.
The use of the unconditional mode
does not guarantee application integrity, so use it with caution.
It is, however, an effective method of promoting dependent software
components that you plan to integrate at a later date. The Unconditional
mode field is not retained on the Promote panel. If Unconditional
is used, the panel is changed to Conditional when the promote returns
to the panel.
- Report
- To
perform verification and report generation processing. The report
contains a list of members eligible for promotion.
- Output control
- Specify the destination for messages and the report when they
are executed (Ex) or submitted (Sub), by entering the corresponding
destination number: 1 for Terminal, 2 for Printer, 3 for Dataset,
or 4 for None.
- Workstation Promote
- Specify whether the promote needs a workstation connection. For
Foreground, SCLM verifies that an ISPF workstation connection exists
before executing the promote. For Batch, SCLM verifies that the information
required to initiate an ISPF workstation connection has been set by
a previous build or promote or from the workstation build pull-down.
If not, SCLM prompts the user to enter this information before the
build job is submitted. If the promote does not require a workstation
connection, do not use this field.
- Process
- You can call the processing part of the Promote - Entry Utility
from the interactive or batch environment by selecting Execute or
Submit, respectively. If you request batch processing by selecting
Submit, you must specify the job statement information which is used
in the JCL generated for batch processing.
For information about
using a unique jobname on the jobcard in batch processing, see Batch Processing.
- Printer
- Specify the printer output class.
- Volume
- Specify the volume on which SCLM should save data sets.