×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Thu04-Apr-2011 09:57 , Vern Hamberg wrote:
If you SAV/RST, many of these things will be handled correctly. For
example, if the objects exist that will handle a stored procedure -
if they exist when you CREATE PROCEDURE, the procedure information
gets put into the program object, so that, when it is restored, the
procedure is created automatically. I still don't completely trust
this, since the program doesn't need to exist when you create the
procedure or function, but it might help. <<SNIP>>
A message should be issued at completion of CREATE .. EXTERNAL NAME
to suggest when the procedure or function is not eligible for the
restore to effect automatic registration. That the referenced object
does not exist or was created with a language [such as CL or MI; OPM
generally] which does not support saving the SQL information would be
reason for the message SQL7909 "Routine &# was created, but cannot be
saved and restored." being logged. As the message alludes, the origin
is per "the routine's attributes could not be saved in the associated
program or service program object. If the *PGM or *SRVPGM object is
saved and then restored, the SQL catalogs will not be updated with
the attributes for this routine."
Regards, Chuck
This mailing list archive is Copyright 1997-2024 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
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
