× 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.



Hi,

Just a wild guess based on a situation we had here, and serving on memory
how it was explained to me then.

The restore process will check the SP program object whether it contains a
CREATE PROCEDURE statement associated with it. This information is normally
stored in the object, and can be retrieved by DMPOBJ OBJ(YOURLIB/YOURSPPGM)
OBJTYPE(*PGM)

The QSYS2/SYSPROCS table is updated with that information by the restore
process.

We have had a situation where the SP program object did not contain such
CREATE PROCEDURE statement associated with it.

The procedure was created when the program object did not exist. Like this:

CREATE OR REPLACE PROCEDURE
myproc
LANGUAGE RPGLE
EXTERNAL NAME 'FAKELIB/MYSPPGM'
;

An SQL message SQL7909 was issued but ignored:
Message . . . . : MYPROC was created, changed, or dropped, but object not
modified.

The program object was an external RPG program, and it was compiled later.
Since the information about MYPROC was not correct, the program object was
not updated with the SQL CREATE information.
This caused that the stored procedure was not recreated at restore time.

Best regards,
Arco Simonse



2016-12-20 16:29 GMT+01:00 Paul Bailey <PabloMotte+Midrange@xxxxxxxxx>:

Hi,

I'm having some confusing results recently. We're keeping a backup of "last
night's" live data library on our system. We save the live data library to
tape every night, then use CLRLIB to empty the backup library, and finally
RSTLIB to restore the save from the tape to the backup library.

I'm expecting every file, logical, table, view, data area, stored procedure
and user-defined function (everything specific to that library) to be
removed then restored long before we turn up for work in the morning.

We've found that *some* stored procedures do not get recreated during the
RSTLIB. Are my expected results incorrect? CLRLIB and RSTLIB should work on
SQL "objects" just like they do on traditional objects, right?

We've recently moved to IBM os v7.1, and are slowly introducing DB2 stored
procedures for use on our website.


-Paul.
--
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.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.