Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
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:
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 Man’s control file. It is a
VSAM file that holds all significant data about current and previous Change Packages.
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.
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.
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.
· 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 aren’t
there already. The Change Package is now ready for Testing.
· 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 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.
· 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.
OPTION ===>
This panel is displayed when option 1 is selected from the change man primary option menu.
OPTION ===>
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.
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)
Panel 1 of 4.
OPTION ===>
DEPARTMENT ===>
3-Super, 4-Participating)
All the fields are required for the first time you create a Change Package. SO Enter the Relevant
data and press Enter.
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
------------------------- CREATE: PACKAGE DESCRIPTION ------ Row 1 to 12 of 12
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
Implementation Instructions:
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
Panel 3 of 4
---------------------- CREATE: INSTALLATION INSTRUCTIONS --- Row 1 to 12 of 12
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
Create onsite information:
Use this panel to select the install date and time. Ensure that these fields are correct, and modify
them or the contacts fields as necessary.
Panel 4 of 4
COMMAND ===>
INSTALL DATE/TIME
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.
The Checkout Process:
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.
OPTION ===>
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.,
OPTION ===>
LIBRARY DSORG ===> PDS (Personal library: PDS, SEQ, PAN, LIB)
Stage:
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.
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.
The Staging Process:
Stage Options:
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
Panel 1 of 1
OPTION ===>
This panel is used to select the components in your change package that you want to edit,
compile, delete, display history etc. OPTION 2 from previous screen
COMMAND ===>
LANGUAGE: COBOL370
COMPILE PROCEDURE ===> COBOL370 (Blank for list; ? for designated procedure)
COMPILE PARMS OR JOB NAME ===>
(Enter JOB Name for PROCs requiring associated JOB for JCLCHECK)
===> //
MSGCLASS=T,NOTIFY=VEN080___________________________________________
===> //*_____________________________________________________________________
This panel is an optional panel that is customized for each customer site.Enter a ‘Y’ for the
options that you wish to select. Press Enter on the preious menu.
COMMAND ===>
Package List:
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
COMMAND ===>
DEPARTMENT ===>
3-Super, 4-Participating)
This panel displays the Change Packages selected from the previous panel . There are 36
different line commands available for this panel, which can be placed on CMD filed.
PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTION AUD
CREATOR
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.
OPTION ===>
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.
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.
OPTION ===>
R - Relink single load module
blank - Display LCT member selection list for multiple member processing
LCT MEMBER LIST ===> (Y - Yes or N - No; member list will be created with input
library type)
MEMBER NAME ===> (Blank for list; required for options R/D)
===> //
MSGCLASS=T,NOTIFY=VEN080___________________________________________
===> //*_____________________________________________________________________