ChangeMan Basic Training

ChangeMan ZMF Basic Training Guide 1
ChangeMan ZMF Basic Training
Throughout these materials, persons who are involved in training may be referred to as
developers or administrators. Nothing in this material should be construed to indicate
any discrimination based on race, color, religion, sex, age, national origin, disability,
marital status, disabled or Vietnam Era Veteran status, or sexual orientation.
Notice: This document is an unpublished work protected by the United States

copyright laws and is proprietary to AT&T Intellectual Property. Disclosure, copying,
reproduction, merger, translation, modification, enhancement, or use by anyone other
than authorized employees or licensees of AT&T companies without the prior written
consent of AT&T Intellectual Property. is prohibited.
This document has been prepared and distributed pursuant to a strict review process.
Under no circumstances should changes be made to this document without first
submitting the changes for review to the author.
Proprietary Information: Not for use or disclosure outside the AT&T family of
companies, except under written agreement.
2005-2012 AT&T Intellectual Property. All rights reserved.
All company, product, and service names may be trademarks or registered trademarks of their respective
owners.
All company, product, and service names may be trademarks or registered trademarks of their respective
owners.
Revised: December 13, 2012
Proprietary Information: Not for use/disclosure

outside of AT&T Communications Inc. and its affiliated companies.
Table of Contents
TABLE OF CONTENTS..............................................................................................................................................2
CHAPTER 1- INTRODUCTION................................................................................................................................5
ABOUT THIS GUIDE.....................................................................................................................................................5
CAN USERS PLAY AROUND IN CHANGEMAN?............................................................................................................6
WHERE DO DEVELOPS DO THEIR WORK WHEN THEY HAVE A REAL APPLICATION?...............................................6
CHAPTER 2 GETTING STARTED........................................................................................................................9
GETTING HELP............................................................................................................................................................9
APPLICATIONS..............................................................................................................................................................9
UNDERSTANDING LIBRARY STRUCTURE.....................................................................................................................9
BASELINE LIBRARIES.................................................................................................................................................10
PACKAGE STAGING LIBRARIES..................................................................................................................................12
ALL CMN HLQ LIBRARIES......................................................................................................................................12
APPLICATION CONFIGURATION..................................................................................................................................12
DEVELOPMENT STEPS SUMMARY..............................................................................................................................12
CHAPTER 3 CREATING A PACKAGE...............................................................................................................15
SETTING THE PACKAGE OPTIONS..............................................................................................................................16
PACKAGE DESCRIPTION.............................................................................................................................................17
INSTALLATION INSTRUCTIONS...................................................................................................................................18
COMPLEX AND PARTICIPATING PACKAGES................................................................................................................19
SITE INFORMATION....................................................................................................................................................20
CHAPTER 4 CHECKOUT AND STAGE.............................................................................................................23
CHECKOUT WARNING...............................................................................................................................................25
ADDING MORE COMPONENTS...................................................................................................................................27
CHAPTER 5 ADDING NEW COMPONENTS....................................................................................................29
STAGE FROM DEVELOPMENT.....................................................................................................................................29
CREATE NEW IN CHANGEMAN..................................................................................................................................30
CHAPTER 6 EDITING AND COMPILING........................................................................................................33
PROCESSING PACKAGE COMPONENTS.......................................................................................................................33
COMPARISON REPORT................................................................................................................................................35
COMPILING................................................................................................................................................................36
BROWSING COMPILE OUTPUT LISTINGS (LST).........................................................................................................37
DATASETS TO USE FOR EXTERNAL TESTING.............................................................................................................39
CHAPTER 7 PROMOTION..................................................................................................................................40
PROMOTING IN CHANGEMAN....................................................................................................................................40
PROMOTION LEVELS..................................................................................................................................................40
PROMOTING PACKAGE CONTENTS............................................................................................................................41
FINDING THE PROMOTION LIBRARY DATASETS.........................................................................................................43
MULTIPLE PROMOTIONS AND CLEAN-UP..................................................................................................................44
OTHER BENEFITS OF PROMOTION.............................................................................................................................44
CHAPTER 8 AUDIT...............................................................................................................................................45
AUDIT EXPLAINED.....................................................................................................................................................45

AUDITS WHEN TO RUN..........................................................................................................................................45

AUDITS HOW ARE THEY CONTROLLED?................................................................................................................45
AUDIT EXTENDING ITS REACH...............................................................................................................................46
RUNNING THE AUDIT.................................................................................................................................................46
INTERPRETING THE AUDIT OUTPUT...........................................................................................................................47
AUTO-RESOLVE OUT-OF-SYNCHS.............................................................................................................................49
CHAPTER 9 FREEZE AND APPROVE..............................................................................................................50
THE FREEZE REQUIREMENT......................................................................................................................................50
FREEZING A PACKAGE...............................................................................................................................................50
UNFREEZING..............................................................................................................................................................51
PACKAGE APPROVAL AND AOTS TICKET REQUIREMENTS.......................................................................................51
APPROVAL NOTIFICATIONS........................................................................................................................................52
APPROVALS AND SOFTWARE DISTRIBUTION AND BASELINING.................................................................................52
HOW TO APPROVE.....................................................................................................................................................53
BASELINE RIPPLE......................................................................................................................................................54
CHAPTER 10 QUERY............................................................................................................................................55
WHAT IS QUERY?......................................................................................................................................................55
PACKAGE QUERY.......................................................................................................................................................55
COMPONENT QUERY..................................................................................................................................................57
IMPACT ANALYSIS......................................................................................................................................................58
CHAPTER 11 UPDATING A PACKAGE.............................................................................................................61
Chapter 12 Deleting or Renaming a Baseline Component........................................................................................62

Chapter 1- Introduction
About This Guide
ChangeMan ZMF is a software product developed by Serena. Its goal is to help implement software
component changes while minimizing errors and mistakes which often occur during the software
development life cycle.
ChangeMan functionality is invoked via a series of panels and menus, all of which are rather intuitive to
use. The concepts behind the use of ChangeMan are relatively simple, but they may be different than
techniques or tools currently being used.
Each application group using ChangeMan ZMF can customize it, for the most part, to meet their own local
working practices within the SDLC. That is to say, no two applications have to use ChangeMan in exactly
the same way, although most follow a template developed to fit into AT&Ts software development
processes. Some unique configurations may be needed because some applications may have more
testing requirements than others, or different compile procedures are needed to support the use of
different software products (i.e.,, IMS, CICS), etc. This training guide is intended to help developers
understand the basic options available within the ChangeMan tool. This guide does not provide training
on how a particular application handles a particular function, but is strictly general in scope.
This guide will walk through the typical SDLC template developed for ChangeMan and it will point out
places where some applications may differ from the norm. This guide and the ChangeMan ZMF tool are
for developers who create or change software components for Z/OS (MVS) applications. ChangeMan
ZMF is not designed to function with mainframe VM or mid-range (UNIX, SOLARIS, etc.) operating
systems.
The reader should be aware that each application will have one or more Local Administrators assigned
from within their team to establish the SDLC support processes within the ChangeMan ZMF tool during
the applications configuration and to provide Level 1 support for developers who are learning how to use
ChangeMan or who encounter problems while using it.
Also please be aware that there are numerous shortcuts within ChangeMan that eliminate the need to
navigate through all the panel menus shown in this training guide, but until the products functionality and
embedded quality steps are fully understood, it is easier to follow the flow through the panel menus as
defined herein.
Finally, please note that not every tool used in each region (cS / cT / cB) is mentioned in this document.
An assumption is made that when a tool is mentioned in this document, the user knows what the
equivalent tool is that is used and how to use it. For example, this document contains references to SSO
which is a sysout viewing tool. If SSO is not installed on a system, the user should know the equivalent
tool, such as JesMaster or SAR. References to SDSF may also have an equivalent tool of JesMaster or
SDLC.
Full documentation on ChangeMan can be found on the ChangeMan website at:

http://mvsha00.sbc.com/appl/prodsupt/products/chgman/ChangeMan.html
ChangeMan manuals, AT&T-specific Frequently Asked Questions (FAQ) and more can be found in this
site. Users are encouraged to visit this site, sign up for the ChangeMan Users Email Listserv, that allows
them to receive emails about product changes or recently discovered problems encountered during use.

Any user who encounters a problem with the ChangeMan product should first report the problem to their
ChangeMan Local Administrator, who should attempt to resolve the problem. If a solution is not apparent,
the Local Administrator should then send an email to changemn@att.com, requesting assistance from the
ChangeMan Technical Support Team. For emergencies, visit the ChangeMan website above and click on
Contact Us.
Can Users Play Around in ChangeMan?
Yes!
Throughout this guide, there are screen shots of the ChangeMan panels. These screen shots were taken
from a testing application known as CLAS.
In cS, new users can use the CLAS application in CHGMAN on SLT1 to play and try out the ChangeMan
functions documented in this guide.
In cT, new users can use the TRNG application in CHGMAN on ALT3 to play and try out the ChangeMan
functions documented in this guide.
If a user desires to do this, they must have their SA use ATTsa to request access to one of these
ChangeMan applications.
For CLAS in cS, the SA must request access to the following on SLT1:
General Resources: CLAS, CLASPRM1, CLASPRM2 CLASPRM3, CLASAPR1, CLASAPR2, CLASAPR3
Resource Class: $CHGMAN
Access Needed: UPDATE
Dataset: CMN.CLAS.TEST
Access Needed: READ (only read is allowed)
For TRNG in cT, the SA must request access to the following on ALT3:
General Resources: TRNG, TRNGPRM1, TRNGPRM2 TRNGPRM3, TRNGAPR1, TRNGAPR2, TRNGAPR3
Resource Class: $CHGMAN
Access Needed: UPDATE
Dataset: CMN.TRNG.TEST
Access Needed: READ (only read is allowed)
Once access is granted, the user will be able to type CHGMAN on the TSO panel and play around in
one of these applications, per the instructions found in this guide.
Where Do Develops Do Their Work When They Have a Real Application?
All development work for classic S applications is done on one of four development instances of
ChangeMan as shown below. When an application is set up in ChangeMan, they will be told what site
they will do their development on, based on where their test system resides.
SLT1 - AA00 SF01 - AAT3 SLT2 - CQ90 SL04 - BSYS

(Site O) (Site E) (Site I) (Site R)
Started Task=CMNDAAO Started Task=CMNDT3G Started Task=CMNDCQI Started Task=CMNDBSR

All development work for classic T applications is done on the ChangeMan instance shown below. In cT,
there is only one location where development work is done.
ALT3 - AH00
(Site P)
Started Task=CMNDT3P
At this time, the Classic B region is not licensed for ChangeMan ZMF use. See the Global SCM Teams
website for more general SCM information and specific information about other SCM tools used in these
regions:
Global SCM

Chapter 2 Getting Started

Type CHGMAN on the ISPF command line to invoke the Started Task, ChangeMan ZMF, and the
following panel will appear:
AA00 ---- SERENA ChangeMan 5.5.3 Primary Option Menu INIT Complete
OPTION ===>
1 Build - Create, update and review package data

2 Freeze - Freeze or unfreeze a package
3 Promote - Promote or Demote a package
4 Approve - Approve or reject a package
5 List - Display (to process) package list
6 Reports - Generate ChangeMan batch reports
7 Release - Extended Release Management
A Admin - Perform administrative functions
C M+R - Merge+Reconcile (formerly CDF)
D Delete - Delete or undelete a package
L Log - Browse the activity log
M Monitor - Monitor internal scheduler or packages in limbo
O OFMlist - Online Forms package list
Q Query - Query packages, components and relationships
R Revert - Revert a package to DEV status
T Tutorial - Display information about SERENA ChangeMan
X Exit - Exit SERENA ChangeMan
Press ENTER to process; enter END command to exit.
This is the Primary Option Menu in ChangeMan. All development work done from within the ChangeMan
environment starts with this panel.
Note: Some menu selections shown above are only available to ChangeMan ZMF Local Administrators
and will not be visible to developers.
Getting Help
On any ChangeMan panel, context-sensitive help is available by hitting PF1. In addition, if any warning or
error message appears in the upper-right corner of the screen, a longer, more meaningful, description of
the error is available by hitting PF1. When reporting a problem to a Local Administrator or to the
CHANGEMAN MVS mailbox, always press PF1 to view the long error message and then copy and paste
the entire screen shot and the long message into the email.
Applications
Applications are defined within ChangeMan to meet the specific needs of the business. Ideally, each
application will be identified in MOTS and the name assigned in ChangeMan will closely mimic the MOTS
abbreviation, although that is not always possible because the ChangeMan application name is limited to
4 alphanumeric characters. Some application families are actually defined in ChangeMan as several
applications; others are combined.
Understanding Library Structure

.
A host of libraries can be used with ChangeMan to meet the specific needs of an
application through various stages of testing (promotion) but two sets of libraries are
always present for each application as development tasks are performed within the
Tool:

o Baseline Libraries library naming convention format follows:

CMN.appl.BAS@.typ where CMN is a constant standing for ChangeMan, appl is the 4-
character application name, BAS is a constant standing for baseline, @ is the ChangeMan
Development Site ID, and typ is the 3-character component library type (i.e.,
CMN.CLAS.BASO.JCL).
o Package Staging Libraries library naming convention format follows:
CMN.appl.STG@.#nnnnnn.typ where CMN is a constant standing for ChangeMan, appl is

