regardless of the fact that IBM has been benevolent enough to include SQL
catalogue registration in the SAV/RST process, it is not encouraging that
support as end-all-be-all for porting SQL catalogue registries.
You really need to have a re-runnable SQL script that runs all appropriate
DROPs followed by all appropriate CREATE PROCEDURE statements.
That way you can incorporate the script into your existing program and
invoke it using RUNSQLSTM (for example). Of course, the drawback is that
script would have to be maintained, instead of relying on inherent SAV/RST
support to take care of you. But that's a not necessarily a bad thing.
Bottom line is that 'nontraditional' objects require some accommodation in
Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
Subject: view sysprocs and library consolidation
Here is the command used to copy the objects in a library
(sql procedures and all other objects in the library that are not
source physical files or database physical or logical files)
other commands are used for these
CPY OBJ(&OBJ) TOOBJ(&TOOBJ) REPLACE(*YES) +
the obj/toobj parameters are retrieved from a dspobjd
if anyone knows of anything else I should be afraid of let me know.
seemed to work for a lifetime of traditional programming objects
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact