Ovum ChangeManZMF

ChangeMan ZMF - Serena Software
Ian Wesley: ian.wesley@ovum.com

Clive Burrows: clive.burrows@ovum.com
May 2004
Expert advice
CHANGEMAN ZMF - SERENA SOFTWARE
1
At a glance
Developer
Serena Software, San Mateo, California, USA
www.serena.com
Version
ChangeMan ZMF version 5.3, ZDD version 3.2, Merge and Reconcile (M+R) version
4.1.0, TeamTrack 6.0 and Enterprise Change Portal (ECP) version 3.2
Evaluation summary
Key points
• IBM mainframe product with variants tuned to different environments.
ChangeMan ZDD provides a Windows interface to mainframe functionality
• Data held in partitioned datasets (PDSs), extended partitioned datasets (PDSEs),
CA Panvalet and/or CA-Librarian. Control data held in VSAM and DB2
• ChangeMan ZMF is fully XML enabled with XML integrations with ChangeMan
ZDD and ChangeMan ECP
Strengths
• Good extended lifecycle support with TeamTrack (for application lifecycle process
automation) and StarTool DA (for integrated dump analysis)
• Good management of production integrity
• Good merge tool including library merge
Points to watch
• Poor user interface – but matches most mainframe interactive system productivity
(ISPF)/PDF-based facilities
• M+R is at extra cost, as with competing mainframe products
• Poor documentation
© Ovum 2005. Unauthorised reproduction prohibited

2
Ratings
1 2 3 4 5 6 7 8 9 10
Team support
Replicated repositories Not relevant for mainframe CM tools
Configuration management
Change management
Build and release support
Process management
Project support
Usability
Administration
Price guide
ChangeMan ZMF pricing is MIPS-based and starts at $42,750. ChangeMan ZDD is
priced per MIPS, starting at $15,000. ChangeMan M+R pricing is MIPS-based,
starting at $22,000. ChangeMan ECP pricing includes seat and MIPS-based
components, with ten seats priced at $500 and the MIPS component starting at
$15,000.
Components
The principal ChangeMan ZMF product offerings are:
• ChangeMan ZMF Server, which is evaluated here
• ChangeMan ZDD, which simulates a network file system to provide access from
Windows 2000, XP or NT 4.0 to ChangeMan ZMF components, datasets and jobs
on a z/OS or OS/390 system. ChangeMan ZMF components, datasets and job
output are accessed as though they were local files or files on a Windows
network
• ChangeMan M+R, for integrating new releases of vendor application software
with in-house customisations and for integrating concurrently developed in-house
software
• ChangeMan ECP, which is used to web-enable the change management
process. Managers are able to review and approve changes in both ChangeMan
ZMF and ChangeMan DS, allowing for centrally managed lifecycles and co-
ordinated deployment of multiplatform applications

3
• ChangeMan ERO (Enterprise Release Option), which provides release

management for large application changes with multiple versions of the same
source in different releases
• ChangeMan ZMF Online Forms Manager option, which extends ChangeMan
ZMF to manage online versions of business forms associated with change-related
business processes
• ChangeMan ZMF DB2 option, for management of DB2 application objects such
as plans, packages, DBRMs, stored procedures, user-defined functions and DB2
triggers. This option also allows the creation of multiple logical DB2 testing
environments in a single physical DB2 system
• ChangeMan ZMF IMS option, for management of IMS application objects,
including MFSs, PSBs, DCBs and ACBs. This option also allows the creation of
multiple logical IMS testing environments in a single physical IMS system
• ChangeMan ZMF Info/Man option, for integrating ChangeMan ZMF with IBM
Tivoli’s Information change-tracking product
• ChangeMan ZMF APS option, for integrating Micro Focus’s APS with
ChangeMan ZMF
• extended lifecycle support is provided with TeamTrack, which provides
application lifecycle process automation. TeamTrack IDs can be associated with
ChangeMan ZMF. TeamTrack also provides change management and problem
tracking.
• StarTool DA has the ability to make an XML call to ChangeMan ZMF to associate
source code to aid production abend dump analysis.
Terminology
Change package
The means by which a new application, or change to an existing application, is

described, scheduled, prepared and implemented into production. It may consist of
one or more library components. Each package is identified by a unique change
package ID consisting of the application mnemonic and a sequential six-digit number
(for example, PAYR000001). All changes are referenced in ChangeMan ZMF’s
control file, Package Master, which is a VSAM file that holds all significant data about
current and previous change packages.
The ChangeMan ZMF Library Environment
ChangeMan ZMF manages the transition from development to production libraries by

using staging libraries, which are specific to each change package. Existing
production components are copied into the development environment, where they
can be modified and tested. The ChangeMan ZMF staging libraries can be used for
both editing and testing. If private libraries are used during editing, components will
be copied into the staging libraries before testing.

4
Production libraries may be the same as baseline libraries, depending on how

ChangeMan ZMF is configured. The baseline libraries contain a current production
version (baseline 0) and up to 999 previous versions of the production component
(baseline –1, –2 and so on). When a new production component is installed, the
baseline libraries are ‘rippled’. This means that the new version becomes the current
version, and what was the current version becomes the –1 version and so on. In
addition, versions are tracked when baseline libraries are updated, and users can
also choose to have each work-in-process version saved.

5
Ovum’s verdict
In a nutshell
ChangeMan ZMF has an established track record as a mainframe CM system.
Lifecycle processes are managed well, as is the safe migration of changes into the
production environment.
ChangeMan M+R is an essential add-on to ChangeMan ZMF. In a market where

parallel development is now an essential requirement, Serena and other mainframe
CM vendors should no longer be charging extra for supporting this functionality.
Verdict
ChangeMan functionality for mainframes centres on ChangeMan ZMF, ChangeMan
M+R (Merge and Reconcile) and ChangeMan ZDD. These products are likely to be
essential for most users. Access to mainframe functionality and data from a Windows
environment is supported via ChangeMan ZDD and Serena XML Services, but this
does not support web access. Web access to mainframe information is only
supported for changes through ChangeMan Enterprise Change Portal (ECP), but this
has the advantage that it can access linked multiple ZMF repositories and multiple
ChangeMan DS repositories. This link feature is termed an Enterprise Change
Package.
Users selecting ChangeMan ZMF will need to assess the cost of the additional
products against the benefits they provide.
ChangeMan ZMF uses the concept of a change package to move changes through
their lifecycle. After a change package is created, components are checked out from
the ChangeMan ZMF baseline libraries and placed in a development library, so that
modifications can be performed. These libraries are where source code is compiled
and load modules are created, using standard ISPF/PDF file tailoring of skeletons.
ChangeMan ZMF establishes and monitors the relationship between source and all
generated components such as DB2 DBRM, Object Decks and Executables.
Change packages can be frozen either during the development phase or in a quality
assurance phase, depending on local development standards. ChangeMan ZMF then
supports an online approval process to obtain the necessary electronic ‘signatures’
for further migration of the changes into production use. ChangeMan ZMF also
supports an emergency process for getting urgent changes into production.
Extended lifecycle support and change & issue management is provided with
TeamTrack, which provides application lifecycle process automation. TeamTrack IDs
can be associated with ChangeMan ZMF.
TeamTrack maps, tracks and enforces business processes down to the task level,
and thereby allows users to control and automate business processes, manage

6
issues throughout the lifecycle of their projects, and facilitate collaboration among all
team members.
TeamTrack has a good graphical workflow editor that allows process managers to
map every step in the workflow of their projects without needing a database
administrator or developer.
ChangeMan ZMF supports concurrent check-out of components for parallel

