Download - Compuware Test Drive ISPW Change a COBOL … Drive/ISPW...S_Explorers_TW_Test_Drive.pdf exercise before starting any tutorial script. If, at any point during your experience, your

1

Compuware Test Drive

ISPW Change a COBOL program with Fallback and Deploy Revised: 7/17/2020

This tutorial will review how to make changes to a COBOL 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

Generate (AKA Compile) ................................................................................................................ 15

Promotion ...................................................................................................................................... 19

NEXT STEPS .................................................................................................................................... 46


3

Getting Started with SCM - ISPW

The goal of this Test Drive is to make a change to a COBOL 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 to a program

• Generating/compiling

• Promotion to Production

• View deployment of module

• Fallback a module

• View versions of module

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 COBOL program (TPROG02, 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 COBOL program using Topaz editor then generate and promote it through the Application Life-Cycle to Production.

First, you will find and add a COBOL 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 COB, this will allow you to focus only on the COBOL program components available in your stream | application at the PRD level. Click Apply (circled).


9

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

Scroll through the list and find TPROG01 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 COBOL program into. Type a description and click OK.

ISPW will issue a message confirming that the Assignment was successfully created. Click OK (screenshot not shown).


11

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

A message will be displayed to inform you that the task has been added to your Assignment. Click OK (screenshot not shown).


12

Your Assignment has been created and you should now have a COBOL 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. A developer will spend most of their time in an Assignment container.

Note that the COBOL 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.

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.

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

those levels.


13

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.

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

The version’s source will be presented in the Topaz editor for editing. If you see the message below you can either click Yes or check Use this as the default and do not ask again and


14

then click Yes. This will download the contents of the copybooks, so they can be used by the Topaz editor for various activities.


15

Change the source using the Topaz editor (don’t break the program).

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

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

Generate (AKA Compile)


16

The COBOL program will be generated/compiled, and your Assignment Task List will be updated to reflect the new status.

• The Operation will be Generate

• The User ID, Date/Time will be updated

• The Message will be updated to reflect the successful completion of the generate

Now it is time to compile/generate the program, so we can do our testing. To do this, right-click on TPROG01 and click Generate.

The status column will display a message indicating that the Task is being generated. The screen will refresh automatically when the generate is done. At that time, the Task will be updated with the date and time of the generate, the user who performed the generate and the operation will reflect a generate has occurred.

Ensure that the generate worked and ended with a return code zero.

View the generate listing to do this. If the program did not generate correctly, fix the error and regenerate.


17

After the generate finishes you can browse the Generate listing at any time.

To do this, right-click on the Task and click “View Generate Listing.”

You will get this informational message if there are characters in your listing that can’t be converted for display purposes. If you do get it this is not a problem and you can click OK.


18

Scroll up and down, notice that everything is available that you normally see in a compile listing.

Close the Listing display when you are finished.

You can also view the output of the generate job.

Right-click on the task and click “View Generate Job Output.”

This displays the output of the job that did the Generate.


19

Close the Job Output display when you are finished.

Promotion


20

At this point you have

• Edited a COBOL program

• Used the Topaz Editor to help you make your changes

• Generated your program

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.


21

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.

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 as well).


22

Note the Operation column shows Generate as the last operation. The SET processor performed a promotion and then a generation as ISPW recognized a generate was required for COBOL types at the QA1 level based on the configuration of this application. This can be configured by the ISPW administrator.

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.


23

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 as well as the highlighted Level in the picture).

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)


24

The promotion is successful. The last Operation shows Promote and the STG box in the life cycle has been highlighted. The source and its parts have all been promoted to STG and no recompile was done.

Click OK.


25

Let’s view the Parts that were promoted along with the source.

Highlight TPROG01, right-click, select View, Parts.

You can see the different parts that were promoted along with the Cobol source. There is an Object and Load module, a listing and the Compuware Source Listing (part DMEM). When TPROG01 and its Parts reaches production some of these Parts will be deployed to runtime libraries. Close the ISPW Parts view.

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


26

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 COBOL program, and its parts will be promoted

You can monitor the progress by clicking the refresh button.

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


