Scribd Logo
Upload

Welcome to Scribd!

  • 244 views

    ChangeMan - Presentation - Level 1.

    Uploaded by

    Bharat Sahni
    ChangeMan - Presentation- Level 1.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    ChangeMan - Presentation - Level 1.

    Uploaded by

    Bharat Sahni
    244 views33 pages
    ChangeMan - Presentation- Level 1.

    Original Title

    ChangeMan - Presentation- Level 1.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    ChangeMan - Presentation- Level 1.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    244 views33 pages

    ChangeMan - Presentation - Level 1.

    Uploaded by

    Bharat Sahni
    ChangeMan - Presentation- Level 1.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 33

    VisionPLUS

    ChangeMan Tool Overview


    Level 1
    Presented By Swathi Peicharla

    Agenda
    Introduction Overview of ChangeMan Lifecycle Close

    What is ChangeMan ?

    Change Man is a comprehensive system designed to provide both reliable & streamlined implementation of software changes from development into production.

    Change Man lets you quickly implement an automated infrastructure that delivers tangible and long-term benefits.

    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.

    Lifecycle Automation
    Checkout Create Stage Audit Promote

    Promote
    Install Approve Freeze

    Backout

    Lifecycle Automation: Create


    Checkout Create Stage

    Audit Promote

    Backout

    Install

    Approve Freeze

    Promote

    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.

    Create Change Package

    Lifecycle Automation: Checkout


    Checkout Create Impact Analysis Stage

    Audit Promote

    Backout

    Install

    Approve Freeze

    Promote

    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.

    Lifecycle Automation: Checkout


    Baseline Libraries Staging Libraries Created
    Application Package Number Library Type Source Load DBRM etc.

    Application Grouping Exists Source Members Only one version Created


    Unless parallel development enabled

    can be checked out

    Development Libraries
    (new applications)

    Lifecycle Automation: Stage


    Checkout Create Impact Analysis Stage

    Audit Promote

    Backout

    Install

    Approve Freeze

    Promote

    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.

    Lifecycle Automation: Stage


    Staging Libraries Load Members Created
    Edit, Compile & Link

    Libraries Created Unique to Package

    Editing Uses Staging Libraries

    Lifecycle Automation:
    Checkout Create Impact Analysis

    Audit
    Stage

    Audit

    Promote

    Backout Install Approve Freeze Promote

    Lifecycle Automation: Audit


    The audit process identifies out-of-synch condition with in the Baseline Libraries 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 that calls them A package containing a load component that does not match its source component Member Not being active Member Copied, but not staged

    Lifecycle Automation: Promotion Checkout


    Create Impact Analysis Stage

    Audit

    Promote

    Backout

    Install

    Approve Freeze

    Promote

    Lifecycle Automation: Promote


    Promotion allows a package to be moved through various levels of testing. For example, promote from system testing to acceptance testing.

    Promote
    Staging Libraries UNIT Testing Libraries UNIT Testing . . . ACCT Testing Libraries ACCT Testing
    Members Copied

    Other Processing Eg. (JCLCHECK)

    A Quick Recap
    Production
    Baseline Libraries

    Checkout Development
    Staging Libraries

    Stage

    Promote Testing
    Unit

    Promotion System Libraries

    ..

    QA

    Lifecycle Automation: Freeze Checkout


    Create Impact Analysis Stage

    Audit

    Promote

    Backout Install Approve Freeze Promote

    Lifecycle Automation: Freeze


    The freeze process locks the package and makes the package available for the promotion and approval processes.

    Lifecycle Automation: Freeze


    Package Master
    Audit Checked

    Install jobs created

    Approvers informed
    Changes Between Audit/Freeze HIghlighted Package can no longer be CHANGED

    Lifecycle Automation: Approve Checkout


    Create Impact Analysis Stage

    Audit

    Promote

    Backout

    Install

    Approve Freeze

    Promote

    Lifecycle Automation: Approve


    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: Install


    Checkout Create Impact Analysis Stage

    Audit

    Promote

    Backout

    Install

    Approve Freeze

    Promote

    Lifecycle Automation: Install


    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

    Install Jobs Executed


    final approval Change Man internal scheduler

    external scheduler

    Copies to production

    Ripples baseline

    Lifecycle Automation: Backout Checkout


    Create Impact Analysis Stage

    Audit

    Promote

    Backout

    Install

    Approve Freeze

    Promote

    Lifecycle Automation: Backout


    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


    Complete Package Only


    Package in BAK Status

    Need to re-Audit re-Freeze re-Approve Install

    A Quick Recap
    Production
    Baseline Libraries

    Checkout Development
    Staging Libraries

    Stage

    Promote Testing
    Unit

    Promotion System Libraries

    ..

    QA

    Production

    Production Libraries

    Thank You

    You might also like