development, and will ensure that each user of a version is aware of the actions of
other users. ChangeMan M+R is able to automate the merging of program versions,
each program version consisting of many individual source components. ChangeMan
M+R is able to reconcile up to eight different versions of a program, identifying
differences and conflicts in multiple versions of the same component, and assisting in
the resolution of any conflicts.
ChangeMan M+R has the capability to merge libraries consisting of thousands of files
and can analyse the semantics of code (in some languages) and thus ignore
cosmetic differences that have no impact on the eventual executable code. A
complexity metric is also generated, which allows users to assign the most
experienced staff to the most complex merge resolution tasks.
The ChangeMan ZMF user interface is the familiar, but poor, IBM ISPF Panel
interface, with a good choice of default options and easily identifiable mandatory
fields. The options displayed on menus are tailored to the access permissions of each
user. Serena provides additional interfaces through ChangeMan ECP (a web-based
portal that provides managers with cross-platform views) and ChangeMan ZDD,
which integrates desktop IDEs with the ChangeMan ZMF environment.
When to use
ChangeMan ZMF is a strong contender for many mainframe sites, particularly those
requiring a high degree of integrity for software changes to the production
environment. The change package approach and lifecycle process provides good
control over changes. Development and production standards are well supported, and
ChangeMan ZMF has the flexibility to support emergency procedures.
Support for maintaining the integrity of production sites as approved change

packages are released (including geographically remote sites) is very good.
We recommend that all ChangeMan ZMF prospects ensure that TeamTrack and
ChangeMan M+R is also acquired. Other products associated with ChangeMan ZMF
can be considered separately, based on their merits in relation to costs.

7
Product overview
The architecture for ChangeMan ZMF and ZDD is shown in Figure 1.
Figure 1 ChangeMan ZMF and ZDD architecture
SERNET Z/OS server
ZMF SubTask
Serena XML Services
IBM TCP/IP
Clients
Windows XP
Windows 2000
Windows NT 4.0
Source: Serena Software
ChangeMan ZDD allows desktop programmers to edit mainframe components from

their IDEs without the need for mass data transfers, thereby maintaining the integrity
of mainframe software assets during desktop development (software components
never leave the mainframe).
The ChangeMan ZMF architecture is centred on the change package (a concept that
Serena claims to have pioneered) and the management and control of all activities
associated with putting that change package into production use. A change package
is a grouping of all the components required to implement a software change into
production (source, copybook, load, JCL, control cards, compiling procedures
documentation and other components).
Many ChangeMan ZMF features are directed at maintaining the integrity of production
systems and the enforcement of the user’s standards for change. However,
pragmatic features that recognise the flexibility needed to deal with real-world

8
emergencies temper this. Changes cannot be migrated into production without

ChangeMan ZMF documenting the event and ensuring that the migration is
authorised – even if ChangeMan ZMF has to follow emergency procedures for
emergency situations.
Examples of features relating to integrity and control over the production environment
include the following:
• ChangeMan ZMF has an auditing function that reviews all changes in a change
package to verify accuracy and completeness. Component regression errors are
found, along with build sequencing problems – for example, when copybooks
have been changed after the programs that use them have been compiled
• when a change package is presented for migration into production, ChangeMan
ZMF processes the content of the change package to calculate a ‘token’
associated with that change package. After all approvals have been obtained and
the change package is ready for production use, ChangeMan ZMF re-calculates
the token for the change package. If the newly calculated token is not the same
as the original, the change package is not applied to the production system
• when developers are working on a change, they are free to use their preferred
tools and methods. When this development work is complete and the change
package is presented for test and approval, ChangeMan ZMF will rebuild all
executables using the standard site processes (which can be different for test and
production libraries)
• ChangeMan ZMF uses the site’s security system, and can assign additional
access restrictions to items under its control
• ChangeMan ZMF can install a change package at a remote site, with controls on
the time of installation and (user-defined) limits on the number of change
packages installed during any time period.
• enterprise change packages (managed by ChangeMan ECP) provide the ability
to link change packages on any two ChangeMan systems throughout the
lifecycle. This capability enables changes to enterprise applications across
multiple platforms, from mainframe to the Web, to be co-ordinated from a single
point
• staging versions allows ChangeMan ZMF to maintain an unlimited number of
incremental versions of components under development within a change
package. Developers can roll back to previous development versions, as well as
previously released versions
• consolidated promotion combines the previous local and remote promotion into a
consolidated single facility to move change packages within testing environments
on local as well as networked hosts and servers
• ChangeMan ZDD provides access to ChangeMan ZMF from Windows NT, 2000
or XP. Components, datasets and job output appear as though they were local
PC files or files on a Windows network. ChangeMan ZDD provides direct access
to ChangeMan ZMF-controlled software assets from a wide range of desktop
IDEs.

9
ChangeMan ZMF is flexible about the way configured components are managed, and
supports PDSs, CA Librarian files or CA Panvalet files. It automatically stores
previous versions of components as full copies (inherent for load modules), or using a
reverse base/delta technique known as ‘stacked reverse delta’.
Figure 2 shows the platform and interface aspects of ChangeMan ZMF and related
products.

10
Figure 2 Platform and interface aspects

ChangeMan ZMF TeamTrack
Server z/OS Windows NT Server 4.0, SP 6A; Windows
2000 Server; Windows 2000 Advanced
Server
Windows Server 2003 family
OS/390
Client Mainframe panel interface Windows NT Server 4.0, SP 6A; Windows
2000 Server; Windows 2000 Advanced
Server
Windows Server 2003 family
Windows XP Professional
Any IDE with Windows NT, XP and
2000 for ChangeMan ZDD
Database Metadata is stored in VSAM; impact Microsoft Access 97, 2000 or 2002 (drivers
analysis is stored in VSAM or DB2 provided)
SQL Server, version 7 or 2000
IBM DB2 Universal Database, version 8.1
Oracle, versions 8i or 9i up to version 9.2
Components can be stored in PDSs,
PDSEs, CA Panvalet and/or
CA Librarian
Network SNA and TCP/IP TCP/IP
Web server Any Windows-based web server for Microsoft IIS, version 4.0, 5.0 or 6.0
ChangeMan ECP. Apache is
Sun Java System Web Server
distributed with ChangeMan ECP
Sun ONE, version 6.0
Browser Microsoft Internet Explorer for Microsoft Internet Explorer, version 5.01 SP
ChangeMan ECP 2 to version 6
Netscape Communicator, versions 4.6 to
4.7, 6.2, 7, and 7.1
Apple Safari 1.0 (on Macintosh)
Mozilla 1.3.1
Netscape Navigator for ChangeMan
ECP
Handheld Most browsers available on handheld
devices computers and PDAs can be used to access
TeamTrack
Tested configurations include Pocket
Internet Explorer on PocketPC, Eudora Web
on PalmOS, and AvantGo on both platforms
In addition, TeamTrack may function

11
correctly on non-tested browsers and mobile

devices.†
† Note that TeamTrack does not yet deliver WAP

