Promote from STG1 to QA
This section provides information about how to promote to QA.
Promote from STG1 to QA
Type P to promote the module from the STG1 level to the QA level, or use the Slash command again to see the Tool Bar options, click Promote, and press Enter.
The confirmation screen shown in the following figure is displayed. Press Enter to continue.
Promote from STG1 to QA
COMMAND ===>
Use existing Set ID:
or
Specify Details for new Set:
Operation P
Change Type S
Implement Data 2014-08-28 (YYYY-MM-DD)
Implement Time 02:10:00 (HH:MM:SS - use 24 hour clock)
Prefix
Description CHANGE CYCLE EXAMPLE 2
Applid PLAY
Owner KARYNS
Release
Level STG1
For new or existing Set:
Lock Set Y (Y or N)
Hold Set N (Y or N)
Press ENTER to continue or END to terminate/CANCEL
Approvals Required to Proceed
Approvals are now required to go from STG1 to QA.
In this particular example, approvals were not required for the module to be promoted from DEV1 to STG1, but to show ISPW’s flexibility, two approvals are now necessary from the QUALITY Approver group in order to proceed from STG1 to QA.
In a real organization, QA staff may be in the Quality Approver group, Auditors may be in the Audit approver group, project managers may be in the Team Leader approval group, and so on.
Task List Status is Updated to “Approval Reqd”
The following figure shows the first example of a Status field message. While approvals are still pending, this Approval Reqd message continues to be displayed. ISPW also uses email for notifications, but messages in the Status field are not easily missed and are visible to everyone working in this Assignment.
Task List Promotion Status Message
Command ===> Scroll ===> CSR
More -->
+----------------------------------------------------------------------------+
| Select(/) Add Approve Close Join Reset Show/Hide Work ++/-- |
+----------------------------------------------------------------------------+
Type Name Lev Op A User Appl Date MM DD Time Status
____ ________ ____ __ _ ________ ____ __________ _____ __________________
__ AMAC GDSMRL17 QA P USER17 PLAY 2013-03-07 09:00
__ AMAC RELEAS17 QA P USER17 PLAY 2013-03-07 09:00
__ ASM QKQ17 QA G USER17 PLAY 2013-03-07 09:00
__ CLST TREXX03 STG1 P KARYNS PLAY 2014-08-28 02:04 SP: P Approval Reqd
__ COB TPROG01 DEV1 PLAY
__ COB TPROG59 DEV1 G USER01 PLAY 2007-07-24 21:28
__ COPY TCPYA01 DEV1 PLAY
__ COPY TCPYA02 DEV1 S CLIVE PLAY 2002-11-25 04:46
__ COPY TCPYB01 DEV1 PLAY
__ COPY TCPYB02 DEV1 PLAY
__ COPY TCPYZ01 DEV1 PLAY
__ JOB TJOB01 DEV1 PLAY
-------------------------------- Bottom of List -------------------------------
Approvals Done via Approval Groups
Approval Groups are basically associated users who have authorization to do some special function in ISPW. Approval Groups are set up and administered in RACF (or ACF2 or Top Secret), and Sites may have as many different Approval Groups as necessary.
Approval Groups may be set up for notification only, which can be helpful to Operations or Audit staff, who are then automatically notified as Releases enter the QA or Pre-production level, for example.
Approvers Notified
Approvers are notified by email or by periodically checking the Approver List (Type A to Approve) to see items for their attention. As already mentioned, while approvals are pending, the Approval Reqd message continues to be displayed, and everyone accessing this Assignment will see it.