P – Promote
This section provides information about Promote.
P – Definition
Type P to Promote a module to the next level in the change cycle hierarchy.
Promote May—or May Not—Do Generates
Depending on the “from” and “to” levels, the Promote operation may simply copy the source and executables from one level to the next, or it may copy the source only and regenerate all the executables.
The rules for each Application for each Type at each level are site-definable.
Lower Levels Cleaned Up
Typically, as modules move up to the next level, the source and executables at the lower level are automatically deleted, unless otherwise specified.
Production Promote Does Not Regenerate
The final Promote to Production always copies both the source and executables (if applicable) to the Production level, but typically does not regenerate the executables (although this, again, is site-definable). This keeps the update window small and ensures the module versions in Production are the versions that were tested.
Db2 Binds at Each Level
With Db2 applications, binds may be done at each level, as defined in ISPW’s repository.
Promote May Check Syntax or Do Generates
Promote may also invoke applicable syntax check routines and/or Generates. Modules that fail to generate cleanly are flagged in the Status field and could potentially be frozen until a successful generate occurs.
Lev Indicates Physical Change Cycle Level
The Lev column shows each Task’s physical level (for example, DEV, INT, QA, etc.) in the change cycle.
Doing Fixes to a Module at STG1
Using the earlier checkout example with Copybook TCPYB03, in the Task List this Copybook appears at the STG1 level and at the DEV1 level. For this example, assume there were problems with the module in STG1 that required fixing. To accomplish the fix, the module was added to the Task List again, checked out from STG1, and updated in DEV1.
Two Versions of TCPYB03
When ready, Promote will try to elevate Copybook TCPYB03 from DEV1 to STG1 again. However, there is already a copy at STG1.
Promote Conflicts Error Screen
The screen illustrated in the following figure is displayed, warning the user that the module is already at the STG1 level and will be overlaid by the DEV1 version. Depending on the security definition, it may be that only project leaders or special approvers will have the authority to do this operation.
Promote Conflicts Error Screen
