MKS Implementer 2006 Administration Guide

Chapter 3: Implementer Administration
146
For information on using object version stamping in check out and promotion, see the
MKS Implementer 2006 User Guide.
NOTE Due to IFS constraints, Implementer does not support stamping issue or DR
numbers directly to IFS objects. However, for inquiry and reporting through
Implementer, the information is available in the repository.
To set up issue or DR object stamping
1 From the Implementer Menu, type option 45, System Control, and press ENTER. The
System Control Maintenance panel displays.
2 Press PAGE DOWN three times.
3 In the Activate issue object stamping field, specify Y to activate this feature. For more
information on this field, see “Activate object version stamping” on page 70.
4 Press ENTER to process the change.
Object Version Stamping
Implementer allows you to stamp objects, lock records, and repository records with a version
number at pre-determined stages within the development cycle. This provides an audit trail
that allows you to track every version of an object. It also allows you to identify specific
information about deployed objects under change control.
The version number scheme and development stage the object is stamped in, either
check out, check out and promotion, or user-defined, is determined by the versioning method
you define in System Control. Implementer automatically increments the version number
based on the versioning method you specify. During the applicable development stage,
Implementer updates the description of the object by recording the new revision number in
the APAR ID attribute. The repository record is updated when you run the build list as
described in the next section.
During the build list for a *PRD environment, Implementer stamps the version number to the
repository record for each object in the production environment (repository records for *TST
and *QAC environments have a blank version number) as follows:
If the object has a valid version number, then Implementer assigns that version to the
repository record. For details, see “Environment Repository Build” on page 117.
If the object does not have a version or has an invalid version, then Implementer assigns
the version number 1 or 1.0 (based on the defined versioning method) to the repository
record. If a user-defined versioning method is specified, a user exit is allowed for you to
set the version number.