Process to move Stored Procedures from staging to prod library within same DB2 system

Anne Leonard

Process to move Stored Procedures from staging to prod library within same DB2 system

Hello,
  We are on DB2 V11, z/OS.   I am curious how other companies are handling the process of moving DB2 Stored procedures from a staging library to a Prod library, within the same DB2 system.  We have a current process, which is an in-house job, that is very complicated and has many issues.  Our current process starts with the developer/dba moving the stored procedure to a "staging" library.  We have scheduled jobs that run throughout the day that copy that stored procedure to production library(within same DB2 system), along with deleting it from the staging library, refreshing WLM, STOP/START the DB2 Proc, along with some other behind the scenes steps.  This entire process is written in SAS, C, and REXX.  We are thinking there must be other, less complicated options for doing this process.  Do you have an in-house process for this also?  Are there any purchased software options that you are using to complete this task?  Any purchased software options that maybe aren't sold for this purpose, but can be used to complete this process?  We are looking at our options at this point.

 

Thanks.

Anne

Edited By:
Anne Leonard[Organization Members] @ Oct 09, 2019 - 01:02 PM (America/Central)
Anne Leonard[Organization Members] @ Oct 10, 2019 - 11:23 AM (America/Central)

David Simpson

Process to move Stored Procedures staging to production within same DB2 system
(in response to Anne Leonard)
Just to clarify… it sounds like you are talking about “External” stored procedures (perhaps written in COBOL) as opposed to “Native” SQL PL procedures, right?

From: Anne Leonard <[login to unmask email]>
Sent: Wednesday, October 9, 2019 1:02 PM
To: [login to unmask email]
Subject: [DB2-L] - Process to move Stored Procedures staging to production within same DB2 system


Hello,
We are on DB2 V11, z/OS. I am curious how other companies are handling the process of moving DB2 Stored procedures from development to Production libraries within the same DB2 system. We have a current process, which is an in-house job, that is very complicated and has many issues. Our current process starts with the developer/dba moving the stored procedure to a "staging" library. We have scheduled jobs that run throughout the day that copy that stored procedure to production library(within same DB2 system), along with deleting it from the staging library, refreshing WLM, STOP/START the DB2 Proc, along with some other behind the scenes steps. This entire process is written in SAS, C, and REXX. We are thinking there must be other, less complicated options for doing this process. Do you have an in-house process for this also? Are there any purchased software options that you are using to complete this task? Any purchased software options that maybe aren't sold for this purpose, but can be used to complete this process? We are looking at our options at this point.



Thanks.

Anne

-----End Original Message-----

Anne Leonard

RE: Process to move Stored Procedures staging to production within same DB2 system
(in response to David Simpson)

Yes, External stored procedures written in COBOL.  Thank you for helping me clarify that.

 

Anne

Binyamin Dissen

Process to move Stored Procedures staging to production within same DB2 system
(in response to Anne Leonard)
How do you handle the promotion of standard DB2 applications?

What are your concerns?

On Wed, 9 Oct 2019 11:01:51 -0700 (MST) Anne Leonard <[login to unmask email]>
wrote:

:>Hello,
:>  We are on DB2 V11, z/OS.   I am curious how other companies are handling the process of moving DB2 Stored procedures from development to Production libraries within the same DB2 system.  We have a current process, which is an in-house job, that is very complicated and has many issues.  Our current process starts with the developer/dba moving the stored procedure to a "staging" library.  We have scheduled jobs that run throughout the day that copy that stored procedure to production library(within same DB2 system), along with deleting it from the staging library, refreshing WLM, STOP/START the DB2 Proc, along with some other behind the scenes steps.  This entire process is written in SAS, C, and REXX.  We are thinking there must be other, less complicated options for doing this process.  Do you have an in-house process for this also?  Are there any purchased software options that you are using to complete this task?  Any purchased software options that maybe aren
:> 't sold for this purpose, but can be used to complete this process?  We are looking at our options at this point.

--
Binyamin Dissen <[login to unmask email]>
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel


Should you use the mailblocks package and expect a response from me,
you should preauthorize the dissensoftware.com domain.

I very rarely bother responding to challenge/response systems,
especially those from irresponsible companies.

Anne Leonard

RE: Process to move Stored Procedures staging to production within same DB2 system
(in response to Binyamin Dissen)

Hello,

  What I'm trying to determine is how other companies handle DBA/user written Stored Procedures.  Do you allow others to have access to the stored procedure library?  How do your DBAs/users get their new/updated stored procedures into the stored procedure library?  Our process is internal and very difficult to follow, and we've been finding some issues with it.  I'm just wondering if any other companies handle this process with a particular software product?  Do you have an in-house written routine that makes this move for the DBA's?  Do you allow your DBA's to update the stored procedure library themselves?  

 I'm not referring to promoting stored procedure code from a development environment to a production environment, I'm just moving Stored Procedures from a "staging" library to the stored procedure library within the same DB2 system.  We currently do not allow DBA's/users to access our Stored procedure library themselves.

 I hope this clarifies the question better.

 

Thanks.

Anne

Bill Gallagher

[External] Process to move Stored Procedures staging to production within same DB2 system
(in response to Anne Leonard)
Anne,

It sounds like you are referring to external stored procedures, i.e. written in COBOL or some other host-based language and instantiated as load modules, is that correct?

If so, then we use Endevor for that kind of processing.

Bill Gallagher | Senior Systems Engineer, DBA | Data Administration

From: Anne Leonard <[login to unmask email]>
Sent: Thursday, October 10, 2019 12:51 PM
To: [login to unmask email]
Subject: [External] [DB2-L] - RE: Process to move Stored Procedures staging to production within same DB2 system


Hello,

What I'm trying to determine is how other companies handle DBA/user written Stored Procedures. Do you allow others to have access to the stored procedure library? How do your DBAs/users get their new/updated stored procedures into the stored procedure library? Our process is internal and very difficult to follow, and we've been finding some issues with it. I'm just wondering if any other companies handle this process with a particular software product? Do you have an in-house written routine that makes this move for the DBA's? Do you allow your DBA's to update the stored procedure library themselves?

I'm not referring to promoting stored procedure code from a development environment to a production environment, I'm just moving Stored Procedures from a "staging" library to the stored procedure library within the same DB2 system. We currently do not allow DBA's/users to access our Stored procedure library themselves.

I hope this clarifies the question better.



Thanks.

Anne

-----End Original Message-----
________________________________
This message (including any attachments) may contain confidential, proprietary, privileged and/or private information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient of this message, please notify the sender immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.

TRVDiscDefault::1201

Anne Leonard

RE: [External] Process to move Stored Procedures staging to production within same DB2 system
(in response to Bill Gallagher)

Endeaver is a product we have looked at.  I'm curious, I'm assuming you need to do a refresh of WLM, STOP/START the DB2 Proc, etc., for stored procedures to allow dba's to test out their changes.  When do you do that step?  Or do you execute these commands just once a day?   Is it a manual process?  The way we have this setup, we need to follow those procedures, is it not required any longer?  

 

Thanks.

Anne

Patrick Bossman

[AD]RE: [External] Process to move Stored Procedures staging to production within same DB2 system
(in response to Anne Leonard)

This is the sort of thing we create automated deployments.  In our demos we use git or rtc as the scm, and Urban Code Deploy as the orchestrator, using IBM Db2 DevOps Experience to compare and generate the DDL and dependency handling steps. 

You can direct email if you want to hear/see more.

 

Best Regards,

Patrick Bossman