Change man

© 2003 Kanbay Incorporated - All rights reserved

Change Man

Change Man

Purpose• To Learn about Change Man process.

Change Man

Introduction

▲What is Changeman?

▲What will it do for me?

▲What do I use Changeman?

Change Man

What is Changeman

Changeman is used to develop and install various types of source code into a mainframe environment Changeman provides security for the code

Changeman insures a backup of the current source code and can create backups of multiple generations

Changeman provides a backout procedure to allow for recovery of the original code

Change Man

What will it do for Me

Allow a developer to capture a copy of the current production code

Permit a developer to edit the code

Provide a developer with different environments in which code can be tested

Allow a developer via the approval process to install the edited code into production

Change Man

Support for Changeman

Requests for assistance on a Changeman question or problem can be sent to the ADSHELP mailbox

To obtain a copy of the training guide, send a request to the Changeman Administrator

If urgent assistance is needed please call the Helpdesk and open a Netman ticket

Change Man

Support for Changeman

Changeman Administrators :

HCS

Joe Friendrich CAL190 Primary Contact 757-4200 Ext.

7175

Cathy Olivieri -Moss EMP323 Backup Support (630) 350-6729

HFN

Cathy Olivieri -Moss EMP323 Primary Contact (630) 350-6729

Joe Friendrich CAL190 Backup Support (408) 757-4200 ext.

7175

Change Man

Key Terms

Staging data sets : Created by Changeman to store the contents of the developer’s changes

Library types : 3 character identifier of the type of source or non-source code that will be changed,

i.e jcl, prc , etc

Source : Code that has a process executed.

For example

Cobol2 or Assembler compile.

Change Man

Key Terms

Non Source : Code that is edited but has no special process run against it. For example, procs, jcl c control cards, etc

Baseline: the current production module

Audit : A process that checks the validity of changes based on current baseline and concurrent development

Checkout : A process that provides the developer a baseline copy of module

Staging : A process used to edit, compile etc a module

Change Man

Creating a Changeman Package

Signon to ‘TSOXC’

At the main menu, Type in ‘C’ on the command line

This option displays Changeman’s Build Menu

Change Man

Change Man 4.1.OP Primary Option Menu Option

1. Build - Create, update and review package data

2. Freeze - Freeze or unfreeze a package

3. Promote - Promote or demote a package

4. Approve - Approve or reject a package

5. List - Display (to process) package list

B. Backout - Back out a package in production

D Delete - Delete or undelete a package

L Log - Browse the activity log

N Notify - Browse the Global Notification File

O OFMlist - Online Forms package list

Q Query - Query packages, components and relationships

R Revert - Revert a package to DEV status

X Exit - Exit Change Man

Press ENTER to process; enter END command to exit.

Change Man

Change Man 4.1.OP Primary Option - Menu Option Option ==> 1

1. Build - Create, update and review package data














Change Man

Build Options 0. Dates Display the installation calendar

1. Create Create a new package

2. Update Update package information

3. OFM Create, update, approve or review online forms

4. Utility Rename and Scratch information

5. Checkout Check out components form baseline or promotion

6. Stage Stage, edit browse and delete components

7. Audit Audit a package

8. Recompile Recompile source code from baseline or promotion

9. Relink Relink or delete load modules

B Browse Browse print copy baseline or promotion

C Compare Compare staging to baseline or promotion

L Listing Browse compressed listings

S Scan Scan baseline for character strings

Z Compress Compress change package Staging Libraries

Press ENTER to process; Enter END command to exit

Change Man

Create a New Package Option ==> LL Long method - Prompt for package description and special instructions

Package Title

==> Test new application PCRS

Application => XXXX Blank or pattern for list

Requester’s Name => Joe Friendrich

Requester’s Phone => 7175

Spurf/Incident/Problem => xxxxxxxxx (E######, W#######,

Must use the correct project number G#####, P98#####-S

S=1,2,3,A)

Package Level => 1 (1-Simple, 2-Complex, 3-Super , 4-Participating)

Package Type => Planned (Planned or Unplanned)

Package Time Span => Perm (Permanent or Temp)

Package To Copy Forward => (Optional package Nme)

Unplanned Reason Code => (*for list)

Temp Change Duration => (In days)

Press ENTER to process; Enter END command for exit.

Change Man

Create : Package Description

Command ==> Scroll ==> CSR

Press ENTER or END to continue or type CANCEL to exit

(minimum one line , maximum 46 lines)

!!! _A brief and detailed description of the contents of the Changeman package.

!!!!

******Bottom of data*******

!!!!

!!!!

Change Man

Create : Installation Instructions

Command ==> Scroll ==> CSR


Contingency ==> 3 1- Hold production and contact analyst

2- Backout change continue production

3- Other ==> call Developer

Scheduler ==> (CMN, Manual )

(minimum one line maximum 46 lines)

!!!!_A brief set of instructions regarding the procedures to follow for the installation of this package. Example could be; what to do if this package causes a production abend’.!!!!

Change Man

Create : On Site Information

Command ==>


Install Date/ Time

YYMMDD From to Primary/Backup contacts Phone #

980425 0001 2339 “primary contact” xxx xxxx

“backup contact” xxx xxxx

Change Man

Processing a Component

Once a package is created the developer must populate it with components that need to be updated or created for the production environment

Checkout moves a copy of the current baseline component into the appropriate staging data set

Staging allows the developer to edit the component

Change Man

Build Options Option ==> 5

0. Dates Display the installation calendar










