Question: I have defined some external stored procedures using Microfocus Cobol in my database and every time I make a change to them, I have to shut down DB2 to get the new version picked up. Is there any better way to do this?
This is true for all external routines that use external,
Why do we have routines in DB2? They allow us to include custom functionality inside our databases. But why do we need them? Should we use them?
As a follow up to last week’s article on error handling in stored procedures, this week we are sharing a video of a presentation by Linda Claussen of Themis Education. Linda details several additional ways to think about error handling.
The concepts in this article were incorporated into the DB2 Native SQL stored procedures from my own experience in using the log4net utility with several C# applications. My logging examples consist of 3 basic components, and an example on how to add the logging to a DB2 Native SP.
We live in a massively multithreaded world. Lots of actions are occurring around us. We are jumping from one task to another. Every now and then, we have to slow down and stop what we are doing to let another task make its way in the stream of activities. That task isn’t necessarily ours.