Changeman User Manual
Changeman User Manual
Changeman User Manual
Change Man is a system that manages and automates the process of migrating software, or applications, from a development environment to a production environment. Change Man can manage the installation of a variety of components, such as: Copy code used to compile the programs Batch programs written in Assembler, COBOL, COBOL II, or PL/I CICS programs written in Assembler, COBOL, COBOL II, or PL/I Programs written in Easytrieve, etc.,
IB
The first step is to Create a Change Package. A Change Package contains all of the elements to be edited and installed into production, and is identified by a unique package ID automatically generated by Change Man. When a Change Package is created, the information that Change Man needs in order to track and control the package is entered. This includes the implementation instructions, whether it is a temporary or permanent change, the installation date and time, etc.
The typical next step is to Checkout components from baseline. With checkout, components from your baseline libraries are copied to either a Change Man staging library or to a personal development library where changes can be made.
Changes may now be Edited in either the Change Man staging or in the development libraries. Once editing is completed, the components are ready to Staged. We use the STAGE function within Change Man to edit a component, compile and link edit a program. Components such as copy members are simply copied into the staging libraries, if they arent there already. The Change Package is now ready for Testing.
An overview of the Change Man life cycle is given below. It is a step-by-step description of the actions necessary to migrate a change from development to production within Change Man.
IN
NOTE: The baseline libraries contain a current production version (baseline 0) and up to 999 (max.) previous versions of the production component (baseline -1, -2, etc.). When a new production component is installed, the baseline libraries are rippled. This means that the new version becomes the current version, what was the current version becomes the 1 version, and so on.
FR
Change Man manages the transition from development to production libraries by using staging libraries, which are specific to each Change Package. Existing production components are copied into the development environment where they can be modified and tested. The Change Man staging libraries can be used for both editing and testing. If private libraries are used during editing, components will be copied into the staging libraries prior to testing.
A Change Man Change Package is the means by which a new application or change to an existing application is described, scheduled, prepared, and implemented into production. It may consist of one or more library components. Each package is identified by a unique Change Package ID consisting of the Application Mnemonic and a sequential number (e.g. HFC002939). All changes are referenced in the Package Master, which is Change Mans control file. It is a VSAM file that holds all significant data about current and previous Change Packages.
ES
.c om
IBMMAINFRAMES.com
The audit process ensures that no unexpected problems will occur. For example, if a component in the production library has been changed since it was checked out, Change Man alerts you to the problem by creating an out-of-sync condition for the package. After successfully passing the audit, the next step is to Freeze the Change Package. This locks the package(prohibiting further changes), and makes the package available for the promotion and approval processes. Promotion allows a Change Package to be moved through various levels of testing (e.g. promote from system testing to acceptance testing).
Once the package has been installed, Change Man will perform the Baseline Ripple. Baseline Ripple is the process that Change Man executes to version all package components, i.e.: 0 becomes 1, -1 becomes 3, etc. and the new baseline 0 version is installed.
IB
IN
FR
Create, update and review package data Freeze or unfreeze a package Promote or demote a package Approve or reject a package Display (to process) package list Concurrent Development Facility Delete or undelete a package Browse the activity log Browse the Global Notification File Online Forms package list Query packages, components and relationships Revert a package to DEV status Display information about Change Man Exit Change Man
ES
.c om
NOTIFICATION UPDATED
Once all of the necessary Approvals have been done, the package is ready to be installed. The installation process depends upon the option used for installation, while creating package.
IBMMAINFRAMES.com
-------------------------------- BUILD OPTIONS -------------------------------OPTION ===> 0 1 2 3 4 5 6 7 8 9 B C L S Z Dates Create Update Custom Utility Checkout Stage Audit Recompile Relink Browse Compare Listing Scan Compress Display the installation calendar Create a new package Update package information Create, update, approve or review custom forms Rename and Scratch information Check out components from baseline or promotion Stage, edit, browse and delete components Audit a package Recompile source code from baseline or promotion Relink or delete load modules Browse\print\copy baseline or promotion Compare staging to baseline or promotion Browse compressed listings Scan baseline for character strings Compress change package Staging Libraries
When you create the Change Package, you are defining the outer structure of the change Package. You specify the date and time for installations, whether the package is temporary or permanent, the installation site, and implementation instructions, etc. Once you have completed the following four panels, the package is automatically assigned a unique Change Package ID.
Panel 1 of 4.
------------------------- CREATE: CREATE A NEW PACKAGE -----------------------OPTION ===> L Long method - Prompt for package description and special instructions
PACKAGE TITLE ===> APPLICATION REQUESTER'S NAME REQUESTER'S PHONE WORK REQUEST ID DEPARTMENT PACKAGE LEVEL
IN
FR
===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===>
IB
PACKAGE TYPE
PACKAGE TIME SPAN PACKAGE TO COPY FORWARD UNPLANNED REASON CODE TEMPORARY CHANGE DURATION
All the fields are required for the first time you create a Change Package. SO Enter the Relevant data and press Enter.
This panel is to allow you to define package control information. This panel is displayed when option 1 is selected form the previous menu (Build Change Package)
(1-Simple, 2-Complex, 3-Super, 4-Participating) (Planned or Unplanned, Unplanned is for Emergency Loads ) (Permanent) (Optional package name) (* for list) (In days)
ES
.c om
IBMMAINFRAMES.com
General Information:
This panel allows you to enter a description of the Change Package. It should be as complete and descriptive as possible. Panel 2 of 4
Implementation Instructions:
Panel 3 of 4
---------------------- CREATE: INSTALLATION INSTRUCTIONS --- Row 1 to 12 of 12 COMMAND ===> SCROLL ===> CSR Press ENTER or END to continue or type CANCEL to exit. CONTINGENCY ===> 1 1-Hold production and contact analyst
SCHEDULER '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' '''' ''''
IB
(minimum one line, maximum 46 lines) ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________ ________________________________________________________________________
IN
===> CMN
FR
(CMN)
Use this panel to specify how the package is to be installed. This include the installation method,and specific implementation instructions to be used by in the individual overseeing the installation
(minimum one line, maximum 46 lines) '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ '''' ________________________________________________________________________ ******************************* Bottom of data ********************************
ES
.c om
IBMMAINFRAMES.com
------------------------- CREATE: PACKAGE DESCRIPTION ------ Row 1 to 12 of 12 COMMAND ===> SCROLL ===> CSR
IB
Checkout:
Use this panel to enter the checkout information, such as the package to which the component is to be checked out, the type of component, how the component is to be checked out(foreground of batch), and the name of the component that is to be checked out, etc.,
----------------------------------- CHECKOUT ---------------------------------OPTION ===> L - List libraries where component is located ===> HFCG003413 (Package or Application name) ===> (Name or Pattern for list; "ABCDEF" OR Pattern of only "*" Checks Out all
IN
Base/Prom - Checkout from baseline or promotion libraries Package - Checkout package components
FR
Once the package is created next process Is checkout. select option 1.5 from primary option menu. Use this panel to select the list of components to be viewed. Select from components in the baseline libraries, or components already defined to the Change Package from a previously coped package.
After the information in the above panel is filled, press ENTER Change man will then automatically create your change package, return you to the first CREATE panel, and display the change package number in the upper right hand corner of the panel.
ES
WARNING: "From Install" time of 0200 will automatically set the "To Install" time to 0230 . This is to enforce the 0200 load time for online modules.
.c om
IBMMAINFRAMES.com
Components LIBRARY TYPE LANGUAGE SOURCE LIBRARY ===> CP1 ===> ===> 0 related to Library Type. (Blank for list) (Applies to source code; * for list) (Baseline 0 to -n; Promotion +1 to +n) (S-Staging library, P-Personal library) (Personal library: PDS, SEQ, PAN, LIB) (Y/N) (1-Online, 2-Batch)
CHECK OUT TO ===> S PERSONAL LIBRARY ===> LIBRARY DSORG ===> PDS CONFIRM REQUEST CHECKOUT MODE ===> YES ===> 1
Stage:
Panel 1 of 1
IB
1 2 3
IN
- Stage components from development libraries - Process package components - Specify component list selection criteria
FR
Use this panel to tell Change Man where to get the components that are to be staged. Choose from a personal library or from existing components within the Change Package option is 1.6
Use the panels on the following page to complete the staging process for your Change Package components. Once these panels are completed, the component list will be displayed. From it you may browse ,edit,delete,recompile,display the source/load relationship, or stage a component for a list of valid selection codes.
ES
Once the components have been check out, they must be STAGED. you will use the STAGE function within Change Man to edit a component, compile and link edit a program, or to submit another transformation type of process like a JCL scan etc.
.c om
IBMMAINFRAMES.com
This panel is used to compile and optionally link a source component. Panel 2 of 3.option is S on the previous menu CMD option.
PACKAGE ID: HFCG003411 STAGED NAME: LIBRARY TYPE: LANGUAGE: DATASET NAME:
STATUS: DEV
IB
JOB STATEMENT INFORMATION: ===> //VEN080U JOB (050D,WD1A),'CHNGMAN COMPARE',CLASS=W,____________________ ===> // MSGCLASS=T,NOTIFY=VEN080___________________________________________ ===> //*_____________________________________________________________________ ===> /*ROUTE PRINT PUNE______________________________________________________ Press ENTER to process; Enter END command to exit.
IN
COMPILE PROCEDURE ===> COBOL370 (Blank for list; ? for designated procedure) COMPILE PARMS OR JOB NAME ===> (Enter JOB Name for PROCs requiring associated JOB for JCLCHECK) LINK EDIT PARMS ===> DB2 PRE-COMPILE ===> NO (Y/N) OTHER OPTIONS ===> YES (Y to display other options)
FR
LCC261 HI3 - IMS Online COBOL LE/370 load to ILM COBOL370 D131.CP000000.CMN.HFCG.#003411.HI3
------------------- STAGE: COMPILE AND LINK EDIT / JCL CHECK -----------------COMMAND ===> INSTALL DATE: 990420
ES
.c om
IBMMAINFRAMES.com
------------------------- STAGE: HFCG003411 COMPONENTS ----COMMAND ===> NAME TYPE STATUS CHANGED LANGUAGE PROCNAME __ ETRTDATA CP1 ACTIVE 990403 045047 __ LCC261 HI3 INCOMP 990405 062822 COBOL370 COBOL370 __ LSADL05 HI3 ACTIVE 990403 042020 COBOL370 COBOL370 __ LSAETAD HI3 ACTIVE 990403 042045 COBOL370 COBOL370 __ LSAL05P HI3 ACTIVE 990403 045624 COBOL370 COBOL370 __ LSAL05PC CP1 ACTIVE 990403 045220 __ LSAL051 HI3 ACTIVE 990403 042233 COBOL370 COBOL370 __ LSAUL05 HI3 ACTIVE 990403 042342 COBOL370 COBOL370 __ LSEL05M HI3 ACTIVE 990403 042422 COBOL370 COBOL370 __ LSPL05 HI3 ACTIVE 990403 042546 COBOL370 COBOL370 __ LSPL05G CP1 ACTIVE 990403 045057 __ LSRL05M HI3 ACTIVE 990403 042653 COBOL370 COBOL370 ******************************* Bottom ********************************
Row 1 to 12 of 12 SCROLL ===> CSR ID REQUEST VEN214 VEN080 VEN214 VEN214 VEN214 VEN214 VEN214 VEN214 VEN214 VEN214 VEN214 VEN214 of data
----------------------------- STAGE: USER OPTIONS ----------------------------COMMAND ===> NAME: LCC261 TYPE: HI3 LANGUAGE: COBOL370 ??? ENTRY TO DLITCBL DROP INCLUDE STMTS XPEDITER COMPILE INCLUDE MQSERIES USER USER USER USER USER USER OPTION OPTION OPTION OPTION OPTION OPTION 10 12 14 16 18 20 ===> Y ===> ===> ===> ===> ===> ===> ===> ===> ===>
JCK FULL LISTING USER OPTION 11 USER OPTION 13 USER OPTION 15 USER OPTION 17 USER OPTION 19
Use Y or N to select or deselect additional processing options; Press ENTER to continue; Enter END command to exit.
Package List:
--------------------------- PACKAGE LIST PARAMETERS --------------------------COMMAND ===> SPECIFY SELECTION CRITERIA: PACKAGE ID ===> HFCG PACKAGE STATUS ===> CREATOR'S TSO-ID WORK REQUEST ID DEPARTMENT PACKAGE LEVEL ===> ===> ===> ===> ===> ===> ===> ===> ===> ===> ===>
FR
IB
PACKAGE TYPE PACKAGE TIME SPAN FROM INSTALL DATE TO INSTALL DATE FROM CREATION DATE TO CREATION DATE OTHER PARAMETERS
IN
Use the Package List panels as an alternative way to perform a variety of Change Man functions. Use this panel to select the Change Packages to be listed. If the Package Name field is left blank, you can select the application for which you would like to see a package list. Option is 5 from Primary change man screen
(Full name or pattern; blank for list) (DEV, FRZ, APR, REJ, DIS, INS, BAS, BAK, OPN, CLO, TCC or DEL)
(1-Simple, 2-Complex, 3-Super, 4-Participating) (Planned or Unplanned) (Permanent or Temporary) (YYMMDD) (YYMMDD) (YYMMDD) (YYMMDD) (Y/N)
ES
.c om
IBMMAINFRAMES.com
COMPILE ONLY ===> CICS PRE-COMPILE ===> EASYTRIEVE NO NAME ===> FORMAT TO IMSTEST ===> (TEST MFS IS DEFAULT)
Utilities:
Recompile:
The Recompile function can be used to resolve some of the out-of-sync conditions that can occur from the Audit process. The recompile is done from baseline or promotion, directly into staging libraries.
R - Recompile one component L - List libraries where component is found blank - Display member selection list PACKAGE ID COMPONENT NAME SOURCE LIBRARY TYPE LANGUAGE LIBRARY LEVEL
After Entering the required data press Enter. You would get the Recompile job information screen where the data has to be entered and press ENTER. Your job is submitted.
IB
IN
FR
===> HFCG003411 ===> (Blank or pattern for list) ===> (Blank for list) ===> (Blank for list) ===> (Baseline 0, Promotion 1 to n)
ES
.c om
IBMMAINFRAMES.com
Relink: Any time a statically linked subroutine has been modified, relinking is required. Use think function to delete a relinked or recompiled load module from your Change Package.
-------------------------- RELINK/DELETE LOAD MODULES ------------------------OPTION ===> R - Relink single load module D - Delete relinked/recompiled module blank - Display LCT member selection list for multiple member processing PACKAGE ID RELINK FROM LCT MEMBER LIST
IB
IN
FR
IBMMAINFRAMES.com
INPUT LIBRARY TYPE TARGET LIBRARY TYPE MEMBER NAME R/D) COMPILE PROCEDURE ===> (Blank for list) LINK EDIT PARMS ===> DB2 PRE-COMPILE ===> (Y/N) OTHER OPTIONS ===> YES (Y/N for additional user options) JOB STATEMENT INFORMATION: ===> //VEN080V JOB (050D,WD1A),'CHNGMAN COMPARE',CLASS=W,____________________ ===> // MSGCLASS=T,NOTIFY=VEN080___________________________________________ ===> //*_____________________________________________________________________ ===> /*ROUTE PRINT PUNE______________________________________________________
===> HFCG003411 ===> S (S-Staging or B-Baseline) ===> (Y - Yes or N - No; member list will be created with input library type) ===> BLM (Blank for list) ===> BLM (Blank for list) ===> (Blank for list; required for options
ES
.c om