Download - ChangeMan - Presentation- Level 1
-
8/22/2019 ChangeMan - Presentation- Level 1.
1/33
VisionPLUS
ChangeManTool
OverviewLevel 1
Presented By
Swathi Peicharla
-
8/22/2019 ChangeMan - Presentation- Level 1.
2/33
Agenda
IntroductionOverview of ChangeMan Lifecycle Close
-
8/22/2019 ChangeMan - Presentation- Level 1.
3/33
Change Man is a comprehensive system designed toprovide both reliable & streamlined implementation of
software changes from development into production.
Change Man lets you quickly
implement an automated inf rastructure
that delivers tangible and long-term
benefits.
What is ChangeMan ?
-
8/22/2019 ChangeMan - Presentation- Level 1.
4/33
Features Of ChangeMan
Unique package concept guarantees the coordination of your change
Concurrent development is managed
Controls version discrepancy and out-of-synch component relationships
Maintains listings on-line for immediate access
Provides notifications
Full suite of on-line and batch query and reporting capabilities
Maintain historical information in a single repository.
-
8/22/2019 ChangeMan - Presentation- Level 1.
5/33
Create
Checkout Stage Audit
Freeze
Promote
ApproveInstallBackout
Lifecycle Automation
Promote
-
8/22/2019 ChangeMan - Presentation- Level 1.
6/33
Stage Audit
Promote
ApproveInstallBackout Freeze
CreateCheckout
Lifecycle Automation:
Create
Promote
-
8/22/2019 ChangeMan - Presentation- Level 1.
7/33
Create Change Package Within Change Man, a Change Package is the vehicle in which all
changes are moved from a development environment to a production
environment.
A change package may contain one or more components (source,
copybook, load, JCL, control cards, compiling procedures,
documentation, and other components) which are required to
implement a software change.
-
8/22/2019 ChangeMan - Presentation- Level 1.
8/33
Create Change Package
-
8/22/2019 ChangeMan - Presentation- Level 1.
9/33
Stage Audit
Promote
PromoteApproveInstallBackout
Impact
Analysis
Freeze
CreateCheckout
Lifecycle Automation:
Checkout
-
8/22/2019 ChangeMan - Presentation- Level 1.
10/33
Checkout The checkout process allows to copy components from baseline
libraries to a Change Man staging library or to a personal
development library where you can make changes.
-
8/22/2019 ChangeMan - Presentation- Level 1.
11/33
BaselineLibraries
DevelopmentLibraries(new applications)
Source
Load
DBRMetc.
Onlyone version
can be checked out
Unless parallel
development
enabled
Staging Libraries Created
Application
Package Number
Library Type
Application Grouping ExistsSource Members
Created
Lifecycle Automation:
Checkout
-
8/22/2019 ChangeMan - Presentation- Level 1.
12/33
Stage Audit
Promote
PromoteApproveInstallBackout
Impact
Analysis
Freeze
CreateCheckout
Lifecycle Automation:
Stage
-
8/22/2019 ChangeMan - Presentation- Level 1.
13/33
Stage
Components such as fixes,Control cards or copy members are
copied into the staging libraries, if they are not there already.
For source components, staging will run the appropriate
translation procedures to create associated load modules.
-
8/22/2019 ChangeMan - Presentation- Level 1.
14/33
StagingLibraries
Edit, Compile
&Link
Libraries
Created
Uniqueto
Package
Load Members Created
Editing Uses Staging Libraries
Lifecycle Automation:
Stage
-
8/22/2019 ChangeMan - Presentation- Level 1.
15/33
Stage Audit
Promote
PromoteApproveInstall
Backout
Impact
Analysis
Freeze
CreateCheckout
Lifecycle Automation:Audit
-
8/22/2019 ChangeMan - Presentation- Level 1.
16/33
The audit process identifies out-of-synch condition with in the BaselineLibraries and other participating packages.
It Checks whether package is complete and logically correct
MUST RUN Prior to Freeze
Out-of-synch conditions could result from:
Copybooks being modified after compiling the source component thatcalls them
A package containing a load component that does not match its sourcecomponent
Member Not being active
Member Copied, but not staged
Lifecycle Automation:Audit
-
8/22/2019 ChangeMan - Presentation- Level 1.
17/33
Stage Audit
Promote
ApproveInstallBackout
Impact
Analysis
Freeze
CreateCheckout
Lifecycle Automation:
Promotion
Promote
-
8/22/2019 ChangeMan - Presentation- Level 1.
18/33
Promotion allows a package to be moved through
various levels of testing. For example, promote from system testing to
acceptance testing.
Lifecycle Automation:Promote
-
8/22/2019 ChangeMan - Presentation- Level 1.
19/33
StagingLibraries
Members
Copied
Other
Processing
Eg. (JCLCHECK)
UNIT Testing LibrariesUNIT Testing
.
.
.
ACCT Testing LibrariesACCT Testing
Promote
-
8/22/2019 ChangeMan - Presentation- Level 1.
20/33
Baseline
Libraries
StagingLibraries
Checkout
Production
Development
Testing Unit Promotion
Libraries
Promote
Stage
System .. QA
A Quick Recap
-
8/22/2019 ChangeMan - Presentation- Level 1.
21/33
Stage Audit
Promote
PromoteApproveInstall
Backout
Impact
Analysis
Freeze
CreateCheckout
Lifecycle Automation:
Freeze
-
8/22/2019 ChangeMan - Presentation- Level 1.
22/33
The freeze process locks the package and makes the package
available for the promotion and approval processes.
Lifecycle Automation:Freeze
-
8/22/2019 ChangeMan - Presentation- Level 1.
23/33
PackageMaster
Install jobs created
Approvers informed
AuditChecked
Changes
Between
Audit/FreezeHIghlighted
Package can
no longer
be CHANGED
Lifecycle Automation:
Freeze
-
8/22/2019 ChangeMan - Presentation- Level 1.
24/33
Stage Audit
Promote
PromoteApproveInstallBackout
Impact
Analysis
Freeze
CreateCheckout
Lifecycle Automation:
Approve
-
8/22/2019 ChangeMan - Presentation- Level 1.
25/33
The approval process consists of browsing the package information and
Staging Libraries for quality control and standards and selecting to
Approve (or Reject) the package.
A change package must be in Frozen (FRZ) status to be Approved or
Rejected.
Lifecycle Automation:Approve
-
8/22/2019 ChangeMan - Presentation- Level 1.
26/33
Stage Audit
PromoteApproveInstallBackout
Impact
Analysis
Freeze
CreateCheckout
Lifecycle Automation:
InstallPromote
-
8/22/2019 ChangeMan - Presentation- Level 1.
27/33
After all of the approvals have been gathered by Change Man, the
package is ready to be installed.
Installation depends on whether or not an internal scheduler is set up
If no scheduling system is specified, the package goes through the
Installation process immediately.
If a Scheduling system is specified , the package follows the respective
Scheduling system.
Lifecycle Automation:Install
-
8/22/2019 ChangeMan - Presentation- Level 1.
28/33
Install Jobs Executed
final approval
Change Man internal scheduler
external scheduler
Copies to production
Ripples baseline
Lifecycle Automation:
Install
-
8/22/2019 ChangeMan - Presentation- Level 1.
29/33
Stage Audit
PromoteApproveInstallBackout
Impact
Analysis
Freeze
CreateCheckout
Lifecycle Automation:
BackoutPromote
-
8/22/2019 ChangeMan - Presentation- Level 1.
30/33
If there is a problem with the change package after it has been Installed,
the change package is backed out by deleting the updated component in
production and then retrieving the previous version of application
software from the Backup Library.
ChangeMan will back out the entire package by copying the components
from the Backup Libraries to overlay production.
The package status is changed from BAS to BAK.
Lifecycle Automation:
Backout
-
8/22/2019 ChangeMan - Presentation- Level 1.
31/33
Complete Package Only
Package in BAK StatusNeed to re-Audit
re-Freeze
re-Approve
Install
Lifecycle Automation:
Backout
-
8/22/2019 ChangeMan - Presentation- Level 1.
32/33
Baseline
Libraries
StagingLibraries
Checkout
Production
Development
Testing Unit Promotion
Libraries
Promote
Stage
System .. QA
Production ProductionLibraries
A Quick Recap
-
8/22/2019 ChangeMan - Presentation- Level 1.
33/33
Thank You