Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 63 views

    Change Man: Changeman Is Used in Development Enviroment, For Easy Version Controlling of Components

    Uploaded by

    Leo
    This document provides instructions for using the Changeman tool for version controlling components in a development environment. It describes the basic steps a developer would take to: 1. Create a package to group the components being changed. 2. Check out components from production or a baseline version into the package for editing. 3. Stage local changes to the components into the package. 4. Promote the package to a test region once changes are compiled for testing.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd

    Change Man: Changeman Is Used in Development Enviroment, For Easy Version Controlling of Components

    Uploaded by

    Leo
    63 views9 pages
    This document provides instructions for using the Changeman tool for version controlling components in a development environment. It describes the basic steps a developer would take to: 1. Create a package to group the components being changed. 2. Check out components from production or a baseline version into the package for editing. 3. Stage local changes to the components into the package. 4. Promote the package to a test region once changes are compiled for testing.

    Original Description:

    Changeman

    Original Title

    Changeman

    Copyright

    © © All Rights Reserved

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides instructions for using the Changeman tool for version controlling components in a development environment. It describes the basic steps a developer would take to: 1. Create a package to group the components being changed. 2. Check out components from production or a baseline version into the package for editing. 3. Stage local changes to the components into the package. 4. Promote the package to a test region once changes are compiled for testing.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    63 views9 pages

    Change Man: Changeman Is Used in Development Enviroment, For Easy Version Controlling of Components

    Uploaded by

    Leo
    This document provides instructions for using the Changeman tool for version controlling components in a development environment. It describes the basic steps a developer would take to: 1. Create a package to group the components being changed. 2. Check out components from production or a baseline version into the package for editing. 3. Stage local changes to the components into the package. 4. Promote the package to a test region once changes are compiled for testing.

    Copyright:

    © All Rights Reserved
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    of 9

    CHANGE MAN

     
     Changeman is used in development enviroment,
    for easy version controlling of components   
      

    What will it do for me?

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


    (base version)

    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

    What team member will do when he/she given a task?

    1. Create a package

    2. CHECK OUT components from production/baseline (if that program


    already
    exists) or STAGE a component (program/jcl/proc/dbb ....) after
    developed the component in local directory into pakcage.

    3. Edit/delete the components and sumit for compilation

    4. For testing he can PROMOTE that package to testing region

    STEP 1 -- CREATING PACKAGE

    FOllowing screen is the CHANGE MAN mainscreen


    Type 1 at option prompt, you will get following screen

    Type 1 at OPTION prompt, you will be prompted with following screen


    press ENTER,
    It will show two screen, there you need to enter the details of
    package (usaually audit program
    details). then it will careate the package name using APPLICATION
    type that you provided.

    In our case it is - SRK1002833 (pakcage number)

    STEP 2 -- CHECK OUT (coping from


    baseline/production)

    Changeman Mainscreen
    Type 1 at option prompt, you will get following screen

    type 5 at OPTION prompt, you will prompted with the following screen
    . . . . . . . . . . . . . . . . . . . . . . . .
    . .
    ------------------------------- CHECKOUT OPTIONS
    -----------------------------
    OPTION ===>

    PACKAGE ID ===> FCM1002833

    1 Base/Prom - Checkout from baseline or promotion libraries


    2 Package - Checkout package components

    Press ENTER to process; Enter END command to exit.

    Type 1 at OPTION prompt, you will prompted with the following screen

    In the below screen COMPONENT NAME and LIBRARY TYPE should be entered

    . . . . . . . . . . . . . . . . . . . . . . . .
    . . .
    ----------------------------------- CHECKOUT
    ----------------------------------
    OPTION ===>

    L - List libraries where component is located

    PACKAGE ID ===> SRK1002833 (Package name)

    COMPONENT NAME ===> PROG1 (Name or Pattern for list; "ABCDEF" OR


    "ABC*")
    Pattern of only "*" Checks Out all
    Components
    related to Library Type.
    LIBRARY TYPE ===> HC3 (Blank for list)
    LANGUAGE ===> (Applies to source code; * for list)
    SOURCE LIBRARY ===> 0 (Baseline 0 to -n; Promotion +1 to
    +n)

    CHECK OUT TO ===> S (S-Staging library, P-Personal


    library)
    PERSONAL LIBRARY ===>
    LIBRARY DSORG ===> (Personal library: PDS, PDSE, SEQ,
    PAN, LIB)

    CONFIRM REQUEST ===> NO (Y/N)


    CHECKOUT MODE ===> 1 (1-Online, 2-Batch)
    LOCK COMPONENT ===> NO (Y/N)

    Press ENTER to process; Enter END command to exit.


    The component (program/copybook etc...) that you entered will be
    copied to your package SRK1002833

    STEP 3 - STAGING (coping component from local pds)

    Type C;;1;;6 in ISPF screen, you will get following screen

    . . . . . . . . . . . . . . . . . . . . . . . .
    . . .
    -------------------------------- STAGE OPTIONS
    --------------------------------
    OPTION ===>

    PACKAGE ID ===> SRK1002833

    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.

    Type 1 at OPTION prompt, you will prompted with the following screen

    . . . . . . . . . . . . . . . . . . . . . . . .
    . . .
    --------------------------- STAGE: FROM DEVELOPMENT
    ---------------------------
    COMMAND ===>

    PACKAGE ID: FCM1002833 STATUS: DEV INSTALL DATE:


    20030415

    ISPF LIBRARY:
    PROJECT ===>
    GROUP ===>
    TYPE ===>
    MEMBER ===> (Blank or pattern for list; * for all
    members)
    WARNING * will stage all members in
    dataset
    OTHER PARTITIONED OR SEQUENTIAL DATASET:
    DATASET NAME ===> <---------- provide your local pds
    with member name
    ORGANIZATION ===> (PDS, SEQ)

    LIBRARY TYPE ===> <------ HB3 (for bach programs)


    LANGUAGE ===> <------ cobol 370 (for cobol
    program)
    STAGE NAME ===> <------- Member name (program/copy
    book)
    CONFIRM REQUEST ===> YES (Y/N)
    STAGE MODE ===> 1 (1-Foreground, 2-Batch)
    SUPPRESS MESSAGES ===> (Y/N; applies to batch stage)

    Press ENTER to process; Enter END command to exit.

    next JCL WILL COME , NEXT JOB WILL BE SUBMITTED FOR COMPILATION OF
    COMPONENT

    STEP 4 - EDIT COMPONENTS IN CHANGE MAN


    TYPE 'E' TO EDIT , 'B' TO BROWSE the component , infront of the
    components
    after editing , if you press f3 2 times, and press enter it will
    submit the job for compilation

    STEP 5 - PROMOTION

    After compiled the components in the change man , we need to promote


    it to respective region
    Before doing this, you should know the region, in which you want to
    test
    (region number you should know, usaully it is a number between 1 to
    99)

    Type C;3 in ispf menu you will get following screen,

    . . . . . . . . . . . . . . . . . . . . . . . .
    . . .
    ---------------------------- PROMOTE CHANGE PACKAGE
    ---------------------------
    COMMAND ===>

    PACKAGE ID ===> SRK1002833

    Press ENTER to process; Enter END command to exit.

    type SRK1002833 (pakage name) and type enter

    . . . . . . . . . . . . . . . . . . . . . . . .
    . . .
    ---------------------------- PROMOTE CHANGE PACKAGE
    ---------------------------
    COMMAND ===> SCROLL
    ===> PAGE

    PACKAGE ID: SRK1002833 CREATOR: VXDD50 STATUS: DEV INSTALL DATE:


    20030415

    CURRENT PROMOTION LEVEL: STAGING - 0


    MAXIMUM PROMOTION LEVEL: ALLIMS - 98

    ACTION REQUESTED ===> (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


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

    type 'P' at ACTION REQUESTED ===>

    to promote all components in SRK1002833

    You might also like