V – Version List
Type V beside a module to see its different versions in the Change Cycle. As shown in the following figure, the Check Versions message in the Status column is displayed if there are conflicting component versions in the Change Cycle.
Using the V Command
22.01 COMPONENT VERSION LIST Row 1 of 4
Command ===> Scroll ===> CSR
More -->
Inactive: N
Appl: PLAY SubAppl: PLAY Type: COB Name: TPROG02
Lev iVer bVer rVer Op A User Date MM DD Time Status
____ ____ ____ ____ __ _ ________ __________ _____ ____________________
__ QA 6 5 5 G USER002 2022-05-14 13:19
__ STG1 7 6 6 P USER002 2022-05-14 13:19
__ PRD 4 3 3 P USER001 2022-05-11 14:02
__ FIX 0 4 4 C USER003 2022-05-16 13:01 => Check Versions
------------------------------- Bottom of List -------------------------------
“Check Versions” Message
The Check Versions message in the Status field continues to be displayed as long as there are conflicting versions in the Change Cycle. Though Code Pipeline can also send email messages, this message is more visible and persistent.
The example in the following figure shows a COBOL module that has been at STG1 for a long time, and now has many warnings about other activity in the Change Cycle:
Check Versions Message
Command ===> Scroll ===> CSR
More -->
+-----------------------------------------------------------------------------+
| Select(/) Add Approve Close Join Reset Show/Hide Work ++/-- |
+-----------------------------------------------------------------------------+
Type Name Lev Op A User Date MM DD Time Status
________ ________ ____ __ _ ________ __________ _____ ____________________
__ CLST TREXX03 STG1 P USER003 2022-05-16 15:12
__ CLST TREXX03 DEV1 OK USER003 2022-05-16 16:03
__ COB TPROG01 DEV1 G USER002 2022-05-16 10:19
__ COB TPROG02 DEV1 G USER001 2022-05-16 10:11
__ COB TPROG02 FIX C USER003 2022-05-16 13:01
__ + COB TSUBR01 STG1 I USER002 2022-05-16 14:24
+--------------------------------------------------------------------------+
| W: A version was checked out to level DEV1 by user USER005 |
| W: A version was checked out to level DEV1 by user USER003 |
+--------------------------------------------------------------------------+
__ COB TSUBR02 DEV1 G USER003 2022-05-16 15:19
__ COPY TCPYA01 STG1 G USER002 2022-05-16 10:14
__ COPY TCPYA02 DEV1 G USER002 2022-05-16 10:14
__ COPY TCPYB01 STG1 P USER002 2022-05-16 10:14
__ COPY TCPYB02 DEV1 P USER002 2022-05-16 10:14
------------------------------- Bottom of List -------------------------------
Versions of Module TCPYA03
The Component Version List in the following figure shows 10 different versions of module TCPYA03, which are color-coded to show modules in the Change Cycle versus backup versions. The light blue rows are historical versions in PRD and a backed up version in STG1, which are archived to the Code Pipeline Warehouse. From this list, Code Pipeline users have a high level view of who has which version at which level, and what version each was based upon.
Versions Listed
Command ===> Scroll ===> CSR
More -->
Inactive: Y
Appl: PLAY SubAppl: PLAY Type: COPY Name: TCPYA03
Lev iVer bVer rVer Op A User Date MM DD Time Status
____ ____ ____ ____ _ _ ________ __________ _____ ____________________
__ STG1 13 12 12 P USER001 2022-05-19 13:15
__ QA 12 11 9 P USER002 2022-05-18 13:15
__ PRD 11 9 9 P USER002 2022-05-17 13:15
__ PRD 9 8 8 P USER003 2022-05-16 13:15 => History
__ PRD 8 6 6 P USER002 2022-05-15 13:15 => History
__ DEV2 0 6 6 C USER001 2022-05-15 13:15 => Check Versions
__ PRD 6 5 5 P USER001 2022-05-14 13:15 => History
__ PRD 5 4 4 P USER003 2022-05-13 13:15 => History
__ PRD 4 2 2 P USER002 2022-05-12 13:15 => History
__ PRD 2 0 0 P USER001 2022-05-11 13:15 => History
------------------------------- Bottom of List -------------------------------
IVer, bVer and rVer Variables
The bVer column shows the “based-upon” version number. The rVer column shows the version this one may replace. The iVer column shows Code Pipeline’s internal version number, which is 0 until the module is promoted to the first controlled level above the update level. Code Pipeline sets warnings or stops module overlays depending on these version numbers.
See C-Checkout-Copy for more information on the version variables.
Four Versions in the Change Cycle; Many Versions in Backup
In this example, four different versions of TCPYA03 are active at the same time. They are in PRD, QA, STG1, and DEV2 as shown in the following structure diagram. There are also several historical versions, which are in backup.
Four Versions in Change Cycle
Example Could Have Seven Versions
It is possible to have versions checked out in every single level shown in this Change Cycle diagram, which could be up to seven different versions in the Demo/Training System’s PLAY application.
Try B to Browse
Type B beside a module to view/browse the content of a version.
Many Code Pipeline operations such as Compare, History, Work, and Print are valid from the Version List. In fact, most Code Pipeline operations work from the various list displays in Code Pipeline.