B BrowseBrowse print copy baseline or promotion






Change Man

Checkout Options

Option ===> 1

Package ID ===> PCRS1

1. Base/Prom - Checkout from baseline or promotion libraries

2. Package - Checkout package components

Press ENTER to process Enter END command to exit.

Change Man

Checkout PCOCD100 checked out

Option ==>

L- list libraries where component is located

Package ID => PCRS000001 (Package or Application name)

Component Name => PC0CD100 (blank or pattern for list ;* for all member)

Library type => JCL (Blank for list )

Source Library => 0 (Baseline 0 to -n Promotion +1 to +n)

Confirm Request => YES (Y/ N)

Checkout Mode => 2 (1- Online, 2-Batch)

Press ENTER to process; Enter END command to exit.

Change Man

Build Options Option ==> 6

0. Dates Display the installation calendar










B BrowseBrowse print copy baseline or promotion






Change Man

Stage Options

Option ===> 2


1. Dev - Stage components from development libraries

2. Package - Process package components

3. Parms - Specify component list selection criteria

Press ENTER to process Enter END command to exit.

Change Man

Stage : PCRS000001 Components Row 1 to 2 of 2

Command ===>

R Name Type Status Chged Lang Procnme ID

E PHCM0016 JCL Checkout 980423 085939 Cal190

********Bottom of data********

Change Man

Auditing A Changeman Package

When the developer is done updating the module, an audit is done on the package.

If the audit produces acceptable return code, the package is frozen

The package can now be tested in development and/ or Quality Assurance.

Change Man

Audit Change Package

Command ==>


Audit Staging Libraries Only ===> NO (Y/N)

Auto Resolve of Out -Of-synchs ===> No (Y/N)

Job Statement information:

=>// Cal190H Job (Qhcmq, Chgman), ‘Changeman’,

=> // Class=W , Msgclass =X,notify = Cal190

=> //*

Press ENTER to process; Enter END command to exit.

Change Man

Testing

Change man provide up to 99 testing environments

Promotion is the method used to move the developer’s changes to the testing environment

To promote package the developer should freeze the package before promoting to developer should Freeze the package before promoting to development or QA

Developers have authority to promote to development

Quality Assurance has authority to promote to QA

Change Man

Change Man 4.1.OP Primary Option Menu Option Option ==> 21. Build - Create, update and review package data














Change Man

Freeze Options

Option ==> 2

Package ID ==> PCRS000001

1. Online - Freeze package Online

2. Batch - Freeze package in batch

3. - Function is not available

4. Reset - Reset indicator after unsuccessful batch freeze

Automatic promotion after freeze ===> No (Y/N)

Online or batch promotion ===> B (O-Online , B-Batch)

Press ENTER to process; Enter END Command to exit

Change Man

Change Man 4.1.OP Primary Option Menu Option

Option ==> 31. Build - Create, update and review package data














Change Man

Promote Change Package

Command ===>


Press ENTER to Process; Enter END Command to exit

Change Man

Promote Change Package

Command ==> Scroll ===> CSR

PKG ID : PCRS000001 Creator: Ven017 STAT: FRZ Install Date : 9804300

Current promotion level : STAGING - 0

Maximum promotion level : QTESTING-10

Action Requested => P (P - Promote, D-Demote, C-Check for overlay)

Online or Batch => B (O - Online, B- Batch )

Level to check => 1 (Required for Action C)

PROMOTE/DEMOTE HISTORY LVL NICKNAME, DATE TIME ID

Change Man

Promote Options

Option ===>F

F - Full promotion of the entire package to another promotion level

S - Selective promotion of components to another promotion level

PKG ID : PCRS000001 Creator : VEN017 STAT: FRZ Install DTE : 980430

Current Promotion Level : STAGING -0

Maximum promotion level : QTESTING -10

Next Promotion Level ===>1

Job Statement information :

//Cal190R JOB (Qhcmq, CHGMAN), CHANGEMAN’,_

//CLASS =W, MSGCLASS=X, NOTIFY=CAL190_

(User will need to create jobcard the first time you use Changeman )

Press ENTER to process; Enter END Command to exit.

Change Man

Installing a Changeman Package

Once a package has been tested the approval process will install the package into production.

The package is now ready to be approved by the different approvers as defined by the Changeman administrator

Once a package is fully approved and the date and time parameters are met, the Changeman scheduler will submit necessary jobs to install the package into production.

Change Man

Change Man 4.1.OP Primary Option - Menu Option Option ==> 41. Build - Create, update and review package data














Approve/Reject Options

Option ==> 1

Package ID : PCRS000001 Status : FRZ Install DATE : 980425

1. Approve - Approve or reject a change package

2. Reasons - Display reasons a package was rejected

3. Query - Query change package

4. Reset - Reset approval in progress indicator

Press ENTER to process Enter END command to exit

Change Man

Approval List

Command ===> Scroll ===> CSR

Press Enter to process; enter END command to exit

PACKAGE ID : PCRS000001 STATUS : FRZ INSTALL DATE : 980425

Approver Description ID DATE TIME SEQ STATUS

_a QA Acceptance Testing Completed 005

_a Application Devl Manager OK for Production 045

Change Man

Summary

Change man is a ‘Best in Class’ tool used at HI for updating and creating new processes that run on a mainframe environment

Change man offers ‘Security’ of all source code

Change man provides a ‘Backout Procedure’ to insure that a component can be restored to its original state if necessary

Change man saves Multiple Generations of a source module

Change Man

Change man

Education

Transcript of Change man