the 4-character application name, STG is a constant standing for Staging, @ is the
ChangeMan development Site ID, # is a constant standing for the word number, nnnnnn is
the 6 digit sequence number ChangeMan assigns to an applications package, and typ is the
3-character component library type (i.e., CMN.CLAS.STGO.#000001.JCL).
The contents of all libraries owned by ChangeMan can be viewed outside of the Tool by using ISPF 3.4.
Baseline Libraries
All of an applications software components (source code, load modules, control cards, PROCS, JCL,
etc.) will be kept in the ChangeMan baseline at the applications development site (AA00 on SLT1, BSYS
on SL04, etc.). These should be the same, with the possible exception of component transformation
items, as the "live" components that are running in production sites; however, some applications may also
maintain some unique components used for testing or test data generation in the baseline, as well.
Component changes should start with a copy of the baseline version of a component or, possibly, an
enhanced version of a baseline component that is already being updated within ChangeMan for another
project or release (when concurrent development is in progress).
Some of the CLAS applications baseline library set on SLT1 in ISPF 3.4 is shown below:
Menu Options View Utilities Compilers Help
DSLIST - Data Sets Matching CMN.CLAS.BAS*.* Row 1 of 40

Command ===> Scroll ===> CSR
Command - Enter "/" to select action Message Volume

-------------------------------------------------------------------------------
CMN.CLAS.BASO.CPY PAP044
CMN.CLAS.BASO.CPY.DELTA MIGRAT2
CMN.CLAS.BASO.CTC PAP102
CMN.CLAS.BASO.CTC.DELTA MIGRAT2
CMN.CLAS.BASO.DBB PAH027
CMN.CLAS.BASO.DBB.DELTA MIGRAT2
CMN.CLAS.BASO.DBR PAP086
CMN.CLAS.BASO.DBR.MINUS1 MIGRAT2
CMN.CLAS.BASO.JCL PAH027
CMN.CLAS.BASO.JCL.DELTA MIGRAT2
CMN.CLAS.BASO.JC1 PAP072
CMN.CLAS.BASO.JC1.DELTA MIGRAT2
CMN.CLAS.BASO.LCT PAP069
CMN.CLAS.BASO.LCT.DELTA MIGRAT2
CMN.CLAS.BASO.LOD PAP083
The library list shows a different PDS for each component type associated with the application. All
component types within ChangeMan are restricted to a 3 alphanumeric name identifier that makes up the
last node in the library name. For example, COBOL copybooks are CPY , load modules use LOD (or
other load types like LD1, LDS, etc.), and JCL for JCL components. The "DELTA" and "MINUS-" named

library datasets shown are used by ChangeMan to backup previous versions of the baseline.
Components in all baseline libraries can only be updated by checking them out into a ChangeMan
package.
Use the browse command to view the components list directly from this panel.
DSLIST - Data Sets Matching CMN.CLAS.BAS*.* Row 1 of 40


-------------------------------------------------------------------------------
CMN.CLAS.BASO.CPY PAP044
CMN.CLAS.BASO.CPY.DELTA MIGRAT2
CMN.CLAS.BASO.CTC PAP102
CMN.CLAS.BASO.CTC.DELTA MIGRAT2
CMN.CLAS.BASO.DBB PAH027
CMN.CLAS.BASO.DBB.DELTA MIGRAT2
CMN.CLAS.BASO.DBR PAP086
B CMN.CLAS.BASO.JCL PAH027
CMN.CLAS.BASO.JCL.DELTA MIGRAT2
CMN.CLAS.BASO.JC1 PAP072
CMN.CLAS.BASO.JC1.DELTA MIGRAT2
Individual components can then be browsed except for those in the *.DELTA libraries, which are encoded
and only represent the actual parts of the component that were changed in a previous version of the
baseline (whereby they get their name of DELTA).
Menu Functions Confirm Utilities Help
BROWSE CMN.CLAS.BASO.JCL Row 00001 of 00005

Name Prompt Size Created Changed ID
_________ IEBCOPY1 14 1989/10/20 2002/05/15 10:01:00 MB8147
_________ IEBCOPY2 14 2000/09/30 2000/09/30 19:37:53 MF7484
____B____ IEBCOPY3 14 2000/09/30 2000/09/30 19:38:13 MF7484
_________ IEBCOPY4 14 2000/09/30 2000/09/30 19:38:27 MF7484
_________ IEBCOPY5 14 2000/09/30 2000/09/30 19:38:45 MF7484
**End**
Menu Utilities Compilers Help
BROWSE CMN.CLAS.BASO.JCL(IEBCOPY3) - 01.00 Line 00000000 Col 001 080

********************************* Top of Data **********************************
//USERID8M JOB (22G0,9520,01,2,,,1),'TEST JCL',CLASS=A, 00010000
// REGION=2000K,NOTIFY=&SYSUID,MSGCLASS=E 00020000
//S1 EXEC PGM=IEBCOPY,REGION=2000K 00030000
//**************************************************************** 00040000
//***** THIS IS TEST JCL FOR THE CHANGE MAN NEW USERS CLASS 00050000
//**************************************************************** 00060000
//SYSPRINT DD SYSOUT=* 00070000
//SYSOUT DD SYSOUT=* 00080000
//SYSUT1 DD DSN=AB1234.CLAS.JCL.TEST,DISP=SHR 00090000
//SYSUT2 DD DSN=AB1234.CLAS.JCL.TEST.NEW,DISP=(,CATLG,CATLG), 00100000
// SPACE=(CYL,(5,5,20)),UNIT=SYSDA 00110000
//SYSIN DD * 00120000
COPY OUTDD=SYSUT2,INDD=SYSUT1 00130000
/* 00140000
******************************** Bottom of Data ********************************

Package Staging Libraries

A package is simply a series of partitioned data sets (PDSs) controlled by ChangeMan through the
Package Master (a VSAM dataset). The Package Master contains the metadata describing the package
and dictating how it will be managed within the Tool. The PDSs that make up the package can be
browsed by using ISPF 3.4, but they may not be updated outside of the ChangeMan tool.
The panel below shows a sample of the type of libraries that could be associated with a package.
ChangeMan supports over 300 component types which includes some that are actually managed as a
PDS but deployed as sequential (flat) files in test and production.
DSLIST - Data Sets Matching CMN.CLAS.STG*.#002724.* Row 1 of 7


-------------------------------------------------------------------------------
CMN.CLAS.STGO.#002724.CPY PAP012
CMN.CLAS.STGO.#002724.CTC PAP012
CMN.CLAS.STGO.#002724.JCL PAP012
CMN.CLAS.STGO.#002724.PRC PAP012
CMN.CLAS.STGO.#002724.LDN PAP082
CMN.CLAS.STGO.#002724.LOD PAH040
CMN.CLAS.STGO.#002724.LST PAP063
CMN.CLAS.STGO.#002724.OBJ PAP063
CMN.CLAS.STGO.#002724.SRC PAP099
CMN.CLAS.STGO.#002724.SEQ PAP104
These libraries can be concatenated within testing environments to perform low-level tests (i.e., Unit Test)
and they can be promoted to other ChangeMan controlled libraries that can be used for higher levels of
testing (i.e., chain, system, etc.). Chapter 7 will cover the ChangeMan Promotion process in detail.
All CMN HLQ Libraries

Components in any CMN HLQ library cannot be edited and saved outside of ChangeMan because the
ChangeMan tool owns the CMN HLQ and only READ access is granted to application team members
and other interested parties (STDs, PMs, etc).
Application Configuration
The Global SCM team will configure an application in ChangeMan and work with the applications local
administrator and the CHANGEMAN TECHNICAL SUPPORT team to initially load an applications
software baseline. The Global SCM team will also conduct local administrator training and assist
developers, if needed, when they initially attempt to use ChangeMan.
Development Steps Summary

Once an application has established a software baseline within ChangeMan, components can be
changed for new projects, releases, or production fixes. Chapter 3 below describes, in detail, the start of

the development process within ChangeMan, but the following is a summary of the basic steps that must
be performed in order to implement a change using the Tool:
Create a new package

Put copies of component into the package by
o Checking them out of the baseline (mandatory for known components)
o Staging them from Development Library (i.e., an ATTUID library new components only)
Stage/Edit components within the package (mandatory)
o Compile if necessary (source components only)
Test components from the package staging libraries (optional).
Promote package components to appropriate testing level libraries (chain, system, etc. - optional
quality step)
o Demote and make testing fixes, if necessary
Audit the package (mandatory quality step)
o To resolve any existing out of synch conditions
Freeze the Package (mandatory quality step for components ready for production deployment)
Approve the Package (mandatory quality step before production deployment)
Installation begins after the final approval (applies only when ChangeMan is being used for
software distribution)
o Distribution occurs immediately after final approval. This is when the ChangeMan staging
libraries are transmitted to the install location(s) in preparation for production deployment.
o Production installation (occurs based on the install date/time of the package and
associated deployment instructions provided by application in the AOTS Change
Record).
Baseline the package
o Components are copied from the package into the applications baseline libraries
Follow this link for a graphical overview of the steps in the ChangeMan ZMF development cycle:
CMN Roadmap.doc
Each of these steps will be discussed in the following chapters in detail. ChangeMan Out of the Box
development options are intuitive and fairly easy to use; however, each application may see a need to
implement customizations that will more easily allow its developers to more closely follow their own local
practices within the SDLC. The Applications Local Administrator will determine if customizations are
needed and can implement them with help from the ChangeMan Technical Support Team. Follow this link
to learn more about creating and using (existing) ChangeMan ZMF customizations:
ChangeMan ZMF Customizations

Chapter 3 Creating a Package

Making software changes within ChangeMan requires the creation of a Package. A package can be
opened by any development team member and can also be used by anyone else within the development
team (RACF Group controlled). A package can be associated with a development project or release, or
any part there of. A package is nothing more than a logical collection of physical software components
and associated metadata, contained in staging libraries by type, that can be updated and tested for some
predefined unit of work assigned to the application.
To create a package, option 1 from the Primary Option Menu must be selected:
AA00 ---- SERENA ChangeMan 5.5.3 Primary Option Menu INIT Complete
OPTION ===>
1 Build - Create, update and review package data

2 Freeze - Freeze or unfreeze a package
3 Promote - Promote or Demote a package
4 Approve - Approve or reject a package
5 List - Display (to process) package list
6 Reports - Generate ChangeMan batch reports
7 Release - Extended Release Management
A Admin - Perform administrative functions
C M+R - Merge+Reconcile (formerly CDF)
D Delete - Delete or undelete a package
L Log - Browse the activity log
M Monitor - Monitor internal scheduler or packages in limbo
O OFMlist - Online Forms package list
Q Query - Query packages, components and relationships
R Revert - Revert a package to DEV status
T Tutorial - Display information about SERENA ChangeMan
X Exit - Exit SERENA ChangeMan
Press ENTER to process; enter END command to exit.
The Build menu panel is then displayed. Choose Option 1, Create a New Package:
-------------------------------- BUILD OPTIONS -------------------------------

OPTION ===> 1
0 Dates - Display the installation calendar

1 Create - Create a new package
2 Update - Update package information
3 Custom - Create, update, approve or review custom forms
4 Utility - Rename and Scratch information
5 Checkout - Check out components from baseline or promotion
6 Stage - Stage, edit, browse and delete components
7 Audit - Audit a package
8 Recompile - Recompile source code from baseline or promotion
9 Relink - Relink load modules
B Browse - Browse\print\copy baseline or promotion
C Compare - Compare staging to baseline or promotion
L Listing - Browse compressed listings
S Scan - Scan baseline for character strings
Z Compress - Compress change package Staging Libraries
Press ENTER to process; Enter END command to exit.
The next few panels allow the developer to describe the purpose for creating the package. Some of the
options selected within these panels, along with the information entered, will impact how the package is
managed by ChangeMan during development life cycle, who approves it, and how and when it will be
distributed, installed, and baselined.

Setting the Package Options

The first panel displayed, Create a New Package, is the most important one, as it defines the basic
parameters that will be used by ChangeMan to control the package:
------------------------- CREATE: CREATE A NEW PACKAGE ------------------------

OPTION ===>
PEXIT=PKGC
PACKAGE TITLE
===> Test Application for training
APPLICATION ===> CLAS (Blank or pattern for list)

REQUESTER'S NAME ===> Joe Developer
REQUESTER'S PHONE ===> 555-0000
WORK REQUEST ID ===>
DEPARTMENT ===> JULY (or Scheduled Release)
PACKAGE LEVEL ===> 1 (1-Simple, 2-Complex,
4-Participating)
PACKAGE TYPE ===> PLANNED (Planned or Unplanned)
PACKAGE TIME SPAN ===> PERM (Permanent or Temporary)
PACKAGE TO COPY FORWARD ===> (Optional package name)
UNPLANNED REASON CODE ===> (* for list)
TEMPORARY CHANGE DURATION ===> (In days)
ATTACH PACKAGE TO RELEASE ===> NO (Yes/No)
Following is a description of each field and what values were used. As mentioned before, Individual
application families, who follow local working practices, often create customizations that dictate what is
entered in this panel. The application's Local Administrator (LA) or Quality Control contact should have
documentation to define the correct values that should be entered.
Field Description
Package Title This should be a descriptive summary that briefly identifies the purpose for creating the
package. It can be helpful in locating a specific package through the ChangeMan query
function when the Long description option is used.
Application This is the four character ChangeMan application name within which the package is
being created.
Requester's An informational field identifying the package creator.
Name
Requester's The package creators phone number
Phone
Work Request This field is very application-specific and occasionally is used in a specific way defined
ID to ChangeMan through customizations.
Some applications use it to refine package approval notifications by entering
their Senior Technical Director reference number.
Some applications enter the PMT or AOTS CR Number that justifies the work
being done through the package.
Some applications use it to assign the package to a specific batch processing
cycle (see ChangeMan ZMF Customizations for more information).
Some applications define other uses or do not use it at all.
Department Some applications, that have several releases in development at the same time,
(or Scheduled use this field to identify concatenation sequences that support their concurrent
Release) development process.
Some applications define other uses or do not use it at all.
Package Level Defines the relationship of the package to others in the applications
development process.
Simple packages Used exclusively by most applications and designates that
the package is related to no other packages in existence within the application.

Participating A package related to a complex package for purposes of

component recognition from package to package within ChangeMan for a
particular development process. Although each participating package is
physically separate from all other participating packages, using this package
level allows ChangeMan to see components within them (for the purposes of
concatenating copybooks during compiles) components in any other
participating packages associated with a Complex package.
Complex a logical collection of participating packages.
Package Type Planned indicates to ChangeMan that the package being created is for a
planned project or release.
Unplanned indicates that the package is being created for an unplanned fix
(may be an emergency fix, but not required).
Note: Unplanned packages can be assigned abbreviated approval paths to
expedite the distribution of software components to production environments for
down jobs, etc.
Package Time Always set to PERM AT&T does not allow Temporary packages
Span
Unplanned Unplanned packages require the entry of a reason code. The applications Local
Reason Code Administrator should provide some guidance as to what reason code to use
under what circumstances. Typing an asterisk ( *) in this field and hitting enter
will bring up a list of valid reason codes to choose from.
Temporary not allowed to be used at AT&T. Can only be set to N.
Package
Duration
Attach not allowed to be used at AT&T. Can only be set to N.
Package to
Release
Hit Enter to display the Package Description panel:
Package Description
------------------------- CREATE: PACKAGE DESCRIPTION ------ Row 1 to 12 of 12

COMMAND ===> SCROLL ===> CSR
Press ENTER or END to continue or type CANCEL to exit.
(minimum one line, maximum 46 lines)

'''' PMT # 123456 Adding new user option for small business customers______
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
This panel can be used to fulfill the documentation requirements to meet the applications local SDLC
local practices. Many applications require the entry of a PMT or AOTS Defect number along a meaningful
explanation of the reason for making the change. The entry of at least something is required on the 1 st line
of this panel, even if it is just "n/a".
Hit Enter to display the Installation Instructions panel:

Installation Instructions
---------------------- CREATE: INSTALLATION INSTRUCTIONS --- Row 1 to 12 of 12
Px=MANL
Press ENTER or END to continue or type CANCEL to exit.
CONTINGENCY ===> 3 1-Hold production and contact analyst

2-Backout change, continue production
3-Other ===> n/a
Install Information - used for each site:

YYYYMMDD FROM TO PRIMARY/BACKUP CONTACTS PHONE NUMBERS
20071231 2300 2359 Joe Developer____________ 555-0000______
Jane Team-Lead___________ 555-0001______
SCHEDULER ===> ESP (CMN, Manual, ESP or CTM)
'''' Have a Happy New Year!_____________________________________________

'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
'''' ________________________________________________________________________
Some fields in this panel are not used at AT&T since the data would be redundant to that which must be
provided in the AOTS change records; however, some data must be entered to satisfy ChangeMan:
By default, enter a 3 in the CONTINGENCY field and N/A in the OTHER field.
Enter a start date and time that corresponds to the Local Schedule Start date/time entered (or to be
entered) in the AOTS CR that will be used to document the change for Enterprise Change Management
purposes.
If ChangeMan is being used to automatically distribution and install packages into production
environments this panel is used to identify the default install date and time for each possible
install site established for the application.
o Enter a C in the YYYYMMDD column to populate it with the current date.
If ChangeMan is not yet being used for distribution, the date and time entered controls when the
software is baselined, and the execution of the baseline ripple in ChangeMan.
o The date could equate to either the baseline - no later than date for packages assigned
to the Manual scheduler, or the actual packages install date/time, for packages using
the CMN scheduler.
More information about ChangeMan schedulers will be provided later in this document.
Enter the Primary/Backup Contacts and their phone numbers. Ideally, the Primary Contact in the
ChangeMan package would be the same as the Primary Contact entered into the AOTS CR but there is
no editing to enforce this.
Enter the Scheduler (CMN, MANUAL, ESP or CTM). The scheduler identifies which method is used to
implement the packages components into production. If the application is using ESP or Control-M, the
ESP or CTM values will be pre-populated. If not, CMN or MANUAL will be pre-populated, based on
the applications configuration. The scheduler determines the method used to perform installations. Only
the MANUAL or CMN schedulers are acceptable to use prior to turning on ChangeMans automatic
distribution and installation facilities for an application. Once software distribution is turned on for an
application, the scheduler impacts how and when components are not only baselined but also when they
are installed in production as follows:

MANUAL ChangeMan will immediately deliver and install the components into all install
locations assigned in the package when the package is given final approval. No EPAS/EMAS
intervention.
CMN ChangeMan will deliver components to the assigned install sites as soon as the final
approval is applied. However, the components will not be installed by ChangeMan until the exact
install date/time entered into the package arrives. This is done without EPAS/EMAS intervention.
o This scheduling method is normally only used for installing components into test
environments; however, its use is also permitted for installing certain software tools
supported by the Program Products Support Team (i.e., MVS PKZIP).
ESP (used in the cS region) Upon final approval, ChangeMan will NDM the components into
holding libraries at each install site. At the date/time agreed upon by EPAS/EMAS and the
application, the components will be installed into production through ESP jobs/events that were
generated by ChangeMan on each install site. This is the required method when EPAS/EMAS is
responsible for an applications production deployment in the cS region.
Note: Once the ESP scheduler is turned on for an application, MANUAL or CMN can no longer
be used.
CTM (used in the cT region) Upon final approval, ChangeMan will NDM the components into
holding libraries at each install site. At the date/time agreed upon by EPAS/EMAS and the
application, the components will be installed into production through Control-M jobs that were
generated by ChangeMan on each install site. This is the required method when EPAS/EMAS is
responsible for an applications production deployment in the cT region.
Note: Once the Control-M scheduler is turned on for an application, MANUAL or CMN can no
longer be used.
Finally, enter some info in the notes lines at the bottom of the panel. Internal team working practices may
determine if specific info needs to be entered here but ChangeMan dictates that something must be
entered, even if it is N/A. Hit enter or PF3 key to exit this panel and continue.
Complex and Participating Packages

If the package was defined as a Participating package, another panel, Affected Applications, will be
displayed to give the developer the option of "connecting" the package to a complex package:
------------------------ CREATE: AFFECTED APPLICATIONS ----- Row 1 to 12 of 12

Press ENTER to continue or type CANCEL to exit.
COMPLEX/SUPER PACKAGE ID ===> __________
APPL
'''' ____
'''' ____
'''' ____
'''' ____
'''' ____
'''' ____
'''' ____
'''' ____
'''' ____
'''' ____
'''' ____
'''' ____
Enter the complex package number in the field provided. Also, if applicable, enter the ChangeMan
application name(s) affected by the participating package(s). If the package was Complex, the
following panel will be displayed into which the participating packages assigned to it can be entered.

---------------------- CREATE: COMPLEX/SUPER INFORMATION --- Row 1 to 12 of 12

PACKAGE ID: CLAS002724 STATUS: OPN
Press ENTER to continue or type CANCEL to exit.
PACKAGE ID
'''' CLAS002723
'''' __________
'''' __________
Enter the number(s) of the participating package(s) and hit Enter.

Note: From a software distribution perspective participating packages are treated just like any simple
packages and, as such, each must be final approved before it can be released into the distribution
process. Complex packages are not approved or used in any way by the software distribution process.
Site Information
The final panel in the package creation process shows the install date/time and developer contacts in
relation to all of the default install sites assigned to the application. ChangeMan always assumes that a
package will be installed in all install sites defined for the application at the date and time assigned when
the Installation Instructions panel was filled in.
Notes:
Install sites are defined in the ChangeMan Administration panel, A.8, when the application is initially
configured by Global SCM.
The Install Date/Time field should always reflect a future date/time; otherwise, an error will be
displayed when an attempt is made to freeze or approve the package.
--------------------------- CREATE: SITE INFORMATION --------- Row 1 to 1 of 1

Press ENTER or END to create the package or type CANCEL to exit.
Enter * in line command field for site selection list. PEXIT=PKGI
INSTALL DATE/TIME
SITE YYYYMMDD FROM TO
PRIMARY/BACKUP CONTACTS PHONE NUMBERS
'''' SLTESTP_ 20061231 2300 2359 Joe Developer____________ 314-555-0001_
Jane Team-Lead___________ 314-555-0002_
'''' SDL2B___ 20061231 2300 2359 Joe Developer____________ 314-555-0001_
Jane Team-Lead___________ 314-555-0002_
'''' STLOUISC 20061231 2300 2359 Joe Developer____________ 314-555-0001_
Jane Team-Lead___________ 314-555-0002_
******************************* Bottom of data ********************************
Some applications may only have one production install site, other may have many, but all applications
will always show at least one development install site (i.e., SLTESTP, ATT3TEST, etc.), no matter which
ChangeMan scheduler is used (CMN, MANUAL, ESP or CTM). Production sites will not be shown on the
panel, however, until software distribution is turned on for the application.
The install date and/or time shown for each site can be changed by keying over the fields on this
panel.
If the user desires to use todays date as the install date, then a C can be entered in the
YYYYMMDD column to change it to the current date.
Any install site may be deleted by entering a D at the beginning of the line, where applicable.
Also, an option in the ChangeMan panel exists that allows a developer to change the install dates for a
package after the package has been created. To use this option key CMNINSTL on any command line
(except for the panel above) and the following display window will pop-up that will allow the user to mass
change any of the information shown.

Command ===>
Enter data elements that need to be updated:
ChangeMan Package: CLAS002724
Date: 20070101 /- days or yyyymmdd

From: ____ /- hrs/mins or hhmm
To: ____
Prim: ________________________ _______________________
Back: ________________________ _______________________
Press enter twice; once to process the change and, again, to confirm it.
Once the information on the Site Information panel is correct, press enter and the primary option menu
reappears. A message showing that the package was created appears in the upper-right hand corner of
the panel:
-------------------------------- BUILD OPTIONS ------------ CLAS002724 CREATED

OPTION ===>

Note: ChangeMan assigns the package a name, beginning with the four-letter application name, and
followed by a six-digit sequential number. It is recommended that the developer make a note of the
number. ChangeMan provides a query to find packages after they have been created. The Query function
will be discussed later.
Once a package has been created, components can be added to it and changed for assigned work. This
will be discussed in Chapter 4.

Chapter 4 Checkout and Stage

Most software changes start with an existing component that resides in the applications baseline library.
In order to make changes to a component contained in the ChangeMan baseline, it must first be checked
out into a package. This is called Checkout and can be accessed by selecting Option 5 in the Build
Options menu:
----------------------- BUILD OPTIONS --------------------------------

OPTION ===> 5

Selecting Option 5 causes the following panel to be displayed.
---------------------- CHECKOUT OPTIONS ------------------------------

OPTION ===> 1
PACKAGE ID ===> CLAS002724
1 Base/Prom - Checkout from baseline or promotion libraries

2 Package - Checkout package components
3 Release - Checkout components from a release
Choose Option 1 and hit enter to start the checkout process:
-------------------------- CHECKOUT ----------------------------------

OPTION ===>
L - List libraries where component is located
PACKAGE ID ===> CLAS002724 (Package name)
COMPONENT NAME ===> CLS* (Blank or pattern for list; * to Checkout ALL)
LIBRARY TYPE ===> (Blank for list)
SOURCE LIBRARY ===> 0 (Baseline 0 to -n; Promotion +1 to +n)
CONFIRM OVERLAY ===> YES (Y/N)

CHECKOUT MODE ===> 1 (1-Online, 2-Batch)
LOCK COMPONENT ===> NO (Y/N)
Enter the component name to be checked out and complete the other fields in this panel per the
information in the table below:

Package ID The package number into which the components being checked out will be
copied. This name will be pre-filled with the developers most recently created
package.
Component Name The name of the component to check out. Leave this field blank or enter a
partial name follower by a wildcard asterisk to get a list of possible
candidates..
Library Type Enter a three character software component library type (i.e., SRC, CPY, etc.)
used within ChangeMan. Leaving the field blank will provide a list of
component types where the component name enter above exits.
Source Library Enter a number that corresponds to the baseline version of the component to
be checked out. Normally, a zero will be entered to allow the current version of
the component to be checked out.
ChangeMan also maintains previous versions of each component which can

also be checked out. The entry of negative numbers will retrieve or
reconstruct previous component versions and place them in the package (i.e.,
to prepare a packages contents to revert to the last previous version of a
component, enter a -1).
In addition, "promoted" components can be checked out into a package from

a promotion test environment (i.e., system test) to support concurrent
development requirements. This is allowed even though the package
containing those components has not yet been baselined. To do this, enter a
positive number that corresponds to the applications targeted promotion level
(i.e., +10, +20, etc.).
Confirm Overlay Enter a "Y" (Yes) to prevent accidentally overwriting any components in the
package.
Checkout Mode Enter a 1 for Online.
Lock Component Entering a "Y" (Yes) in this field ensures that only the users ID associated
with the checkout can edit the component within the package..
Entering a "N" allows any of the applications developers to edit the

component (assuming RACF Group authorization for the other developers
allows update access).
Note: Whether a "Y" or "N" is entered, other application team members can
still check out the same component into other packages for concurrent
development purposes; however, ChangeMan does create an awareness
when this occurs. This will be discussed in more detail later in the document.
Hit Enter to continue and the panel below will be presented. In this example, the Component Type field
was left blank so ChangeMan presented a selection list of all of the component types where the
named, wild-carded component resides in the baseline. Enter a S to select the desired type and, again,
hit Enter.
---------------- LIBRARY TYPE SELECTION LIST -------- Row 1 to 9 of 9

LIB DESCRIPTION
_ CPY Copy Library
_ CTC Control Cards
_ JCL Job Control Language
_ JC1 JCL - General
_ PKG DB2 - Bind Package Statements
_ DBB DB2 - Bind Plan Statements
_ LCT Link Control Cards
_ PRC Job Procedure Library
S SRC Source Library

ChangeMan then displays a list of all of the components within the select component type:
CHECKOUT FROM SRC/LVL(0) - CMN.CLAS.BASO.SRC ----------------- Row 1 to 9 of 9

NAME STATUS VV.MM CREATED LAST MODIFIED SIZE INIT ID
_ CLSPGM01 16.01 1999/04/13 2005/05/02 10:57 59 60 T04463
_ CLSPGM02 10.01 1999/04/13 2004/03/04 10:51 59 60 T04462
_ CLSPGM03 11.01 1999/04/13 2004/02/23 09:20 60 60 T03617
_ CLSPGM04 09.01 1999/04/13 2004/04/08 09:25 60 60 T04462
S CLSPGM05 12.01 1999/04/13 2005/01/24 10:10 60 60 T04463
_ CLSPGM06 11.01 1999/04/13 2004/09/09 09:10 60 60 T03618
_ CLSPGM07 12.02 1999/04/13 2005/02/21 09:50 60 60 T04463
_ CLSPGM08 05.01 1999/04/13 2001/10/23 10:15 59 60 MB8147
_ CLSPGM99 07.01 2000/09/28 2001/10/23 10:15 61 60 MB8147
Enter a S to select the desired SRC component and hit Enter to have it checked out into the package.
Note that the baseline library name is displayed at the top of the panel.
Checkout Warning
The following warning panel will be presented if the selected component is already checked out into
another package as a result of the applications requirement to do Concurrent Development. This
notification panel is intended to warn the developer that code merging may be required, or that the
component checkout should, perhaps, be done from some other libraries (i.e. promotion libraries) within
ChangeMan, rather than the baseline, itself..
---------------------------------- CLSPGM05.SRC -------------- Row 1 to 7 of 7

Press ENTER or END to process or enter CANCEL command to exit.
This component is included in the following packages:
PACKAGE ID STA PROMOTED VV.MM LAST ACTION SIZE PROCNAME ID RELEASE

CLAS002708 DEV STAGING 12.02 2005/01/11 11:22 60 LECOBOL T04464
Hit Enter to confirm the checkout or enter Cancel to stop.

Note: If the checkout process is continued, all users who have the component checked out in other
packages will receive a TSO notification informing them that the component has been checked out the
baseline again.
The following panel will be displayed to confirm that the component was checked out.
AA00 OUT FROM SRC/LVL(0) - CMN.CLAS.BASO.SRC --------------- LANGUAGE ASSUMED

COMMAND ===> SCROLL ===> PAGE
_ CLSPGM01 16.01 1999/04/13 2005/05/02 10:57 59 60 T04463
_ CLSPGM02 11.01 1999/04/13 2007/01/30 07:00 59 60 JF7438
_ CLSPGM03 11.01 1999/04/13 2004/02/23 09:20 60 60 T03617
_ CLSPGM04 09.01 1999/04/13 2004/04/08 09:25 60 60 T04462
_ CLSPGM05 CHECKOUT 13.01 1999/04/13 2005/06/13 12:44 60 60 CP1951
_ CLSPGM06 11.01 1999/04/13 2004/09/09 09:10 60 60 T03618
_ CLSPGM07 12.02 1999/04/13 2005/02/21 09:50 60 60 T04463
_ CLSPGM08 05.01 1999/04/13 2001/10/23 10:15 59 60 MB8147
_ CLSPGM99 08.01 2000/09/28 2007/01/30 07:14 61 60 JF7438
The selected component is now ready to be Staged. This step is necessary in order to be able to edit or
compile (SRC types) within a package. Hit PF3 to back out and the Build options menu will be displayed
as shown below.

AA00 --------------------------- BUILD OPTIONS -------------------------------

OPTION ===> 6

Enter a 6 to begin the Stage process and hit Enter and the Stage Options panel will be displayed.
AA00 --------------------------- STAGE OPTIONS --------------------------------

OPTION ===> 2
PACKAGE ID ===> CLAS002724 PX=STG0
1 Dev - Stage components from development libraries

2 Package - Process package components
3 Parms - Specify component list selection criteria
Enter a 2 to Stage the component that is in Checkout status in the package and hit Enter .
AA00 -------------------- STAGE: CLAS002752 COMPONENTS ------- Row 1 to 5 of 5

COMMAND ===> SCROLL ===> ----
NAME TYPE STATUS CHANGED PROCNAME ID REQUEST
_S_ CLASPGM05 SRC CHECKOUT 20071205 095347 LECOBOL JD1234
Enter a S to execute the Stage and hit Enter to display the Confirmation panel.
AA00 ---------------------- CONFIRM STAGE REQUEST -----------------------------

COMMAND ===>
PACKAGE ID: CLAS002724

COMPONENT NAME: CLASPGM05
COMPONENT TYPE: SRC
LANGUAGE: COBOL
STATUS: CHECKOUT
CHANGED DATE: 20071205
CHANGED TIME: 095443
PROCEDURE NAME: LECOBOL
TSOID: JD1234
Press ENTER to process; Enter END command to cancel request.
When a source-type component has been initially staged, ChangeMan will always present the developer
with an opportunity to compile it as shown below:
.

------------------------- STAGE: COMPILE AND LINK EDIT ------- HISTORY ASSUMED

COMMAND ===>
PACKAGE ID: CLAS002724 STATUS: DEV INSTALL DATE: 20051205
STAGED NAME: CLSPGM05

LIBRARY TYPE: SRC - Source Library
DATASET NAME: CMN.CLAS.STGO.#002724.SRC
LANGUAGE ===> COBOL (Blank for list; applies to source code)

COMPILE PROCEDURE ===> LECOBOL (Blank for list; ? for designated procedure)
COMPILE PARMS ===>
LINK EDIT PARMS ===>
JOB STATEMENT INFORMATION:

===> //JD12341A JOB (HR00,XXXX,999,999),'CLAS724:CLSPGM05 CMP',______________
===> // NOTIFY=JD1234,SCHENV=CMN@HA00DP______________________________________
===> //*_____________________________________________________________________
===> //*_____________________________________________________________________
Hit Enter to execute the compile or PF3 to exit and have ChangeMan display the packages component
list menu.
Note: More information on compiling is provided in Chapter 6.
AA00 -------------------- STAGE: CLAS002752 COMPONENTS ----- REQUEST CANCELLED

_E_ CLASPGM05 SRC INCOMP 20071205 095443 LECOBOL JD1234 CANCEL
Enter an E and hit Enter to start the edit session.

Note: At this point the components status goes from Checkout to INCOMP (incomplete) on SRC type
components and it will stay INCOMP until they are successfully compiled, at which time the status
changes to Active.
Adding More Components
Additional components can be added to the package at this point by hitting PF3 to return to the Stage
Options panel, or by using again PF3 to back out and return to the Build Options; making the Checkout
panel, again, available. In the example below a copybook is added to the package.
----------------------------------- CHECKOUT ------------------- 1 CHECKED OUT

OPTION ===>
L - List libraries where component is located
PACKAGE ID ===> CLAS002724 (Package name)
COMPONENT NAME ===> (Blank or pattern for list; * to Checkout ALL)

LIBRARY TYPE ===> CPY (Blank for list)
SOURCE LIBRARY ===> 0 (Baseline 0 to -n; Promotion +1 to +n)
CONFIRM OVERLAY ===> YES (Y/N)

CHECKOUT MODE ===> 1 (1-Online, 2-Batch)

Enter a different component type (in this case CPY) and hit Enter to again obtain a list of available
components. In this example, since the component name was left blank, all of the copybook components
within the baseline library are presented to the developer.
CHECKOUT FROM CPY/LVL(0) - CMN.CLAS.BASO.CPY ----------------- Row 1 to 8 of 8

_ CLSBK01 10.01 2001/09/12 2002/01/10 12:42 7 15 MB8147
_ CLSBK02 04.05 2000/06/05 2002/05/22 08:19 8 5 MB8147
_ CPYBK01 08.01 2000/06/05 2004/10/14 09:19 7 15 T04463
_ CPYBK02 10.01 2000/06/05 2005/02/21 09:12 8 5 T04463
S CPYBK03 09.01 2000/06/05 2005/05/02 11:03 8 5 T04463
_ CPYBK04 12.01 2000/06/05 2004/09/08 11:15 8 5 T03618
_ CPYBK05 16.01 2000/06/05 2005/01/24 10:14 8 5 T04463
_ CPYBK99 04.01 2000/09/28 2002/01/10 11:49 8 5 MB8147
The concludes the discussion related to the updating of known, baselined components in ChangeMan
ZMF. When new components need to be added to a ChangeMan package they can be brought into the
package from private libraries and Staged for Development or simply created within the ChangeMan
Stage panel. This topic is covered in Chapter 5.

Chapter 5 Adding New Components

Stage from Development
Stage from Development allows developers to introduce new components into a ChangeMan package
that were created in a private library (i.e., ATTUID library).
-------------------------------- BUILD OPTIONS --------------------------------

OPTION ===> 6

Enter option 6 in the Build panel and hit Enter to display the Stage Options panel.
-------------------------------- STAGE OPTIONS -------------------------------

OPTION ===> 1

Insure that the targeted package number is correct, or change it, and then enter Option - 1 and hit Enter
to display the Stage: From Development panel.
--------------------------- STAGE: FROM DEVELOPMENT ---------------------------

COMMAND ===>
ISPF LIBRARY:
PROJECT ===>
GROUP ===>
TYPE ===>
MEMBER ===> (Blank or pattern for list; * for all members)
OTHER PARTITIONED OR SEQUENTIAL DATASET:

DATASET NAME ===> JD1234.CONTROL
ORGANIZATION ===> (PDS, SEQ, PAN, LIB, OTH)
LIBRARY TYPE ===> CTC (Blank for list)

STAGE NAME ===> NEWCTCRD (Optional if organization not SEQ)
CONFIRM REQUEST ===> YES (Y/N)
STAGE MODE ===> 1 (1-Foreground, 2-Batch)
SUPPRESS MESSAGES ===> YES (Y/N; applies to batch stage)

Either of the top two sections of this panel can be used to identify the from location of the component to
be added to the package. Choose one area or the other and then enter the component type and name to
be added to the package.
Note: In order for ChangeMan to access this dataset, the developer must have already granted
ChangeMan RACF "read" authority on that dataset to user CHGMAN. The developer must plan ahead
for this as the Grant does not become effective until the CHGMAN started task is bounced (task
bounces occurs nightly).
An allocation/open error message will be issued if an attempt is made to stage a component before the
grant process takes effect. The full RACF error can be found in the ChangeMan started task log in
SDSF/JesMaster. Visit the ChangeMan website and click on Frequently Asked Questions; locate the
RACF section and then click on the question regarding the Allocation Error.
The following additional fields are also present on the Stage from Development panel:
Confirm Request Leave as "Y". This will warn the user if an overlay situation exists
Stage Mode Leave as 1 for Foreground.
Suppress Messages Not applicable in foreground mode ignore..
Lock Component This prevents other developers from updating or editing the copy of this
component in the package. It does not prevent another developer from
bringing the same component into another package.
Once a component is staged from development, it will appear in the package alongside any components
that have been added to or checked out into it
Create New in ChangeMan

ChangeMan also offers the developer the opportunity to create a new component from the Stage panel.

COMMAND ===> EDIT NEWCNTL1.CTC SCROLL ===> ----
__ CLASPGM05 SRC CHECKOUT 20071205 095347 LECOBOL JD1234
On the command line enter the word edit followed a blank space and the components name and the
component types ChangeMan Low Level Qualifier (i.e., CTC). Hit Enter to display an empty member
panel wherein the developer can key the component information using standard editing functions.
AA00 SCRATCH.JD1234.A03A9C19.T9E83207.CTC Columns 00001 00072

Command ===> Scroll ===> PAGE
****** ***************************** Top of Data ******************************
'''''' 4142260444
'''''' 4142260445
'''''' 4142260446
'''''' 9208881234
''''''
''''''
''''''
''''''
''''''
''''''
****** **************************** Bottom of Data ****************************
Hit enter to compress the edit panel.

AA00 SCRATCH.JD1234.A03A9C19.T9E83207.CTC Columns 00001 00072

Command ===>
Scroll ===> PAGE
****** ***************************** Top of Data ******************************
000100 4142260444
000200 4142260445
000300 4142260446
000400 9208881234
PF3 out of the edit panel to save the new component in the package.

__ CLASPGM05 SRC INCOMP 20071121 144838 LECOBOL JD1234
__ CPYBK03 CPY CHECKOUT 20071205 114451 JD1234
__ NEWCNTL1 CTC ACTIVE 20071205 123937 JD1234
Now, all of the components in the package have been staged and are available for editing. Source-types
can also be compiled and linked after the editing is done and they are ready to be tested. Chapter 6
provides more information on how these things can be accomplished.

Chapter 6 Editing and Compiling

In ChangeMan, making changes to components within a package must be done after Staging. Once
staged, components can be changed using a common ISPF edit session.
In order to access the components in a package and make changes, choose Option 6 from the Build
menu:
-------------------------------- BUILD OPTIONS --------------------------------

OPTION ===> 6

Then choose Option 2 Process Package Components, ensuring that the package number specified is
correct:
-------------------------------- STAGE OPTIONS --------------------------------

OPTION ===> 2

Processing Package Components

The panel below will list the components that have been checked out or staged from development:
------------------------- STAGE: CLAS002724 COMPONENTS ------- Row 1 to 2 of 2

__ CLSPGM05 SRC INCOMP 20050613 104405 LECOBOL JD1234
******************************* Bottom of data ********************************
There are several line commands that can be used from this panel. Enter a ? on any line to see a
complete list. The more commonly used ones can be found in the table below:
B Enter Browse mode on this component.

E Enter Edit mode on this component.

D Delete a component from the package.

Note that this has no impact on the baseline or
any other version; it simply removes the
component copy from the package and indicates
to ChangeMan that the component is no longer
checked out.
S Shortcut to Staging a component that has been
checked out of the baseline. Note, that if this
option is used, ChangeMan will force a SRC
type component into the compile process, and it
will not be staged if the developer exits (PF3)
out of the compile.
R Recompile a source-type component.
The following example demonstrates what happens when a source-type component is edited.

_E_ CLSPGM05 SRC INCOMP 20050613 104405 LECOBOL JD1234
Enter E for edit and hit enter and ChangeMan will open the component in a standard ISPF edit panel.
Note: All ISPF primary and line edit commands are available within this panel:
EDIT SCRATCH.JD1234.A0370BD2.T8034941.COBOL Columns 00001 00072

****** ***************************** Top of Data ******************************
010000 010000 IDENTIFICATION DIVISION.
020003 020000 PROGRAM-ID. CLSPGM05.
020004 020004 AUTHOR. Joe Developer
030000 030000 ENVIRONMENT DIVISION.
040000 040000 INPUT-OUTPUT SECTION.
050000 050000 FILE-CONTROL.
060000 060000 SELECT ONLY-FILE,
070000 070000 ASSIGN VSAMFILE,
080000 080000 ORGANIZATION IS INDEXED,
090000 090000 ACCESS DYNAMIC,
100000 100000 RECORD KEY IS ONLY-KEY,
110000 110000 FILE STATUS IS ONLY-FILE-STAT.
120000 120000 DATA DIVISION.
130000 130000 FILE SECTION.
140000 140000 FD ONLY-FILE.
150000 150000 01 ONLY-REC.
160000 160000 02 ONLY-KEY.
170000 170000 03 ONLY-ACCOUNT PIC X(10).
180000 180000 03 ONLY-TYPE PIC XX.
190000 190000 03 ONLY-DSN PIC X(44) OCCURS 2.
After the editing of the component is complete, hit PF3 to save the change and exit the edit session.
Note: In this example, only the program authors name was changed to demonstrate how ChangeMan
works after an edit session. It should be noted that ChangeMan recognizes when an edit session
concludes without any changes being made; in these cases ChangeMan does nothing and returns the
developed to the package component list panel.

Comparison Report
ChangeMan provides a comparison report that shows the before and after lines of code that were
changed during the edit session.
BROWSE SCRATCH.JD1234.A0370BD2.T8034941.OUTLIST Line 00000000 Col 001 080

********************************* Top of Data **********************************
S E R C M P A R (MVS - 550 - 20040831) 2 TEXTONLY MONDAY JUNE 1
SYSUT1=CMN.CLAS.STGO.#002724.SRC(CLSPGM05),SYSUT2=SCRATCH.JD1234.A0370BD2.T80349
010000 IDENTIFICATION DIVISION.
020000 PROGRAM-ID. CLSPGM05.
++++++++|+++.+<++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7+>
D 020004 AUTHOR. JOE CODER.
--------|---.----1----.----2----.----3----.----4----.----5----.----6----.----7--
I 020004 AUTHOR. JOE DEVELOPER
++++++++|+++.+<++1++++.++++2++++.++++3++++.++++4++++.++++5++++.++++6++++.++++7+>
030000 ENVIRONMENT DIVISION.

040000 INPUT-OUTPUT SECTION.
Hit PF3 to exit after reviewing the report and ChangeMan will provide an opportunity to compile any
source-type component that was changed.
------------------------ COMPARISON REPORT DISPOSITION ------------------------

OPTION ===>
REPORT DATASET NAME: 'SCRATCH.JD1234.A0370BD2.T8034941.OUTLIST'
REPORT DISPOSITION ===> D D - Delete

K - Keep
PD - Print and Delete
PK - Print and Keep
JOB STATEMENT INFORMATION IF DISPOSITION IS PD OR PK:

===> //JD123411A JOB (HR00,XXXX,999,999),'COMPONT COMPARE RPT',_______________
===> //*_____________________________________________________________________
===> //*_____________________________________________________________________
Press ENTER or END to process

Enter CANCEL command to exit without saving changes.
To proceed with the compile, hit enter, or hit PF3 to exit (edit updates have already been saved). The
comparison report can be given a disposition, at this point, by changing the delete default option. By
changing the option to PK a job will run to send the report to SSO.
Note: The job card shown about reflects the parameters of the compile job that will be submitted; it may
be edited, if deemed necessary, by the developer.
ChangeMan will provide a current development warning panel at this point if a component is also present
in another package. This warning is similar to the one produced when the component was originally
checked out of the baseline.
---------------------------------- CLSPGM05.SRC -------------- Row 1 to 8 of 8

Press ENTER or END to process or enter CANCEL command to exit.
This component is included in the following packages:

PACKAGE ID STA PROMOTED VV.MM LAST ACTION SIZE PROCNAME ID RELEASE

CLAS002724 DEV 13.00 2005/06/13 10:44 60 LECOBOL JD1234
CLAS002708 DEV STAGING 12.02 2005/01/11 11:22 60 LECOBOL T04464
Note: Other developers do not receive another concurrent development TSO message at this point.
Compiling
ChangeMan provides a Compile User Option panel when the developer hits the enter key on the
Comparison Report panel above. If the component just edited was checked out of the ChangeMan
baseline, or some promotion library, all of the values on this panel will be set and should not need to be
changed. Thats because the components compile options were picked up as component history by
ChangeMan when the applications baseline was initially loaded or when the component was first created
in the Tool.
If the component being changed in this edit session is new, the developer will have to select the
appropriate compile parameters. Refer to the ChangeMan User Guide found under Documentation at
this link - ChangeMan ZMF, or consult with the applications Local Administrator for guidance.
AA00 n: SWBT --- CLSPGM05.SRC/COBOL --- User Options

COMMAND ===>
CICS N/C/L ==> N IMS Y/N ==> N DB2 Processing ==> N

DATAGATE Y/N ==> N ISPF Y/N ==> N N = No DB2
TeraData Y/N ==> N TCP/IP Y/N ==> N C = Compile/Link
MQ Series O/B/N ==> N Comp/Link/Pre O/L/P ==> L L = Link Only
CE Pre-Comp Y/N ==> N O = Comp Only D = Force Listing
CPXP Pre-Comp Y/N ==> N L = Comp/Link P = Pre-compile
PBCF Pre-Comp Y/N ==> N P = Comp/Prelink/Link ENTRY Statement ==> N
YM88 Module Y/N ==> N Oracle Pre-Comp ==> N N = NORMAL
SRXCOPY Y/N ==> N N = No Oracle D = DLITCBL
ORBIX Ver. C/P/N ==> N Y = Pre-Comp/Link
TYPE: C/S/L/N ==> N D = Y & Force Listing
C =Current C =Client L = Pre-link/Link only
P =Previous S =Server System Prog. C Y/N ==> N
N =No ORBIX L =Libs
DDIO File (Y/N): N DDIO DSN: HLQ.APPL.DDIO

(NOTE: The second node must be CLAS and the last node should be AKR/DDIO)
Press ENTER to continue; Enter END command to exit.
ChangeMan submits a job to execute the compile and link process when Enter is hit on this panel.
When the job ends, a typical TSO notification message is sent to the developer. The compile results can
be viewed in detail under the developers ATTUID in SSO.
Notice that a XPEDITER library can be defined at the bottom of this panel. Note that there are special
naming constraints that must be followed when naming a DDIO dataset.
12.52.28 JOB01341 $HASP165 JD12341A ENDED AT MASTER MAXCC=4 CN(INTERNAL)

***
ChangeMan returns to the Process Package Components panel. The Status of the compiled component
still shows INCOMP. The panel needs to be refreshed in order to see the new status after the compile.

COMMAND ===> R SCROLL ===> CSR
__ CLSPGM05 SRC INCOMP 20050613 104405 LECOBOL JD1234 EDITSTG

Enter a R (to Refresh) and hit Enter to see if the status has been changed. If the compilation was
successful, the status will be set to Active; otherwise, it will remain INCOMP.

__ CLSPGM05 SRC ACTIVE 20050613 125226 LECOBOL JD1234
__ CLSPGM05 LDN ACTIVE 20050613 125226 LECOBOL JD1234
__ CLSPGM05 LOD ACTIVE 20050613 125226 LECOBOL JD1234
__ CLSPGM05 LST ACTIVE 20050613 125226 LECOBOL JD1234
__ CLSPGM05 OBJ ACTIVE 20050613 125226 LECOBOL JD1234
The status as shown above for the compiled SRC member is now ACTIVE, which means that the
component has been successfully compiled and a load module (LOD), along with some other compile
outputs (OBJ, LDN, and LST), have been staged and set to Active as well.
Any components within a package, excluding the outputs produced by a compile, can be edited in the
same manner as shown above for the SRC component.
Note: The act of changing a copybook or other component types used within a source-type component
(i.e., SRC for called modules), that are changed after the using Source has been compiled, will not force
the Using Source component to be recompiled again. This potential problem (out-of-sync condition),
however, will be recognized by ChangeMan during the Audit step. The Audit process will be discussed in
Chapter 8 below.
Browsing Compile Output Listings (LST)

One of the outputs of a compile is a source listing (LST component type) dataset. It is maintained in a
compressed format, so it cannot be browsed directly using ISPF 3.4. Instead, it must be viewed in
ChangeMan by using the L option found in the Build Options panel.
-------------------------------- BUILD OPTIONS --------------------------------

OPTION ===> L

Select L and hit Enter to see the following panel:

-------------------------- BROWSE COMPRESSED LISTINGS -------------------------

OPTION ===>
SPECIFY SELECTION CRITERIA:

APPLICATION ===> (Required if PACKAGE ID not supplied;
Non-blank: staging/baseline listings;
Blank: staging listings only)
AREA LISTINGS ===> NO (Y/N - ERO only)
COMPONENT NAME ===> (Blank or pattern for list)
LIBRARY TYPE ===> LST (Blank for list)
FROM DATE ===> (YYYYMMDD)
TO DATE ===> (YYYYMMDD)
PROMPT FOR LISTING DISPOSITION ===> NO (Y/N)
Enter either the ChangeMan package number on the first line or the application name (to see the
program listings in the baseline) on the second line, not both (If the application name is used it will
always override the package name, and the packages compile listing will not be displayed).
Leave the Component Name field blank and hit Enter to view a list of all source-type listings within the
package:
-------------------------- BROWSE COMPRESSED LISTINGS -------- Row 1 to 1 of 1

Press END command to exit.
NAME LEVEL VV.MM CREATED CHANGED SIZE INIT ID

S CLSPGM05 STAGING 01.00 2005/06/13 2005/06/13 12:52 1150 1150 CHGMAN
To browse a listing, enter a S to select it.
BROWSE SCRATCH.JD1234.A0370BD2.T81B17AE.OUTLIST Line 00000060 Col 001 080

CMN1400I - Session established with Change Man started task.
Library search order: PDS/SYS05164.T125219.RA000.JD12341A.NULLPDS.H03
PDS/CMN.CLAS.STGO.#002724.CPY (CPY)
PDS/CMN.CLAS.BASO.CPY (CPY)
LV -MEMBER--- VV.MM --CREATE-- --LAST CHANGED-- SIZE INIT -USERID- -- L I B R
--- C O M P O N E N
00 CLSPGM05 13.01 1999/04/13 2005/06/13 12:44 60 60 JD1234 SYS05164.T
01 CPYBK01 08.01 2000/06/05 2004/10/14 09:19 7 15 T04463 CMN.CLAS.B
01 CPYBK02 10.01 2000/06/05 2005/02/21 09:12 8 5 T04463 CMN.CLAS.B
01 CPYBK03 10.00 2000/06/05 2005/06/13 10:49 8 5 JD1234 CMN.CLAS.S
fix this line
01 CPYBK04 12.01 2000/06/05 2004/09/08 11:15 8 5 T03618 CMN.CLAS.B
test component desc
01 CPYBK05 16.01 2000/06/05 2005/01/24 10:14 8 5 T04463 CMN.CLAS.B
CMN1410I - Session terminated with Change Man started task.
CMN5400I - Time of day at end of job: 12:52:21 - Condition Code on exit: 0
Record count in ====> 00060
Record count out ===> 00131

Datasets to Use for External Testing

Testing is always done outside of ChangeMan but the contents of a ChangeMan packages components
can be accessed from within batch test JCL by adding JOBLIB or STEPLIB statements that reference the
packages staging libraries. The JOBLIB or STEPLIB statements will have to be modified each time a new
package is created and used in testing, in order to take in the new staging libraries (as staging libraries
are uniquely named for each package).
Another alternative is to promote the contents of the package to a specific set of promotion libraries that
are always referenced in a set of test JCL that is unique to a particular testing environment (i.e., Chain
test). More information will be provided on promotions in Chapter 7.

Chapter 7 Promotion
Promoting in ChangeMan
For most development teams, the teams developers working on a project or a release will eventually
have a need to run a group test of all their changed components. These tests are best handled within a
common sets of libraries dedicated to a particular level of testing. These are known as Promotion
Libraries in ChangeMan and they can be made available, as needed, within each application during the
configuration process.
Promotion in ChangeMan involves copying executable components from individual package staging
libraries into libraries designated to predefined types of testing (i.e., System Test). ChangeMan promotion
libraries can then be referenced from within batch or online test environments and are reusable, time-
after-time, as projects or releases are worked on by the application team.
Note: The number (types) and use of promotion libraries within ChangeMan is totally optional and each
application can determine their own needs in relation to Promotions.
Also, the process of promotion in ChangeMan is totally separate from the process of Installing.
ChangeMan promotions are limited to testing, where ChangeMan installations can impact either test or
production environment libraries. The types of tests that can be conducted from within promotion areas
varies in order to support an applications local practices and satisfy their quality assurance needs. Some
typical promotion library sets include the following:
o Chain Test
o System Test
o Acceptance Test
o CLEC Test
o Performance Test
Promotion Levels
ChangeMan works under the assumption that sets of promotion libraries relate to testing processes or
quality practices that have a higher level of importance or control, as components are moved from one set
of libraries to another; therefore, within ChangeMan, each set of promotion libraries are assigned unique
level numbers. This assignment is arbitrary and there is no mandated need within ChangeMan to promote
components from one level to the next in any strict order; however, this may be a requirement imposed by
the applications local testing practices. The developer must become familiar with the promotion level
names, and level numbers assigned to them, in order to insure that the promotion libraries are used as
intended within the teams testing procedures.
Promotions with ChangeMan can take place Locally (on the DASD complex where the ChangeMan
development instance resides) or Remotely (on another test or production complex where the
applications test environment(s) exist.
ChangeMan handles both promotion destinations easily and its remote promotion capability is basically
transparent to the user. In either case, ChangeMan never loses track of where the components are
located and easily allows for the components to be recalled (demoted) when deemed necessary by the
developer or quality control group within the team. Individual applications can control who can promote (or
demote) to which promotion level by assigning individuals within a team to different RACF groups.
Work with the applications Local Administrator to establish promotion levels within the application that
meet the needs of the business. Questions about the use of an applications promotion libraries should
always be directed to the Local Administrator.

Promoting Package Contents

Select Option 3 from the ChangeMan Primary Option Menu to Promote and the following panel will be
presented:
----------------------- PROMOTE/DEMOTE A CHANGE PACKAGE -----------------------

OPTION ===> P
P Promote
D Demote
Enter P on the command line and the package number and hit Enter to see the Promotion Site List
panel displayed.
SLT1 ------------------------- PROMOTE SITE LIST ------------- Row 1 to 2 of 2

PX=RPM1
PACKAGE ID: CLAS002724 STATUS: DEV INSTALL: 20080206
DEMOTE REQD ------------- LAST PROMOTION DETAILS --------------

SITE NAME PRIOR SITES TYPE PROMOTION LVL DATE TIME USER
S SLTESTP NO 0
_ ATT3TEST NO 0
******************************* Bottom of data ********************************
Enter a S on the line containing the desired promotion site and hit Enter to see the Promotion Options
panel displayed.
------------------------------- PROMOTE OPTIONS -------------------------------

OPTION ===> PEXIT=RPM3
F - Full promotion of the entire package to another promotion level
S - Selective promotion of components to another promotion level
H - Display promotion/demotion history for this site
O - Check for potential overlay at next promotion level
PACKAGE ID: CLAS002724 CREATOR: JD1234 STATUS: DEV INSTALL DATE: 20051205
PROMOTION SITE : SLTESTP

CURRENT PROMOTION LEVEL: STAGING + 0
NEXT PROMOTION LEVEL ===> 10 (blank, * or 0 for a list)

BYPASS OVERLAY CHECK ===> NO (Y-Yes or N-No)
===> //JD12341A JOB (HR00,XXXX,999,999),'CLAS724:10 PROMOTED',_______________
===> //*_____________________________________________________________________
===> //*_____________________________________________________________________
Two promotion options are available along with some query capabilities as shown above:

o full promotion - all the components in the chosen package are copied into a promotion library
set.
o selective promotion - selected individual components are copied into a promotion library from
the package.
The Next Promotion Level field specifies the next highest promotion level available for the package
within the application. As stated before, promotion levels are given numbers, but a higher number does
not always mean a more "advanced" promotion. Applications may choose to use different promotion
levels to indicate the promotion libraries for different release, for example, where all levels represent an
equal level of importance. The Local Administrator should document the significance of promotion levels
and the purpose of each.
Key over the default level number or enter an asterisk (*) to see a list of those that are available on the
next panel.
It is recommended that the Bypass Overlay Check field remains a "N". Thats because other developers
may have promoted their packages containing the same component(s) into the same area being targeted
for this package. If set to Y, the latest version promoted will overlay the previous version.
If set to N, the overlay check will inform the developer that an overlay of the same component is about to
occur. The users can do then merge changes in one package or another and then promote the merged
component into the desired promotion library set.
The following diagram illustrates a typical promotion scenario:
Promotion Levels
In this case, three developers are each working on different components. Each promotes their packages
staging library components to promotion level 10 for chain testing. This copies the components to these
libraries, but does not remove the components from the packages staging libraries. As a result, the
individual developers still have the option to update the components in their packages, make changes,
compile, and re-unit test from the staging libraries prior to re-promoting.

After the chain test in complete the packages can be then promoted to the system test library set.
Hitting Enter on the panel above submits a batch promotion job that will trigger a TSO notification
message, as shown below, to the developer when it finishes:
CMN402I - CLAS002724 PROMOTED TO SLTESTP UNIT LEVEL 10 2005/06/14 @ 12:29:52. C

N(INTERNAL)
12.29.53 JOB07268 $HASP165 JD12341A ENDED AT MASTER MAXCC=0 CN(INTERNAL)
***
A packages components can be removed from the promotion library set, by demoting them using the
same D option on the following panel:
----------------------- PROMOTE/DEMOTE A CHANGE PACKAGE -----------------------

OPTION ===> D
P Promote
D Demote
Both selective or full demotes are available, as well. Demoting components found defective during testing
ensures that they will not be used for the impacted testing level until they are fixed and re-promoted;
however, demoting components is optional and local practices may dictate the need to-do or not-to-do it.
Finding the Promotion Library Datasets

Each promotion level library has a unique set of PDSs associated with it. There is a defined promotion
dataset naming convention as shown below:
CMN.APPL.PRMx.promoname.typ
where CMN is a constant, APPL is the ChangeMan application name, PRM is a constant, x is the
one character ChangeMan Deployment Site ID (i.e., the C in STLOUISC), promoname is the
alphanumeric name assigned to the promotion level (i.e., chain), and typ is the ChangeMan component
type (i.e., CTC for control cards). These libraries can be browsed using ISPF 3.4 command but cannot be
changed outside of ChangeMan.
DSLIST - Data Sets Matching CMN.CLAS.PRM*.* Row 1 of 18


-------------------------------------------------------------------------------
CMN.CLAS.PRMO.CHAIN.CTC MIGRAT2
CMN.CLAS.PRMO.CHAIN.JCL MIGRAT2
CMN.CLAS.PRMO.CHAIN.PRC MIGRAT2
CMN.CLAS.PRMO.CHAIN.LOD MIGRAT2
CMN.CLAS.PRMO.CHAIN.DAT PAH026
CMN.CLAS.PRMO.SYSTEM.CTC MIGRAT2
CMN.CLAS.PRMO.SYSTEM.JCL MIGRAT2
CMN.CLAS.PRMO.SYSTEM.PRC MIGRAT2
CMN.CLAS.PRMO.SYSTEM.LOD MIGRAT2

CMN.CLAS.PRMO.SYSTEM.DAT PAP076
All promotion libraries can be utilized in the applications external testing environments by adding JOBLIB
or STEPLIB cards pointing to them in batch JCL streams or including them in the concatenation list of
online environments.
Multiple Promotions and Clean-up

As components promoted from one level to the next (as in the example above, from level 10 to 20), this
causes ChangeMan to automatically clean up (empty) the components in the level 10 library set. And,
when ChangeMan sends components to test and/or production install sites, the clean-up of the
components from the last used promotion library set occurs, as well.
The components continue to reside in the packages staging libraries, however, until they are eventually
aged off after the package has been baselined.
Note: There is an AT&T customization that allows an application to eliminate this clean-up process, if so
desired. The applications Local Administrator can activate this customization at the component level from
within the CMNTOOLS Configuration Manager panel (option 5.5). For more information visit the
ChangeMan ZMF website and select Writing and Using Customizations. ChangeMan ZMF Website
Other Benefits of Promotion

In addition to having a common set of libraries from which to test, promotion is also useful because it
allows "sharing" of components with other developers within the application, or across any of the
ChangeMan applications that reside on an applications development complex.. The example below is a
common scenario and is a different situation than shown above.

Chapter 8 Audit
Audit Explained
At any time during the development life cycle, changes made to software components could create "out of
synch" conditions in relation to the applications baseline libraries or other in-progress changes. The Audit
Process warns developers that these situations exist. The following are two examples where audit
provides the developers with a benefit that eliminates risk during the SDLC.
1. Source type components are checked out, updated, and compiled and then a copybook, that is
also in the same package and used by the source program, is changed.
o Audit Findings - The package would be found to be out of synch with itself.
o Developer Action Recompile the source program.
2. A control card is checked out of the baseline into a planned package for future release work. The
next day, an application teammate checks out the same control card into an unplanned package
to make an emergency fix; then, has the fix installed in production and baselines the fix package.
o Audit Findings the planned packages component has a version that is "out of synch" with
the baseline version.
o Developer Action Merge the fix change into the existing component or recheck out the
component and make release updates to it.
Audits When to Run

Audits may be run anytime during the development lifecycle; however, the most important time is to run
one is after the components for a given work assignment have been checked out into a package and all
required changes are thought to be made. This should be prior to any actual testing being done. This
insures that the packages contents include the most current version of the components prior to testing
and eliminates potential rework that could be attributed to unknown out-of-sync conditions.
Although running Audit as described above is optional, there comes a time in the development life cycle
when running an audit is mandatory. This occurs prior to progressing any package through the first quality
step imposed by ChangeMan ZMF, i.e. freezing the package. (Chapter 8 provides details on the
package freezing and approval steps).
Audits How Are They Controlled?

ChangeMan can be configured to assign different levels of control to the Audit process. The Local
Administrator normally determines what is the best audit level to impose on the application and it is set
within ChangeMans administrative configuration PARMS panel.
The lowest audit level permissible is 1 and this setting means that Audit is required but any return code
(except for an abend) is acceptable. This audit level is, however, not allowed when an application starts
using ChangeMan for software distribution. Using this audit level does allow the application so develop
software at a higher risk level, despite the fact that out-of-sync situations are still identified to the
developer, because they can be arbitrarily ignored.
Once an application starts using ChangeMan for software distribution a level of 2 is the lowest allowed.

A 2 dictates that Audit is required and the return code must not exceed 12. A return code greater than
12 implies that there are out-of-sync conditions within the packages staging libraries (example 1 above).
The highest audit level is a 5 , which means that audit prior to freezing is mandatory and the return code
must be zero.
Global SCM recommends that the audit level should be set to a 4. This means that audit prior to freezing
is mandatory and the return code must not exceed 4. A return code greater than 4 implies that there are
out-of-sync conditions within the packages staging libraries or between the package staging libraries and
the baseline (example 2 above).
Audit Extending Its Reach

Audit does not compare a package to any other packages within the application, unless the package is a
Participating package. In that case, all the Participating packages tied-together by a Complex package
are treated as one large package during Audit. Also ChangeMan can be configured by the Local
Administrator to consider the applications promotion libraries which will treat out-of-sync conditions
identified within them in a manner similar to those found in the baseline.
o Also, in order to support AT&Ts Enterprise Change Management policy, ChangeMan audits have
been enhanced to validate that an AOTS Change Record number has been entered for the
package via CMNTOOLS, option 1.1. More information about the AOTS Audit Check can be
found by following this link:
Using ChangeMan Customizations
Running the Audit

To run audit, enter the Build menu, and choose Option 7 Audit.
----------------------------- AUDIT CHANGE PACKAGE ----------------------------

COMMAND ===>

AUDIT STAGING LIBRARIES ONLY ===> NO (Y/N)
AUTO RESOLVE OF OUT-OF-SYNCHS ===> NO (Y/N)
WARNING - ONLY USE AUTO RESOLVE AFTER YOU HAVE REVIEWED A NORMAL AUDIT
AND YOU HAVE ALREADY DETERMINED HOW MANY JOBS WILL BE SUBMITTED.
INCLUDE HISTORY RECORDS ===> NO (Y/N)
FORMAT REPORT FOR PRINTING ===> NO (Y/N)
AUDIT PARTICIPATING PACKAGE
AS A SIMPLE PACKAGE ===> NO (Y/N)
AS A PRIMARY PACKAGE ===> NO (Y/N)
BY DEPARTMENT NUMBER ===> NO (Y/N)
CROSS APPLICATION AUDIT ===> NO (Y/N) - (Simple package only)
===> //JD12341A JOB (HR00,XXXX,999,999),'CLAS724 AUDIT',_____________________
===> //*_____________________________________________________________________
===> //*_____________________________________________________________________
Enter the package number, keep the default settings at NO, and modify the Job Card as needed; then hit
Enter which will submit a batch job that will return a TSO notification message summarizing the audits
results as follows:
CMN2696I - PACKAGE CLAS002724 PASSED AUDIT WITH A RETURN CODE OF 12. CN(INTERNAL)
In this example, the condition code reflects the highest severity code for an out-of-synch condition yet the
Audit passed; therefore, the Audit Level setting for the CLAS application must be a 2. This example

illustrates why developers should actually look at the audit results details even though audit has not failed,
as a 12 return code error is very significant. In theory, if an audit passes, the development life cycle can
be continued but it is recommend that all non-zero audit return codes be researched, no matter what the
applications audit level is set to.
Audit results details can be viewed in SSO.
SYSNAME ===> AA00 ------ SSO Sysout (Today Is 05165) -------------- Job 1 Of 3
Job Name Nbr MaxCC Sys Started Ended Lines Description
B JD12341A 1690 0012 AA00 05165/1341 05165/1342 898 CLAS724 AUDIT
JD12341A 7268 0000 AA00 05165/1229 05165/1229 1,197 CLAS724:10 PROMOTED
JD12341A 1341 0004 AA00 05164/1252 05164/1252 4,237 CLAS724:CLSPGM05 CMP
****************************** BOTTOM OF DATA *********************************
Interpreting the Audit Output

Once in browse mode in SSO max down to the bottom of the sysout report to see the error summary:
BSYS e JA2645X - SSO.D1454143.T207317.JA2645X' --- LINE 00002211 COL 001 080

AT&T Audit Summary Report For Package CLAS2747
------------------------------------------------
RC Description
-- ------------------------------------------------------------
08 ChangeMan Audit Report. The Max passing RC: 12
00 AOTS Tracking Number Validation
To quickly find the various audit reports in this job, issue one of
the following FIND commands on the ISPF command line:
For ChangeMan Audit Report ==> F '.AUDITRPT' FIRST

For AOTS Tracking Number Rpt ==> F 'YK109-00I' FIRST
The highest audit return code based on the errors identified

above and the AOTS tracking number validation parm is: 08
-) .YK138 .SYSOUT 19
There are actually 2 lines within the report that show distinctly different audit errors:
o ChangeMan Audit Report line that provides a summary of the highest return code found while
ChangeMan did the out-of-sync audit checking described above.
The complete list of errors can be found in the Audit Chapter in the ChangeMan User
Guide which can be located by following this link:
ChangeMan Audit - Out of Sync Conditions
o AOTS Tracking Number Validation line that provides summary information from the piece of
Audit developed as an AT&T customization that enforces Enterprise Change Management policy
is being complied with.
Note: This line is only applicable to those applications using ChangeMans software distribution
feature.
Below these lines is a helpful job-aid that provides specific information about Audit return codes that
are greater than zero.

The following is a snap-shot of the out-of-sync portion of the audit report that shows 2 types of errors:
Browse JD12341A - SSO.D1342056.T605165.JD12341A -- LINE 00000869 COL 001 080
Out-of-synch messages (hint - search for "!" marks)
DUPLIC! (Staging duplicates baseline) ===> 0
SYNCH0! (Not in scope of audit or unknown) ===> 0
SYNCH1! (ISPF statistics not available) ===> 0
SYNCH2! (Compile/designated proc differ) ===> 0
SYNCH3! (Unparsable load module) ===> 0
SYNCH4! (CPY problem in staging) ===> 0
SYNCH5! (CPY high-date problem in baseline)===> 8
SYNCH6! (Activity file not checked out) ===> 0
SYNCH7! (Called subroutine in staging) ===> 0
SYNCH8! (Called subroutine in baseline) ===> 0
SYNCH9! (Source and load discrepancy) ===> 0
SYNCH10! (Version regression problem) ===> 0
SYNCH11! (Component hash discrepancy) ===> 0
SYNCH12! (Orphan module in staging) ===> 0
SYNCH13! (Baseline/staging discrepancy) ===> 0
SYNCH14! (Components not in active status) ===> 0
SYNCH15! (Source to relationship problem) ===> 1
SYNCH16! (CPY low-date problem in baseline)===> 0
SYNCH17! (CPY deleted problem in staging) ===> 0
SYNCH18! (LOD deleted problem in staging) ===> 0
In this example audit found one SYNCH15 error and eight SYNCH5 errors.
Enter the following "find" (F) function on the command line to find the error details:
F SYNCH15 FIRST
The first occurrence of a SYNCH15 error is located:
Copybook Source Copybook

Name VV.MM Created Changed Size Init Tso-id Name Name
12.01 1999/04/13 2005/01/24 10:10 0060 0060 T04463 CLSPGM05
CPYBK01 08.01 2000/06/05 2004/10/14 09:19 0007 0015 T04463
CPYBK02 10.01 2000/06/05 2005/02/21 09:12 0008 0005 T04463
CPYBK03 09.01 2000/06/05 2005/05/02 11:03 0008 0005 T04463 SYNCH15! CPYBK03
CPYBK04 12.01 2000/06/05 2004/09/08 11:15 0008 0005 T03618
CPYBK05 16.01 2000/06/05 2005/01/24 10:14 0008 0005 T04463
The column on the right identify where the SYNCH15 error occurred. In this case, the out-of-sync
condition occurred between CLSPGM05 and CPYBK03. The description of this error is:
SYNCH15! CC 12 A baseline copybook has a later date/time than the version of the copybook in the
package that was used during the compilation of the flagged source code component.
A re-compile of the source component in the package will fix this error; however, there are still have other
errors (all SYNCH5) that may have to be addressed. The description the SYNCH5 errors follows:
SYNCH5! CC 08 A staging version of a copybook has a more recent activation date than a baseline
version of the source calling it
This occurs between our CPYBK03 component and a number of other programs in the application
baseline that were not checked out into the package. It means that these other programs have not been
recompiled, but probably should be, as they need to include the changed copybook as well. The SYNCH5
error is not as severe as our SYNCH15. The developer would have to evaluate the impact of these errors
and take the corrective action as required or, perhaps, do nothing; because the part of the copybook that
was changed may have only been a redefinition of a "filler" space, and only the program in the package
will use the new data assigned through the redefinition.

Auto-Resolve Out-Of-Synchs
An option exists to resolve some conditions that can be solved manually by checking out and/or
recompiling components. The following SYNCH errors can be auto-resolved using this option; 2, 4, 5, 7,
8, 9, and 15,
----------------------------- AUDIT CHANGE PACKAGE ----------------------------

COMMAND ===>

AUDIT STAGING LIBRARIES ONLY ===> NO (Y/N)
AUTO RESOLVE OF OUT-OF-SYNCHS ===> NO (Y/N)
WARNING - ONLY USE AUTO RESOLVE AFTER YOU HAVE REVIEWED A NORMAL AUDIT
AND YOU HAVE ALREADY DETERMINED HOW MANY JOBS WILL BE SUBMITTED.
INCLUDE HISTORY RECORDS ===> NO (Y/N)
FORMAT REPORT FOR PRINTING ===> NO (Y/N)
AUDIT PARTICIPATING PACKAGE
AS A SIMPLE PACKAGE ===> NO (Y/N)
AS A PRIMARY PACKAGE ===> NO (Y/N)
BY DEPARTMENT NUMBER ===> NO (Y/N)
CROSS APPLICATION AUDIT ===> NO (Y/N) - (Simple package only)
===> //JD12341A JOB (HR00,XXXX,999,999),'CLAS724 AUDIT',_____________________
===> //*_____________________________________________________________________
===> //*_____________________________________________________________________
Set AUTO RESOLVE OF OUT-OF-SYNC ERRORS TO Y and ChangeMan will run the audit, then
check out needed components into the package, stage them, and re-compile the source programs.
Notes:
o Always run audit initially with this option turned off, so that errors can be evaluated prior to having
ChangeMan perform this function.
o Once an out-of-sync error has been fixed, audit will again have to be run before the package can
be frozen.

Chapter 9 Freeze and Approve
The Freeze Requirement

Once a package has had its components staged, changed, compiled (source-type components only),
promoted (optional), tested, and it has passed audit, it must be frozen. This is a quality step that is
inherent in ChangeMan tool that, once done, indicates that the packages contents will no longer be
modified and its components are ready for approval, software distribution, and baselining. The Freeze
action will change the status of the package to from DEV to FRZ.
Freezing a Package
To Freeze, select Option 2 Freeze, from the Primary Options Menu.
-------------------------------- FREEZE OPTIONS -------------------------------

OPTION ===>
1 Online - Freeze package online

2 Batch - Freeze package in batch
3 Selective - Selectively unfreeze/refreeze package components
4 Reset - Reset indicator after unsuccessful batch freeze
5 Re-Build - Re-submit install JCL build request
Always use Option 1 to initially Freeze the entire package. When complete, the Freeze Options panel is
redisplayed with a Package Frozen message in the upper-right hand corner, indicating that the action
was successful.
Note: It is not recommended to initially perform selective freezes. Selective freezes may be done to re-
freeze a component after it has been selectively unfrozen, due to a quality error found when doing higher
levels of testing.
-------------------------------- FREEZE OPTIONS --------------- PACKAGE FROZEN

OPTION ===>
1 Online - Freeze package online

2 Batch - Freeze package in batch
3 Selective - Selectively unfreeze/refreeze package components
4 Reset - Reset indicator after unsuccessful batch freeze
Applications that are using ChangeMan for software distribution will have their install JCL components
generated by ChangeMan during the freeze process; this may cause the freeze process to run a bit
slower. A TSO notification message is sent to the developer indicating the install JCL has been generated
prior to the Package Frozen panel notification shown above.

Unfreezing
Depending on how an application is configured, the developer or someone of a higher authority within the
application, can "unfreeze" a package in the event that a situation arises that necessitates that one or
more components within the package must again be changed and tested. This can be accomplished by
using the "Revert" option, or by selectively unfreezing individual components within the package.
Note: When this occurs, demotion of components in promotion libraries is normally optional.
Package Approval and AOTS Ticket Requirements

Package Approval is another inherent quality step in ChangeMan ZMF. It is basically the way an authority
figure within the application attests to the fact that all development and testing tasks have been
successfully completed, as called for within the applications documented SDLC.
Some application development processes call for more that one level of approval (i.e., approval to System
Test, then approval to Production), and this can be easily be built into the applications ChangeMan
configuration; however, ChangeMan, itself, only requires one level of approval.
Individual approver groups for planned and unplanned packages may be different. This is accomplished
by assigning different Controlling RACF Resources to different RACF Groups owned by the application.
It is also important to note that if a package is to be installed into production using either the CHGMAN-to-
ESP or the CHGMAN-to-Control-M interface, the application must first attach an AOTS ticket number to
their package in ChangeMan, prior to approving the package at the final (highest) level.
An AOTS ticket number is attached to a ChangeMan package by using CMNTOOLS, option 1;1 (Tracking
# Entry). The application name and package number must be entered on the panel. Then an AOTS
ticket number must be entered for each production site to which the package will install. An AOTS ticket
is NOT needed for test system install sites. An example of an AOTS ticket entry is shown below for
application SAMS, package number 000002:
AH00 -------- Tracking Number Update For SAMS000002 --------------------------

Primary Commands:
CAncel - Cancels any changes that were not "saved"
SAve - Validate and save changes, then return to this panel
END/PF3 - Validate and save changes, then exit the update process
VAlidate - Validate entries, then returns to this panel (NOT saved)
COpy - Copy the entries being displayed to a save area
PAste - Paste the saved entries onto the current screen
To update an existing row simply overtype the data.

I# - Insert A - AOTS Change Mgmt Ticket (No Validation Performed)
R# - Repeat B - AOTS Trouble Mgmt Ticket (No Validation Performed)
D - Delete
| | Number | Type | Site |-------------- Messages -----------------------|

__ 0000452449 A AL04P5__
__ 0000000000 _ AL04P4__
******************************* Bottom of data ********************************
In the example above, AL04P5 is the applications production install site. Notice that a ticket number has
been entered, along with TYPE=A, indicating that this is an AOTS change ticket. No ticket number was
entered for the AL04P4 site, which happens to be the applications test system install site.

Once the AOTS ticket number is entered, it is recorded in the ChangeMan database. It can be modified if
needed at any time prior to final approval of the package. Once the final approval of the package is done,
the AOTS ticket number will automatically appear in the email that is generated and sent to
EPAS/EMAS/Managed Ops informing them that a package is waiting to be installed.
Currently, there is no interface between ChangeMan and the AOTS Ticketing System that forces the
developer to enter an AOTS ticket via CMNTOOLS, prior to the final approval of the package being done.
It is up to the approver to ensure that a valid AOTS ticket has been entered for the package in
CMNTOOLS.
Approval Notifications
Freezing a package triggers ChangeMan to notify (via e-mail) designated approvers that is time to
approve the package. The designated approvers are identified in an approval list set up during the initial
configuration of the ChangeMan application. They are associated with the package type, planned and
unplanned, so different package types can have different people notified and approving. It should be
noted, however, that the people receiving the notifications are not the only ones who can approve a
package, as approval authority is granted in ChangeMan by RACF Group.
Approvals and Software Distribution and Baselining

When the final approval is applied to the package (the final and first approval will be one-in-the-same
when an application has only one approval level), one or more actions can be taken by ChangeMan
depending upon the Scheduler entered when the package was created. 1
MAN (Manual) 2 - the components in the package get installed and/or baselined as soon as
the approval is applied. No EPAS/EMAS intervention!
o One caveat..... the packages install date and time must not have already past; if it
has, the package install date/time will have to be changed before the approval can be
applied.
CMN (ChangeMan) 3 the packages components will be distributed to the production and
test sites associated with the package. Upon arrival, the components will be staged and then
await the install date and time specified in the package to arrive. Once it does arrive, the
components will be installed into the datasets assigned to their specific component type
without EPAS/EMAS intervention.4
o When all the packages install sites have all successfully been installed, the
components in the package will be baselined (Triggered off the final sites
confirmation that ChangeMan has successfully installed).
It should be noted that if software distribution is not turned on yet, and CMN
is the scheduler, the baseline ripple will occur at the date and time assigned
to the package, and no other actions will take place.
ESP (ESP applies to cS production sites only. By default the Test install site will use CMN
even though the package shows ESP.) - The packages components will be distributed to the
production and test sites associated with the package. Upon arrival, the components will be
1
Any reference to components being installed in production only applies when an applications component type(s) are marked as
Install in Production in the applications ChangeMan administration panel (A.B)
2
The use of the MAN scheduler is not acceptable to EPAS/EMAS and, therefore, may not be used when EPAS/EMAS is
responsible for the applications installations.
3
The use of the CMN scheduler is not acceptable to EPAS/EMAS and, therefore, may not be used when EPAS/EMAS is
responsible for the applications installations.
4
One installation dataset can be assigned to one component type per each install location in the applications administration panel
(A.P). ChangeMan does not distinguish between test and production install sites. It treats them all the similar manner.

staged and an ESP install event containing the install JCL jobs will be created in an ON
HOLD status. EPAS/EMAS will then be notified that install jobs are pending via email.
EPAS/EMAS will release the jobs according to the instructions provided by the application in
the AOTS record and/or OIG.
o When all the packages install sites have all successfully been installed (including
test), the components in the package will be baselined. This is triggered off the final
sites confirmation that ChangeMan has successfully installed the packages
components.
CTM (CTM applies to cT production sites only. By default the Test install site will use CMN
even though the package shows CTM.) - The packages components will be distributed to the
production and test sites associated with the package. Upon arrival, the components will be
staged and a Control-M install application containing the install JCL jobs will be created in an
ON HOLD status. EPAS/EMAS will then be notified that install jobs are pending via email.
EPAS/EMAS will release the jobs according to the instructions provided by the application in
the AOTS record and/or OIG.
o When all the packages install sites have all successfully been installed (including
test), the components in the package will be baselined. This is triggered off the final
sites confirmation that ChangeMan has successfully installed the packages
components.
How to Approve
The approvers must select Option 4 Approve from the Primary Option Menu in order to see the
following panel. By default, the last ChangeMan package worked on by the approver will be pre-filled
in the package ID field. The approver must be aware of this and change it, if necessary, before
proceeding.
COMMAND ===>

PACKAGE ID ===> CLAS002724 (Full name or pattern; blank for list)
APPROVAL ENTITY NAME ===> (Approvals for this security entity)
NOTIFIED USER ID ===> (Packages for which user was notified)
DEPARTMENT ===> (Department # or Scheduled Release)
SITE AFFECTED ===>
PACKAGE LEVEL ===> (1-Simple, 4-Participating)
PACKAGE TYPE ===> (Planned or Unplanned)
PACKAGE TIME SPAN ===> (Permanent or Temporary)
FROM INSTALL DATE ===> (YYYYMMDD)
TO INSTALL DATE ===> (YYYYMMDD)
FROM CREATION DATE ===> (YYYYMMDD)
TO CREATION DATE ===> (YYYYMMDD)
OTHER PARAMETERS ===> (Y/N)
Verify the package number, or change it, and hit Enter.
The next panel provides the approver with several options but, generally, only Option 1 Approve
should be used; however, the Query option can provide the approver with a quick access to package
information that may enhance their understanding of the reason for the change package.
Note: It is recommended to never use the reject option as it has ramifications that make it difficult to move
the package along in the future if a final decision to is made to go ahead with the approval at a later date.
Rather than rejecting the package, it is better for the approver to just do nothing and resolve issues that
might warrant a rejection off-line.

OPTION ===> 1
PACKAGE ID: CLAS002724 STATUS: FRZ INSTALL DATE: 20051205
1 Approve - Approve or reject a change package

2 Reasons - Display reasons a package was rejected
3 Query - Query change package
4 Reset - Reset approval in progress indicator
The approver will then be presented with a panel containing the approval line containing their title. Enter a
A, for Approve and hit Enter in order to have ChangeMan change in the packages status to APR. If
the application is using the software distribution feature in ChangeMan, when the approval takes place,
ChangeMan will distribute the software in the staging libraries to all install locations.
PACKAGE ID: CLAS002724 STATUS: FRZ INSTALL DATE: 20051205
APPROVER DESCRIPTION ID
DATE TIME SEQ LP STATUS
A TECHNICAL DIRECTOR APPROVER
10
Baseline Ripple
When the components in the package are baselined as described above, the baseline ripple occurs.
During this process, the previous version of a packages components residing in the baseline are pushed
back, and become the -1 (minus one) version, the minus one version becomes -2, and so on. Each
application can specify how many previous versions of each component type to retain, although there are
defaults established during the applications configuration that usually are sufficient for most applications.
At this point, the software development lifecycle has been completed. A review of the basic steps follows:
Create a new package

Add component to the package by:
o Checkout
o Stage from Development
Stage/Edit components
o Compile if necessary
Test components from package staging libraries
Promote package components for appropriate higher levels of testing
o Demote and make testing fixes as needed
Audit or re-audit the package
o Resolve out of synch conditions, if necessary
Freeze the Package
Final approve the package
Distribute the package to install sites
Install package contents
Baseline the packages contents.

Chapter 10 Query
What is Query?
The query functions allow the developer to view or look up information about a package or a component.
In addition, ChangeMan offers the ability to perform an "impact query" to determine which components
are affected when other components are changed. Query offers many options the following are just
some examples of the most useful features.
Package Query
All queries can be accessed from the Primary Option Menu by selecting Option Q. From here, one of
several types of queries can be accessed. The examples below cover 3 of the most useful ones:
AA00 --------------------------- QUERY OPTIONS -----------------------------------------------
OPTION ===> P
P Package - Query package information

C Component - Query component information
I Impact - Impact analysis of subordinate components
B BofM - Component bill of materials
A Approve - Approve In Limbo packages
Entering a P for Package Query provides a panel that allows access to package information. The
selection criteria entered will filter the results and the asterisk (*) can be used as a wild card to provide
selectable lists.
--------------------------- QUERY PACKAGE PARAMETERS --------------------------

COMMAND ===>

PACKAGE ID ===> CLAS* (Full name or pattern; blank for list,
or '*' to select all packages)
PACKAGE STATUS ===> (DEV, FRZ, DFZ, APR, REJ, DIS, INS,
BAS, BAK, OPN, CLO, TCC or DEL)
CREATOR'S TSO-ID ===> JD1234
DEPARTMENT ===> (Department # or Scheduled Release)
SITE AFFECTED ===>
PACKAGE LEVEL ===> (1-Simple, 2-Complex,
3-Super, 4-Participating)
PACKAGE TYPE ===> (Planned or Unplanned)
PACKAGE TIME SPAN ===> (Permanent or Temporary)
FROM INSTALL DATE ===> (YYYYMMDD)
TO INSTALL DATE ===> (YYYYMMDD)
FROM CREATION DATE ===> (YYYYMMDD)
TO CREATION DATE ===> (YYYYMMDD)
OTHER PARAMETERS ===> (Y/N)
Hitting Enter will search for all packages meeting the given criteria:
------------------------------ QUERY PACKAGE LIST ------------ Row 1 to 8 of 8
PACKAGE ID STA INSTALL LVL TYPE WORK REQUEST DEPT PROMOTE AUD CREATOR
__ CLAS002555 DEV 20040905 SMPL PLN/PRM JD1234
__ CLAS002556 DEV 20030805 SMPL PLN/PRM JD1234
__ CLAS002568 DEV 20030805 SMPL PLN/PRM 9876543 OCTS JD1234
Some package details are shown on the package list panel. In this example, package CLAS002568 is
currently in DEV (development) status, its install date is shown, and it's a simple package. Also, it had a
Work Request number entered of 9876543 and its Department is OCTS. And, it is not in any Promotion
library set, since that field is blank, and it has not been audited.
The status refers to the current state of the package. Some valid statuses are shown in the table below:
DEV Development status; package contents can be added to, deleted from, or changed.
FRZ Package has been frozen; notification sent to approvers.
APR Approval process has begun; at least one approver has approved.
DIS Package contents has been are sent to remote or local install sites (ChangeMan catcher
sites).
DIS-ACK The install sites have acknowledged back to the development site that the components
to be installed, along with the JCL to do the install, have been received.
INS Package has been installed in a least one site.
BAS Package contents have been baselined and the ripple has taken place.
Enter a SCM on any line to view more details:
------------------------ PACKAGE INFORMATION CATEGORIES ---- Row 1 to 18 of 21


CREATOR: JD1234 AUDIT RC:
_ General
_ Non-Source
_ Source
_ Source and Load Relationship
_ Component Userid Work List
_ Renames and Scratches
_ Approval List
_ Site/Install Date Information
_ Site Activities Date and Time
_ Custom Forms
_ Participating Package(s)
_ Status Start Date and Time
_ Revert Reasons
_ Backout Reasons
_ Promotion History
S Promotion Libraries
_ Development Staging Libraries
_ Production Staging Libraries
All of these options are fully explained in the ChangeMan 5.6.1 Users Guide. In essence, each package
has basic properties as well as a history for example, when it was frozen and when it was
promoted/demoted.
Selecting Source or Non-Source will show a list of respective components in the package. In this
example, the Promotion Libraries were chosen to be looked at and, therefore a list of the valid
promotion levels is displayed.
--------------------- CLAS/SLTESTP - PROMOTION LEVELS -------- Row 1 to 3 of 3
PACKAGE ID: CLAS002555 CREATOR: JJ1234 STATUS: DEV INSTALL DATE: 20040905
NICKNAME ENTITY LEVEL PROCEDURE

_ UNIT CLAS 10 CMN$$PRM
S CHAIN CLAS 20 CMN$$PRM
_ SYSTEM CLAS 30 CMN$$PRM
Selecting a promotion level shows the actual library dataset names (on either the development or remote
system) where components would be copied if promoted to that level:
Note: On local promotes (those staying on the applications development complex), the shadow library
name is the same as the promotion library. When remote promote is being used, both the shadow and the
promotion library names will be different in order to designate where the promoted components were
actually sent.
------------------ CLAS/SLTESTP - PROMOTION LIBRARIES ------ Row 1 to 3 of 5

PROMOTION NAME: CHAIN LEVEL: 11
PACKAGE ID: CLAS002555 CREATOR: JJ1234 STATUS: DEV INSTALL DATE: 20040905
SYSLIB
LIB EXCLUDE TARGET LIBRARIES
JCL Y CMN.CLAS.PRMO.CHAIN.JCL_______________________ Shadow
CMN.CLAS.PRMO.CHAIN.JCL_______________________ Library 1
____________________________________________ Library 2
____________________________________________ Library 3
PRC Y CMN.CLAS.PRMO.CHAIN.PRC_______________________ Shadow
CMN.CLAS.PRMO.CHAIN.PRC_______________________ Library 1
____________________________________________ Library 2
____________________________________________ Library 3
LOD Y CMN.CLAS.PRMO.CHAIN.LOD_______________________ Shadow
CMN.CLAS.PRMO.CHAIN.LOD_______________________ Library 1
____________________________________________ Library 2
____________________________________________ Library 3
Many other functions and attributes are available with the Package Query feature. Follow this link to see
all the options. ChangeMan 5.6.1 Users Guide.
Component Query
A component query will provide information about who checked out a component and what package it is
in, or where it was promoted to.
AA00 --------------------------- QUERY OPTIONS -----------------------------------------------
OPTION ===> C
P Package - Query package information

C Component - Query component information
I Impact - Impact analysis of subordinate components
B BofM - Component bill of materials
A Approve - Approve In Limbo packages

Enter a C is the Query menu to display the Component Query panel:
-------------------------- QUERY COMPONENT PARAMETERS -------------------------

COMMAND ===>

COMPONENT NAME ===> CLSPGM05 (Full name or pattern)
COMPONENT TYPE ===> SRC (Full library type or pattern)
APPLICATION ===> CLAS
PACKAGE ID ===>
PROCEDURE NAME ===>
TSOID ===>
DISPLAY MODE ===> SHORT (S-Short, L-Long)
CHECKOUT/STAGING
FROM DATE ===> (YYYYMMDD)
TO DATE ===> (YYYYMMDD)
Enter the component name, type, and application name to see all current packages containing that
component. Changing the Display Mode field to Long will also show any packages that contained that
component that have been installed into baseline as well as those that have been aged off the system
(Note: Package retention is user definable during application configuration).
------------------------------ CLSPGM05.SRC HISTORY ---------- Row 1 to 8 of 8

Press ENTER to continue; Enter END command to exit.
PACKAGE ID STA PROMOTION VV.MM LAST ACTION SIZE SETSSI ID

_ CLAS002724 DIS 13.01 2005/06/15 07:00 60 557D7731 JJ1234
_ CLAS002708 DEV 0 STAGING 12.02 2005/01/11 11:22 60 54B3AE55 T04464
Notice that the promotion level for package CLAS002708 shows STAGING. This indicates that the
package contents were promoted but subsequently demoted. Enter a S to display the details about the
components in the selected package.
Impact Analysis
Entering an I on the Query menu will invoke an impact analysis. An impact analysis is useful to find out
which components are affected when a subordinate component is changed.
------------------ IMPACT ANALYSIS OF SUBORDINATE COMPONENTS ------------------

COMMAND ===>
SPECIFY SEARCH CRITERIA:
Subordinate component name ===> CPYBK03

Library type ===> CPY
Application ===> CLAS
Type of relationship ===> COPYBOOK
SPECIFY RESULTS FILTER CRITERIA:
Superior component name ===>

Library type ===>
Application ===>

Subordinate Component Name (the name of the component being changed), Library type, and
Application Name, and the type of relationship to be checked. Hit Enter to have ChangeMan provide the
relationship information as follows based on the relationship entered:
Relationship Information Provided

COPYBOOK lists programs affected by changing this copybook
SUBROUTINE lists programs that statically call this subroutine
JCL-PROCEDURE lists JCL which invokes this procedure via EXEC
PGM NAME/SYMBOL lists JCL which invokes this program via EXEC PGM=
DSN NAME/SYMBOL lists JCL which references this dataset via a DD DSN statement
Filter the results further by filling in the fields at the bottom of the panel. The example below shows the list
of components impacted by a change to CPYBK03:
-------------------- Impact Analysis Results Selection List Row 1 to 9 of 9

List of components which reference

Appl:Type CLAS : CPY Name CPYBK03
with a relationship of COPYBOOK
which satisfy these criteria
Appl:Type * : * Name *
Component Name Found in Appl:Libtype (common baselines)

_ CLSPGM01 CLAS:SRC
_ CLSPGM02 CLAS:SRC
_ CLSPGM03 CLAS:SRC
_ CLSPGM04 CLAS:SRC
_ CLSPGM05 CLAS:SRC
_ CLSPGM06 CLAS:SRC
_ CLSPGM07 CLAS:SRC
_ CLSPGM08 CLAS:SRC
_ CLSPGM99 CLAS:SRC
Chapter 11 Updating a Package
When a package is initially created a basic set of characteristics (i.e., Installation Date, Time) are
assigned using required panels. At some point during the SDLC it may become necessary to change one
or more of these characteristics. For example, a new project may have been added to the release whose
components are in the package and a description update is required. Or, if a complex package is being
used, another participating package may need to be added.
Select Option 2 Update on the Build menu to make these changes. The Update Package
Information panel will then be displayed. Select the option on it that meets the needs of the pending
change.
Note: Each option selected will display a different panel that is similar to those used when the package
was first created. Within them, the current settings will be displayed and can be keyed over to make the
needed changes. Be aware that packages can only be updated when they are in DEV status, and that
there are a few fields (i.e., Package Level), cannot be modified once the package is created.
AA00 -------------------- UPDATE: PACKAGE INFORMATION ---------

OPTION ===>
PACKAGE ID ===> CLAS002754 PX=PGN0
1 Control - Update package control information

2 General - Update general description
3 Instruction - Update installation instructions
4 Dependencies - Update job scheduling dependencies
5 Affected Apps - Update affected applications
6 Complex/Super - Update cmpx/supr package information
7 Install Dates - Update install date and site information
8 Complex/Super - Change complex/super package to CLO status
9 Complex/Super - Change complex/super package to OPN status
D DB2 Information - Update DB2 package information
E User Information- Change package user information
I IMS Information - Update IMS package information
R Release Info. - Change package Release information

Chapter 12 Deleting or Renaming a
Baseline Component
Baseline library components may be deleted or renamed. These two change functions are handled in a
similar manner as other change functions previously described, by doing it in a package. The package
must contain the "commands" to delete or rename the targeted baseline component. When the package
gets approved and baselined, the changes occur in the baseline,
Enter the Build Options menu, then select Option 4 Utility.
----------------------- UTILITY: RENAME/SCRATCH OPTIONS -----------------------

OPTION ===>
1 Baseline - Select baseline components to scratch or rename

2 Package - Process scratch or rename requests in package
Select Option 1.
------------------------- UTILITY: BASELINE SELECTIONS ------------------------

OPTION ===>
R - Rename a component
S - Scratch a component
blank - Display component selection list
LIBRARY TYPE ===> (Blank for list)

COMPONENT ===> (Blank or pattern for list)
NEW NAME ===> (Required for option R)
* The following options are available from a component selection list:

L - Locate component R - Rename component S - Scratch component
B - Browse component H - Component History I - Short History
Enter the desired action (scratch delete or rename) on the command line along with the required
information when remaining is selected, hit Enter, and one of the following messages will be displayed in
the upper-right hand corner of the panel.
o NO RELATED SCRATCHES in the case of Scratches

o RENAME INFO. SAVED in the case of Renames.
These messages indicate that the scratch or rename commands were been added to the package.
The pending Rename or Scratch commands can be viewed in the Utility: Rename/Scratch Options panel
by entering Option 2. Pending actions (not finalized until the package is approved) can be deleted by
entering a D on the desired line.
---------------------------- UTILITY: CLAS002725 LIST -------- Row 1 to 1 of 1

REQ NAME RENAME TYPE CHANGED ID STATUS FUNCTION
_ SCR CLSPGM05 SRC 2005/06/15 11:04 CP1951 ACTIVE
_ REN FA RENAMEFA CTC 2005/06/15 10:56 JJ1234 ACTIVE
Note: The scratch and rename functions will also impact the production install environments if the
application is using ChangeMan for software distribution.

ChangeMan Basic Training

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

ChangeMan Basic Training

Caricato da

Copyright:

Formati disponibili

ChangeMan ZMF Basic Training Guide 1

ChangeMan ZMF Basic Training

Notice: This document is an unpublished work protected by the United States

2005-2012 AT&T Intellectual Property. All rights reserved.

Revised: December 13, 2012

Proprietary Information: Not for use/disclosure

Proprietary Information: Not for use/disclosure

AUDITS WHEN TO RUN..........................................................................................................................................45

Chapter 12 Deleting or Renaming a Baseline Component........................................................................................62

Proprietary Information: Not for use/disclosure

About This Guide

Full documentation on ChangeMan can be found on the ChangeMan website at:

Proprietary Information: Not for use/disclosure

Can Users Play Around in ChangeMan?

Where Do Develops Do Their Work When They Have a Real Application?

SLT1 - AA00 SF01 - AAT3 SLT2 - CQ90 SL04 - BSYS

Proprietary Information: Not for use/disclosure

Proprietary Information: Not for use/disclosure

Chapter 2 Getting Started

1 Build - Create, update and review package data

Press ENTER to process; enter END command to exit.

Understanding Library Structure

Proprietary Information: Not for use/disclosure

o Baseline Libraries library naming convention format follows:

o Package Staging Libraries library naming convention format follows:

CMN.appl.STG@.#nnnnnn.typ where CMN is a constant standing for ChangeMan, appl is

Menu Options View Utilities Compilers Help

DSLIST - Data Sets Matching CMN.CLAS.BAS*.* Row 1 of 40

Command - Enter "/" to select action Message Volume

Proprietary Information: Not for use/disclosure

DSLIST - Data Sets Matching CMN.CLAS.BAS*.* Row 1 of 40

Command - Enter "/" to select action Message Volume

Menu Functions Confirm Utilities Help

BROWSE CMN.CLAS.BASO.JCL Row 00001 of 00005

Menu Utilities Compilers Help

BROWSE CMN.CLAS.BASO.JCL(IEBCOPY3) - 01.00 Line 00000000 Col 001 080

Proprietary Information: Not for use/disclosure

Package Staging Libraries

Menu Options View Utilities Compilers Help

DSLIST - Data Sets Matching CMN.CLAS.STG*.#002724.* Row 1 of 7

Command - Enter "/" to select action Message Volume

All CMN HLQ Libraries

Development Steps Summary

Proprietary Information: Not for use/disclosure

Create a new package

ChangeMan ZMF Customizations

Proprietary Information: Not for use/disclosure

Chapter 3 Creating a Package

1 Build - Create, update and review package data

Press ENTER to process; enter END command to exit.

-------------------------------- BUILD OPTIONS -------------------------------

0 Dates - Display the installation calendar

Press ENTER to process; Enter END command to exit.

Proprietary Information: Not for use/disclosure

Setting the Package Options

------------------------- CREATE: CREATE A NEW PACKAGE ------------------------

APPLICATION ===> CLAS (Blank or pattern for list)

Proprietary Information: Not for use/disclosure

Participating A package related to a complex package for purposes of

Hit Enter to display the Package Description panel:

------------------------- CREATE: PACKAGE DESCRIPTION ------ Row 1 to 12 of 12

Press ENTER or END to continue or type CANCEL to exit.

(minimum one line, maximum 46 lines)

Hit Enter to display the Installation Instructions panel:

DSLIST - Data Sets Matching CMN.CLAS.BAS. Row 1 of 40

DSLIST - Data Sets Matching CMN.CLAS.BAS. Row 1 of 40

DSLIST - Data Sets Matching CMN.CLAS.STG.#002724. Row 1 of 7