12
Changes
Since last evaluation
Recent enhancements include the following:
• integration of ChangeMan ZMF with TeamTrack
• Enterprise Release Option (ERO) provides a way to manage many packages
from many applications in a series of dynamic but dependent releases. This
option contains parameters to offer the flexibility to set up release development,
testing, and installation the way that fits each business’s needs, and extends the
ChangeMan ZMF audit function to protect the integrity of the production
• ChangeMan ZMF now includes documented XML services for customer use to
replace remote procedure calls (RPCs) and the batch APIs. Customers can
access services through well-formed XML pages, or can use the Cobol, PL/I and
assembler-based copybooks and sub-routines to call services
• DB2 Option now provides special management of DB2 stored procedures,
triggers and user-defined functions. Processing for these DB2 objects is defined
in new skeletons, a new Selectable Option parameter on the Library Types
definition panel, and new sub-type options on a panel under the DB2 Logical
Subsystems panel
• user option enhancements enable users to select a Change Package List that
contains only packages that are still in the development and testing phases of the
package lifecycle. A new selection option for Package Status includes packages
in development and freeze status. When a Complex package is selected, all of
the participating packages are also displayed
• validation of entries in the Install Date/Time field is enhanced to consider
timezone differences for remote production sites. A time difference parameter can
be set in each site definition so a package Install Date/Time can be entered that
is valid for a production site, but has already passed at the development site
• Serena further expanded the ability to provide program-to-program
communication through the introduction of XML services. The XML services
interface provides a standardised method to retrieve and display data from the
task started by ChangeMan. Used in combination with ChangeMan ZDD, XML
services permit reporting and manipulation of information through standard
interfaces, such as Microsoft Excel, web browsers (for example, Netscape and
Internet Explorer), Microsoft Project, Crystal Reports and Microsoft Access.
• integration of the Serena StarTool products with the ChangeMan products. Star
Tool DA and StarTool FDM are now ChangeMan ZMF-aware and can be used to
view changes to both source and files.

13
Future enhancements
Planned enhancements include:
• several initiatives to expand the focus and process of enterprise change
management (ECM). The most prominent of these is the Serena Application
Framework for Enterprises (SAFE) announced in September 2003. SAFE will
provide a process-centric framework surrounding the application lifecycle,
providing the context for application change
• ERO is being extended to provide a more in-depth and flexible process for
managing testing environments, including managing complex DB2 Bind and IMS
Gen processes
• Serena XML Services will be enhanced to create more services for managing
ERO and standard promotion testing environments
• a new release of the Micro Focus APS Option will integrate with the latest APS
version and provide automation opportunities for ChangeMan ZMF customers
• new REXX-based reporting using Serena XML Services. These reports will
replace and expand on reports currently available in SAS and Assembler
• a new release of the ChangeMan ZMF InfoMan Option to allow multihost
communication between ChangeMan ZMF and InfoMan.

14
Company background
History
Serena Software was founded in 1980 and became a publicly quoted company in
February 1999. In 1988, it launched its core product, Change Man (now known as
ChangeMan ZMF).
Apart from the various ChangeMan products covered in this evaluation, other
products available from Serena include:
• Comparex – this automates file comparison and system testing. Comparex can
compare source, loads and any type of file to any other, as in IMS to DB2. Fields
or records can be compared even if they are in different formats. For example,
DB2 Row Date Fields can be compared with IMS Segment Date Fields, even
though the storage format is different
• ChangeMan SSM – System Software Manager. This improves system software
reliability and accelerates disaster-recovery efforts for maximum system software
uptime. Detects, tracks, synchronises and provides audit trails for software
changes across multiple systems or logical partitions (LPARS)
• StarTool FDM – File and Data Management. This enables development and
editing of text and databases for a variety of MVS data types. It provides data
management capabilities, such as dataset space allocation and file recovery
• StarTool DA – DA Batch and DA CICS. This provides dump management, with
analysis and diagnostic capabilities for system and application abends
• StarTool APM – Application Performance Manager. This provides both realtime
and historical performance statistics to pinpoint areas within an application that
need to be tuned to deliver the desired response and turnaround time
• StarTool IOO – I/O Optimiser. This uses industry-accepted rules to automatically
tune I/O operations
• StarTool RB VSAM – Record Backup for VSAM. This reduces the time and
resources needed to back up VSAM data by detecting changes at the record
level.
In June 1999, Serena completed its acquisition of Diamond Optimum Systems to

extend its range of CM support to Unix and NT platforms. This product was originally
named eChange Man by Serena, but is now called ChangeMan DS and is evaluated
separately in this series.
In May 2003, Serena acquired TeamShare for $18 million. TeamShare is best known
for its TeamTrack workflow engine, which is centred on defect and issue
management. Previously, in December 2002, Serena and TeamShare jointly
announced integration between TeamTrack and ChangeMan DS

15
In May 2004 Serena finalised the acquisition of Merant, adding PVCS Professional
and Dimensions to its CM portfolio. The acquisition was a cash and share deal that
valued Merant at $380 million. This acquisition makes Serena the second largest
provider of enterprise change management (or ECM) software solutions with a
combined installed base of over 15,000 customers.
Commercial
Serena’s total revenues in calendar 2003 (fiscal 2004 for Serena, whose fiscal year
runs from 1 February to 31 January) were $105.5 million compared with $95.8 million
in 2002. A summary of Serena’s quarterly revenues is shown in Figure 3.
Figure 3 Serena’s quarterly revenues
$ million
35
30
Revenue
Profit
25
20
15
10
0
Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4
1998 1999 2000 2001 2002 2003
Calendar years
The quarterly drop in revenues in 2001 was common to many vendors and is due to
adverse trading conditions in the US during that period. There are now signs of a
recovery in growth.

16
Serena’s revenues in calendar 2003 (fiscal 2004) were derived from:

• new licences – 43.1%
• maintenance – 48.3%
• services – 8.6%.
Geographically, 71% of Serena’s revenues are derived from North America with the
remainder coming from European operations.
Serena’s headquarters are in San Mateo, California. It has international offices in the
Benelux region, Canada, France, Germany and the UK.
Serena has more than 500 ChangeMan ZMF customers worldwide, with tens of
thousands of users. ChangeMan ZMF customers include American Express, Bank of
America, Caterpillar, Citigroup, Credit Suisse, Duke Energy, Ford Motor Company,
ING, SBC Communications and UBS.
Character and direction

Serena aims to provide a total solution to the problem of locating, fixing and
managing changes to application and system software. It is a technically driven
company, strongly focused on change management and productivity tools for IBM
mainframe users. Its products are used in more than 3,600 data centres worldwide,
including many financial institutions, high-tech companies and energy companies.
Serena specialises in enterprise change management (ECM), which it defines as the

infrastructure and process of managing change to all aspects of a company’s
business application environment. The Serena vision is to provide management
across mainframe OS/390, z/OS, Unix, Linux, Windows, AS/400, HP NonStop
(Tandem) and HP MPE. Serena intends to converge ChangeMan ZMF and
ChangeMan DS to provide an integrated enterprise-wide management solution for the
management of e-business applications.
Serena is focused on CM integration across platforms with links between applications

on distributed systems and applications on mainframe systems. Serena ChangeMan
ECP provides a web interface to allow central management of multiplatform lifecycles
and co-ordinated development and deployment of enterprise applications.
ChangeMan ECP provides a single point from which enterprise change management
can be enforced.
Serena is working on several initiatives to expand the focus and process of ECM. The
most prominent of these is the Serena Application Framework for Enterprises (SAFE),
announced in September 2003.
SAFE provides a process-centric framework surrounding the application lifecycle,

providing the context for application change.
This framework enhances Application Lifecycle Management (ALM) by enabling

companies to manage application design, development, quality assurance,

17
deployment and support across platforms and across processes. SAFE will enable
cross-process integration, linking the people, tools and assets involved throughout the
application lifecycle.
Serena claims that SAFE extends the application lifecycle and promotes seamless
collaboration across various business and technical roles and responsibilities, helping
an organisation to run more smoothly. With SAFE, customers will be able to reduce
costs and increase enterprise efficiency.
Following the acquisition of TeamShare Serena has adopted TeamTrack as the

change management system of choice and is gradually phasing out the ALM product.
The acquisition of Merant means that Serena needs to communicate the role of each
of its four SCLM products to the market. The role of Dimensions’ agent to support
mainframe users is not in conflict with ChangeMan ZMF as Serena has adopted a
similar agent technology for ChangeMan DS.