27

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.


28

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:


29

• 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. Highlight TPROG01, right-click, select View, Approvals.

You will see two approvers. Right-click on CWEZMGR and select Approve. This will approve the promotion and all Parts will be promoted to PRD. Close the ISPW Approval window. ISPW will now perform the promotion of the Tasks collected in the SET to the PRD Level.


30

You can see in the updated screen below that:

• SET processing has completed

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


31

• A Deploy has taken place

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

Notice 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.


32

Now let’s open the Deployment view.

Click Window, Show View, Other. Expand ISPW, highlight ISPW Deployment and click Open.

The Deploy view is opened. Click on the filter.


33

Select Today’s date and click OK.

This view will show all tasks which were deployed today.


34

Highlight the task completed for this Test Drive, right-click and View Package Details.

This shows the modules that were deployed and the datasets they were deployed to. Highlight the first BATCH deploy. You will see in the lower window the program that was deployed and the name of the dataset it was deployed to, along with other information.


35

If you highlight the next program you will see the Source Shared Directory (SSD) where the Compuware Listing was stored. You can continue through all the programs if you wish. Notice the tasks were deployed to 2 different LPARs, CWC2 and CWCC.

Click Cancel.

Now select View Request Details.


36

This View contains additional detailed information on the deploys. You will see all the information pertaining to the deploy request, dates, times, dataset names, etc.


37

Click on the first Item 1 TPROG01 LOAD Completed under Pkg 1 and copy the name of the Storage dataset. Click OK and click on Host Explorer.

Expand Test Drive, right-click on z/OS Datasets, select Add Filter.


38

Paste the dataset name in the filter. Click OK.


39

The filter should be added pointing to the dataset.

Expand the arrow.

You should see TPROG01 in the datset showing that the deploy was successful. If you like, the same exercise can be done for all the other deployed modules.


40

Back in the ISPW perspective Life Cycle view, we can see from the PRD level box that V3 is in PRD. Your version numbers may be different. Close the ISPW Deployment View. There turns out to be an error in our program and it needs to be removed from production. To do this a Fallback will be performed. A Fallback will take the current production version and put it in the warehouse and bring the prior production version back as the latest production version. Return to ISPW (click on the ISPW perspective), right-click on the program and select Fallback.

Once Fallback is selected you will receive the following message.

Click OK to continue.

An approval is required to do the Fallback at the PRD level. Click on the inactive task.


41

Right click the PRD stage and select Approve.

Click on the view menu (a downward pointing triangle). This will allow you to view inactive tasks.


42

Select Show Inactive Tasks.

Scroll to the right to see the version information. Here you can see that V1 (internal version) has been brought out of the Warehouse and is the current production version and V2 (internal version) has been placed in the Warehouse and is now inactive. Your version numbers may be


43

different. Turn off the inactive task button. Now only the current version V1 appears as the internal version. Your screen may have a different version number.


44

Right-click the task and select View, Component Versions.

You see the current PRD version. Make sure to select Show Inactive Versions. You will see all the

inactive and the active PRD versions. Note that the last operation is Implement. This means that in addition to the Fallback in PRD, a deploy was done to restore the deploy datasets to the correct version of the code. You have completed your Test Drive, now it is time to close the assignment.


45

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.

Click on ISPW Containers.

To Close your Assignment, right-click on your Assignment and click “Close.”

A Close confirmation panel is presented.

Click OK to complete the Close.

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.


46

You are done – your job has been to change a Cobol program, promote it through the Stream to PRD. Examine the deployed modules and perform a Fallback on the module in PRD. As a part of this exercise, you have used the Compuware Topaz Workbench and ISPW to execute a workflow and:

• Created an Assignment

• Checked out a Cobol program to the DEV1 level

• Changed it using the Topaz editor

• Compiled/Generated the program

• Promoted the Task from DEV1 to QA1

• Promoted the Task from QA1 to STG

• Promoted from STG to PRD a deploy was initiated automatically

• Viewed the Deployed Tasks

• Performed a Fallback

• Viewed the Version History of the Task

• Closed your Assignment to complete the change cycle

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/