Stored objects life cycle management

Shay Miller

Stored objects life cycle management

Hello.

In the last few months we are implementing more and more native sql objects in DB2 (User defined functions, native stored procedures, table functions).

For the 2 first objects, DB2 has it's own version management.

We are using a standard Software change management product (Endevor) for application objects (COBOL programs, JCLs, parms, etc.) and we are not sure if to use DB2 mechanism or to manage these objects in endevor as well. 

Also, we have an automated tool to propagate changes in DB2, but we are currently defininig said objects manually because the tool doesn't support them.

Can anyone share what is the policy/ process of life cycle management/source control/ change tracking for these objects in your shops?

 

Thanks, shay.

Michael Hannan

RE: Stored objects life cycle management
(in response to Shay Miller)

Suggest to keep source in source manager, each version, and manage similarly to View source. Table functions are like a cross between a routine and a super powerful view  with plug in parameters. I think of them more like Views.

One would not keep source code only in the DB2 Catalog, I think. However I can see that history of ALTERs needs to be kept too. I don't know if people normally ALTER table functions or not.

Michael Hannan,
DB2 Application Performance Specialist
CPT Global Ltd

António Barata

Stored objects life cycle management
(in response to Shay Miller)
Hello
In our installation, we have now IBM’s RTC - Rational Team Concert.
We had Emdevor for many years, but replaced it by RTC, which is far better, because it integrates with front end applications, has real time sintax checker (at least for COBOL) and a very good debug tool.
It manages changes during all life cycle to every type of object - programs, JCL, DB2 objects, has a 3270 emulator and a very interesting interface with z/OS so one can easily access files on the mainframe.
On the other hand, it runs on a Java virtual machine, which makes the compilation and promotion processes a little slower.
I work with mainframes for almost 40 years, and I really think that this is a very good solution.
António

> On 28 Jan 2020, at 16:56, Shay Miller <[login to unmask email]> wrote:
>
> 
> Hello.
>
> In the last few months we are implementing more and more native sql objects in DB2 (User defined functions, native stored procedures, table functions).
>
> For the 2 first objects, DB2 has it's own version management.
>
> We are using a standard Software change management product (Endevor) for application objects (COBOL programs, JCLs, parms, etc.) and we are not sure if to use DB2 mechanism or to manage these objects in endevor as well.
>
> Also, we have an automated tool to propagate changes in DB2, but we are currently defininig said objects manually because the tool doesn't support them.
>
> Can anyone share what is the policy/ process of life cycle management/source control/ change tracking for these objects in your shops?
>
>
>
> Thanks, shay.
>
>
> Site Links: View post online View mailing list online Start new thread via email Unsubscribe from this mailing list Manage your subscription
>
> This email has been sent to: [login to unmask email]
> Try BCV5, the BCV5 Masking Tool, & XDM a rapid Refresh/Clone/TDM Suite for Db2 z & distributed.
> DBARS -Audit,record,& block Db2 accesses to sensitive data real-time, NO audit trace or log required
> http://www.ESAIGroup.com/IDUG
>
>
> Use of this email content is governed by the terms of service at:
> http://www.idug.org/p/cm/ld/fid=2
>