18
Product evaluation
Team support
1 2 3 4 5 6 7 8 9 10
Good, basic versioning and workspace management. Merge tool for supporting
parallel development is part of Merge and Reconcile (M+R) and is priced separately.
M+R has strong features for processing multiple files (for example, a library) and can
prioritise merge conflicts for resolution by a complexity measure.
Version control
ChangeMan ZMF views changes at a high level through the concept of a change
package. A change package is a collection of components that are related to each
other for a particular change. A typical change package might include source
modules, load modules, copybook, JCL and documentation.
ChangeMan ZMF uses the change package identifier to control component versions.
The package identifier is used to track all component versions. When a package is
checked out from production, the package identifier is associated with this checked
out version. This package identifier is then permanently associated with this
component version.
ChangeMan ZMF also keeps track of the version and modification number of a
component, following the IBM standards vv.mm (where vv is the component version
and mm is the modification number).
Users typically work at the change package level and component versioning can be
done at the change package level, and at each component edit version.
A change package is created first, and then the user associates the component
check-out with the change package identifier.
ChangeMan ZMF allows administrators to configure the check-out function with

various restrictions, rules and options – depending on the needs of a project or site.
Examples include the ability to:
• disallow parallel development
• restrict check-out to components previously associated with a change package
• restrict check-out privileges to specific users.
In our opinion, most users will wish to apply the restriction that check-out can only be
to ChangeMan ZMF staging libraries. This will give a fuller version history, provide
greater controls on compilation processes and help maintain the integrity of source-

19
to-load relationships. This is especially important if parallel development is being

undertaken.
When all components associated with the change package are completed, it is frozen
in order to prevent further modification and to position it for promotion and approval
processing.
Parallel development
ChangeMan ZMF supports parallel development by optionally permitting more than
one user to check-out the same component from its secured libraries (provided that
each check-out is associated with a different change package). Parallel development
within the scope of a single change package is not supported (except by preventing
multiple developers from having access to the same component at the same time).
When a change package is promoted, ChangeMan ZMF detects duplicate modules in

the package, in the target promotion dataset, and in the history record (these
duplicates may have conflicting changes). It then gives users the option to continue
the promotion (in which case the version in the change package will become the
latest version in the promotion dataset) or to cancel it.
If the promotion is cancelled, developers will need to determine whether there are any
conflicts between the common modules. ChangeMan M+R (Merge and Reconcile)
can process up to seven different versions of the same component, providing different
views in a context that highlights the conflicts and assists their reconciliation. M+R
performs the following steps:
• compiles member lists of the base/derivative libraries and matches members in
version sets that have the same name
• loads the chosen base members and the derivatives’ members into storage
• compares the base version with each of the derivatives, records the differences,
then compares and combines them
• stores the base version and the differences in the M+R database
• identifies conflicts and single changes
• calculates the degree of complexity of the reconciliation effort, writing comments
about the event to the M+R database
• displays a full view of the M+R database, formatted graphically and in colour, for
reconciliation.
For some languages (Cobol, PL/1, Assembler and JCL), M+R now includes language
analysis to identify cosmetic alterations that do not affect the executable code. These
are not reported as conflicts, thus reducing the number of changes needing analysis
and resolution.

20
Mass merging
ChangeMan M+R includes many features directed towards comparing an entire
library containing thousands of files, and the use of complexity metrics is particularly
relevant to supporting this process.
One of the main functions of M+R is merging updated vendor code into production
systems, which may themselves have been modified. This is shown in Figure 4.
Figure 4 Merging updated vendor code with production systems
Production software
release (n) mod
A D
Vendor software Production software

M+R
release (n) release (n+1) mod
Vendor software
release (n+1)
M+R compares version A with version B to identify the changes and modifications
added to the vendor release locally. It then compares A with C, to identify the
vendor’s changes between release n and n+1. M+R merges and combines the
differences with version A, so that they can be reconciled using the merge tool.
Finally, M+R extracts the reconciled code and creates version D, which is the new
(n+1) vendor release plus all the needed customisations, minus those user fixes that
have already been addressed in the vendor’s (n+1) release. Version D will need
testing.
Figure 5 shows the M+R feature in operation. Strong use of colour for semantic
information is a key feature of this product.

21
Figure 5 M+R command screen
The symbols in the line number show lines inserted or deleted in different versions.
Different changes in two variants are marked as (<>). An inserted line is shown as (>)
followed by an identifier for the variant contributing that insertion. If the same line has
been inserted in two variants, it is shown as >>AB, and deleted lines are identified by
the symbol <.
M+R features are not accessible through ChangeMan ZDD because the ZDD focus is
to integrate with workstation IDEs that normally contain comparison and merge tools.
The ChangeMan Diff utility (inherited from ChangeMan DS) provides a subset of the
merge and reconciliation features found in ChangeMan M+R.
In massive consolidation efforts (such as vendor code reconciliation), M+R can be

used to consolidate an entire library containing thousands of programs. The display in
Figure 6 shows a consolidated workplace with version members.

22
Figure 6 Consolidated workplace
In the screen shown in Figure 6, the symbols shown against each file name indicate
the following:
$ the derivative is different from the base

= the derivative is equal to the base
@ the base version
. the member is missing in the corresponding library
b the file is a banner. Banner files are not compared, but only merged on top of the
consolidated version
The action column (blank in the example shown in Figure 6) contains the last action
performed on the base/derivative set of members:

23
Blank Member version not yet executed

*Execute Compared and merged member versions
*Reconcl Fully or partially compared member versions
**Export Exported consolidated member versions
The complexity (COMPL) column indicates the level of differences between the
versions (high, medium or low). A blank entry means that all versions are equal and
thus no reconciliation is needed.
The complexity measure is based on the number of single changes and whether they
are simple deletions or insertions or combined replacements involving both deletions
and insertions, and the number of conflicts and whether they involve just two
derivatives or more than two derivatives. Users can adjust the parameters to select
different limits for the levels of complexity generated by the analysis.
The combination of features in ChangeMan M+R considerably reduces the effort

involved in merging large numbers of files, and provides the metrics to allow the most
complex merges to be handled by the most experienced staff.
Managing web objects

ChangeMan ZMF is a general-purpose CM tool that does not have features specific
to web page management.
Serena provides ChangeMan DS for web code and content management. (Please
see Ovum’s evaluation of ChangeMan DS for more information.)
IDE integration
IDE integration is not an issue for mainframe products.
ChangeMan ZDD, which supports desktop development for z/OS, is integrated with
IDEs such as Visual Age Cobol, Visual Age PL/1 and WebSphere Enterprise
Developer (WSED).
Over 100 Serena XML services are delivered with ChangeMan ZMF to provide an
integration API. ChangeMan ZDD uses this interface to access ChangeMan ZMF
metadata from Windows. An ISPF-based modelling tool is included as well as
interfaces to Cobol, PLI and REXX.
ChangeMan ZMF can interface with other products such as IBM Tivoli’s Information
Management, IMS, DB2, CA Panvalet, CA Librarian, APS, JCLPrep, Interest,
Expediter, SmartTest, Docu/Text and Jobscan.
Details of ChangeMan ZMF integrations are available at:
http://www1.serena.com/solutions/index.cfm?nav=IDE
Navigation to this location is reached through the solutions menu and not the
products menu.

24
Replicated repositories
1 2 3 4 5 6 7 8 9 10
Not relevant for mainframe CM tools
This section is not relevant to mainframe CM tools and is therefore not evaluated.
The Replicated repositories section addresses a style of development where different

