ISPW Change a REXX program - Compuware Drive/ISPW... · 2020-04-02 · 1 Compuware Test Drive ISPW...

1

Compuware Test Drive

ISPW Change a REXX program Revised: 4/2/2020

This tutorial will review how to make changes to a REXX program in ISPW. From sign out to changing code to generating and promotion.

The Mainframe Software Partner for the Next 50 Years

2

Contents

Getting Started with SCM - ISPW ..................................................................................................... 3

Code Changes ................................................................................................................................... 8

Promotion ...................................................................................................................................... 16

Task History and Auditing .............................................................................................................. 23

NEXT STEPS .................................................................................................................................... 34


3

Getting Started with SCM - ISPW

The goal of this Test Drive is to make a change to a REXX program and promote it to production using ISPW. Compuware ISPW enables developers to quickly and safely build, test and deploy mainframe their code.

This test drive will take you through the following activities:

• Creating an Assignment

• Code changes

• Generating/compiling

• Promotion to Test and Production runtime environments

Instructions:

• This guide contains many screenshots to provide a visual reference

• Every action you must take is in BOLD

• Please note each place that you must enter your own specific ID or number

• You must complete each step before proceeding to the next to successfully follow the guide

NOTE: if you wish to rerun this Test Drive Script, simply pick the same element if you ended successfully and start over. If you did not end successfully pick another REXX program (TREXX02, 03,04, etc.) to use and start the script over. Any other errors will require a call to ISPW support.


4

The Compuware Test Drive Experience requires that users complete the Building Your Environment

http://resources.compuware.com/hubfs/Test%20Drive/Building_Environment_with_Host_and_JES_Explorers_TW_Test_Drive.pdf

exercise before starting any tutorial script. If, at any point during your experience, your host connection times out, you may need to log back into the Test Drive host connection.

To get started in the Topaz Workbench:

1. Open the Host Explorer perspective

2. Click on the arrow next to Hosts

3. Right-click on Test Drive and select Login

4. Logon on with the user credentials that were provided to you for with the Test Drive and click OK

5. Select ISPW from the Compuware menu




5

Click the ISPW Repository Explorer view


6

During this Test Drive you will encounter terms specific to ISPW. Here is a glossary for your convenience.

Term Description

Application Business Area

Stream Development Life-Cycle used by one or more Applications

Life-Cycle Transitional Code States (DEV, QA, PROD) in the Development Life-Cycle

Level Instance of a Code State (DEV, QA, PROD)

Component SCM managed object such as a Cobol source member.

Component Version An immutable version of a Component.

Task An instance of a unit of work. For example, a change to a Component.

Part A generated object such as a load module, or a Listing or a DBRM

Warehouse Storage location for inactive historical or overlaid Component Versions (source and parts).

Assignment Container A package of one or more, usually related, Tasks. A development container that is used to organize and manage development work.

Release Container A package of Tasks from one or more Assignment Containers. An operational container that is used to organize and manage operational releases.

Set Container A package of Tasks at an instance in time. A special ISPW container that is used internally to organize and manage work requests.

Add Task Make a statement of intent, often because of some impact analysis.

Checkout Task Copy source to development area

Edit Task Make a change to the source in the development area.

Generate Task Execute Compile and Link processes.

Promote Task Move Task forward to the next Level in the Life-Cycle.

Regress Task Move Task backwards to the previous Level in the Life-Cycle.

Delete Task Remove a Task from the development area

Fallback Task Restore previous version of Task.

Deploy Task Implement Task in one or more Run Time environments.


7

Substitute your values in the screenshots

In this Test Drive the screen shots provided have used specific values that may differ from your assigned values. These were provided in your email notice.

While taking the test drive, you must substitute your assigned values!

Variable Your Assigned Values

Application Txxx*

Assignment Prefix Txxx*

* For the value of xxx, substitute the last three digits of your test drive username.


8

Code Changes

