Looks like backup/restore is the best option but need to use SQL to create the library (schema) and not let the restore do it. Procedures for put back OK but journaling was not. Creating the schema setup default journaling and the restore then attached tables to the journal in the restore library.
Create save file
Savlib of source lib
iNav or STRSQl to create the schema (library)
Rstlib to target lib
Delete save file
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Panayiotis Petrou [3813]
Sent: Wednesday, March 30, 2011 2:32 AM
To: Midrange Systems Technical Discussion
Subject: RE: Best practice to duplicate a library with SQL stored procedures
Check out this article
www.ibm.com/developerworks/data/library/techarticle/0305milligan/0305milligan.html
Panayiotis (Pete) Petrou
zVSE and Websphere MQ System Administration Information Technology Division Bank Of Cyprus Tel 357-22-12-8473 panayiotis.petrou@xxxxxxxxxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Birgitta Hauser
Sent: Wednesday, March 30, 2011 8:08 AM
To: 'Midrange Systems Technical Discussion'
Subject: AW: Best practice to duplicate a library with SQL stored procedures
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)
--
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