teams work on separate repositories that require synchronising at times and
frequencies determined by the user. While these repositories can be on the same
system for performance reasons, some users select this mode of working to support
teams at different geographic locations, with replicated repositories on different
servers. Other users will choose to use a single repository or multiple independent
distributed repositories controlled by a metadata repository.
All CM tools – even those that offer a replicated option – can support geographic
working using network and/or Internet access to a single server.
Multiple repositories
ChangeMan ZMF users work from a single repository or from several independent
repositories making use of the library merge features described under Team support
to share updated code. ChangeMan ZMF does not support the replication of a
repository to multiple servers for further development on each server and the
subsequent regular synchronisation of changes as defined by the Ovum criteria for
this section of the evaluation.
The Ovum criteria for Replicated repositories assume a distributed development

model. In the mainframe development model, components are not distributed for
additional changes. The use of a single repository accessed from several locations is
covered in the Team support section.
There is a need to share copybooks and load modules across mainframe

development centres. This distribution is handled in the same way as production
installations. The other development centres are set up as production sites for
delivery.
Change synchronisation
ChangeMan ZMF does not support the replication and synchronisation of changes on
different servers. However, ChangeMan ECP does go some way towards providing
an equivalent facility, as well as extended facility to cover ChangeMan DS change
information.
Change packages on multiple ChangeMan ZMF instances and change packages on

multiple ChangeMan DS servers can be linked as enterprise change packages to
provide a cross-platform software change lifecycle managed by ChangeMan ECP.

25
ChangeMan ECP is a web-based tool that provides a single point of control for central
reporting and approval capabilities for ChangeMan ZMF and ChangeMan DS.
ChangeMan ECP provides a web interface that allows managers to respond to
software changes made to ChangeMan ZMF and/or ChangeMan DS. ECP allows
users to be notified by e-mail and voice communication devices through the use of
wireless access and pervasive computing standard protocols (WAP and PvC).
ChangeMan ECP can control, search, interrogate and generate reports on both the
ChangeMan DS and ChangeMan ZMF products, including multiple repositories
managed independently by each product.
The ChangeMan ECP web browser interface allows users to:

• access all change management information from a single view
• review and approve software changes
• respond to change notifications sent via e-mail and voice communication devices
• query and report on various activities, including graphical reports that show:
package status (number of packages in various states)
package level (number of packages defined as super, simple, complex and
participating)
package type (planned, unplanned, temporary and permanent)
• set administration functions.
ChangeMan ECP therefore gives a common view of changes across multiple

repositories and allows for certain management activities (retrieving information &
reports and approving changes). ChangeMan ECP can access all ChangeMan DS
and ChangeMan ZMF systems in a client company. This access is customisable to
allow enterprise change managers to define those systems they are interested in.
Configuration management
1 2 3 4 5 6 7 8 9 10
There is reasonable configuration management control over files of different types

associated together for build or other purposes. Good impact analysis and traceability
support. ChangeMan ZMF supports both the package-oriented approach and release
management with the ability to store and access components from a developer’s tool
of choice.
Configuration specification
In ChangeMan ZMF, the concept of a change package is the specification of a
configuration of related items for a single purpose. The change package is auditable
and traceable through the development lifecycle. The ChangeMan ZMF ERO

26
(Enterprise Release Option) enables release managers to plan and deploy production
releases that contain complex configurations, with components from hundreds of
packages.
Workspace management
ChangeMan ZMF components are held in secured libraries. A baseline library stores
the most current version of production components, in addition to a predefined
number of previous versions. ChangeMan ZMF has the ability to promote change
packages through multiple shared, pseudo-production promotion environments,
where integrated system testing may be performed. These promotions are secured as
if they are promotions to production, and ChangeMan ZMF will control all updates.
Check-out is the ChangeMan ZMF process of copying components from the secured
libraries to the user’s personal workspace for modification in a future change, or to
staging, where it can be immediately edited. In performing check-out to staging
libraries, ChangeMan ZMF dynamically manages the space and will prevent out-of-
space abends, clean up the space and conserve DASD.
Impact analysis
ChangeMan ZMF provides an impact analysis facility to capture, query and enforce
relationships between components. These include relationships between source and
executable code, and other relationships based on common references to copybooks,
SQL Include components, CA Panvalet ++Include components, CA Librarian-Inc
components called subroutines and JCL fields (such as program name or dataset
name).
Serena recommends that ChangeMan ZMF’s DB2 option is licensed and installed,
since the impact analysis features exploit the relational capability of a DB2 table. A
limited impact analysis capability exists if the DB2 option is not available but, in this
case, relationships are not automatically updated during the final stages of migration
into production.
The ChangeMan ZMF audit function inspects staging libraries to detect ‘out-of-synch’
components such as:
• copybooks that have been changed after a source program has been compiled
• source programs that need to be recompiled due to a copybook change
• called sub-routines that have been changed after a referencing source program
has been compiled and linked.
Figure 7 shows an example of an impact analysis report.

27
Figure 7 ChangeMan ZMF audit impact analysis report
Traceability
ChangeMan ZMF captures dependencies through the analysis it performs as
components are ‘staged’ from the user environment into ChangeMan ZMF’s control,
and at the final lifecycle stage as they progress into production.

28
The query facility for relationships displays all upstream and downstream
relationships for a requested component.
Change management
1 2 3 4 5 6 7 8 9 10
Change package style of working is central to ChangeMan ZMF and all work is
carried out in this context. Many reports are available, but there is no graphical
display of information (except in TeamTrack) – although data can be exported to
create this. ChangeMan ECP provides a full set of graphical reports for enterprise
change managers.
Problem tracking
TeamTrack is now the problem tracking system for ChangeMan ZMF.
TeamTrack’s end-user interface is browser-based and is organised by solutions,

which include fields, workflows, projects, notifications, reports, tables, table
relationships and scripts. Solutions enable users to track items following a workflow
process. The user interface is configurable – an example is a manager’s interface as
shown in Figure 8.

29
Figure 8 Example TeamTrack user interface
TeamTrack can be configured so that issues (and other information) can be submitted
in several ways:
• through the browser interface by internal or external users, such as customers or
partners
• through e-mail
• from one TeamTrack database to another TeamTrack database.
Figure 9 shows the browser interface for submitting issues.

30
Figure 9 TeamTrack issue submission
The fields marked in red are mandatory.
TeamTrack offers realtime access to the system via a browser installed on a

handheld device. Users can use a handheld device with a compatible HTML browser
and a connection to the TeamTrack server. This can be a direct connection or via a
proxy server, such as AvantGo.
The mobile browser interface offers many of the same features available when
accessing TeamTrack from a browser on a workstation. For example, with
appropriate privileges, users can:
• access all solutions available to them
• view their homepage for each solution
• view, submit, transition, update and delete primary items
• view, update and delete associated items
• search by keyword or item ID and prefix.
• execute listing and graphical-style reports

31
• execute built-in reports

• view the change history, state change history, version control history, and
subtasks.
As an issue progresses it typically changes ownership. The new owner and other
designated users (for example, the team manager) are informed of the ownership
change by e-mail. The team manager has access to an overview screen as shown in
Figure 8.
ChangeMan ZMF users need to implement a TeamTrack lifecycle state and user role
so that it matches their ChangeMan ZMF lifecycle. For users of the default ZMF
lifecycle an equivalent TeamTrack lifecycle is provided by Serena with the TeamTrack
for ChangeMan solution.
Change control
TeamTrack now provides an issue tracking tool that can track problems, change
requests and team tasks. The way this is accomplished is described in Problem
tracking, but with a workflow tailored for managing each task.
Change packages
The change package concept is central to ChangeMan ZMF’s control of
development.
A change package is a grouping of all the components required to implement a