Your development task in this Test Drive is to change a REXX program using Topaz editor, then promote it through the Application Life-Cycle to Production.

First, you will find and add a REXX program into an ISPW Assignment from which you can perform all this work.

• Change the Stream to CWEZ

• Change the Application to your assigned application value (Txxx, where xxx is your unique number)

• Set the Level to “PRD” and ensure the Level option is set to “Selected level only” or “All found in level and above” both settings will return the same results since there is nothing above PRD.

• Filter the view even further by setting the Type to CLST, this will allow you to focus only on the CLST program components available in your stream | application at the PRD level. Click Apply (circled).


9

The ISPW Repository View lists the TREXX Components for your application.

Scroll through the list and find TREXX01 at level PRD. Right-click on it and click Add to Assignment with Checkout.


10

From the Add Task dialog box, select NEW to the right of Assignment. This will allow you to create a new Assignment Container to put your ASM program into. Type a description and click OK.

A message will be displayed providing you with your new Assignment name. Click OK.

Your new Assignment has been created and is ready to have Tasks added to it. An Assignment Container is the only Container Type in ISPW that Tasks can be added to. The Assignment Container is where a developer will spend much of their time.


11

Our new Assignment number will appear in the Assignment field. Click OK.

A message will be displayed to inform you that a task has been checked out. Click OK.


12

Your Assignment has been created and you should now have a REXX program in it. The Assignment Task List view will open and the Task that was added will be listed. Every operation that needs to be performed on this Task and other Components which are impacted by changing this Task (edit, impact analysis, compile, promote, deployment etc..) can be performed from this Assignment or other Assignments.

To see the ISPW Life-Cycle path structure that was constructed for the Application, click once on the Task and then click on the View Life-Cycle icon.


13

Note that the REXX program in the Assignment is checked out and sitting in the DEV1 level. The Checkout Date/Time and User ID is reflected in the Task information. At checkout, a destination level for the checkout was chosen – DEV1.

A picture of the Life-Cycle is presented. You will notice the levels containing the Versions of the highlighted REXX program are colored indicating the existence of a version of that Component at those levels.

From this picture it is very easy to visually see where Versions exist. By choosing the DEV1 Level, you have defined the Path to Production → DEV1-QA1-STG-PRD. Other versions of these Components may also exist at other levels and may be passing thru the other three paths – FIX, DEV2 or DEV3.

Four paths were created for the application – one for emergencies starting at level FIX and three for development starting at DEV1, DEV2 and DEV3. The application level structure is customizable when defining the applications to ISPW. Any number of paths can be defined with a minimum of three Levels.


14

Now that you have a Version of a REXX program the next step would be to make changes to it. To do this either right-click on TREXX01 and click Edit or simply double-click on it.

Change the source using the Topaz editor. Once you have made your changes, close the Topaz editor view. Click Yes to save the changes.


15

Note the Operation, Date/Time and User ID fields have been updated to reflect the change in the Task status.


16

Promotion

At this point you have

• Edited a REXX program

• Used the Topaz Editor to help you make your changes

• Saved your changes

Now you are ready to promote your changes to the QA1 level. To promote the Task to the QA1 level, right-click on the Task and click Promote.


17

This action will create a Set Container. Sets are a special category of container that are used to conduct operations such as promotion and deploy. They are temporary and created by ISPW as needed for the work. This allows you to promote subsets of Tasks within an Assignment container without the need to act on all the Tasks at once.

Once you click Promote the selected Task(s) are placed in a SET container for the promotion.

The ISPW Set processor will:

• Perform the promotion of the source to QA1

• Cleanup the DEV1 level (source and parts if applicable)

• Perform generates, in order, of all the Task(s) in the SET which require a generation

Click OK.


18

In the screenshot below, you can see the promote operation has completed – the Task has been promoted to QA1 (see the Level value and the Operation in the Task List ). The SET processor performed a promotion.

Let us assume all the testing at the QA1 level has been successfully completed and you are ready to promote to the STG level. Select the Task as before, right-click and click Promote.

