Application Change Management for DB2 for OS/390

Iris Wilde

Application Change Management for DB2 for OS/390
Our current system to manage the migration of DB2 object changes into production is a (sometimes error-prone) mix of manual procedures, clists and COBOL programs. Several co-workers have proposed developing a better in-house solution that would employ CA-Endevor (our source management system). Before we get started, I'd like to ask you all about your experiences with DB2 Change Management. What products or in-house solutions do you use? What's your experience and/or advice about different approaches? Just curious: is anyone out there using the CA-Endevor for DB2 product? Thanks in advance for your input!

Iris Wilde,
[login to unmask email],
TD Bank

[login to unmask email]

Re: Application Change Management for DB2 for OS/390
(in response to John O'Conner)


We use Endevor for our source code. We also maintain our DCLGEN's and
production DB2 utilities
under Endevor.

Endevor is a good configuration management tool which seems to provide a lot of
functionality when used
properly. It does however require that you have a experienced Endevor
administrator or alot of time to train someone thoroughly, and Endevor
administrators are not so easy to find.

Howard Jung
[login to unmask email]





[login to unmask email] on 12/14/99 03:52:44 PM

Please respond to [login to unmask email]

To: [login to unmask email]
cc: (bcc: Howard Jung Jr/CIV/CSC)
Subject: Application Change Management for DB2 for OS/390



Our current system to manage the migration of DB2 object changes into production
is a (sometimes error-prone) mix of manual procedures, clists and COBOL
programs. Several co-workers have proposed developing a better in-house
solution that would employ CA-Endevor (our source management system). Before we
get started, I'd like to ask you all about your experiences with DB2 Change
Management. What products or in-house solutions do you use? What's your
experience and/or advice about different approaches? Just curious: is anyone
out there using the CA-Endevor for DB2 product? Thanks in advance for your
input!

Iris Wilde,
[login to unmask email],
TD Bank

John O'Conner

Re: Application Change Management for DB2 for OS/390
(in response to Iris Wilde)
We are using BMC Change Manager.  We are pleased with it.  It remembers to
do those things that are easy to forget (rebind packages, regrant
privileges, image copy, etc.).  It knows when table changes require a
Drop/Create and it remembers to unload/reload that table.  It's flexible
enough, it's reliable, and we get good support.  These things are probably
true for comparable products from other vendors.
 
Having set procedures to follow and applying them consistently is much more
important than the product you are using.  The worst of both worlds would be
having procedures that involve using a migration tool, then making some
changes manually (i.e. without using the tool).  We migrate changes through
9 copies of our primary database (each with about 180 tablespaces, 300
indexes).  If we lose track of which changes have been applied to which
databases, it takes a while to sort things out. 
 
John O'Conner
[login to unmask email]

-----Original Message-----
From: Iris Wilde [mailto:[login to unmask email]
Sent: Tuesday, December 14, 1999 12:53 PM
To: [login to unmask email]
Subject: Application Change Management for DB2 for OS/390




Our current system to manage the migration of DB2 object changes into
production is a (sometimes error-prone) mix of manual procedures, clists
and COBOL programs.  Several co-workers have proposed developing a
better in-house solution that would employ CA-Endevor (our source management
system).  Before we get started, I'd like to ask you all about your
experiences with DB2 Change Management.  What products or in-house solutions
do you use?  What's your experience and/or advice about different
approaches?  Just curious:  is anyone out there using the CA-Endevor for DB2
product?  Thanks in advance for your input! 
 
Iris Wilde,
[login to unmask email],
TD Bank



Roy Brickley

Re: Application Change Management for DB2 for OS/390
(in response to hjung@CSC.COM)
Just a thought -
Our company has Endevor/MVS and for a brief period tried out Endevor
for DB2. Endevor/DB2 was dropped, as it didn't provide us any extra
functionality for coordinating DBA actions (using Platinum) and
Endevor for programs/DBRMS/binds.

With the recent acquisition of Platinum by CA, and its previous
acquisition of Legent (thus, CA-Endevor), does anyone know if CA plans
to integrate RC/Migrator more closely with Endevor, or will(has) CA
enhanced Endevor/DB2 to interface with Endevor?

Roy Brickley
APL


______________________________ Reply Separator _________________________________
Subject: Re: Application Change Management for DB2 for OS/390
Author: "DB2 Data Base Discussion List" <[login to unmask email]> at internet-gateway
Date: 12/14/99 4:09 PM




We use Endevor for our source code. We also maintain our DCLGEN's and
production DB2 utilities
under Endevor.

Endevor is a good configuration management tool which seems to provide a lot of
functionality when used
properly. It does however require that you have a experienced Endevor
administrator or alot of time to train someone thoroughly, and Endevor
administrators are not so easy to find.

Howard Jung
[login to unmask email]





[login to unmask email] on 12/14/99 03:52:44 PM

Please respond to [login to unmask email]

To: [login to unmask email]
cc: (bcc: Howard Jung Jr/CIV/CSC)
Subject: Application Change Management for DB2 for OS/390



Our current system to manage the migration of DB2 object changes into production
is a (sometimes error-prone) mix of manual procedures, clists and COBOL
programs. Several co-workers have proposed developing a better in-house
solution that would employ CA-Endevor (our source management system). Before we
get started, I'd like to ask you all about your experiences with DB2 Change
Management. What products or in-house solutions do you use? What's your
experience and/or advice about different approaches? Just curious: is anyone
out there using the CA-Endevor for DB2 product? Thanks in advance for your
input!

Iris Wilde,
[login to unmask email],
TD Bank



Slot J.P.

Re: Application Change Management for DB2 for OS/390
(in response to Roy Brickley)
Iris,

The Endevor solution might work if you are looking at storing
individual objects. You will have to think about the size of this objects
Database DDL, Tablespace DDL and/or Table and Index DDL.
Implementing database changes with Endevor is not used within our
shop. CA-Endevor is merely used as a storage for DDL version control

We use CA Endevor, but because of its inability to distribute changes
onto the DB2 objects some departments started to use workarounds.
In our shop we use BMC Change Manager to implement changes. After
each change we have to take a full baseline of the Database DDL
including the authorisations. Thus we can easily do a fall back to an
earlier release of the database by comparing the different baselines.
This DDL can also be stored in CA-Endevor.
However, we still want to get a better grip on things. So we are in a
process of using a relational database modelling tool for all our
relational databases for different DBMS's. This will produce
Conceptual models, Fysical models and in the end DDL for the specific
DB2 database.
With the use of Change manager we import this DDL and compare it
with the DDL of that specific database in the specific subsystem and
make the changes happen.

The programs which are using DB2 are stored and ditributed with te
use of CA-Endevor. In the future we might get a problem with stored
procedures. We donÀt know yet where we will store the entries within
the sysibm.sysprocedures? We havenÀt figured out yet, but someone
else on the list mentioned it a few days earlier. They used a standard
format PDS member and the programmer filled that with the entry
parameters. So this PDS member could be stored in CA-Endevor.

Sofar some remarks on the technical side. You might also want to think
about political implications. WhoÀs responsible for the changes on the
database. The DBA or te CA-Endevor Administrator? In case of stored
procedures you might get into a fight between programmers and dbaÀs³

Good luck and kind regards,

Jaap Slot
Sr DB2 DBA
Rabofacet BV
[login to unmask email]
phone: +31 (0)30 2152220
fax: +31 (0)30 2151921

This email reflects only my personal opinion and not necessarily my
employers opinion.

--- original message ----
To: [login to unmask email]
cc: (bcc: Howard Jung Jr/CIV/CSC)
Subject: Application Change Management for DB2 for OS/390



Our current system to manage the migration of DB2 object changes
into production
is a (sometimes error-prone) mix of manual procedures, clists and
COBOL
programs. Several co-workers have proposed developing a better
in-house
solution that would employ CA-Endevor (our source management
system). Before we
get started, I'd like to ask you all about your experiences with DB2
Change
Management. What products or in-house solutions do you use?
What's your
experience and/or advice about different approaches? Just curious: is
anyone
out there using the CA-Endevor for DB2 product? Thanks in advance
for your
input!

Iris Wilde,
[login to unmask email],
TD Bank