In the effort to develop the SP, UDF, UDTF, and so forth, one would be expected to capture the statements used to build this function. This would be saved in a source member, so that if/when you need to rebuild that object, you have it ready. To "compile" this source, use RUNSQLSTM to process the SQL script.
We use TurnOver to implement our Stored Procedures and UDFs. The product handles the build of these object types.
Hth,
-Eric DeLong
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Robert Rogerson
Sent: Wednesday, November 16, 2011 12:20 PM
To: Midrange Systems Technical Discussion
Subject: Keeping track for SPs, UDFs and service programs/procedures...
Hi all,
How are others keeping track of all the stored procedures, UDFs and
procedures being developed in your shop?
Our plan for the future is to create hundreds of these objects and we
would like a way to keep track and search what we've created.
An open source Power solution would be preferred but is not necessarily.
Does anyone have any suggestions or comments as to how they are managing
this?
Thanks,
Robert Rogerson
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
midrange.com
