Cataloging Stored Procedures
Need to know if anyone has a package or process to do the actual storing of information around a Stored Procedure? My area is being tasked with becoming the Librian for all of our stored procedures whether created with true Sequel or RGP with imbedded SQL. I am looking for a way out side of say our change management tool to track them.
As we continue to create UI screens my area will be responsible for obtaining the data for all users directly on or called off a server. I need a way to know exactly what we already have and what it constists of.
Software/Hardware used:
Software/Hardware used:
ASKED:
November 13, 2006 6:55 AM
UPDATED:
December 25, 2009 5:35 AM
Answer Wiki:
scottcrill@premiseinc.com
has a save restore sql procedure tool.
To see all answers submitted to the Answer Wiki: View Answer History.
For a quick look at it, anything which is actually registered as a stored procedure is listed in QSYS2/SYSROUTINE, while the parameters to it are in QSYS2/SYSPARM. You should be able to get basic information about the procedures currently defined by querying these tables.
Unusual question… As the previous comment indicates, all available info is already stored by the system in the ‘system database catalog’. That’s a fairly strong implication of the fundamental requirements of a relational database.
So, you want to set up some limited copies of some of the catalog? Or are you expecting to add more info into some secondary tables outside of the catalog? If so, why not simply store that info in the catalog itself. If you can manage to ue up all of the LongComment and other attributes, you’re probably generating way too much documentation.
It will begin to obstruct actual productive work. Since this project already seems to be started, it’s probably obstructing work now. It’s likely that you could be assigned to something else that would actually provide value.
Maybe your site simply needs to provide some training on what the catalog can really do for you.
Tom