RE: view sysprocs and library consolidation

Elvis - thanks much the system now works great.

the previous entries are still in sysprocs but the new ones were added.

is there a command to clean up the sql catalogues?

Thanks again


Jim Horn

This email is intended only for the person or entity
to which it is addressed and may contain information
that is privileged, confidential or otherwise protected
from disclosure. If you are not the named addressee
or an employee or agent responsible for delivering
this message to the named addressee, you are not
authorized to read, print, retain copy, and disseminate
this message or any part of it. If you have received this
message in error please notify us immediately by email,
discard any paper copies and delete all electronic files
of this message.

message: 5
date: Tue, 9 Sep 2008 11:23:29 -0500
from: "Elvis Budimlic" <ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx>
subject: RE: view sysprocs and library consolidation

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.

HTH, Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com

-----Original Message-----
Subject: view sysprocs and library consolidation

I am indeed an old dog learning new tricks.

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?
Jim Horn