In the screenshot below, you can see the promote operation has completed – the Task has been promoted to STG (see the Level value and the Operation in the Task List).

Note the Operation column shows Promote as the last operation. The SET processor performed a promotion. This can be configured by the ISPW administrator.

A Set container is created. The selected Task(s) are placed in a SET container for the promotion. The ISPW Set processor will:

• Perform the promotions of all the parts to STG

• Cleanup the QA1 level (source and parts if applicable)


19

Assuming all the testing at the STG level has been successfully completed, you are now ready to promote the Tasks to the PRD level.

Select the Task as before, right-click on it and select Promote.

In this screenshot, as the Task(s) in the SET are being processed, you can see:

• The Task will be selected for a Promote

• ISPW will start a SET processor for this SET

• The REXX program will be promoted

You can monitor the progress by clicking the refresh button.


20

Note: ISPW uses your installation’s security (RACF/Top Secret/ACF2) to manage process security (granular control of permissions by user and function). Process security defines who can perform which commands at which levels in the Life-Cycle.

While a Developer can perhaps request the Promote operation when promoting to the STG and QA1 levels, perhaps a Change Coordinator role is responsible for requesting the Promotion to PRD.

One or more approvals can be put in place for each application/level promotion, including but not limited to Application Manager, QA Manager, Impact, DBA, JOB Scheduling, Peer, or VP roles.

A Set container will be created. The selected Task(s) are being placed in a SET container for the promotion. The ISPW Set processor will:

• Perform the promotions of all the parts to the PRD Level

• Cleanup the STG level source and parts as applicable

The application has been configured to require an approval for the Promotion to PRD. Click OK.


21

Below the STATUS shows the Tasks are locked in a SET for a Promote process but the SET needs approval before the promote can proceed.

The Approval can be performed from:

• Topaz/ISPW

• TSO/ISPW in the ISPF interface

• Web interface (including mobile browser)

For this Test Drive you will do the approval from Topaz/ISPW. To perform the approval, click on the task, then right-click on the STG box in the Life-Cycle diagram. Click “Approve.” ISPW will now perform the promotion of the Tasks collected in the SET to the PRD Level.


22

You can see in the updated screen below that:

• SET processing has completed

• The ASM program has been processed for a Promotion and is now at the PRD level

The Promotion to the PRD level has completed. The source and parts for the ASM program were moved to the PRD level Life-Cycle libraries and the STG level libraries were cleaned up as appropriate.

Notice if the Operation column shows Implement as the last operation, ISPW performed any tasks that were configured for deploy and activation.

An example of a Deploy Implementation activity is the copy of the executable load module into a CICS or IMS runtime library.

Examples of an activation activity would be a DB2 Plan or Package Bind or a CICS New copy.


23

Task History and Auditing

As Tasks are processed thru the Life-Cycle, ISPW records the “major” operations performed against the Task, who performed the operation and the date/time the operation was performed. At any time, a Task’s history can be viewed.

To view the Operation history for the TREXX01 Task, right-click on the Task, mouse over “VIEW” and click “Task History”.


24

A new view will open and display the operations which were performed against this Version of Component TREXX01 in the TXXX Application. This history is part of the ISPW Audit trail which is kept forever and can be viewed at any time. Double click the date/time column to sort. Close the “ISPW Task History” View by Clicking on the “Close window” button. ISPW keeps the history of all the versions of a Component.

To view the existing versions of the REXX program TREXX01, right-click on the Task, mouse over “View” and click “Component Versions”.


25

The “ISPW Component Versions” View will open, displaying all the versions of your Component.

The display shows for all the Versions of the Component

• ISPW internally assigned Version number

• Base Version number that the Component is based on

• Last operation

In the configuration of the application, the number of source versions kept at the PRD level is “All”, so all the versions listed below have the source associated with the version stored in the ISPW Warehouse. Click the Show Inactive Versions button.

