Managing SQL stored procedures (was: How are you modernising your as400 applications?)

albartell wrote:
> A stored procedures definition is stored in system tables, and there are
> only one set of them on a machine, which made moving from dev, to test, to
> QA, to production problematic because the stored procedure had to be deleted
> and recreated each time (you couldn't just move the object). In the end I
> believe we ended up writing our own exit point extensions within the change
> management software to handle everything.

*** WARNING: Vendor message forthcoming!

MKS Implementer can manage moving stored procedures (of many flavors)
from dev to qa (multiple levels), and qa to production.  The promotion
process handles de-registering them from old library in the system
tables and re-registering them in the new library.

SQL aside, when you are working in a multi-tiered environment it is
critical that you have a solid mechanism in place to manage your change.
  When you're talking about html, java, and rpg, in a single application
... cross-platform is obviously important.  All it takes is one mistake
and your web server, back end, and database get all out of sync and you
end up being in a world of hurts.

david
(and, yes, I do work for MKS in addition to running these lists)