software change into production – regardless of their type. Change packages may be
built for any type of change, including:
• permanent, a package that is enduring and is only deleted by an authorised user
• temporary, which may never be a formal part of a baseline and is automatically
deleted from production after a specified number of days
• unplanned, which is created for an emergency situation – often out of business
hours. Approval is based on an abbreviated approval list
• simple, a standalone change unrelated to any other change package
• complex, the parent change package for two or more change package
applications that have related or interdependent changes.
At creation time, a unique number is assigned to the change package to enable

cross-referencing. When a developer adds components to a change package, that
information is added to the Package Master (ChangeMan ZMF’s control file
containing information about current and previous change packages).
A TeamTrack lifecycle needs to be created to mirror the ChangeMan for ZMF change
package workflow.

32
Reports and metrics

ChangeMan ZMF produces more than 25 different reports and all are available as
online queries. These cover:
• package information, as summarised under problem tracking
• component information – similar to change package information, but relating to a
particular component
• impact analysis of component relationships (as summarised earlier under Impact
analysis).
All ChangeMan ZMF reports are delivered as REXX using Serena XML Services.
Serena XML services have replaced the previous SAS and Assembler-based
reporting. Users have full access to modify the REXX code and create custom
reports. In addition to the delivered REXX and Serena XML Services reports, users
can use the ChangeMan XML facility to develop custom queries. The results of the
query can be accessed through MVS or retrieved through ChangeMan ZDD, and
formatted using standard products such as Microsoft Excel, Crystal Reports, Mozilla,
or standard web browsers to display and manipulate the results. Figure 10 shows an
Excel view of ChangeMan ZMF XML retrieved data.
Figure 10 Excel view of XML data from ChangeMan ZMF

33
ChangeMan ZMF provides only a few metrics, mostly related to conflict resolution
following parallel development. One of these is particularly interesting: the
ChangeMan ZMF Merge+Reconcile option provides a high-level capability to
consolidate up to seven versions of a complete software system. The M+R option can
calculate a degree of complexity metric on a scale from one (low) to ten (high) to
measure the amount of effort required for each reconciliation.
This is useful in several ways. It allows the most complex tasks to be assigned to the
most experienced users, and could provide a trigger for a review of the reconciliation
strategy (for example, to a two-stage process), in order to reduce the overall
complexity.
TeamTrack provides a rich set of reports and graphics and includes a management to
show selected graphics on a single screen image. Figure 11 shows a TeamTrack
management dashboard.
Figure 11 TeamTrack management dashboard

34
Build and release support

1 2 3 4 5 6 7 8 9 10
Good general build capability, with footprints to support accurate rebuilding. Good
release support, including automatic and co-ordinated installation to remote sites.
Building
ChangeMan ZMF uses standard ISPF/PDF tailoring of skeletons for compile, BINDS
and other translation procedures. During translation, a token is produced and saved
with the listing, providing a fingerprint for ensuring source-load integrity. This is
produced by a hashing algorithm, which assists in the guarantee of the source-to-load
relationship.
ChangeMan ZMF allows translation procedures to be flexible during development, so

developers are free to use the tools of their choice, but it enforces production
standards when a change package is ready to be promoted. Existing compile
procedures may be used after minimal modification.
Rebuilding
A change package can be regenerated as required. If the build process has been
standardised, then rebuilds are guaranteed to be identical to the original. If the build
process is not standardised, then an individual user’s actions cannot be replicated,
and thus a rebuild may differ from the original (for example, different compiler options
may be used).
ChangeMan ZMF has a baselining capability, which allows earlier baselines to be

reproduced without the need for rebuilding.
Release support
Once a change package has been approved for production release, and a date and
time have been set for installation, ChangeMan ZMF controls the process of
installation.
Installation can also be made on remote sites, using standard transmission facilities
such as TCP/IP, FTP, Direct Connect (formerly NDM), Netmaster or XCOM 6.2 –
under the same ChangeMan ZMF control. A remote site can be:
• a separate computer in another building
• a separate computer in the same building
• a logical CPU on the same machine as part of a LPAR (logical partition) without
shared DASD.

35
Installation depends on whether or not an internal scheduler has been set up by the
global administrator, or if the installation JCL has been specially modified.
There are four install options:

• install immediately
• install later when an approved user triggers installation
• add job to non-ChangeMan ZMF scheduler’s list (in this case, the operator must
still demand the job for the package to be installed)
• ChangeMan ZMF will check every few minutes for any packages that are ready
for installation, and install those that meet the criteria.
The first action ChangeMan ZMF takes upon installation is to backup those
components about to be changed. ChangeMan ZMF then undertakes a baseline
ripple: the changes to be installed become production components, the previous
production component becomes version –1, version –1 becomes version –2 and so
on.
If there is a problem with a change package after it is installed, it can be backed out
by deleting the updated component in production and then retrieving the previous
version of the software from the application library.
ChangeMan ZMF’s Audit function can be used to verify a change package at any
time, even after the change package has been frozen and approved. Change
managers are encouraged to continuously run Audit to manage concurrent
development and code regression issues.
Process management
1 2 3 4 5 6 7 8 9 10
Good basic support for lifecycle processes and user roles. Recognises and supports
the need for emergency development paths. Excellent support is provided for change
and issue management lifecycles with TeamTrack.
Lifecycle support
An overview of the ChangeMan ZMF lifecycle is given in Figure 12, showing the
actions necessary to migrate a change from development to production within
ChangeMan ZMF.

36
Figure 12 ChangeMan ZMF lifecycle
Create Checkout Stage (Promote)

(DEV) (modify Test
components) (DEV)
(DEV)
(Audit)
Impact
(Unfreeze) analysis
(FRZ) (DEV)
(Revert) Freeze (Promote)

(REJ) (FRZ) Test
(DEV)
(Backout) Approve
(BAK) (APR)
Baseline Ripple Baseline Ripple

(BAS) (BAS)
Main process flow

Optional processes
• The first step is to create a change package. A change package contains all of
the elements to be edited and installed into production, and is identified by a
unique package ID automatically generated by ChangeMan ZMF. When a change
package is created, the information that ChangeMan ZMF needs in order to track
and control the package is entered. This includes the implementation instructions,
whether it is a temporary or permanent change, and the installation date and
time.
• Typically, the next step is to check-out components from the baseline. With
check-out, components from your baseline libraries are copied to either a
ChangeMan ZMF staging library or a personal development library where
changes can be made.
• Changes may now be edited in either the ChangeMan ZMF staging or in the
development libraries.
• Once editing is completed, the components are ready to stage. For source
components, staging will ordinarily run the appropriate translation procedure to

37
create associated load modules. Components such as documentation or copy

members are simply copied into the staging libraries (if they are not there
already). The change package is now ready for testing.
• Depending on the installation, the change package must pass an audit before
‘freeze’. The audit process ensures that no unexpected problems will occur. For
example, if a component in the production library has been changed since it was
checked out, ChangeMan ZMF creates an ‘out-of-synch’ condition for the
package.
• After successfully passing the audit, the next step is to freeze the change
package. This locks the package (prohibiting further changes) and makes the
package available for the promotion and approval processes.
• Promotion is an optional step. After successfully staging all components in the
change package, the change package may then be promoted. Promotion allows a
change package to be moved through various levels of testing (for example,
promoted from system testing to acceptance testing). Components may also be
promoted to remote hosts.
• Once all the necessary approvals have been gathered by ChangeMan ZMF, the
package is ready to be installed. If the manual installation method was selected
when the package was created, the package will be installed immediately after
the final approval. If the CMN method (ChangeMan ZMF’s internal scheduler)
was selected, ChangeMan ZMF will automatically install the package on the date
and time specified at package creation. If an external scheduler is used (for
example, CA7, ESP, ZEKE or JOBTRAC), ChangeMan ZMF will convey the
install information to that scheduler, so that it can install the change package.
• Once the package has been installed, ChangeMan ZMF will perform the baseline
ripple. This is the process that ChangeMan ZMF executes to version all package
components (that is, 0 becomes –1, –1 becomes –2, –2 becomes –3 and so on)
and the new baseline 0 version is installed.
TeamTrack provides excellent workflow support for change and issue management.
TeamTrack workflows are created using the TeamTrack Administrator shown in
Figure 13 users drag and drop squares, connect them with arrows and create a self-
documenting process that guarantees repeatability.