Double-click on any version to view a version’s source. Close the Topaz editor window and the “ISPW Component Version” View by clicking on the “Close Window” buttons.


26

When changes are made to Prod, it is possible for those new Production changes to fail miserably such that management wants the changes backed out. To back-out in ISPW, select the Task in your Assignment, right-Click on the selected Task and Click on “Fallback”.

A Fallback operation will archive the current Production level source and parts into the ISPW Warehouse and then bring back the previous version of the source and parts and Deploy (where required). (The Fallback can be on selected Tasks in a Release or the entire Release).


27

A Fallback is different from a Regress. A Regress will copy the code back to the prior level, where a Fallback will bring code out of the warehouse at that level and restore a previous release to be the production release.

Click OK to confirm the Fallback operation.

Before the Fallback processing can happen, PRD level approvals are required. Note the status of each of the tasks. The Set is awaiting approval. To issue the approval, click once on the inactive task, then right-click on the PRD box in the Life-Cycle diagram and click Approve. The Set processor will begin processing the Fallback operation.


28

The Set has backed up the Prod source and reinstated the previous version and Deployed (where necessary). A Fallback does not necessarily have to be to the -1 version. Older versions can be selected for the Fallback as well.

To confirm the Fallback has worked, look at the “ISPW Component Versions” View. To do this Right-Click on the active version of TREXX01, mouse over “View” and click “Component Versions”.

Note below the Tasks now reflect a Fallback has been performed and the old task is now inactive. If you do not see the inactive task, please click on the inactive button.

Note the current PRD version number is one less than the previously listed PRD version – that is the current PRD version is the version that was there prior to your promotion and the -1 version is the version you initially promoted.


29

As a Developer you are now finished with your Assignment, so it can be closed. Assignments are closed manually and are usually closed to unclutter the ISPW Container List View.

To Close your Assignment, right-click on your Assignment and click “Close.” A Close confirmation panel is presented.

Click OK to complete the Close.


30

For audit purposes, closed Assignments, Sets and Releases are never deleted from ISPW. They are just filtered out of the standard day-to-day filtering. Once an Assignment, Set or Release is closed it is removed from the standard filtered list, but it is still part of ISPW history and can be viewed at any time. To view the Assignment you just closed, click on the Container view, click on the Filter icon.


31

On the Containers Filter dialog,

Check Assignment and uncheck Release and Set.

Specify your Application and your TD TSO id under Application and Owner.

Select “Show closed containers”. Click OK.

The list of Containers in the ISPW Containers View will update and should present your closed Assignment. Double Click on your Assignment to open it.


32

In the “ISPW Assignment” (this is a new view that has been added to TOPAZ ISPW) view you will see the Tasks which you worked on as part of the development you did in in this Assignment. This information is kept forever. You may also group your tasks and view other assignments. Also note it alerts you to the fact this is a closed Assignment.


33

Now change your containers filter to no longer show closed containers:

Uncheck Show closed containers. Click OK.


34

You are done – your job has been to change a REXX program. As a part of this exercise, you have been able to use Compuware Topaz Workbench and ISPW to execute a workflow:

• Created an Assignment

• Added and checked out a REXX program

• Changed it using Topaz Editor

• Promoted the Task from DEV1 to QA1 with a generate of the program

• Promoted the Task from QA1 to STG

• Promoted the Task from STG to PRD

• Performed an approval

• Performed a Fallback

• Closed your Assignment to complete the change cycle

• Searched for closed containers

Congratulations! This completes the ISPW tutorial for Compuware Test Drive.

NEXT STEPS

Click on the link below to return to the Compuware Test Drive main page and choose your next road trip!

COMPUWARE TEST DRIVE

https://compuware.com/test-drive/

ISPW Change a REXX program - Compuware Drive/ISPW... · 2020-04-02 · 1 Compuware Test Drive ISPW...

Documents

Transcript of ISPW Change a REXX program - Compuware Drive/ISPW... · 2020-04-02 · 1 Compuware Test Drive ISPW...