Re: view sysprocs and library consolidation

MOVOBJ [AFaIK still] would not effect registration into the catalog [nor removal of the old], but I believe CRTDUPOBJ will. I would expect that the CPY would effect invocation of the QLICRDUP [i.e. CRTDUPOBJ] for a request performed on a /QSYS.LIB object, so the outcome I would expect to be the same.?

Although "SQL procedures" was noted, often External SQL procedures is meant or included. For external procedures, if either the procedure was created before the program or the program [attribute, e.g. CLP] does not support the registration of the SQL information on the object itself [i.e. registration is only into the catalog], then even the save\restore of one of those objects would not assist to get the procedure registered in the catalog. For external procedures in those cases, the CREATE PROCEDURE EXTERNAL NAME must be performed again, and DROP SPECIFIC PROCEDURE to rid of the old procedure.

Regards, Chuck

Elvis Budimlic wrote:

CPY support does not (presently) update SQL catalogues, but SAV/RST does. I think the easiest avenue to pursue is to save restore those objects and you'll see that the catalogues have been updated appropriately.

Jim Horn wrote:

I was consolidating some libraries. another programmer had created
sql procedures in one of the libraries I was consolidating. when
I copied the procedure from 1 library to another, the view sysprocs
in qsys2 (and qsys2 in the isap) was not updated for the change. I
believe this is causing run issues.

Is there a way to get sysprocs back in sync?

any insights on this with other programming objects?