38
Figure 13 TeamTrack workflow creation
Extended lifecycle support

Serena is providing extended lifecycle support from requirements to production in a
phased approach, which involves:
• the acquisition of TeamShare, provided Serena with TeamTrack, a process and
change management tool
• the announcement of the Serena Application Framework for Enterprises (SAFE).
This framework extends beyond ALM by enabling companies to manage
application design, development, quality assurance, deployment and support
across platforms and across processes
• delivering integrations to ChangeMan ZMF
• delivering integrations to ChangeMan DS and third-party products (not available
yet).
User roles
User roles are not specifically identified in ChangeMan ZMF, but individual users are
given access to particular functions (for example, authorisation). This allows user

39
roles such as QA to be effected and, if desired, stop the change package from
moving forward.
Project support
1 2 3 4 5 6 7 8 9 10
Good general CM capability to support testing needs, with strong merge capability for
conflict resolution of libraries. ChangeMan ZMF does not link with project planning
tools.
Testing
The ChangeMan ZMF change management and build features ensure that
compliance issues identified as a result of testing can be logged, progressed and
reliably delivered into production.
Testing projects can also have a lifecycle and approval process appropriate to the
stronger orientation to test issues that are common to most application development
tasks.
The likely need to run testing in parallel with other developments is well supported by
the ‘vendor merge’ options in Merge+Reconcile, which is an excellent tool for conflict
resolution.
Project management
ChangeMan ZMF does not link with project planning tools.
Usability
1 2 3 4 5 6 7 8 9 10
Typical mainframe panel displays, but options are tailored to user access authorities.
ChangeMan ZDD provides a Windows interface to mainframe data and functionality.
The ChangeMan ZMF user interface is the typical IBM panel style, second only to the
Unix command line in terms of poor user friendliness. It is, however, the common
interface style for IBM mainframe users. The full ChangeMan ZMF Primary Option
panel display is shown in Figure 14.

40
Figure 14 Primary Option panel display
The options displayed on the menu in Figure 14 are based on the authorisation of the
user.
ChangeMan ZMF dynamically builds this panel after verifying (with the host security
system) what ChangeMan ZMF functions the user may access.
The user that has this panel displayed has the following authorisations granted:
• administrator of some sort (the ‘A’ option is displayed)
• revert packages (the ‘R’ option is displayed)
• back-out packages (the ‘B’ option is displayed)
• monitor packages ‘in limbo’ (the ‘M’ option is displayed).
ChangeMan ZMF users who are developers or approvers are unlikely to have any of
the additional options listed above. Most of the functions that they will use will be
accessed from the Build change package menu, Option 1, on the main menu.
Users adopting ChangeMan ZDD for Windows access to ZMF functionality and data
will see a Windows style of interface on their desktop as shown in Figure 15.

41
Figure 15 ChangeMan ZDD interface
ChangeMan ZDD enables direct access and editing of ChangeMan ZMF assets from
the desktop. In ZDD, the mainframe appears as a driver letter in Windows, and ZMF
libraries and components appear as folders, subfolders and files that can be
accessed by desktop development tools. The integration eliminates the need to
download files, and the need to dedicate resources to the upload/download process.
With ChangeMan ZDD, programmers only need to know their favourite IDEs to
extend mainframe applications. ZDD enables ubiquitous access to the mainframe
from the desktop with an interface for submitting mainframe jobs, viewing JES
input/output queues, and integrating mainframe testing environments.
Web client
ChangeMan ZMF does not have a web interface to CM functionality and data. This
functionality is available to users of ChangeMan ZDD via Windows.
ChangeMan ECP is a web portal for accessing information and providing approvals at
management level. The ECP web interface is shown in Figure 16.

42
Figure 16 ChangeMan ECP web interface
ChangeMan ECP features are described in Replicated repositories.
Documentation
Documentation is vast and generally poor. Although all panels and options are
thoroughly described, there is little overall sense of how to use the product to best
effect. Options are described without comment on why one option might be preferred
to another. There are very few screenshots to show users examples of what they will
see on the screen – a table of field names and the information to be entered in these
screens is used to describe most screens.
The number of products that cover different functionality associated with ChangeMan
ZMF hampers finding information. Most documents are around 200 pages and some
exceed 300 pages. They would all be improved by imposing an arbitrary limit of 100
pages for each document.
Documentation is available in Adobe Acrobat format on a password-protected CD-

ROM.
Online help
Online help is available, conforming to the relevant style for the panel/menu interface.

43
Administration
1 2 3 4 5 6 7 8 9 10
ChangeMan ZMF leaves existing data in situ, simplifying the set-up process.
Administration panels are well presented (given the limitations of the mainframe
environment), but JCL skeletons need to be customised for each link and compile
scenario.
According to Serena, a basic ChangeMan ZMF implementation and initial

customisation takes approximately two weeks to set up and become operational. A
more complex implementation – for example, one involving extensive customisations
– might take between two and six additional weeks, depending on how many third-
party tools are integrated. Most additional time is to allow for organisational and
process adaptation concerns.
ChangeMan ZMF has four administrative domains:

• the global administrator is responsible for setting the high-level rules for the site’s
implementation procedures, for specifying the systems (for example, Panvalet)
with which ChangeMan ZMF is to interact, and the details regarding staging
library allocation. The global administrator is also responsible for determining
which servers are needed and for defining security policies and mechanisms
• the application administrator is responsible for setting the rules of the application
development process – provided they do not breach the global rules. The
application administrator can also set staging library information and determine
compiling procedures for languages used in the application development. In
addition, the administrator configures the promotion and baseline libraries and
creates approval lists, which are used by ChangeMan ZMF to notify strategic
people in the development process that a change package is ready to be moved
onto the next level of integration, testing, or into production
• the ChangeMan ZMF monitor (typically operations analysts) can oversee the site
for change package discrepancies (for example, distribution without distribution
acknowledgement) and can override installation information provided by the user.
The monitor has the ability to release package installs, hold packages back from
installation, change the status of any packages in limbo, and issue the back-out
command
• the general administrator is likely to be an expert in the periodic housekeeping
tasks for ChangeMan ZMF, such as starting up and shutting down the started
task, updating the query information, backing up or recovering the package
master, or clearing the activity log.
The four domains can all be the responsibility of one individual and need not be a full-
time responsibility for the individuals assigned to these tasks.

