AW: Best practice to duplicate a library with SQL stored procedures

["Birgitta Hauser" <Hauser@xxxxxxxxxxxxxxx>]

What about executing a SAVLIB into a save file and restore it into another
schema?

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"


-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Mike Cunningham
Gesendet: Wednesday, 30. March 2011 04:09
An: 'Midrange Systems Technical Discussion'
Betreff: Best practice to duplicate a library with SQL stored procedures

We have a library with only database objects which include not only SQL
tables and view but also SQL stored procedures and some external stored
procedures. A CRTDUPOBJ *ALL from this library to another looks like it
correctly duplicated all objects, include the stored procedures, but the
procedures do not appear on the Navigator list of  procedures because they
are not in the SQL catalog. Is there a better way to duplicate this type of
library or is the only option to keep a script to DROP and CREATE all the
procedures in the library after the CRTDUPOBJ command?  We are on V5R4 (but
hopefully only for another 4 months)