44
ChangeMan ZMF recognises some library types, which it handles in a specific way.
These are CPY, CTC, DBB, DBR, DOC, JCL, LCT, LOD, PRC and SRC. Users can
specify additional types, and can tell ChangeMan ZMF how to handle such
components when they are staged. Options include:
• treat the library type in the same way as source. When this component type is
staged, ChangeMan ZMF will attach the appropriate compiling procedures and
options based on the user’s selections or administrator definitions
• treat the library type as a load module
• treat the library type as a copybook or ‘include’. ChangeMan ZMF will include
these components in the compilers’ SYSLIB concatenation when a source
component is compiled
• perform staging as a simple copy operation using IEBCOPY or a similar
operation.
The various control parameters of ChangeMan ZMF operate at a global level and at
an application level. Global parameters apply to all applications, but individual
applications can modify these (for example, to introduce an extra stage of testing).
ChangeMan ZMF uses a project’s existing libraries in situ. The take-on of project data
is therefore a formality. ChangeMan ZMF uses library types to determine how
components are processed; for example, for source, ChangeMan ZMF knows that
there will be some form of translation needed and an associated load module
generated.
Panvalet users who make use of the full Panvalet ten-character file names may need
an additional review of component names before transferring files to ChangeMan
ZMF control. This is because ChangeMan ZMF assumes PDS naming conventions
(eight characters).
The major effort in implementing ChangeMan ZMF for a project is therefore to set up
a multi-layered project team and assign appropriate security to each user in relation
to the ChangeMan ZMF functions, and to the authorisation and other processes
associated with the ChangeMan ZMF lifecycle.
Various global and local administration parameters need to be set, and JCL skeletons
(which are provided) need to be customised for every link and compile scenario that
exists for a project.
Serena recommends that users should run through an end-to-end test as the first
step of a pilot. This test should take a change package from creation through to
installation. Back-up processing and report generation should then follow, with the
whole process being repeated for different users as necessary.
Users should take advice from Serena’s consultancy services for the initial set-up
procedures and processes.

45
Customer support
Support
In North America, the UK, France, Germany, Austria, Switzerland and the Benelux
countries, Serena has introduced ‘follow the sun’ support, which is seamless to
Serena customers. Incoming calls are automatically routed to the most appropriate
call centre among Serena’s various locations.
Users in other countries should contact their local distributor.
A web service to support customers is also available.
Training
Serena has developed modularised user training courses, which are available from all
distributors:
• an administrator course, between two and five days, to prepare administrators
and assist them in installing and administrating ChangeMan ZMF
• a user/developer course, two separate half-day sessions, using the newly created
ChangeMan ZMF system
• a technical course, a detailed course tailored to individual client needs, usually
lasting three days.
Serena also offers e-learning and computer-based training for users and
administrators.
Courses can be customised for individual customers and can be held on-site.
Standard Serena courses can be found at:

http://www.serena.com/services/serv_cls_offered.html
Consultancy services
Serena and all ChangeMan ZMF distributors offer turnkey consulting support for
installing the product and setting it up for project use. This support uses the principles
of process management practices such as CMM, ITIL, Six Sigma and others to
establish a set of ECM best practices, covering:
• IT organisational planning
• project management
• configuration management deployment.

46
Client re-use disclaimer

• This is a verbatim reproduction of independent material that has previously been
published by Ovum within the last 6 months
• Ovum operates under an Independence Charter. For full details please see
www.ovum.com/about/charter.asp
• Neither Ovum nor the analysts were paid by the client to write any part of the
material
• Ovum may have been paid by the client for the right to re-use the material
• Ovum may have a deal with the client to supply research or consultancy.
However, no other relationship exists between the 2 companies (e.g.
shareholdings, loans, non-executive directorships etc)
• Ovum does not endorse companies or their products
• While we take every care to ensure the accuracy of the information contained in
this material, the facts estimates and opinions stated are based on information
and sources which, while we believe them to be reliable, are not guaranteed. In
particular, it should not be relied upon as the sole source of reference in relation
to the subject matter. No liability can be accepted by Ovum Limited, its directors
or employees for any loss occasioned to any person or entity acting or failing to
act as a result of anything contained in or omitted from the content of this
material, or our conclusions as stated
This material is the copyright of Ovum Ltd.
Ovum does not endorse companies or their products. Ovum operates under an Independence Charter. For
full details please see http://www.ovum.com/about/charter.asp.
Whilst every care is taken to ensure the accuracy of the information contained in this material, the facts,
estimates and opinions stated are based on information and sources which, while we believe them to be
reliable, are not guaranteed. In particular, it should not be relied upon as the sole source of reference in
relation to the subject matter. No liability can be accepted by Ovum Limited, its directors or employees for
any loss occasioned to any person or entity acting or failing to act as a result of anything contained in or
omitted from the content of this material, or our conclusions as stated. The findings are Ovum’s current
opinions; they are subject to change without notice. Ovum has no obligation to update or amend the
research or to let anyone know if our opinions change materially.

Ovum ChangeManZMF

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ovum ChangeManZMF

Uploaded by

Copyright:

Available Formats

ChangeMan ZMF - Serena Software

Ian Wesley: ian.wesley@ovum.com

© Ovum 2005. Unauthorised reproduction prohibited

Replicated repositories Not relevant for mainframe CM tools

Build and release support

© Ovum 2005. Unauthorised reproduction prohibited

• ChangeMan ERO (Enterprise Release Option), which provides release

The means by which a new application, or change to an existing application, is

The ChangeMan ZMF Library Environment

ChangeMan ZMF manages the transition from development to production libraries by

© Ovum 2005. Unauthorised reproduction prohibited

Production libraries may be the same as baseline libraries, depending on how

© Ovum 2005. Unauthorised reproduction prohibited

ChangeMan M+R is an essential add-on to ChangeMan ZMF. In a market where

© Ovum 2005. Unauthorised reproduction prohibited

ChangeMan ZMF supports concurrent check-out of components for parallel

Support for maintaining the integrity of production sites as approved change

© Ovum 2005. Unauthorised reproduction prohibited

SERNET Z/OS server

Serena XML Services

Source: Serena Software

ChangeMan ZDD allows desktop programmers to edit mainframe components from

© Ovum 2005. Unauthorised reproduction prohibited

emergencies temper this. Changes cannot be migrated into production without

© Ovum 2005. Unauthorised reproduction prohibited

© Ovum 2005. Unauthorised reproduction prohibited

Figure 2 Platform and interface aspects

© Ovum 2005. Unauthorised reproduction prohibited

correctly on non-tested browsers and mobile

† Note that TeamTrack does not yet deliver WAP

Source: Serena Software

© Ovum 2005. Unauthorised reproduction prohibited

© Ovum 2005. Unauthorised reproduction prohibited

© Ovum 2005. Unauthorised reproduction prohibited

In June 1999, Serena completed its acquisition of Diamond Optimum Systems to

© Ovum 2005. Unauthorised reproduction prohibited

1998 1999 2000 2001 2002 2003

© Ovum 2005. Unauthorised reproduction prohibited

Serena’s revenues in calendar 2003 (fiscal 2004) were derived from:

Character and direction

Serena specialises in enterprise change management (ECM), which it defines as the

Serena is focused on CM integration across platforms with links between applications

SAFE provides a process-centric framework surrounding the application lifecycle,

This framework enhances Application Lifecycle Management (ALM) by enabling

© Ovum 2005. Unauthorised reproduction prohibited

Following the acquisition of TeamShare Serena has adopted TeamTrack as the

© Ovum 2005. Unauthorised reproduction prohibited

ChangeMan ZMF allows administrators to configure the check-out function with

© Ovum 2005. Unauthorised reproduction prohibited

to-load relationships. This is especially important if parallel development is being

When a change package is promoted, ChangeMan ZMF detects duplicate modules in

© Ovum 2005. Unauthorised reproduction prohibited

Vendor software Production software

Source: Serena Software

© Ovum 2005. Unauthorised reproduction prohibited

Figure 5 M+R command screen

Source: Serena Software

In massive consolidation efforts (such as vendor code reconciliation), M+R can be

© Ovum 2005. Unauthorised reproduction prohibited

Figure 6 Consolidated workplace

Source: Serena Software

$ the derivative is different from the base

© Ovum 2005. Unauthorised reproduction prohibited